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

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MoreBloodWine on August 26, 2014, 09:39:24 PM

Ok, so I get alert popups now. ~~Still no highlighting~~, stale shows 0. Not sure if thatcs good or a glitch lol.

-- Highlighting actually does work but only if have the H figure shown. Can we maybe have the highlight apply to the normal dual figure *like temp) field if the H figure it set to not show ?

ACount is 1 on two of four machines, not sure what ACount is.

Name of the devices still show as S3:1.2.3.4:5678/cgi-bin/etc. etc. etc.

I assume it should just be S3:1.2.3.4:5678, doesn't make sense to have all the other trailing stuff.

The auto scroll to the bottom of the log also works BTW, so thumbs up there.

Lastly... same as before. When the app is exited, all devices but one get erased ;-/

Edit: Whats the UUU in pools mean ?

I don't get the name thing. It shows up properly for me. Where are you seeing it?

Saving isn't working yet when you have the same IP for everything.

As for the column names, see https://bitcointalksearch.org/topic/m.6548589

M

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: DimensionsOfHell on August 26, 2014, 11:11:02 PM

Quote from: MoreBloodWine on August 26, 2014, 09:39:24 PM

Quote from: mdude77 on August 26, 2014, 08:57:17 PM

Here's version 3.1. Mostly fixes on the web scraping side, but there are some tweaks for API users.

v3.1
- Changed the frequency display to show the decimal value instead of rounding.
- Changed the S3 JSON fix to also work if it happens to be marked as an S1.
- Hopefully fixed the problem with an error being thrown on the display grid if you're not using the API.
- Added difficulty (from all 3 pools), reject%, and stale% to the Web scraping routine.
- Changed the Stale % for the API to be calculated, as the value from the API seems to always be zero.
- Changed the log for Web "ant responded" to show the short Ant name instead of the full URL.
- Hopefully changed the log to properly autoscroll to the end of the log so you don't have to.
- Fixed a potential problem that could cause alerts not to trigger when using the Web scraping routines.

Download link: MAntMonitor31.zip

M

Whats the UUU in pools mean ?

I believe the UUU represent the three pools you have set up, either they are UP, or DEAD

That's what I was thinking but figured I'd still ask.

DimensionsOfHell

full member

Activity: 346

Merit: 100

Quote from: MoreBloodWine on August 26, 2014, 09:39:24 PM

Quote from: mdude77 on August 26, 2014, 08:57:17 PM

Here's version 3.1. Mostly fixes on the web scraping side, but there are some tweaks for API users.

v3.1
- Changed the frequency display to show the decimal value instead of rounding.
- Changed the S3 JSON fix to also work if it happens to be marked as an S1.
- Hopefully fixed the problem with an error being thrown on the display grid if you're not using the API.
- Added difficulty (from all 3 pools), reject%, and stale% to the Web scraping routine.
- Changed the Stale % for the API to be calculated, as the value from the API seems to always be zero.
- Changed the log for Web "ant responded" to show the short Ant name instead of the full URL.
- Hopefully changed the log to properly autoscroll to the end of the log so you don't have to.
- Fixed a potential problem that could cause alerts not to trigger when using the Web scraping routines.

Download link: MAntMonitor31.zip

M

Whats the UUU in pools mean ?

I believe the UUU represent the three pools you have set up, either they are UP, or DEAD

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: mdude77 on August 26, 2014, 08:57:17 PM

Here's version 3.1. Mostly fixes on the web scraping side, but there are some tweaks for API users.

v3.1
- Changed the frequency display to show the decimal value instead of rounding.
- Changed the S3 JSON fix to also work if it happens to be marked as an S1.
- Hopefully fixed the problem with an error being thrown on the display grid if you're not using the API.
- Added difficulty (from all 3 pools), reject%, and stale% to the Web scraping routine.
- Changed the Stale % for the API to be calculated, as the value from the API seems to always be zero.
- Changed the log for Web "ant responded" to show the short Ant name instead of the full URL.
- Hopefully changed the log to properly autoscroll to the end of the log so you don't have to.
- Fixed a potential problem that could cause alerts not to trigger when using the Web scraping routines.

Download link: MAntMonitor31.zip

M

Ok, so I get alert popups now. ~~Still no highlighting~~, stale shows 0. Not sure if thatcs good or a glitch lol.

-- Highlighting actually does work but only if have the H figure shown. Can we maybe have the highlight apply to the normal dual figure *like temp) field if the H figure it set to not show ?

ACount is 1 on two of four machines, not sure what ACount is.

Name of the devices still show as S3:1.2.3.4:5678/cgi-bin/etc. etc. etc.

I assume it should just be S3:1.2.3.4:5678, doesn't make sense to have all the other trailing stuff.

The auto scroll to the bottom of the log also works BTW, so thumbs up there.

Lastly... same as before. When the app is exited, all devices but one get erased ;-/

Edit: Whats the UUU in pools mean ?

kgb2mining

member

Activity: 112

Merit: 10

Quote from: paradigmflux on August 26, 2014, 07:44:13 PM

