Bitcoin Forum
May 25, 2017, 05:19:12 AM *
News: If the forum does not load normally for you, please send me a traceroute.
 
   Home   Help Search Donate Login Register  
Pages: [1]
  Print  
Author Topic: Long poll exceptions on Eligius port 80  (Read 1518 times)
strictlyfocused
Jr. Member
*
Offline Offline

Activity: 55


View Profile
June 29, 2011, 01:07:38 PM
 #1

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
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
1495689552
Hero Member
*
Offline Offline

Posts: 1495689552

View Profile Personal Message (Offline)

Ignore
1495689552
Reply with quote  #2

1495689552
Report to moderator
1495689552
Hero Member
*
Offline Offline

Posts: 1495689552

View Profile Personal Message (Offline)

Ignore
1495689552
Reply with quote  #2

1495689552
Report to moderator
1495689552
Hero Member
*
Offline Offline

Posts: 1495689552

View Profile Personal Message (Offline)

Ignore
1495689552
Reply with quote  #2

1495689552
Report to moderator
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin-Qt, which will follow the rules of the network no matter what miners do. Even if every miner decided to create 1000 bitcoins per block, full nodes would stick to the rules and reject those blocks.
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
Luke-Jr
Legendary
*
Offline Offline

Activity: 2170



View Profile
June 29, 2011, 06:21:24 PM
 #2

This probably means there's a transparent proxy interfering. Try disabling LP.

Baazee
Jr. Member
*
Offline Offline

Activity: 35



View Profile WWW
October 13, 2012, 09:37:04 AM
 #3

Can it be that since yesterday, the mining is no longer possible on port 80?

Luke-Jr
Legendary
*
Offline Offline

Activity: 2170



View Profile
October 14, 2012, 01:12:15 AM
 #4

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 Sad

Pages: [1]
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!