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

[mdude77]

I'm declaring v3.4 stable.  There are a few more things I fixed since beta #7.  Thanks everyone for your help.

Here's the full change log:

v3.4
- Added support for the prior version of the S3 firmware.
- Rewrote the Scanning for Ants routine to use the API.  Each address has 5 seconds to respond before it moves to the next.  Enter the first 3 pieces
of the quad address to scan (ie 192.168.0) and it'll scan the segment, adding Ants that it finds if they aren't already there.
- Completely revised the Ant configuration to allow each Ant to have completely configurable options, including name, SSH Port, API Port, and Web Port.
- Fixed the problem with S2 shutdowns not shutting down, but rebooting.
- Fixed the problem with web scraping failing if you don't have 3 pools configured.
- Added the ability to right click -> remove an Ant from the output display.

Download link: MAntMonitor34.zip

M

[tl121]

Here's a very minor glitch in v 3.4b7.

I had Ant Monitor set to sort the Ant Output by uptime, shortest first. This way recently rebooted Ants (X's) get listed first. I have observed that sometimes this list is not sorted correctly, with the most recently rebooted node listed below the previously most recently rebooted node.  (This happens, for example, when I open the Ant Monitor window after getting an annoying popup alert.)

When this happens, clicking the Refreshing in nnn button does a refresh and the list is then sorted correctly.

[mdude77]

Here's a very minor glitch in v 3.4b7.

I had Ant Monitor set to sort the Ant Output by uptime, shortest first. This way recently rebooted Ants (X's) get listed first. I have observed that sometimes this list is not sorted correctly, with the most recently rebooted node listed below the previously most recently rebooted node.  (This happens, for example, when I open the Ant Monitor window after getting an annoying popup alert.)

When this happens, clicking the Refreshing in nnn button does a refresh and the list is then sorted correctly.

Can you provide a screenshot?  This also implies the next time it refreshes it corrects itself.

I don't do anything for the sorting, that's all "built in" functionality.  It wouldn't surprise me if it wasn't perfect, but until I see it, I won't know for sure.

Thanks!

M

[tl121]

You are right, the refresh clears the problem.  The next time I see this I will capture a screen shot. However, this will require me to be sitting in front of my computer at the time Ant Monitor sees an X and issues an alert, since the next refresh will clear the error.  So it may be a while, at least if the weather stays cool...

[mdude77]

You are right, the refresh clears the problem.  The next time I see this I will capture a screen shot. However, this will require me to be sitting in front of my computer at the time Ant Monitor sees an X and issues an alert, since the next refresh will clear the error.  So it may be a while, at least if the weather stays cool...

I can reproduce weird behavior by changing the sort order as well.  I'm not sure what, if anything, I can do about it yet.  But it seems to fix itself, so I think it's a bug in the datagrid control that I may not be able to fix.

M

[Stratobitz]

Really like your software. Will be sending a tip your way tonight of .10 BTC.

Are there any plans to add features?  A great feature would be the ability to update settings, such as Frequency/Rate of the S3+ units.

Also, can you change pool info per miner or only all of them at the same time.

I haven't tried this feature yet because my miners are grouped into lots pointing to different pools.

Anyways thanks again, sending .10 BTC your way for the great work.

Strato

[mdude77]

Really like your software. Will be sending a tip your way tonight of .10 BTC.

Thanks!

Are there any plans to add features?  A great feature would be the ability to update settings, such as Frequency/Rate of the S3+ units.

That's only doable via the web interface or SSH, correct?  I've shied away from putting anything in SSH that, if it goes wrong, could brick your unit.

Also, can you change pool info per miner or only all of them at the same time.

I haven't tried this feature yet because my miners are grouped into lots pointing to different pools.

Anyways thanks again, sending .10 BTC your way for the great work.

Works for all.  Note for S1s and S3s you'll have to enable API updates to cgminer, by default it can only be done locally.

M

[psjw4450]

Really like your software. Will be sending a tip your way tonight of .10 BTC.

Thanks!

Are there any plans to add features?  A great feature would be the ability to update settings, such as Frequency/Rate of the S3+ units.

That's only doable via the web interface or SSH, correct?  I've shied away from putting anything in SSH that, if it goes wrong, could brick your unit.

Also, can you change pool info per miner or only all of them at the same time.

I haven't tried this feature yet because my miners are grouped into lots pointing to different pools.

Anyways thanks again, sending .10 BTC your way for the great work.

Works for all.  Note for S1s and S3s you'll have to enable API updates to cgminer, by default it can only be done locally.

M

How do you enable api updates to cgminer.  Thanks. 

[mdude77]

Really like your software. Will be sending a tip your way tonight of .10 BTC.

Thanks!

Are there any plans to add features?  A great feature would be the ability to update settings, such as Frequency/Rate of the S3+ units.

That's only doable via the web interface or SSH, correct?  I've shied away from putting anything in SSH that, if it goes wrong, could brick your unit.

Also, can you change pool info per miner or only all of them at the same time.

I haven't tried this feature yet because my miners are grouped into lots pointing to different pools.

Anyways thanks again, sending .10 BTC your way for the great work.

Works for all.  Note for S1s and S3s you'll have to enable API updates to cgminer, by default it can only be done locally.

M

How do you enable api updates to cgminer.  Thanks. 

You have to update the cgminer startup/config via SSH.  I don't know the specific details, however I'm certain you can find it with a google search.

Since I've been asked this enough one of the days I'll take the time to find the info and post it here, for use at your own risk.

M

[alesx.onfire]

My antivirus deleted it since 2 weeks ago..
I don't know why, but now, the "icon" is white without any direct access.

[mdude77]

My antivirus deleted it since 2 weeks ago..
I don't know why, but now, the "icon" is white without any direct access.

You'll need to white list it.  For some reason they don't like what my app does.

See the first listing.

M

[Moria843]

Using V3.4b7 and all seems to work fine except I get the following errors.

10/28/2014 5:24:19 PM: Initiated Ant refresh
10/28/2014 5:24:22 PM: ERROR when processing alerts on Rig5 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/28/2014 5:24:22 PM: ERROR when processing alerts on RigS35 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName

Have 8 S1 and 5 S3+. Rig5 is an S1; RigS35 is an S3+. Don't get any errors on the other 11 miners. Configured all the same way. Any idea why I get these errors on the 2 miners above?

[mdude77]

Using V3.4b7 and all seems to work fine except I get the following errors.

10/28/2014 5:24:19 PM: Initiated Ant refresh
10/28/2014 5:24:22 PM: ERROR when processing alerts on Rig5 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/28/2014 5:24:22 PM: ERROR when processing alerts on RigS35 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName

Have 8 S1 and 5 S3+. Rig5 is an S1; RigS35 is an S3+. Don't get any errors on the other 11 miners. Configured all the same way. Any idea why I get these errors on the 2 miners above?

Try upgrading to the latest full version, see if you have the same error.

M

[Moria843]

Updated to the link in your footer. It still gives the errors below and still shows V3.4b7. Looks like same version.

Also, the test e-mail works, but none of the alert e-mails get through as seen earlier by others and may be why I'm getting the errors below.

Is V3.4b7 in your footer link the most recent full version?

Thanks.

10/29/2014 6:46:15 PM: Initiated Ant refresh
10/29/2014 6:46:15 PM: ERROR when processing alerts on RigS31 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/29/2014 6:46:16 PM: ERROR when processing alerts on RigS34 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/29/2014 6:46:16 PM: ERROR when processing alerts on RigS35 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/29/2014 6:46:16 PM: ERROR when processing alerts on RigS33 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
10/29/2014 6:46:17 PM: ERROR when processing alerts on Rig5 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName

[mdude77]

Updated to the link in your footer. It still gives the errors below and still shows V3.4b7. Looks like same version.

Also, the test e-mail works, but none of the alert e-mails get through as seen earlier by others and may be why I'm getting the errors below.

Is V3.4b7 in your footer link the most recent full version?

Wow.  Apparently I didn't update the ZIP file before I pushed it out!

Try it now..

M

[Moria843]

Downloaded v3.4. Working great now. Thanks!

[mdude77]

Downloaded v3.4. Working great now. Thanks!

Thanks for pointing that out.  It's been wrong for quite some time now.

M

[pikachuy]

Anyway to add the S4 to work with this?

[Prelude]

Anyway to add the S4 to work with this?

Add it as an S3. Works for me, mostly.

[mdude77]

Anyway to add the S4 to work with this?

If past history is any indicator, it should work as an S2.

If someone donates me an S4, I'll be happy to add native support.  Otherwise it'll likely be a while...

M