Does anyone know if there's an easier way to upgrade 30-40 S3's?
and has nobody offered to send this M guy a S3 yet? I mean heck, I bet he'd even be willing to pay back the BTC cost of the device once it mines the 0.5 btc or whatever, then he could keep the miner running after that and technically it wouldn't even have cost a cent to hook him up

Not found one yet from the firmware side - although it seems to be a bin file, which means it's probably self-extracting and replaces the kernel and whatever binaries they need. Might be possible if you could upload the file to somewhere and then trigger whatever function the web UI calls via remote SSH calls.

I hacked together some custom shell scripts to do the most common things to them - reboot one or all, change pool settings, deploy the init.d cgminer to be able to play with queue settings and also deploy different asiq freq settings for the S1's. Doing mass changes to these gets real painful once you're over 10, and with over 50 of them it's a true nightmare.

And yes, I did offer an S3 to him recently, but he was already about to receive one, and appears to have.

kgb2mining

member

Activity: 112

Merit: 10

Quote from: mdude77 on August 26, 2014, 05:12:20 PM

Quote from: kgb2mining on August 26, 2014, 04:58:15 PM

Quote from: mdude77 on August 26, 2014, 04:05:13 PM

You should be able to re-apply the firmware.

M

Yep that seems to have done the trick, thanks. Now to find out what is different between that and my custom copy and fix it.

Maybe you blocked API access altogether?

M

Possible. Did a diff on the two files and I'm really not seeing any major difference that I could attribute to blowing it up. But, I'm deploying out the "stock" one with just the queue change now, and they seem to be coming back to life in the monitor. Thanks for the help!

mdude77

legendary

Activity: 1540

Merit: 1001

Here's version 3.1. Mostly fixes on the web scraping side, but there are some tweaks for API users.

v3.1
- Changed the frequency display to show the decimal value instead of rounding.
- Changed the S3 JSON fix to also work if it happens to be marked as an S1.
- Hopefully fixed the problem with an error being thrown on the display grid if you're not using the API.
- Added difficulty (from all 3 pools), reject%, and stale% to the Web scraping routine.
- Changed the Stale % for the API to be calculated, as the value from the API seems to always be zero.
- Changed the log for Web "ant responded" to show the short Ant name instead of the full URL.
- Hopefully changed the log to properly autoscroll to the end of the log so you don't have to.
- Fixed a potential problem that could cause alerts not to trigger when using the Web scraping routines.

Download link: MAntMonitor31.zip

M

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: paradigmflux on August 26, 2014, 07:44:13 PM

Does anyone know if there's an easier way to upgrade 30-40 S3's?
and has nobody offered to send this M guy a S3 yet? I mean heck, I bet he'd even be willing to pay back the BTC cost of the device once it mines the 0.5 btc or whatever, then he could keep the miner running after that and technically it wouldn't even have cost a cent to hook him up

I've got an S3, support is in the latest version, but rumor has it only works if you're using the latest firmware.

Not sure about upgrading them.. aside from one at a time.

M

paradigmflux

sr. member

Activity: 378

Merit: 254

small fry

Does anyone know if there's an easier way to upgrade 30-40 S3's?
and has nobody offered to send this M guy a S3 yet? I mean heck, I bet he'd even be willing to pay back the BTC cost of the device once it mines the 0.5 btc or whatever, then he could keep the miner running after that and technically it wouldn't even have cost a cent to hook him up

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kgb2mining on August 26, 2014, 04:58:15 PM

Quote from: mdude77 on August 26, 2014, 04:05:13 PM

You should be able to re-apply the firmware.

M

Yep that seems to have done the trick, thanks. Now to find out what is different between that and my custom copy and fix it.

Maybe you blocked API access altogether?

M

kgb2mining

member

Activity: 112

Merit: 10

Quote from: mdude77 on August 26, 2014, 04:05:13 PM

You should be able to re-apply the firmware.

M

Yep that seems to have done the trick, thanks. Now to find out what is different between that and my custom copy and fix it.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kgb2mining on August 26, 2014, 03:04:39 PM

Quote from: mdude77 on August 26, 2014, 02:44:32 PM

Quote from: kgb2mining on August 26, 2014, 02:39:24 PM

Ok, so is there any reason why the SSH API would stop working, but the web scrape still works?

All my S3's now show up as ERROR in the panel when using the API call, but when un-checked, it pulls info just fine. Any ideas on how to troubleshoot that?

Are all your S3s using the latest firmware? I thought someone said it doesn't work with the older firmware.

M

Yep, I did the firmware upgrade yesterday, but I did upload a copy of cgminer (the /etc/init.d one) today to change the queue length. I wonder if any changes were made to the default cgminer with the firmware upgrade that I may have just blown away.

Any one got a stock /etc/init.d/cgminer file from the latest firmware I can try?

You should be able to re-apply the firmware.

M

kgb2mining

member

Activity: 112

Merit: 10

Quote from: mdude77 on August 26, 2014, 02:44:32 PM

Quote from: kgb2mining on August 26, 2014, 02:39:24 PM

Ok, so is there any reason why the SSH API would stop working, but the web scrape still works?

