Bitcoin Forum

Other => Beginners & Help => Topic started by: jcoin on June 30, 2011, 01:45:39 PM



Title: HELP error connecting to slush's pool (phoenix 1.5)
Post by: jcoin on June 30, 2011, 01:45:39 PM
2011-06-30 09:36:50: Running command: C:\XXX\guiminer\phoenix.exe -u http://XXXXXXXXX@api.bitcoin.cz:8332 PLATFORM=0 DEVICE=0 -v -k phatk VECTORS BFI_INT AGGRESSION=13 FASTLOOP=false WORKSIZE=256
2011-06-30 09:36:50: Listener for "slush" started
2011-06-30 09:36:51: Listener for "slush": [30/06/2011 09:36:51] Phoenix 1.50 starting...
2011-06-30 09:36:52: Listener for "slush": Traceback (most recent call last):
2011-06-30 09:36:52: Listener for "slush": File "twisted\internet\tcp.pyc", line 529, in connectionLost
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 826, in dispatcher
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 1438, in _connectionLost_WAITING
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 1367, in _disconnectParser
2011-06-30 09:36:52: Listener for "slush": --- <exception caught here> ---
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 494, in connectionLost
2011-06-30 09:36:52: Listener for "slush": File "twisted\web\http.pyc", line 1366, in noMoreData
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 409, in _finished
2011-06-30 09:36:52: Listener for "slush": File "minerutil\_newclient3420.pyc", line 1346, in _finishResponse
2011-06-30 09:36:52: Listener for "slush": exceptions.UnboundLocalError: local variable 'reason' referenced before assignment

Anyone know how to fix this? I can connect to other pools with no problem. I've tried to restart it numerous times over the last 2 days, same error every time.


Title: Re: HELP error connecting to slush's pool (phoenix 1.5)
Post by: jcoin on July 01, 2011, 04:11:06 PM
i can't be the only one getting this error. It comes up a few times for deepbit in a forum search but no one responded with a fix.