Bitcoin Forum

Other => Beginners & Help => Topic started by: strictlyfocused on June 29, 2011, 01:07:38 PM



Title: Long poll exceptions on Eligius port 80
Post by: strictlyfocused on June 29, 2011, 01:07:38 PM
I only get this when connected to Eligius over port 80, when I connect on 8337 it never seems to occur. This is with the PhatK version of poclbm found. This wouldnt be a big deal except Ive got a few miners behind a firewall that will only allow port 80. Im using the phatk version of poclbm found here (http://forum.bitcoin.org/index.php?topic=19169.0)
Code:
29/06/2011 09:02:48, LP connected to s3.mining.eligius.st:80
29/06/2011 09:03:03, long poll exception:
Traceback (most recent call last):
  File "BitcoinMiner.pyc", line 350, in longPollThread
  File "BitcoinMiner.pyc", line 320, in request
  File "json\__init__.pyc", line 307, in loads
  File "json\decoder.pyc", line 319, in decode
  File "json\decoder.pyc", line 338, in raw_decode
ValueError: No JSON object could be decoded
29/06/2011 09:03:04, fc32befc, ERROR (will resend)
29/06/2011 09:03:05, fc32befc, accepted
29/06/2011 09:03:05, Using new LP URL /LP
29/06/2011 09:03:05, LP connected to s3.mining.eligius.st:80
29/06/2011 09:03:21, long poll exception:
Traceback (most recent call last):
  File "BitcoinMiner.pyc", line 350, in longPollThread
  File "BitcoinMiner.pyc", line 320, in request
  File "json\__init__.pyc", line 307, in loads
  File "json\decoder.pyc", line 319, in decode
  File "json\decoder.pyc", line 338, in raw_decode
ValueError: No JSON object could be decoded
29/06/2011 09:03:26, Using new LP URL /LP
29/06/2011 09:03:26, LP connected to s3.mining.eligius.st:80
29/06/2011 09:03:41, long poll exception:
Traceback (most recent call last):
  File "BitcoinMiner.pyc", line 350, in longPollThread
  File "BitcoinMiner.pyc", line 320, in request
  File "json\__init__.pyc", line 307, in loads
  File "json\decoder.pyc", line 319, in decode
  File "json\decoder.pyc", line 338, in raw_decode
ValueError: No JSON object could be decoded
29/06/2011 09:03:41, 1d1e02df, ERROR (will resend)
29/06/2011 09:03:46, 1d1e02df, accepted
29/06/2011 09:03:46, Using new LP URL /LP
29/06/2011 09:03:46, LP connected to s3.mining.eligius.st:80
29/06/2011 09:04:01, long poll exception:
Traceback (most recent call last):
  File "BitcoinMiner.pyc", line 350, in longPollThread
  File "BitcoinMiner.pyc", line 320, in request
  File "json\__init__.pyc", line 307, in loads
  File "json\decoder.pyc", line 319, in decode
  File "json\decoder.pyc", line 338, in raw_decode
ValueError: No JSON object could be decoded
29/06/2011 09:04:04, Using new LP URL /LP
29/06/2011 09:04:04, LP connected to s3.mining.eligius.st:80


Title: Re: Long poll exceptions on Eligius port 80
Post by: Luke-Jr on June 29, 2011, 06:21:24 PM
This probably means there's a transparent proxy interfering. Try disabling LP.


Title: Re: Long poll exceptions on Eligius port 80
Post by: Baazee on October 13, 2012, 09:37:04 AM
Can it be that since yesterday, the mining is no longer possible on port 80?


Title: Re: Long poll exceptions on Eligius port 80
Post by: Luke-Jr on October 14, 2012, 01:12:15 AM
Can it be that since yesterday, the mining is no longer possible on port 80?
Could be - been fighting some iptables issues since a forced reboot a few days ago. Haven't found a good solution yet :(