All my S3's now show up as ERROR in the panel when using the API call, but when un-checked, it pulls info just fine. Any ideas on how to troubleshoot that?

Are all your S3s using the latest firmware? I thought someone said it doesn't work with the older firmware.

M

Yep, I did the firmware upgrade yesterday, but I did upload a copy of cgminer (the /etc/init.d one) today to change the queue length. I wonder if any changes were made to the default cgminer with the firmware upgrade that I may have just blown away.

Any one got a stock /etc/init.d/cgminer file from the latest firmware I can try?

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: kgb2mining on August 26, 2014, 02:39:24 PM

Ok, so is there any reason why the SSH API would stop working, but the web scrape still works?

All my S3's now show up as ERROR in the panel when using the API call, but when un-checked, it pulls info just fine. Any ideas on how to troubleshoot that?

Are all your S3s using the latest firmware? I thought someone said it doesn't work with the older firmware.

M

kgb2mining

member

Activity: 112

Merit: 10

Ok, so is there any reason why the SSH API would stop working, but the web scrape still works?

All my S3's now show up as ERROR in the panel when using the API call, but when un-checked, it pulls info just fine. Any ideas on how to troubleshoot that?

elpres

newbie

Activity: 57

Merit: 0

I am just curious, is there any one that may desire a Java version of this? I've been tossing up the idea for a while and thought it would provide multi-platform support.
I wouldn't be able to get onto it for a while but if there is call for it I may be motivated to do it.

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Quote from: mdude77 on August 24, 2014, 02:47:09 PM

Re reject and stale %, I assume it's just reject / (accepted + rejected) and stale / (accepted + stale)? The numbers pretty close to what I get from the API.

The log bugs me too. I tried a few things already to solve that, and nothing has completely worked yet.

As for the 1 of 4 ... I know why. Oversight on my part. They aren't saving correctly, they all get plopped into one entry. So for now, don't shut it down!

The other things, aside from the name thing, I already have fixed in dev.

M

Wish I could help but I don't know the math used for those values.

Maybe someone else here can help ?

I was doing the whole shutdown thing to test... when I started messing with it I still had old reg values showing up and had to delete the whole Ant folder from regedit. Wont mess with anything else til a new versions out.

As for everything else, sounds good ;-)

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MoreBloodWine on August 24, 2014, 02:33:42 PM

Sounds good M, here's one other thing I think might help. At least with me lol.

I noticed the log reads old to new and you need to scroll down to see new items, might you consider flipping it so the new log items are always at he top so to see older items one would need to scroll down ?

Oh, and about the name thing... it shows fine in config. It's just on the "main" page where the stats are seen does the name show with all the other stuff.

Also, I closed the program out and only one of the four miners showed up when I restarted it.

Re reject and stale %, I assume it's just reject / (accepted + rejected) and stale / (accepted + stale)? The numbers pretty close to what I get from the API.

The log bugs me too. I tried a few things already to solve that, and nothing has completely worked yet.

As for the 1 of 4 ... I know why. Oversight on my part. They aren't saving correctly, they all get plopped into one entry. So for now, don't shut it down!

The other things, aside from the name thing, I already have fixed in dev.

M

MoreBloodWine

legendary

Activity: 1064

Merit: 1001

Sounds good M, here's one other thing I think might help. At least with me lol.

I noticed the log reads old to new and you need to scroll down to see new items, might you consider flipping it so the new log items are always at he top so to see older items one would need to scroll down ?

Oh, and about the name thing... it shows fine in config. It's just on the "main" page where the stats are seen does the name show with all the other stuff.

Also, I closed the program out and only one of the four miners showed up when I restarted it.

mdude77

legendary

Activity: 1540

Merit: 1001

Quote from: MoreBloodWine on August 24, 2014, 01:53:32 PM

Looks like it works, is there a way to omit the full URL and just show the IP ?

So right now the Name might look like this...

1.2.3.4:5678/cgi-bin/luci/;stok=etc. etc. etc.

I think all we rally need shown is just 1.2.3.4:5678.

That's all it's supposed to show. Not sure why it's showing more. Will have to look at that.

Quote

Also, I noticed when web scraping these fields are blank...

Diff, Rej%, Stale%

That's actually intentional. I don't do any calculations for those when using the API, I just display what's from the API. I'll have to look at the numbers on the web UI and see if I can derive the values that the API shows.

The difficulty could be a tricky one. I think the best I can do is show the values from all the pools.

Quote

Here's some other things I noticed.

The freq values are rounding up and not showing true values... like 237.25 shows as 238 and 243.75 shows as 244. I know this might not be a big deal to a lot of people but I'd like it if it shows true and not rounded values.

That's easily fixed.

Quote

There's a few other curiosities I will touch on later, don't want to overload one reply lol

This also keeps coming up from time to time...

Unhandled exception has occurred in your application. If you click Continue, the application will ignore this error and attempt to continue. If you click Quit, the application will close immediately.

Conversion from type 'DBNull" to type 'String' is not valid.

Here's details...

I have an idea what's causing that.

Thanks for the feedback!

M

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