M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner

[mdude77]

Here's the miner info from one of my S4's.

Thank you!

M

[1715516700]

1715516700

[1715516700]

1715516700

[1715516700]

1715516700

[1715516700]

1715516700

[1715516700]

1715516700

[1715516700]

1715516700

[ZymurBits]

Auto reboot went fine as well!   

Just need to be able to identify S4 and set parameters specific to that model.

[mdude77]

Auto reboot went fine as well!   

Just need to be able to identify S4 and set parameters specific to that model.

It's on my to do list.

M

[HPmuirt]

Hello.  That "reboot on failure" option is NOT supposed to be on by default.  Apparently there's a problem somewhere that causes that to turn on of its own accord.   I apologize for that.

As for why one works and one doesn't ... are they using the same firmware?

M

No worries, what's done is done and at least I have learnt from my mistakes and so not set the SSH password, until you find the bug

The firmware is indeed the only difference as 101 is an S3+ and 102 is an older S3 running OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909) firmware, but I would guess so are many of the older S3 units that are using your code.

Cheers n beers

HPmuirt

[mdude77]

Hello.  That "reboot on failure" option is NOT supposed to be on by default.  Apparently there's a problem somewhere that causes that to turn on of its own accord.   I apologize for that.

As for why one works and one doesn't ... are they using the same firmware?

M

No worries, what's done is done and at least I have learnt from my mistakes and so not set the SSH password, until you find the bug

The firmware is indeed the only difference as 101 is an S3+ and 102 is an older S3 running OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909) firmware, but I would guess so are many of the older S3 units that are using your code.

Cheers n beers

HPmuirt

Would you please run the "get miner info" button in the latest beta on your non monitorable S3 and PM me the output please?

Download link: MMinerMonitor40ba.zip

M

[HPmuirt]

Would you please run the "get miner info" button in the latest beta on your non monitorable S3 and PM me the output please?

Download link: MMinerMonitor40ba.zip

M

Get Miner Info sent via PM as requested.

Cheers n beers

HPmuirt

P.S. I thought I would check the log as the new beta also had the reboot selected by default and found the following: -

08/12/2014 23:54:07: M's Miner Monitor v4.0b1 starting
08/12/2014 23:54:07: Initiated Ant refresh
08/12/2014 23:54:08: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:54:08: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:54:08: REBOOTING S3:0.102 via SSH
08/12/2014 23:54:26: Reboot of S3:0.102 FAILED: Permission denied (password).
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:59:11: Initiated Ant refresh
08/12/2014 23:59:11: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:59:11: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:59:11: Need to reboot S3:0.102 but it hasn't been long enough since last reboot

Is the reason that the App cannot monitor unit 102 that it has not accepted the IP address even though the config screen reports the correct IP address?

[mdude77]

Get Miner Info sent via PM as requested.

Cheers n beers

HPmuirt

P.S. I thought I would check the log as the new beta also had the reboot selected by default and found the following: -

08/12/2014 23:54:07: M's Miner Monitor v4.0b1 starting
08/12/2014 23:54:07: Initiated Ant refresh
08/12/2014 23:54:08: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:54:08: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:54:08: REBOOTING S3:0.102 via SSH
08/12/2014 23:54:26: Reboot of S3:0.102 FAILED: Permission denied (password).
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:54:53: ERROR when accessing API on 102: A socket operation was attempted to an unreachable network 0.0.0.102:4028
08/12/2014 23:59:11: Initiated Ant refresh
08/12/2014 23:59:11: ERROR when querying S3:0.102 (step 1): Object reference not set to an instance of an object.
08/12/2014 23:59:11: Attempting to reboot S3:0.102 via the web because the API query errored out.
08/12/2014 23:59:11: Need to reboot S3:0.102 but it hasn't been long enough since last reboot

Is the reason that the App cannot monitor unit 102 that it has not accepted the IP address even though the config screen reports the correct IP address?

