m0mchil / poclbm

PyOpenCL bitcoin miner
Other
681 stars 387 forks source link

Tracebacks when network connection lost #65

Closed mike-hart closed 11 years ago

mike-hart commented 11 years ago

eu.eclipsemc.com:8337 13/04/2013 17:12:17, long poll IO error [Errno 10061] No connection could be made because the target machine actively refused it Traceback (most recent call last): File "GetworkSource.pyo", line 198, in long_poll_thread File "GetworkSource.pyo", line 105, in request File "httplib.pyo", line 958, in request File "httplib.pyo", line 992, in _send_request File "httplib.pyo", line 954, in endheaders File "httplib.pyo", line 814, in _send_output File "httplib.pyo", line 776, in send File "httplib.pyo", line 757, in connect File "socket.pyo", line 571, in create_connection error: [Errno 10061] No connection could be made because the target machine actively refused it

This is repeated over and over when a network connection is lost. Maybe poclbm should start (and notify about) an exponential backoff rather than just continuing to spam the logs every ~3s when connection is lost?

m0mchil commented 11 years ago

Long polling is used together with getwork protocol, which is deprecated. Please use pools with support for stratum protocol.