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

[GuyllFyre]

I also don't know where it's getting this value:
198.105.244.240:4028

That's nowhere near my IP that I put into Ant Monitor.

[GuyllFyre]

Another couple of updates on my progress.
I'm running Vista 32 Bit under VirtualBox in Linux Mint.
The adapter had put itself on a 10.x.x.x range.  I switched that to bridge to my local adapter to get the local network IP on it.

API mode still does not work, same error.
Leaving API unchecked now puts the proper name in but it's not actually displaying anything else for status.

[mdude77]

Another couple of updates on my progress.
I'm running Vista 32 Bit under VirtualBox in Linux Mint.
The adapter had put itself on a 10.x.x.x range.  I switched that to bridge to my local adapter to get the local network IP on it.

API mode still does not work, same error.
Leaving API unchecked now puts the proper name in but it's not actually displaying anything else for status.

What addresses are you entering for your ants?  Can you give a screenshot of your config tab?

M

[mdude77]

I have installed new version but still have some problems with same devices.

I have checked them and there is no wifi error!

Code:

6/21/2014 1:16:58 PM: ERROR when checking alerts on S1:14 (step 1): Conversion from type 'DBNull' to type 'String' is not valid.
6/21/2014 1:16:58 PM: ERROR when checking alerts on S1:51 (step 1): Conversion from type 'DBNull' to type 'String' is not valid.
6/21/2014 1:16:58 PM: ERROR when checking alerts on S2:99 (step 5): Conversion from type 'DBNull' to type 'String' is not valid.

Thanks, this is progress!  Can you get me a screenshot of one the status page for those 3 miners?

M

Here it is:

Can you post a pic of the M's Ant Miner Ant tab?  Are the rows for those Ants in question blank or have an error?

M

[sepehr]

I have installed new version but still have some problems with same devices.

I have checked them and there is no wifi error!

Code:

6/21/2014 1:16:58 PM: ERROR when checking alerts on S1:14 (step 1): Conversion from type 'DBNull' to type 'String' is not valid.
6/21/2014 1:16:58 PM: ERROR when checking alerts on S1:51 (step 1): Conversion from type 'DBNull' to type 'String' is not valid.
6/21/2014 1:16:58 PM: ERROR when checking alerts on S2:99 (step 5): Conversion from type 'DBNull' to type 'String' is not valid.

Thanks, this is progress!  Can you get me a screenshot of one the status page for those 3 miners?

M

Here it is:

Can you post a pic of the M's Ant Miner Ant tab?  Are the rows for those Ants in question blank or have an error?

M

Here it is:

[GuyllFyre]

Another couple of updates on my progress.
I'm running Vista 32 Bit under VirtualBox in Linux Mint.
The adapter had put itself on a 10.x.x.x range.  I switched that to bridge to my local adapter to get the local network IP on it.
API mode still does not work, same error.
Leaving API unchecked now puts the proper name in but it's not actually displaying anything else for status.

What addresses are you entering for your ants?  Can you give a screenshot of your config tab?
M

I figured it out.  Might help to have a bit more info here.
Local IP address makes me think that it's the IP of the Ant and the field below is for description.
When I realized that the local IP is that of the computer on which Ant Monitor is running, and then put the IP of the Ant in the next field down.
You might want to change "Local IP Address" or "Local PC IP" to something like "IP of your PC" or "IP of PC Running Monitor".
Then add a description for the next field like "Antminer IP".
http://www.chaoticcrafts.com/misc/MAntMonitor.png

[mdude77]

Another couple of updates on my progress.
I'm running Vista 32 Bit under VirtualBox in Linux Mint.
The adapter had put itself on a 10.x.x.x range.  I switched that to bridge to my local adapter to get the local network IP on it.
API mode still does not work, same error.
Leaving API unchecked now puts the proper name in but it's not actually displaying anything else for status.

What addresses are you entering for your ants?  Can you give a screenshot of your config tab?
M

I figured it out.  Might help to have a bit more info here.
Local IP address makes me think that it's the IP of the Ant and the field below is for description.
When I realized that the local IP is that of the computer on which Ant Monitor is running, and then put the IP of the Ant in the next field down.
You might want to change "Local IP Address" or "Local PC IP" to something like "IP of your PC" or "IP of PC Running Monitor".
Then add a description for the next field like "Antminer IP".

ahh!  good point.

thanks.

M

[mstrongbow]

*snipped
Local IP address
*snipped

It's IT jargon  
Most won't have issues with this but there will be a few.

[GuyllFyre]

*snipped
Local IP address
*snipped

It's IT jargon  
Most won't have issues with this but there will be a few.

LOL!
I've been doing IT work for 26 years.
When I realized what I did wrong, I felt like an idiot.

I figured that just a small change in description and adding one to the second field, would be enough to help everyone out.
You know, jog our memory as we're trying to not think any more after a day of learning scripting, command line options for various utilities, writing scripts to scan for certain issues, update certain things, automate cleanups and maintenance for others, and deploying customized power options to a series of computers that are being stupid due to default settings that cause problems...

[allcoinminer]

Soon this thread will be
M's Ant (S1/S2/S3) Monitor v2.0 - now with alerts!

Feature Request:
Show the pools entered in ant S1 & S2. If the can be editable more good.

[mdude77]

Can you post a pic of the M's Ant Miner Ant tab?  Are the rows for those Ants in question blank or have an error?

Thanks.  The Alert routine wasn't properly checking to make sure that Ant row didn't have an error.  But that doesn't help me determine why there's an error just yet.  Is there nothing else in your log about those 4?

