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

[cabin]

I'm rebuilding my p2pool node due to a hardware failure.

Running the latest version as of 15 minutes ago from the GIT and I get the following:

Code:

2012-11-30 08:31:34.376732 > Traceback (most recent call last):
2012-11-30 08:31:34.377251 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:34.378040 Requesting parent share b68a0d0b from 75.12.89.18:9333

Not sure if it's worth worrying about or not but posting just in case.

I got this too on a fresh install and fresh git this morning. Did it eventually get all the shares and recover? I'm still getting them after 10 minutes.

I ended up shutting down the pool, waiting about 15 minutes and starting up again.  The message hasn't come back yet and it's been running for almost 2 days now.

Thanks, I had to restart it a few times too.. it seemed to get stuck. But since it got caught up after a couple tries it has been ok for me too. I get a lot of these now.. but I suspect it is just debugging info:

2012-12-01 22:49:14.333000 Peer sent entire transaction 540cdec5afb26f13cc23d20672b54958caae00a826a2330e67e5dc0a68abedc7 that was already received

[tiberiandusk]

Changed my password and it's working again. My old password didn't have any symbols in it and worked fine up until last week. I'm still getting a lot of DefaultException sharereply too long errors.

[forrestv]

Changed my password and it's working again. My old password didn't have any symbols in it and worked fine up until last week. I'm still getting a lot of DefaultException sharereply too long errors.

The sharereply bug should be fixed in git. I'll do another release soon if it's fixed.

[tiberiandusk]

Changed my password and it's working again. My old password didn't have any symbols in it and worked fine up until last week. I'm still getting a lot of DefaultException sharereply too long errors.

The sharereply bug should be fixed in git. I'll do another release soon if it's fixed.

Awesome. Thanks for the quick answer.

[AV]

2012-12-02 17:12:50.987000 > in download_shares:
2012-12-02 17:12:50.988000 > Traceback (most recent call last):
2012-12-02 17:12:50.988000 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-12-02 17:12:50.988000 Requesting parent share f024bcd1 from 24.108.77.4:9333
2012-12-02 17:12:53.795000 > in download_shares:
2012-12-02 17:12:53.795000 > Traceback (most recent call last):
2012-12-02 17:12:53.795000 > Failure: twisted.python.failure.DefaultException: sharereply result: too long

Always...

[forrestv]

P2Pool release 9.3 tag: 9.3 hash: f4a7b14a1314e0ada29b8a6d5fb9e2e52bb4dfe8

Windows binary: http://u.forre.st/u/asugseew/p2pool_win32_9.3.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.3
Source tarball: https://github.com/forrestv/p2pool/tarball/9.3

Changes:
* Fixes "sharereply too long" bug

[BR0KK]

nice i'll upgrade immediately

[rav3n_pl]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

[K1773R]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

Shares: 27 (0 orphan, 0 dead) Stale rate: ~0.0% (0-66%) Efficiency: ~124.7% (42-125%)

[cabin]

I just tried newest version from git overnight. And I have to admit, p2pool is still unusable for me. On my machine with 1GB RAM, p2pool is consuming 523 MB RAM (1002 MB virtual). I have some other processes running on my Debian machine and I cannot give away half of my RAM to p2pool, because of very high swapfile usage. Before v9 it was much lower and p2pool was running absolutely fine. I have to shutdown my node.

After the share reply problems (which were just fixed today) my memory did drop back down a bit, to around 350MB. Network usage does seem to be higher than before though. Not sure of that is low enough to stop the swapping though.

[ninjaboon]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

upgrading from 9.1 to 9.3 now...

[rav3n_pl]

Pool wide DOA drop under 5% but orphan rate in same time around 20%? See hourly stats now. Odd.

[PatMan]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

I'm seeing a pool stale rate of 24% still....

[rav3n_pl]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

I'm seeing a pool stale rate of 24% still....

Code:

Pool rate: 422GH/s (19% stale) Share difficulty: 740

but see hourly graphs:
DOA:7,5%
orphan: 12%
So sum will be 19%
I think this "stale" text should be changed to "DOA+orphan"

[PatMan]

Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade

I'm seeing a pool stale rate of 24% still....

Code:

Pool rate: 422GH/s (19% stale) Share difficulty: 740

but see hourly graphs:
DOA:7,5%
orphan: 12%
So sum will be 19%
I think this "stale" text should be changed to "DOA+orphan"

Yup, that would make sense.

[rav3n_pl]

Pull request sent... ;]

[PatMan]

Pull request sent... ;]

It would be nice if there were two different texts, one for each. It would defo help noobs like me out....lol

[TAiS46]

will there ever be a BFL single support?

[eleuthria]

will there ever be a BFL single support?

You'd have to ask BFL that.  They're the ones who made a poorly designed FPGA that doesn't report back solves until the nonce range is exhausted, and can't be interrupted while doing so.

[TAiS46]

but all other pools are working with bfl singles?