Topic: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner - page 16. (Read 209500 times)
December 31, 2014, 10:19:04 AM
File Not Found for download.
December 30, 2014, 11:06:08 PM
v4.3:
Fixes the problem with errors being thrown on startup if you've never used it before. I forgot to check for that before I published v4.2.
Download link: MMinerMonitor43.zip
M
Fixes the problem with errors being thrown on startup if you've never used it before. I forgot to check for that before I published v4.2.
Download link: MMinerMonitor43.zip
M
December 30, 2014, 10:06:19 PM
Here's v4.2.
- Significantly redid the Alerting logic. Everything is on one tab now, and you set your alert settings for whatever miner type is in the drop down. These changes make it much easier, quicker, and foolproof for me to add support for more miner types. This also means Spondoolie units are now supported individually for alertings.
- Adds support for Antminer S5 units.
- Adds support for Spondoolie SP20, SP30, SP31, and SP35 units. Note that for now you still need to enable API access for this work! See first post for how to do this.
- Spondoolie SP10 is listed, but I don't know if it'll work. Per my conversations with Spondoolie techs, SP20, SP30, SP31, and SP35 behave the same API wise, the SP10 may be different.
Download link: MMinerMonitor43.zip
M
- Significantly redid the Alerting logic. Everything is on one tab now, and you set your alert settings for whatever miner type is in the drop down. These changes make it much easier, quicker, and foolproof for me to add support for more miner types. This also means Spondoolie units are now supported individually for alertings.
- Adds support for Antminer S5 units.
- Adds support for Spondoolie SP20, SP30, SP31, and SP35 units. Note that for now you still need to enable API access for this work! See first post for how to do this.
- Spondoolie SP10 is listed, but I don't know if it'll work. Per my conversations with Spondoolie techs, SP20, SP30, SP31, and SP35 behave the same API wise, the SP10 may be different.
Download link: MMinerMonitor43.zip
M
December 29, 2014, 03:03:37 AM
monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Are your ants remote? Or are they local?
How many ants are we talking about? There was one user on here with 1000 S3s and the app saturated his network when it was scanning. He had to bump up his hardware quality and bandwidth for it to work properly.
M
im only running 14 s3's and 1 c1. all through some low grade 30$ asus I bought like a month ago. now has been discontinued. The ants are local in relation to the machine I am logging into though.
I'm still having issues when it drops to this odd 50/450 pic i just posted. It's like it's not understanding that its actually hashing at 50ghs and not 450ghs.
Then you should be fine. Note that the first hash rate speed listed is the average over the last 5 seconds. That will vary and jump all over the place. The second value is average over all. If it says 450, you should be getting 450 overall. It's the second value my app looks like.
M
seems to be running much better now
*edit**
having problems again. Not detecting in when it drops into that weird 50ghs zone and then on the other average its saying 450ghs its like so weird please help im having to check this stuff so much and not only that im losing 1 machine per block so im losing so much money
December 28, 2014, 01:30:46 PM
monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Are your ants remote? Or are they local?
How many ants are we talking about? There was one user on here with 1000 S3s and the app saturated his network when it was scanning. He had to bump up his hardware quality and bandwidth for it to work properly.
M
im only running 14 s3's and 1 c1. all through some low grade 30$ asus I bought like a month ago. now has been discontinued. The ants are local in relation to the machine I am logging into though.
I'm still having issues when it drops to this odd 50/450 pic i just posted. It's like it's not understanding that its actually hashing at 50ghs and not 450ghs.
Then you should be fine. Note that the first hash rate speed listed is the average over the last 5 seconds. That will vary and jump all over the place. The second value is average over all. If it says 450, you should be getting 450 overall. It's the second value my app looks like.
M
December 28, 2014, 12:34:55 PM
monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Are your ants remote? Or are they local?
How many ants are we talking about? There was one user on here with 1000 S3s and the app saturated his network when it was scanning. He had to bump up his hardware quality and bandwidth for it to work properly.
M
im only running 14 s3's and 1 c1. all through some low grade 30$ asus I bought like a month ago. now has been discontinued. The ants are local in relation to the machine I am logging into though.
I'm still having issues when it drops to this odd 50/450 pic i just posted. It's like it's not understanding that its actually hashing at 50ghs and not 450ghs.
December 28, 2014, 12:24:43 PM
monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
Are your ants remote? Or are they local?
How many ants are we talking about? There was one user on here with 1000 S3s and the app saturated his network when it was scanning. He had to bump up his hardware quality and bandwidth for it to work properly.
M
December 28, 2014, 11:56:19 AM
right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)
Got it. What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1. Most of them are interchangable.
Quote
The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.
please advise
please advise
I'm not sure about that.
Do you have the latest firmware on your S3s? I thought I heard the latest has problems, so maybe one older than latest.M
where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.
I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?
Is the monitor running onsite with the miners, or remotely? The reboots are run via SSH, are the machines accessible via SSH? Check the log tab, it should have info there.
As for firmware, check the bitmain site.
M
monitor is running on site on basic windows machine. I have been having lots of trouble with my ants dropping in hash. I really hope its a switch issue. I'm getting a drop like every 30 minutes.
Does the monitor lag behind a little to reset the machines? It almost seems like if I watch it I drive myself crazy and then if I let it do its own thing it works? Maybe I'm going crazy and/or the machines are resetting so often.
December 28, 2014, 11:04:17 AM
right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)
Got it. What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1. Most of them are interchangable.
Quote
The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.
please advise
please advise
I'm not sure about that.
Do you have the latest firmware on your S3s? I thought I heard the latest has problems, so maybe one older than latest.M
where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.
I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?
Is the monitor running onsite with the miners, or remotely? The reboots are run via SSH, are the machines accessible via SSH? Check the log tab, it should have info there.
As for firmware, check the bitmain site.
M
December 28, 2014, 10:10:37 AM
right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)
Got it. What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1. Most of them are interchangable.
Quote
The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.
please advise
please advise
I'm not sure about that.
Do you have the latest firmware on your S3s? I thought I heard the latest has problems, so maybe one older than latest.M
where do I get the older firmware sir? Also will I be able to load the firmware remotely through the gui? Or would I need to make sure someone is on location to power cycle? I think that also this dropping may be a switch issue.
I'm just not sure why ant monitor is not detecting that drop and auto rebooting. Also just had my #14 unit quit hashing all together and it didn't try to reboot..?
December 28, 2014, 09:20:36 AM
right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)
Got it. What I'd do is mark the S3 that is running at half efficiency as another type of Ant, such as an S1. Most of them are interchangable.
Quote
The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.
please advise
please advise
I'm not sure about that.
Do you have the latest firmware on your S3s? I thought I heard the latest has problems, so maybe one older than latest.M
December 28, 2014, 09:11:17 AM
oh wait okay i figured it out lol...
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
At the moment you can't. The S3 rules apply to all S3s. However, if you set it to reboot when "hashrate" is less than something, it should only affect the degraded miner.
Right?
M
right I understand. If you watch the s3's (at least mine) I am getting two main types of hash drops. The first is where the unit will half in hashing as if a board dies. After reboot this will be fixed (as prior stated this is why i was asking about programing each s3 because 1 of mine is permantly running at half efficiency)
The second is what I have posted below. With this shot notice the first spot is around 50gh/s while the second is showing 450ghs... Why is this doing this? it is only hasing at 50ghs poolside andit is a glitch. for some reason when my miners enter this type of state they will not reboot.
please advise
December 27, 2014, 08:36:48 PM
oh wait okay i figured it out lol...
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
At the moment you can't. The S3 rules apply to all S3s. However, if you set it to reboot when "hashrate" is less than something, it should only affect the degraded miner.
Right?
M
December 27, 2014, 08:25:55 PM
oh wait okay i figured it out lol...
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
I removed it from the "list" because it was only half hasing and I dont know how to program 1 single unit to reset at a specific hash rate not all s3's....
please advise this is solution i need to know how to make 1 single s3 running at half hash to auto reset on its on < hash command. Thanks
December 27, 2014, 07:41:09 PM
im not sure I follow? They are all in the folder they downloaded in... there was no instal it only gave me the option to click on the program I do see the other two files tho.
wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)
edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..
wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)
edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..
Have you customized your SSH username/pw? What does the log show?
M
December 27, 2014, 07:10:00 PM
im not sure I follow? They are all in the folder they downloaded in... there was no instal it only gave me the option to click on the program I do see the other two files tho.
wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)
edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..
another edt*
It sems to be working? Its saying 6.5 th/s mmonitor side tho and 7.1 th/s pool side?
edit*
The antmonitor program is seeing 14 out of 15 miner. Coincidentally the final minder the program is not seeing is only running on 1 blade (other blades problems) Maybe that is why. I just see
? in the uptime window for this miner.
wait nvm BBBBBBBBOOOOMMMMM BABBBBYYY (american savage voice)
edit wait now im just getting alerts but my ants are not rebooting. prety sure i have every possibly reboot setting click and also the < amount set to 200..
another edt*
It sems to be working? Its saying 6.5 th/s mmonitor side tho and 7.1 th/s pool side?
edit*
The antmonitor program is seeing 14 out of 15 miner. Coincidentally the final minder the program is not seeing is only running on 1 blade (other blades problems) Maybe that is why. I just see
? in the uptime window for this miner. December 27, 2014, 04:57:13 AM
I'm getting this error when i scan.
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
Looks like you're trying to run the executable without the included DLLs. Both the Newtonsoft.Json.DLL and Renci.SshNet.dll need to be in the same directory as MMinerMonitor. Let me know if that fixes it.
M
Fixed mine
December 27, 2014, 04:49:13 AM
I'm getting this error when i scan.
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
Looks like you're trying to run the executable without the included DLLs. Both the Newtonsoft.Json.DLL and Renci.SshNet.dll need to be in the same directory as MMinerMonitor. Let me know if that fixes it.
M
December 27, 2014, 02:37:44 AM
I'm getting this error when i scan.
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
Im also not showing any ants on my output view. I am running windows 8 and i have entered the ip addresses manually
December 22, 2014, 05:09:40 PM
Shows the ghs/5s and the Ghs/Avg but no fans speeds etc
This is what there is to show for SPs. Fanspeed is fixed by what you have in the UI, and doesn't show in the output. Xs and frequency are Antminer specific, and as far as I can tell, the SPs don't have an equivalent.
I'll check out the output you listed above, but at first glance it's virtually identical to the SP20, just faster. That's what I was hoping.
Thanks!
M
Jump to: