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

[heslo]

Hi mdude,

Nice job my man - got a little problem though, I'm unable to delete any of the ants - either the old ones (S3's reg'd as S1's) or the newer, correct ones. I keep getting this:


Tried restarting the ants & the program.......

Edit: I see someone beat me to it.........

lol yep! Same problem as me!

[1715449769]

1715449769

[mdude77]

Thanks.  I apparently missed testing that line.

Here's the fix.  The app should say v2.91:

Download link: MAntMonitor291.zip

M

EDIT: Also, I looked to see why the BestShare value comes up as 0 for me on p2pool for my S2 and S3.  Every result from the API that I've seen shows 0, so I don't think this is fixable on my side.

[heslo]

Legend! Many thanks!

[PatMan]

That fixed it mdude - well done!

Regarding your Bestshare issue - I use it on p2pool and don't have that problem - everything shows up as it should.......

A small donation will be heading your way shortly my man 

[mdude77]

That fixed it mdude - well done!

Regarding your Bestshare issue - I use it on p2pool and don't have that problem - everything shows up as it should.......

That's just bizarre then.  I'm using p2pool from git as of 8/19, I'm not using the standard payout address as the username (since it's a private node, it'll default to the right one) so I can track my miners, and I'm using fixed share size as an experiment to try to keep my DOA rate low (it's not working for my S1 or S2 ~5% avg atm).  Also, I'm using a URL of stratum+tcp://address:port.

ie,
stratum+tcp://192.168.0.194:9332
S2+512
abc

What are you doing?

A small donation will be heading your way shortly my man 

Thanks!  Will go to paying off my loan.

I'm hurting on BTC because of the JamesC hosting failure.

M

[PatMan]

OK, I think it's because you're using the set diff (+512) command - I'm letting p2pool decide the diff (I found no advantage in manually setting it).

Try it out 

[mdude77]

OK, I think it's because you're using the set diff (+512) command - I'm letting p2pool decide the diff (I found no advantage in manually setting it).

Try it out 

You're right.  That's odd, especially since my S1 doesn't mind it.

M

[mdude77]

Here's version 3.0:

v3.0
- Added support for S3 Web scraping (non API)
- Fixed a problem that would cause Ants to duplicate on their own

Download link: MAntMonitor30.zip


MoreBloodWine: Give this a whirl.  Since I can't replicate your environment, I'm not sure this will work.  If it doesn't, hopefully I can work through it.

M

[Morblias]

Thanks mdude77! This is amazing! I was getting annoyed logging into each and every one of my antminers to see how they were doing.

[DimensionsOfHell]

Is the 3.0 supposed to be working with the new S3 FW? Because it still isn't working for me. The S3's I have with the new FW show up as "ERROR".

[mdude77]

Is the 3.0 supposed to be working with the new S3 FW? Because it still isn't working for me. The S3's I have with the new FW show up as "ERROR".

Yes, it works for me and others.  One fix I added in here was properly handling cases where the Ant doesn't respond/isn't reachable.  Before it would throw nasty .Net messages.

Check the log.  Maybe it'll tell you something?  Maybe the addresses are wrong?

If you don't see what's wrong, can you post a screenshot of your config?  Maybe it can be spotted that way.

M

[daddyfatsax]

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

[MoreBloodWine]

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

The only thing not working is the web scraping. but M wanted to understandably work on the API first since it's what most people use. Except in cases like me with people who have machines outside of the home network that need monitoring.

[mdude77]

It is working on the new FW. Just uploaded the new FW to all 11 of my S3's. Thanks mdude!! Love this software. Saves me a lot of a headache!!!

The only thing not working is the web scraping. but M wanted to understandably work on the API first since it's what most people use. Except in cases like me with people who have machines outside of the home network that need monitoring.

I think you missed a message?

https://bitcointalk.org/index.php?topic=596178.msg8513191#msg8513191

Web scraping works for me.  But I'm not able to simulate your environment, so I'm not 100% certain it'll work with your config.  Just waiting for you to try it and tell me.

M

[DimensionsOfHell]

Not sure why it won't work for me. I didn't bother upgrading the rest of my S3's because of the monitoring issues.











Hope these help.

[mdude77]

Not sure why it won't work for me. I didn't bother upgrading the rest of my S3's because of the monitoring issues.

Hope these help.

It does.  Is it just those with the newest firmware "Thu Aug 7 10:56:26 CST 2014" that have the problem?  Are you sure it's those that are upgraded that have the problem, and not the other way around?

I didn't bother testing it with the older firmware, just the new.  It wouldn't surprise me at all if it doesn't work anything but the newest firmware.

That "unexpected character" is why it broke as an S1, that's the malformed output that the new firmware creates.  I correct it before I pass it to the parsing routine, and I tried to not correct it if it wasn't necessary, but it's possible I mangled that.

M

[DimensionsOfHell]

I'm more than fairly certain those are the ones that have the newest fw, as those are the ones I actually have issues with. They tend to slow down every few hours, and I have to restart them every few hours to get the hash back up. They rarely get to 440gh/s, and slowly crawl to mid to low 300's after a full day, so I upgraded those to see if it had any improvements. 2 of them had a slight improvement, but two still slow down a lot. I've seen one go down to the low 200's after 3 days. I don't know if it has any hardware issues that conflict with it. I can try also upgrading some other ones to see if it causes the same issues, but I suspect it'll have the same issues.

I even deleted all the old versions, then unzipped the new version and ran it. Same issue. I haven't restarted my computer in a while either, so I'll try that as well. Maybe it's an issue with my computer. I'll update this post in a bit as soon as I get some time to do all that.

[mdude77]

I'm more than fairly certain those are the ones that have the newest fw, as those are the ones I actually have issues with. They tend to slow down every few hours, and I have to restart them every few hours to get the hash back up. They rarely get to 440gh/s, and slowly crawl to mid to low 300's after a full day, so I upgraded those to see if it had any improvements. 2 of them had a slight improvement, but two still slow down a lot. I've seen one go down to the low 200's after 3 days. I don't know if it has any hardware issues that conflict with it. I can try also upgrading some other ones to see if it causes the same issues, but I suspect it'll have the same issues.

I even deleted all the old versions, then unzipped the new version and ran it. Same issue. I haven't restarted my computer in a while either, so I'll try that as well. Maybe it's an issue with my computer. I'll update this post in a bit as soon as I get some time to do all that.

Wait, I see what's wrong!

They're entered as S1s.  Remove them and add them as S3s, and you should be fine.

M

[daddyfatsax]

All my old S3's are still showing up in my monitor. Do I just need to delete the registry files and start over, or is there another way to delete them?

[mdude77]

All my old S3's are still showing up in my monitor. Do I just need to delete the registry files and start over, or is there another way to delete them?

You can select them individually from the config and remove them.

Or delete/rename hkey_current_user\software\mantmonitor\ants

Another short cut for those who were using them as S1s, you can just rename the S1 entries to S3 in that subkey.  If you don't feel comfortable editing the registry, you should delete them through the interface.

M