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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: tl121 on September 29, 2014, 08:57:00 PM

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

tl121

sr. member

Activity: 278

Merit: 254

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

legendary

Activity: 1540

Merit: 1001

Quote from: tl121 on September 29, 2014, 02:05:53 PM

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

sr. member

Activity: 278

Merit: 254

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

legendary

Activity: 1540

Merit: 1001

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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: ZymurBits on September 27, 2014, 08:03:48 AM

I am using b7. The log shows errors when trying to send email on processed alerts.

9/27/2014 8:00:44 AM: M's Ant Monitor v3.4b7 starting
9/27/2014 8:00:44 AM: Initiated Ant refresh
9/27/2014 8:00:45 AM: ERROR when processing alerts on S3:1.158 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
9/27/2014 8:00:45 AM: ERROR when processing alerts on S3:1.157 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName

I can send manual email tests with no errors.

9/27/2014 8:03:03 AM: Alert email sent.

Popup notifications for alerts work fine.

Thanks, that told me what was wrong!

Will be fixed in the next version.

M

ZymurBits

member

Activity: 89

Merit: 10

I am using b7. The log shows errors when trying to send email on processed alerts.

9/27/2014 8:00:44 AM: M's Ant Monitor v3.4b7 starting
9/27/2014 8:00:44 AM: Initiated Ant refresh
9/27/2014 8:00:45 AM: ERROR when processing alerts on S3:1.158 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName
9/27/2014 8:00:45 AM: ERROR when processing alerts on S3:1.157 (step 11): Column named IPAddress cannot be found.
Parameter name: columnName

I can send manual email tests with no errors.

9/27/2014 8:03:03 AM: Alert email sent.

Popup notifications for alerts work fine.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: ZymurBits on September 26, 2014, 07:52:33 AM

Great work so far M! Have one minor issue that has popped up on this version. Email alerts quit working. Can go in and send test message fine but when real alerts occur, no emails. Sad

Are you using beta 7? Alerts were effectively disabled until beta 7 if you weren't using the standard naming convention for the Ants.

M

ZymurBits

member

Activity: 89

Merit: 10

Great work so far M! Have one minor issue that has popped up on this version. Email alerts quit working. Can go in and send test message fine but when real alerts occur, no emails. Sad

mdude77

legendary

Activity: 1540

Merit: 1001

Great, thank you both!

M

fire000

member

Activity: 98

Merit: 10

seconds the above poster M is appears ya debugged it as she working fine here now and rebooting etc

smilingloki

member

Activity: 73

Merit: 10

Quote from: mdude77 on September 25, 2014, 06:14:46 PM

Quote from: mdude77 on September 25, 2014, 06:03:12 PM

I found the problem!

M

Try this... MAntMonitor34b7.zip

M

WE HAVE A WINNER !!!
26/09/2014 1:45:09 p.m.: Initiated Ant refresh
26/09/2014 1:45:09 p.m.: ALERT: S3: 102ATHENA exceeded 1 X count
26/09/2014 1:45:09 p.m.: REBOOTING S3: 102ATHENA via SSH
26/09/2014 1:45:14 p.m.: Reboot of S3: 102ATHENA appears to have succeeded

Well done ! M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: mdude77 on September 25, 2014, 06:03:12 PM

I found the problem!

M

Try this... MAntMonitor34b7.zip

M

mdude77

legendary

Activity: 1540

Merit: 1001

I found the problem!

M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: fire000 on September 25, 2014, 03:43:53 PM

hey mdude I gave that v6 a try no joy there BUT I tied something to just humor myself here and that was to delete the ants out of the program and re set them up via the port scanner on the program I have found that has done the trick on getting the alerts etc working on...

when I 1st set it up I put the ip address in manually myself so could it be connect to that in some shape as that side was picking the ip up and monitor the data from the ants BUT not kicking the warnings and reboot in on it....

Just something I picked up after doing the auto scan on the ports and she running as she should be now....

That is weird. Did you by chance look at the log to see if it said it couldn't find the Ants?

It gives me an idea where to look as to what might be wrong.

Thanks!

M

smilingloki

member

Activity: 73

Merit: 10

giving v6 a go - i kinda like it Cheesy

fire000

member

Activity: 98

Merit: 10

hey mdude I gave that v6 a try no joy there BUT I tied something to just humor myself here and that was to delete the ants out of the program and re set them up via the port scanner on the program I have found that has done the trick on getting the alerts etc working on...

when I 1st set it up I put the ip address in manually myself so could it be connect to that in some shape as that side was picking the ip up and monitor the data from the ants BUT not kicking the warnings and reboot in on it....

Just something I picked up after doing the auto scan on the ports and she running as she should be now....

fire000

member

Activity: 98

Merit: 10

will gave it a crack now and let ya know how we go

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: fire000 on September 25, 2014, 07:22:55 AM

no problem atm is having to manual reboot them here as the alerts are not triggering for some reason has no idea why lol as the api is sending as ya can see hope this helps

Try this one:

Download link: MAntMonitor34b6.zip

If it still doesn't work, check the log, see if it says anything new.

M

fire000

member

Activity: 98

Merit: 10

no problem atm is having to manual reboot them here as the alerts are not triggering for some reason has no idea why lol as the api is sending as ya can see hope this helps

Topic: M's Miner (Ant/SP) Monitor v5.2: alerts,auto/mass/scheduled reboot/mobile miner - page 24. (Read 209561 times)