[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 165.

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

So it appears the problems continue... my node has been effectively offline for the majority of the day today. P2Pool is pegging my CPU at 100% and I'm consistently seeing the "lost contact with bitcoind" message in the logs. Is this solely because of the ridiculous number of unconfirmed transactions that are still flooding the network (nearly 13k at this point)? Granted, my VPS isn't exactly a monster (but not horrible as a dual core droplet).

I'm on the latest version of p2pool and bitcoin core 0.10.2 compiled from source.

To the miners who are on my node, I apologize for the inconvenience this is likely causing you. On the bright side, my miners fall back to ck.'s solo pool, so maybe I'll be lucky and they'll solve a block for me Tongue

.

EDIT: when my node does appear online, and the miners are connected, they're reporting huge rejected hash percentages (25% or more).

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

You are welcome... and welcome to p2pool

.

windpath

legendary

Activity: 1258

Merit: 1027

Things seem to be running smoothly again after the final update at around 3PM EDT today.

There has been a flood of TX's on the bitcoin network, and GBT latency is currently higher than I'd like to see it, but I believe P2Pool is functioning as it should with the latest version.

As Forrest mentioned, on the newest version it appears we are simply rejecting anything from a node with lower than p2pool version 14, I show 100% V 14 peers on my node...

Anyone monitoring how much of the p2pool network we left behind?

Here is the bitcoin transaction flood from today (source linked, click on "txInMemoryPool" on lower left):

squidicuz

newbie

Activity: 58

Merit: 0

Quote from: mdude77 on July 06, 2015, 04:12:21 PM

I upgraded here as well. Here's a message I don't recall seeing before:

Code:

2015-07-06 17:10:22.969017 Peer 104.193.40.248:9333 misbehaving, will drop and ban. Reason: first message was not version message
2015-07-06 17:10:22.969112 Bad peer banned: (u'104.193.40.248', 9333)

Otherwise I'm getting lots of bad peers. For being at 95% on the new version, I sure do get connected to the 5% pretty easily.

M

The bad peers are the remaining forked version 13 peers being removed. Once your node ignores them all, stability will improve. The high transaction volume on the bitcoin network combined with the persistent p2pool share fetching of version 13 nodes, along with some nodes timing out and further adding peer stress, is really hammering everyone.
Updating to the latest version of p2pool from github is needed in order to block the connection spam and stabilize the pool.

mdude77

legendary

Activity: 1540

Merit: 1001

I upgraded here as well. Here's a message I don't recall seeing before:

Code:

2015-07-06 17:10:22.969017 Peer 104.193.40.248:9333 misbehaving, will drop and ban. Reason: first message was not version message
2015-07-06 17:10:22.969112 Bad peer banned: (u'104.193.40.248', 9333)

Otherwise I'm getting lots of bad peers. For being at 95% on the new version, I sure do get connected to the 5% pretty easily.

M

p3yot33at3r

sr. member

Activity: 266

Merit: 250

That would explain a lot, the thought did occur to me earlier:

Quote from: p3yot33at3r on July 06, 2015, 12:20:15 PM

Is that plonker doing another "stress test" again? Cheesy

If this is the case, it happening at around the same time as a forking would have to be intentional I reckon........is it from the same origin as the last time?

xyzzy099

legendary

Activity: 1066

Merit: 1098

Looks like someone is pounding the network with transactions:

https://bitcointalksearch.org/topic/m.11807542

Maybe this accounts for the problems you guys are seeing.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: forrestv on July 06, 2015, 03:08:01 PM

Quote from: p3yot33at3r on July 06, 2015, 02:42:05 PM

Hmmm.......has anyone made contact with forrestv? It would be good to get his take of what's happening........

Hey, I've been watching. You are trying the recent P2Pool commit that blocks pre-v14 peers, right? If that's confirmed to help, I'll make a P2Pool release with it.

Some P2P network thrashing is normal after a fork since you have the unupgraded nodes madly trying to find peers and download the (invalid to them) sharechain. Normally, there are less unupgraded nodes, but this fork was rushed, so I think that that contributed to it.

However, some are reporting high bitcoind CPU usage - P2Pool P2P network activity shouldn't be affecting bitcoind, so I'm not sure about that. Is that happening for Bitcoin users without P2Pool? It might be some similar post-BIP66 effect.

Hi forrestv,

Thanks for chiming in buddy. Yes, using the latest p2pool repo. I'm seeing high cpu usage on both p2pool & bitcoind, but the cpu usage on p2pool is much more prolonged & constantly higher than bitcoind, which seems to have sudden peaks & bursts of high usage - resulting in very high latency issues.

It's a tricky one eh?

I even tried re-downloading the p2pool sharechain......

nonnakip

hero member

Activity: 633

Merit: 591

Quote from: forrestv on July 06, 2015, 03:08:01 PM

However, some are reporting high bitcoind CPU usage - P2Pool P2P network activity shouldn't be affecting bitcoind, so I'm not sure about that. Is that happening for Bitcoin users without P2Pool? It might be some similar post-BIP66 effect.

I noticed when I started P2Pool that my node is carrying about 6000 unverified shares (17354 verified but on start it loaded 23000). I assume these are shares from <14.0. Perhaps all these unverifiable shares are causing the 100% CPU usage and bitcoind work_poller delays?

Would it be better to delete my data directory and redownload share chain? Or just wait until we solve a block and maybe the problem goes away by itself?

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Looks like the network is getting hammered with transactions... I turned off Matt's relay network and restarted everything. Looking at blockchain.info, there's ver 11k unconfirmed transactions currently.

My node is currently trying to put together blocks with 2k transactions...

Code:

2015-07-06 16:11:19.107855 New work for worker! Difficulty: 1217.831707 Share difficulty: 5838904.174398 Total block value: 25.382547 BTC including 1995 transactions
2015-07-06 16:11:52.966132 New work for worker! Difficulty: 1089.745702 Share difficulty: 5838098.085605 Total block value: 25.386081 BTC including 2018 transactions

forrestv

hero member

Activity: 516

Merit: 643

Quote from: p3yot33at3r on July 06, 2015, 02:42:05 PM

Hmmm.......has anyone made contact with forrestv? It would be good to get his take of what's happening........

Hey, I've been watching. You are trying the recent P2Pool commit that blocks pre-v14 peers, right? If that's confirmed to help, I'll make a P2Pool release with it.

Some P2P network thrashing is normal after a fork since you have the unupgraded nodes madly trying to find peers and download the (invalid to them) sharechain. Normally, there are less unupgraded nodes, but this fork was rushed, so I think that that contributed to it.

However, some are reporting high bitcoind CPU usage - P2Pool P2P network activity shouldn't be affecting bitcoind, so I'm not sure about that. Is that happening for Bitcoin users without P2Pool? It might be some similar post-BIP66 effect.

squidicuz

newbie

Activity: 58

Merit: 0

Quote from: nonnakip on July 06, 2015, 02:39:02 PM

NastyPool is running latest (14.0-6-g18b5ad5) and I also see large "LOST CONTACT WITH BITCOIND" blocks. I typed a rather large report of what I could find. But then I check the log again and it is happening right now! When I run bitcoin-cli I have no problems connecting to bitcoind. P2Pool only has 36 file descriptors open (10240 allowed).

Code:

2015-07-06 19:36:05.119752 > Unhandled Error
2015-07-06 19:36:05.119846 > Traceback (most recent call last):
2015-07-06 19:36:05.119973 > File "/home/p2pool/p2pool/p2pool/main.py", line 666, in run
2015-07-06 19:36:05.120065 > reactor.run()
2015-07-06 19:36:05.120160 > File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1169, in run
2015-07-06 19:36:05.120246 >
2015-07-06 19:36:05.120328 > File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1178, in mainLoop
2015-07-06 19:36:05.120427 >
2015-07-06 19:36:05.120511 > File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
2015-07-06 19:36:05.120597 >
2015-07-06 19:36:05.120687 > --- ---
2015-07-06 19:36:05.120773 > File "/home/p2pool/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 19:36:05.120858 > x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 19:36:05.120990 > File "/home/p2pool/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 19:36:05.121082 > raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 19:36:05.121180 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind

EDIT: bitcoind 0.10.2 debug.log shows nothing unusual.

Give it some time, it will stabilize. My node timed out a few more times after I updated, then settled down and hasn't all day. The version 13 peers are creating an issue with the entire pools network, causing higher than normal traffic rates and timeouts.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Hmmm.......has anyone made contact with forrestv? It would be good to get his take of what's happening........

nonnakip

hero member

Activity: 633

Merit: 591

NastyPool is running latest (14.0-6-g18b5ad5) and I also see large "LOST CONTACT WITH BITCOIND" blocks. I typed a rather large report of what I could find. But then I check the log again and it is happening right now! When I run bitcoin-cli I have no problems connecting to bitcoind. P2Pool only has 36 file descriptors open (10240 allowed).

Code:

2015-07-06 19:36:05.119752 > Unhandled Error
2015-07-06 19:36:05.119846 > Traceback (most recent call last):
2015-07-06 19:36:05.119973 >   File "/home/p2pool/p2pool/p2pool/main.py", line 666, in run
2015-07-06 19:36:05.120065 >     reactor.run()
2015-07-06 19:36:05.120160 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1169, in run
2015-07-06 19:36:05.120246 >     
2015-07-06 19:36:05.120328 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1178, in mainLoop
2015-07-06 19:36:05.120427 >     
2015-07-06 19:36:05.120511 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 800, in runUntilCurrent
2015-07-06 19:36:05.120597 >     
2015-07-06 19:36:05.120687 > ---  ---
2015-07-06 19:36:05.120773 >   File "/home/p2pool/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 19:36:05.120858 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 19:36:05.120990 >   File "/home/p2pool/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 19:36:05.121082 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 19:36:05.121180 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind

EDIT: bitcoind 0.10.2 debug.log shows nothing unusual.

Meuh6879

legendary

Activity: 1512

Merit: 1012

Well, we have a "massive blacklist" of 0.9.4 and less ... now.

Here is a debug.log of the 0.11.0 RC3.

perhaps, it's liked to the network activity (overhead !)

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Yeah, frustrating isn't it? Cheesy

I'm seeing some huge cpu usage by both bitcoind & p2pool - over 80% sometimes, my latency has also gone through the roof, even after restarting.

Is that plonker doing another "stress test" again? Cheesy

Edit:

OK, this is getting silly. 99% cpu, & often. Cheesy

:

Never seen it jumping up to these levels before - I'm beginning to think that the problem is not with p2pool or bitcoind, but with the network itself. I'm seeing some crazy amounts of traffic with super high latency, it seems to be working my node to death despite limiting connections, disabling the relaynetworkclient, prioritizing python & bitcoind, QOS & every other trick I can think of.......

I can see by the total p2pool hash rate & the opinions of others in other threads that something is wrong somewhere, but I'm buggered if I know what it is. I'm open to any & all suggestions people.......just hoping it's not the "usual suspects" again, messing with their pools code & screwing up the network somehow........ Sad

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

Quote from: p3yot33at3r on July 06, 2015, 11:32:10 AM

I've not had any issues with the NMC client (using latest namecore), only the bitcoind problem. The pool hash rate has dropped massively - there's obviously a stability problem somewhere - but I haven't seen another disconnect since disabling the relayclient.......yet Wink

This forum constantly dropping isn't helping much either Tongue

LOL... typing a reply, hitting submit only to see, "Bad Gateway" or some other error is a pain

.

I've still got the relay client running and not experiencing any issues with it... at least as far as I can tell. Node seems to have stabilized for the time being, so not sure what was going on earlier...

p3yot33at3r

sr. member

Activity: 266

Merit: 250

I've not had any issues with the NMC client (using latest namecore), only the bitcoind problem. The pool hash rate has dropped massively - there's obviously a stability problem somewhere - but I haven't seen another disconnect since disabling the relayclient.......yet Wink

This forum constantly dropping isn't helping much either Tongue

jonnybravo0311

legendary

Activity: 1344

Merit: 1024

Mine at Jonny's Pool

I just started noticing this behavior on my node as well. I was about to reply that I wasn't seeing it, then as soon as I started typing I got the "lost contact with bitcoind" errors flying through my p2pool logs. Also, I'm noticing the same with the auxblock calls for NMC merge mining. Not sure what's going on here.

Log snippet from NMC error:

Code:

2015-07-06 12:22:36.459226 > Error while calling merged getauxblock on http://127.0.0.1:7333:
2015-07-06 12:22:36.459364 > Traceback (most recent call last):
2015-07-06 12:22:36.459425 > Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:7333 took longer than 5 seconds.

Log snippet showing lost contact with bitcoind:

Code:

2015-07-06 12:23:39.257837 Error when requesting noncached value:
2015-07-06 12:23:39.258283 > Traceback (most recent call last):
2015-07-06 12:23:39.258417 > Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:8332/ took longer than 30 seconds.
2015-07-06 12:23:39.258510 
2015-07-06 12:23:39.259131 > Error getting work from bitcoind:
2015-07-06 12:23:39.259212 > Traceback (most recent call last):
2015-07-06 12:23:39.259269 > Failure: twisted.internet.defer.TimeoutError: Getting http://127.0.0.1:8332/ took longer than 30 seconds.
2015-07-06 12:23:39.438495 P2Pool: 17354 shares in chain (17358 verified/17358 total) Peers: 11 (7 incoming)
2015-07-06 12:23:39.438650  Local: 760GH/s in last 10.0 minutes Local dead on arrival: ~3.3% (2-6%) Expected time to share: 6.7 hours
2015-07-06 12:23:39.438709  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~117.5% (24-118%) Current payout: (0.0000)=0.0000 BTC
2015-07-06 12:23:39.438780  Pool: 997TH/s Stale rate: 14.9% Expected time to block: 2.5 days
2015-07-06 12:23:40.143664 Lost peer 101.100.174.138:46941 - Connection was aborted locally, using.
2015-07-06 12:23:40.342505 New work for worker! Difficulty: 419.298668 Share difficulty: 5782371.706794 Total block value: 25.630668 BTC including 2714 transactions
2015-07-06 12:23:51.731872 Peer sent entire transaction 02c8b5f4fb93ccb26cfde2d76c857f2915b42341bee558c2f5743442c51c9163 that was already received
2015-07-06 12:23:51.762187 Peer sent entire transaction 3a4e6b7d4c33c6a5b3622ce072806806bbba6fb244d6a1da390384b39da5b842 that was already received
2015-07-06 12:23:51.864129 Peer sent entire transaction 02c8b5f4fb93ccb26cfde2d76c857f2915b42341bee558c2f5743442c51c9163 that was already received
2015-07-06 12:23:52.317146 > ########################################
2015-07-06 12:23:52.317516 > >>> Warning: LOST CONTACT WITH BITCOIND for 1.2 minutes! Check that it isn't frozen or dead!
2015-07-06 12:23:52.317690 > ########################################
2015-07-06 12:23:52.317892 P2Pool: 17354 shares in chain (17358 verified/17358 total) Peers: 10 (6 incoming)
2015-07-06 12:23:52.318044  Local: 567GH/s in last 10.0 minutes Local dead on arrival: ~1.4% (0-3%) Expected time to share: 9.0 hours
2015-07-06 12:23:52.318190  Shares: 1 (0 orphan, 0 dead) Stale rate: ~0.0% (0-80%) Efficiency: ~117.5% (24-118%) Current payout: (0.0000)=0.0000 BTC
2015-07-06 12:23:52.318347  Pool: 997TH/s Stale rate: 14.9% Expected time to block: 2.5 days
2015-07-06 12:23:52.984908 > Unhandled Error
2015-07-06 12:23:52.985308 > Traceback (most recent call last):
2015-07-06 12:23:52.985485 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:52.985652 >     reactor.run()
2015-07-06 12:23:52.985854 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:52.986325 >     self.mainLoop()
2015-07-06 12:23:52.986489 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:52.986682 >     self.runUntilCurrent()
2015-07-06 12:23:52.986848 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:52.987004 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:52.987165 > ---  ---
2015-07-06 12:23:52.987294 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:52.987489 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:52.987621 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:52.987745 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:52.987868 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:23:52.988240 > Unhandled Error
2015-07-06 12:23:52.988373 > Traceback (most recent call last):
2015-07-06 12:23:52.988495 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:52.988683 >     reactor.run()
2015-07-06 12:23:52.988807 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:52.988934 >     self.mainLoop()
2015-07-06 12:23:52.989056 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:52.989191 >     self.runUntilCurrent()
2015-07-06 12:23:52.989313 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:52.989436 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:52.989556 > ---  ---
2015-07-06 12:23:52.989677 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:52.989909 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:52.990046 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:52.990170 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:52.990291 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:23:53.006595 > Unhandled Error
2015-07-06 12:23:53.006974 > Traceback (most recent call last):
2015-07-06 12:23:53.007146 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:53.007307 >     reactor.run()
2015-07-06 12:23:53.007470 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:53.007627 >     self.mainLoop()
2015-07-06 12:23:53.007789 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:53.007917 >     self.runUntilCurrent()
2015-07-06 12:23:53.008041 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:53.008164 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:53.008285 > ---  ---
2015-07-06 12:23:53.008506 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:53.008669 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:53.008810 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:53.008946 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:53.009139 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:23:53.010013 > Unhandled Error
2015-07-06 12:23:53.010236 > Traceback (most recent call last):
2015-07-06 12:23:53.010424 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:53.010634 >     reactor.run()
2015-07-06 12:23:53.010839 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:53.011032 >     self.mainLoop()
2015-07-06 12:23:53.011250 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:53.011415 >     self.runUntilCurrent()
2015-07-06 12:23:53.011552 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:53.011737 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:53.011883 > ---  ---
2015-07-06 12:23:53.012011 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:53.012178 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:53.012357 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:53.012494 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:53.012620 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:23:53.013144 > Unhandled Error
2015-07-06 12:23:53.013335 > Traceback (most recent call last):
2015-07-06 12:23:53.013467 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:53.013593 >     reactor.run()
2015-07-06 12:23:53.013717 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:53.013888 >     self.mainLoop()
2015-07-06 12:23:53.014024 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:53.014147 >     self.runUntilCurrent()
2015-07-06 12:23:53.014269 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:53.014391 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:53.014510 > ---  ---
2015-07-06 12:23:53.014674 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:53.014830 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:53.014958 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:53.015087 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:53.015217 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:23:53.015589 > Unhandled Error
2015-07-06 12:23:53.015722 > Traceback (most recent call last):
2015-07-06 12:23:53.015844 >   File "/home/miner/p2pool/p2pool/main.py", line 666, in run
2015-07-06 12:23:53.015966 >     reactor.run()
2015-07-06 12:23:53.016095 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1192, in run
2015-07-06 12:23:53.016222 >     self.mainLoop()
2015-07-06 12:23:53.016342 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 1201, in mainLoop
2015-07-06 12:23:53.016463 >     self.runUntilCurrent()
2015-07-06 12:23:53.016583 >   File "/usr/lib/python2.7/dist-packages/twisted/internet/base.py", line 824, in runUntilCurrent
2015-07-06 12:23:53.016713 >     call.func(*call.args, **call.kw)
2015-07-06 12:23:53.016849 > ---  ---
2015-07-06 12:23:53.016969 >   File "/home/miner/p2pool/p2pool/bitcoin/stratum.py", line 38, in _send_work
2015-07-06 12:23:53.017090 >     x, got_response = self.wb.get_work(*self.wb.preprocess_request('' if self.username is None else self.username))
2015-07-06 12:23:53.017254 >   File "/home/miner/p2pool/p2pool/work.py", line 211, in preprocess_request
2015-07-06 12:23:53.017387 >     raise jsonrpc.Error_for_code(-12345)(u'lost contact with bitcoind')
2015-07-06 12:23:53.017510 > p2pool.util.jsonrpc.NarrowError: -12345 lost contact with bitcoind
2015-07-06 12:24:06.272733 > Peer referenced unknown transaction 61cbf98adbeb8f843ed300add451e33643109e7ad9097e12872a066b4c55400c, disconnecting

EDIT: it's definitely an intermittent thing... because now my node is back to running smoothly again.

p3yot33at3r

sr. member

Activity: 266

Merit: 250

Quote from: Duce on July 06, 2015, 11:07:54 AM

Quote from: p3yot33at3r on July 06, 2015, 11:01:27 AM

Has anyone else started getting bitcoind disconnects since upgrading to the latest version?

Yes, and I went from 10.1 to 10.2 to ensure it was not a Bitcoind version issue. I will not be able to update my node until later today though to see if this solves this issue as well. I hope it does.

Right. I also just noticed the eu relaynetwork was down - so I've disabled it (the latest version didn't work on 14.04 anyway) just in case that had something to do with it.

Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 165. (Read 2591920 times)