Quote from: dmwardjr on January 09, 2017, 08:50:25 AM

Quote from: m1n1ngP4d4w4n on January 09, 2017, 08:25:54 AM

Default for IDLE worker is 15MN. check in your notification menu also that you checked IDLE WORKER. And that monitor box is checked for every of your workers.

Use the API to make your own monitoring too, That's what i do Cool

Sometimes you get false positives (receiving idle mails when your workers are running normally) i checked this behaviour with reccurent API query, so i let email alert but i rely more on the API for monitoring.

Thumbs Up!

I did not have monitor checked on any of my workers. Didn't realize I needed to. Thx man. Appreciate it.

Cheers

Quote from: ocminer on January 09, 2017, 11:43:26 AM

Quote from: armazingerz on January 09, 2017, 10:56:20 AM

Thanx, but it leads me to a couple questions, I checked "My Account" -> "Edit workers" and the hashrate reading is much smaller than the reading from Claymore, which one is accurate?

In the dashboard, your contributors hashrate is measured in H/s and ZEC/Day, and I'm unable to do so much ZEC/Day per H/s. For example, right now I'm supposed to get 0'073 ZEC/day with 411 H/s (Dashboard reading) but actually I'm doing like 0'13 ZEC/Day with 1300 H/s (Claymore reading). There is a huge difference, because with the Dashboard ratio I should be doing 0'23 ZEC/Day instead of 0'13

Quote from: ocminer on January 06, 2017, 08:57:59 AM

@armazingerz:
Check "My Account" -> "Edit workers". You should see the full hashrate there, the Dashboard is cached for performance.

OVH seems to have a bigger issue at the moment, some routes are broken and the servers unreachable, I hope they'll fix it ASAP. From Suprnova's side everything is okay.

Hi !

if your hashrate on "Edit Workers" is much smaller than what you're worker is actually reading there's something wrong. Maybe try to switch to another stratum server (zec.suprnova.cc:2142 instead of zec-eu.suprnova.cc:2142 (or vice versa)) and see if its better than.

The Dashboard is knowingly a bit slower and "lazier" in refreshing, but Edit Workers should match pretty close.. maybe +- 10 %

I had the same issues as you, but you just have to let the miner running for at least 24h before getting anything accurate. Share validation taking time, and all, usually look @ the daily result just before the day change to see what you have made

, also rely on the API to get your current hashrate, it's more accurate than either the dashboard or workers. And don't take it @ face value either, you need to make an average taking the value every 5mn for at least 6h to get your real average. Because how's pool are working your hash will spike or drop depending where you are in your calculation and when the pool is receiving/processing your shares.

Example for me, on a rig that generate about 2500sols/s my lowest value is about 1700-1800, and spike @3400, but if you average all the 5mn values for a whole day, you will get back your hashrate as the daily average.

here is a little bit of log from my monitoring script, as you can see values change alot, if you do an average on thoses values taken every 8mn for about an hour, you get 2508s/sols, and for course average get alot more accurate with more values over a longer course of time, but you get the gist of it Wink

Code:

2017-01-09 15:16:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:16:11 - Current Zcash - Suprnova Hashrate is 3165 this is higher than current treshold 200, mining along :)
2017-01-09 15:24:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:24:12 - Current Zcash - Suprnova Hashrate is 2634 this is higher than current treshold 200, mining along :)
2017-01-09 15:32:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:32:12 - Current Zcash - Suprnova Hashrate is 2722 this is higher than current treshold 200, mining along :)
2017-01-09 15:40:02 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:40:12 - Current Zcash - Suprnova Hashrate is 1808 this is higher than current treshold 200, mining along :)
2017-01-09 15:48:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:48:12 - Current Zcash - Suprnova Hashrate is 2345 this is higher than current treshold 200, mining along :)
2017-01-09 15:56:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 15:56:12 - Current Zcash - Suprnova Hashrate is 2102 this is higher than current treshold 200, mining along :)
2017-01-09 16:00:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:00:12 - Current Zcash - Suprnova Hashrate is 2573 this is higher than current treshold 200, mining along :)
2017-01-09 16:08:02 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:08:12 - Current Zcash - Suprnova Hashrate is 2208 this is higher than current treshold 200, mining along :)
2017-01-09 16:16:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:16:12 - Current Zcash - Suprnova Hashrate is 2361 this is higher than current treshold 200, mining along :)
2017-01-09 16:24:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:24:12 - Current Zcash - Suprnova Hashrate is 2615 this is higher than current treshold 200, mining along :)
2017-01-09 16:32:01 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:32:12 - Current Zcash - Suprnova Hashrate is 3170 this is higher than current treshold 200, mining along :)
2017-01-09 16:40:02 - Zcash - SUPRNOVA API UP HTTP/1.1 200 OK
2017-01-09 16:40:13 - Current Zcash - Suprnova Hashrate is 2185 this is higher than current treshold 200, mining along :)