M

[leptar]

working well here..

[mstrongbow]

*snipped
Local IP address
*snipped

It's IT jargon  
Most won't have issues with this but there will be a few.

LOL!
I've been doing IT work for 26 years.
When I realized what I did wrong, I felt like an idiot.

I figured that just a small change in description and adding one to the second field, would be enough to help everyone out.
You know, jog our memory as we're trying to not think any more after a day of learning scripting, command line options for various utilities, writing scripts to scan for certain issues, update certain things, automate cleanups and maintenance for others, and deploying customized power options to a series of computers that are being stupid due to default settings that cause problems...

 

[mdude77]

Since I had a little bit of time... here's v2.1.  Lots of little things.

v2.1
- Added some more error handling and debug code around the API logic.
- Enabled alerts for the web screenscraping logic (non API).
- Fixed a typo that would complain about an S2 temp alert not being set when it was S1 turned on not S2.
- Visual change to make it clear how to add Ant addresses, and the local IP address is for scanning, nothing else.
- Added an email governor to prevent email alert spam.  Set to this minimum time between EMail alerts.  Note this runs by Ant, and defaults to 10 minutes.
- Added a difficulty column to the Ant output grid.  It assumes the last difficulty for the first "Alive" pool is the right one.
- Added the ability for it to remember column positions.
- Added single instance logic, to prevent you from accidentally running more than one at a time.

Download link: MAntMonitor21.zip

M

[norgan]

Since I had a little bit of time... here's v2.1.  Lots of little things.

v2.1
- Added some more error handling and debug code around the API logic.
- Enabled alerts for the web screenscraping logic (non API).
- Fixed a typo that would complain about an S2 temp alert not being set when it was S1 turned on not S2.
- Visual change to make it clear how to add Ant addresses, and the local IP address is for scanning, nothing else.
- Added an email governor to prevent email alert spam.  Set to this minimum time between EMail alerts.  Note this runs by Ant, and defaults to 10 minutes.
- Added a difficulty column to the Ant output grid.  It assumes the last difficulty for the first "Alive" pool is the right one.
- Added the ability for it to remember column positions.
- Added single instance logic, to prevent you from accidentally running more than one at a time.

Download link: MAntMonitor21.zip

M

Thanks for the update!

[mstrongbow]

Since I had a little bit of time... here's v2.1.  Lots of little things.

v2.1
- Added some more error handling and debug code around the API logic.
- Enabled alerts for the web screenscraping logic (non API).
- Fixed a typo that would complain about an S2 temp alert not being set when it was S1 turned on not S2.
- Visual change to make it clear how to add Ant addresses, and the local IP address is for scanning, nothing else.
- Added an email governor to prevent email alert spam.  Set to this minimum time between EMail alerts.  Note this runs by Ant, and defaults to 10 minutes.
- Added a difficulty column to the Ant output grid.  It assumes the last difficulty for the first "Alive" pool is the right one.
- Added the ability for it to remember column positions.
- Added single instance logic, to prevent you from accidentally running more than one at a time.

Download link: MAntMonitor21.zip

M

Thanks for the update!

Likewise! Looks great. Not sure what I should use in the Parms: box under alert settings but it did alert me using a .wav, so cool!

[sepehr]

Can you post a pic of the M's Ant Miner Ant tab?  Are the rows for those Ants in question blank or have an error?

Thanks.  The Alert routine wasn't properly checking to make sure that Ant row didn't have an error.  But that doesn't help me determine why there's an error just yet.  Is there nothing else in your log about those 4?

M

This is my complete one turn logs with your last update:

Code:

6/22/2014 9:02:29 AM: M's Ant Monitor v2.1 starting
6/22/2014 9:03:31 AM: ERROR when querying S1:14 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:03 AM: ERROR when querying S1:51 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:36 AM: ERROR when accessing API on 19.168.1.99: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 19.168.1.99:4028
6/22/2014 9:05:36 AM: ERROR when querying S2:99 (step 1): Value cannot be null.
Parameter name: s
6/22/2014 9:05:36 AM: ALERT: S1:39 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:49 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:64 exceeded 1 X count
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:42 AM: Alert email sent.

[sepehr]

Can you post a pic of the M's Ant Miner Ant tab?  Are the rows for those Ants in question blank or have an error?

Thanks.  The Alert routine wasn't properly checking to make sure that Ant row didn't have an error.  But that doesn't help me determine why there's an error just yet.  Is there nothing else in your log about those 4?

M

This is my complete one turn logs with your last update:

Code:

6/22/2014 9:02:29 AM: M's Ant Monitor v2.1 starting
6/22/2014 9:03:31 AM: ERROR when querying S1:14 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:03 AM: ERROR when querying S1:51 (step 1): Error reading JObject from JsonReader. Path '', line 0, position 0.
6/22/2014 9:05:36 AM: ERROR when accessing API on 19.168.1.99: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond 19.168.1.99:4028
6/22/2014 9:05:36 AM: ERROR when querying S2:99 (step 1): Value cannot be null.
Parameter name: s
6/22/2014 9:05:36 AM: ALERT: S1:39 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:49 exceeded 1 X count
6/22/2014 9:05:36 AM: ALERT: S1:64 exceeded 1 X count
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:39 AM: Alert email sent.
6/22/2014 9:05:42 AM: Alert email sent.

Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!

[leptar]

It just gets better and better...

thanks...

sent another token of appreciation...

[mdude77]

Solved!
The two S1 devices and one S2 device had old firmwares!
Updated the firmware and the problem solved now!
Thank you!

Excellent!

M