@simonk83 you seem to have a lagging connection with mt.red , happened to me few times, try the other pool if they still have it active or give a try reseting your router
Hmm. Is that this bit:
Code:
2011-08-10 06:51:39+1000 [HTTP11ClientProtocol,client] 'caught, Final response/w
riting'
2011-08-10 06:51:39+1000 [HTTP11ClientProtocol,client] 'Request.finish called on
a request after its connection was lost; use Request.notifyFinish to keep track
of this.'
riting'
2011-08-10 06:51:39+1000 [HTTP11ClientProtocol,client] 'Request.finish called on
a request after its connection was lost; use Request.notifyFinish to keep track
of this.'
Is there any way to catch that (in the code)? Like if it sees it's spamming a massive amount of getworks with no sends, it moves away?
seems so
