Quote from: poolwaffle on March 04, 2014, 10:35:28 AM

Quote from: Nightlander on March 04, 2014, 10:27:32 AM

Any idea for the reason having quite frequent getwork failures? Couple within minutes to an hour.
Server is set to eu, automatic difficulty, couple workers which both act the same.
Finishing my "first day job" in wafflepool and wondering what's up with that, will that cut the whipped cream off my waffles.

First I've heard of it actually. Is it a connection problem perhaps? My guess is if it were a more widespread issue, we would have more complaints about it. Also, EU is our lowest utilized cluster, so its extremely unlikely to be getting bogged down...

Hard to say.. after restarting the router (there haven't been issues with it lately), things seem to work just the same..

[4.3.2014 12:43:39] CGMiner (4920): Network difficulty is now 1 196.
[4.3.2014 12:46:30] CGMiner (4920): Network difficulty is now 9 205.
[4.3.2014 12:47:00] CGMiner (4920): Network difficulty is now 6 137.
[4.3.2014 12:48:31] CGMiner (4920): 1 getwork failure(s) reported.
[4.3.2014 12:48:51] CGMiner (4920): Network difficulty is now 67.
[4.3.2014 12:50:01] CGMiner (4920): Network difficulty is now 1 196.
[4.3.2014 12:53:53] CGMiner (4920): 1 getwork failure(s) reported.

With the another worker the same deal. Usually these haven't been typical issues with these crypto thingies..
Otherwise things seem to run smoothly. Not so much stales nor rejects.