This is odd.  Can you send me screenshots of the miner config for each Ant?  It's interesting that the SSH client has no problems connecting, but somehow the IP client sees it as "0.0.0.102".  I've seen odd behaviors before with the built in IP client (Microsoft's object, not mine) where it can't interpret leading zeros.  I'm guessing the same type of thing is happening here.

M

[mdude77]

I have a question for the Spondoolie's users.

Being fairly new to Spondoolie hardware, I'm currently unclear as to why you'd ever want to auto reboot your miner.  I don't see anything in the stats equivalent to the Ant dreaded "Xs".  The fan speed isn't variable.  If the temperature gets too high, it'll self throttle.  And, rebooting it wouldn't fix a temperature problem anyhow.

I can see there being alerts for temperature and hash speed, but reboots? 

Looking for input please.

Thanks.

M

[mdude77]

Hello.  That "reboot on failure" option is NOT supposed to be on by default.  Apparently there's a problem somewhere that causes that to turn on of its own accord.   I apologize for that.

As for why one works and one doesn't ... are they using the same firmware?

M

No worries, what's done is done and at least I have learnt from my mistakes and so not set the SSH password, until you find the bug

The firmware is indeed the only difference as 101 is an S3+ and 102 is an older S3 running OpenWrt Barrier Breaker r38031 / LuCI Trunk (svn-r9909) firmware, but I would guess so are many of the older S3 units that are using your code.

Cheers n beers

HPmuirt

I found and fixed the "reboot on error" option turning on of it's own accord.  It doesn't default to that, I had a coding error in the miner config screen, you could easily turn it on by accident and not realize it.

Will be right in the next build.

M

[ZymurBits]

I've got a feature request for you M.  I just found out that the machine I use to monitor my Ant's with was off for the last 20+ hours.  When I started it up again, 1/2 of my Ant's were sent an Auto Reboot. (Talk about your boot storms!)  How difficult would it be prompt for a reboot if say the Monitor has only been up for 5 minutes or less?

[mdude77]

I've got a feature request for you M.  I just found out that the machine I use to monitor my Ant's with was off for the last 20+ hours.  When I started it up again, 1/2 of my Ant's were sent an Auto Reboot. (Talk about your boot storms!)  How difficult would it be prompt for a reboot if say the Monitor has only been up for 5 minutes or less?

Hello, please check to see if that "Attempt to reboot ants that get an ERROR on refreshing" option is turned off.  It is off by default, but because of a bug you could turn it on and not realize it by clicking something else.

Also make sure the "don't reboot more than once every" value is set to a realistic number. 

As for a prompt ... the problem with prompts is they tend to cause the program to stop until someone clicks yes/no.  That can be worked around, but it's easier just to avoid it as it doesn't work well with automated programs.

Does that help?

M

[ZymurBits]

The attempt to reboot on Error was unchecked.  I have mine set to reboot every 48 hours - seems to be a nice compromise as I've noticed most of my ants start slowing down (losing hash) after 40 - 60 hours of uptime.

What if instead of a prompt, the program highlighted the systems that would be rebooted during the next refresh cycle?  I currently have my refresh set to 600 seconds so if the reboot occurred 10 minutes after my "48 hour" setting, that wouldn't be a big deal to me.

Just a thought.

Thanks M!

[mdude77]

The attempt to reboot on Error was unchecked.  I have mine set to reboot every 48 hours - seems to be a nice compromise as I've noticed most of my ants start slowing down (losing hash) after 40 - 60 hours of uptime.

What if instead of a prompt, the program highlighted the systems that would be rebooted during the next refresh cycle?  I currently have my refresh set to 600 seconds so if the reboot occurred 10 minutes after my "48 hour" setting, that wouldn't be a big deal to me.

Just a thought.

Thanks M!

That's a decent idea.  Let me see what I can come up with.

Thanks!

M

[opentoe]

Request.

Don't use the Windows registry hive to save the config data. Just use a simple *.ini file so the program can be truly portable. Right now I'd love to copy that whole folder over to another computer and just run it, but I can't. I have to re-configure all the miner's again back into the registry.
Nice work though for sure.

[mdude77]

Request.

Don't use the Windows registry hive to save the config data. Just use a simple *.ini file so the program can be truly portable. Right now I'd love to copy that whole folder over to another computer and just run it, but I can't. I have to re-configure all the miner's again back into the registry.
Nice work though for sure.

It's actually quite easy to export a registry entry and import it into another PC.

Right click the MAntMonitor key/folder on the left and pick Export and save it somewhere.

On the other PC click File -> Import, and import the .reg file you just exported.

M

[mdude77]

Here's v4.0 beta #2.

There is a lot of under the hood code restructuring in this version that should make it easier to add support for more miners types.  I have more changes planned, but I deem this stable enough to publish.

This version:
- Adds tentative support for Antminer S4 units.  It properly processes the API data that was provided to me for an S4.  However, without an actual S4 to test with, I have to label this as "tentative" until someone with an S4 tests it.  This includes the normal alerts.  If you have an S4, I'd really appreciate you trying this as an S4 and let me know what happens.  Please try the manual reboots and shutdown as well if you could!
- Adds alerts for Spondoolie SP20 units.  There's not too much I can alert it that I've found, aside from temperature and hash rate, since fans are fixed and there are no Xs. 

If anyone has any other Spondoolie units aside from an SP20, I'd really appreciate you trying them here as an SP20 and let me know what happens.  If it doesn't work, please use the "Get Miner Info" button to send me the output from your miner!

As always feedback is most welcome.

Download link: MMinerMonitor40b2.zip

M

[gaalx]

Thank you very good software.

[ZymurBits]

Just downloaded.  I'll try the S4 tests you're requesting later today when I'm near one of the units.

Thanks M!

[ZymurBits]

Reboot works but Shutdown just hangs the S4.  Display shows it is hashing at the same speed you issued the Shutdown a but the site reports hashing has stopped.  I can't access the S4 via web or SSH.  However, it does respond to pings.....  Strange.  Are you using SSH or API to attempt shutdown?

[mdude77]

Reboot works but Shutdown just hangs the S4.  Display shows it is hashing at the same speed you issued the Shutdown a but the site reports hashing has stopped.  I can't access the S4 via web or SSH.  However, it does respond to pings.....  Strange.  Are you using SSH or API to attempt shutdown?

That's what a shutdown is.  Seems like it's working.  At that point all you can do is power it off.  That's what you should do before a schedule reboot or shutdown.  Helps prevent the file system from getting corrupt.

It's the same as logging in via SSH and entering "/sbin/shutdown -h -P now"

Thanks for checking!

M