I hooked up and configured 10 blades which are utilizing a proxy on my computer... The problem is the proxy output is quite confusing. It seems like the blades will ALL switch over from one proxy to the other (configure needs 2 servers in blade setup, so I have 2 proxies running, pointing at different pool servers for same pool)
I am using the -q (quiet) command, and am getting a consistent listings of this:
2013-11-30 18:52:26,188 WARNING proxy # [0ms] Share from 'x' accepted, diff 128
2013-11-30 18:52:26,190 WARNING proxy # [0ms] Share from 'x' accepted, diff 128
2013-11-30 18:52:26,197 WARNING proxy # [0ms] Share from 'x' accepted, diff 128
2013-11-30 18:52:26,200 WARNING proxy # [0ms] Share from 'x' accepted, diff 128
I also get this error w/ the proxy after running it for an hr.
--- <exception caught here> ---
File "twisted\internet\defer.pyo", line 134, in maybeDeferred
File "mining_libs\worker_registry.pyo", line 37, in authorize
File "stratum\socket_transport.pyo", line 93, in rpc
stratum.custom_exceptions.TransportException: Not connected
Unhandled error in Deferred:
Unhandled Error
Traceback (most recent call last):
File "twisted\web\server.pyo", line 156, in process
File "twisted\web\server.pyo", line 191, in render
File "twisted\web\resource.pyo", line 216, in render
File "mining_libs\getwork_listener.pyo", line 163, in render_POST
My pool, GHash, sees all the work submitted, but it seems like I'm submitting quite a good amount of stale shares... Anyone know how to fix this??
Difficulty is set at 128, as recommended by the ghash FAQ for 100+gh/s.
