Re: [185 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

Whatever "magic" happened for you it didn't happen for me. I've had P2PoolExtendedFrontEnd installed for a while and still seeing these timeout errors.

2014-01-17 08:49:06.336406 > Unhandled error in Deferred:
2014-01-17 08:49:06.336631 > Unhandled Error
2014-01-17 08:49:06.336702 > Traceback (most recent call last):
2014-01-17 08:49:06.336760 > Failure: twisted.internet.defer.TimeoutError: in ReplyMatcher

What does "ReplyMatcher" do?

ReplyMatcher matches replies to messages sent to bitcoind with responses. It's only used for the get_block_header message, and this error means that bitcoind didn't reply ... either it timed out or bitcoind doesn't have the header in question. So it could suggest that your Bitcoin node is slow or not up-to-date.. but seeing these rarely is normal.

I'm seeing 2 or 3 of these timeouts a minute consistently. I assume that doesn't qualify as rarely.

I'm running Bitcoin-Qt (v0.8.6-beta I believe thats the latest, sum on mine and the latest download are same) and p2pool on a Mac Mini. 8333, 9333 and 9332 ports are forwarded. Miners are on a RaspberryPi running bfgminer. Network is WiFi. My GetBlockTemplate latency mean for the last hour is .197s.

Anything specific I should look at?

Thanks!

Quote from: PatMan on January 17, 2014, 08:26:21 PM

Your wifi......ditch it. Wink

Which link?

Miners to p2pool
bitcoind to world

I have run the miners locally on the Mac Mini and both bitcoind and p2pool, that did seem to make a difference on the timeouts.

From forrestv response, the ReplyMatcher timeouts are between bitcoind and p2pool. So WiFi should not effect, I guess.

My latency and efficiency seem within norms so may be the ReplyMatcher timeouts are just noise.