cabin
|
|
December 02, 2012, 03:50:56 AM |
|
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: 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
|
|
|
|
|
|
|
|
|
There are several different types of Bitcoin clients. The most secure are full nodes like Bitcoin Core, 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.
|
|
|
|
tiberiandusk
|
|
December 02, 2012, 06:00:04 AM |
|
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 (OP)
|
|
December 02, 2012, 06:12:10 AM |
|
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.
|
1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
|
|
|
tiberiandusk
|
|
December 02, 2012, 10:22:00 AM |
|
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
|
|
December 02, 2012, 01:16:40 PM |
|
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...
|
|
|
|
|
BR0KK
|
|
December 02, 2012, 07:54:24 PM |
|
nice i'll upgrade immediately
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 02, 2012, 10:46:59 PM |
|
Pool wide DOA drop under 10%, looks like all troubles are gone. Upgrade
|
|
|
|
K1773R
Legendary
Offline
Activity: 1792
Merit: 1008
/dev/null
|
|
December 02, 2012, 10:51:16 PM |
|
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%)
|
[GPG Public Key]BTC/DVC/TRC/FRC: 1 K1773RbXRZVRQSSXe9N6N2MUFERvrdu6y ANC/XPM A K1773RTmRKtvbKBCrUu95UQg5iegrqyeA NMC: N K1773Rzv8b4ugmCgX789PbjewA9fL9Dy1 LTC: L Ki773RBuPepQH8E6Zb1ponoCvgbU7hHmd EMC: E K1773RxUes1HX1YAGMZ1xVYBBRUCqfDoF BQC: b K1773R1APJz4yTgRkmdKQhjhiMyQpJgfN
|
|
|
cabin
|
|
December 03, 2012, 01:57:52 AM |
|
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
Legendary
Offline
Activity: 2114
Merit: 1002
|
|
December 03, 2012, 04:59:42 AM |
|
Pool wide DOA drop under 10%, looks like all troubles are gone. Upgrade upgrading from 9.1 to 9.3 now...
|
|
|
|
rav3n_pl
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 03, 2012, 03:53:32 PM |
|
Pool wide DOA drop under 5% but orphan rate in same time around 20%? See hourly stats now. Odd.
|
|
|
|
PatMan
|
|
December 03, 2012, 03:54:23 PM |
|
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
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 03, 2012, 06:16:11 PM |
|
Pool wide DOA drop under 10%, looks like all troubles are gone. Upgrade I'm seeing a pool stale rate of 24% still.... 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
|
|
December 03, 2012, 06:21:07 PM |
|
Pool wide DOA drop under 10%, looks like all troubles are gone. Upgrade I'm seeing a pool stale rate of 24% still.... 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
Legendary
Offline
Activity: 1361
Merit: 1003
Don`t panic! Organize!
|
|
December 03, 2012, 06:23:27 PM |
|
Pull request sent... ;]
|
|
|
|
PatMan
|
|
December 03, 2012, 06:55:12 PM |
|
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
|
|
December 03, 2012, 07:48:11 PM |
|
will there ever be a BFL single support?
|
|
|
|
eleuthria
Legendary
Offline
Activity: 1750
Merit: 1007
|
|
December 03, 2012, 07:51:02 PM |
|
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.
|
RIP BTC Guild, April 2011 - June 2015
|
|
|
TAiS46
|
|
December 03, 2012, 07:52:00 PM |
|
but all other pools are working with bfl singles?
|
|
|
|
|