Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade
Upgrade
I'm seeing a pool stale rate of 24% still....
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 611. (Read 2591920 times)
December 03, 2012, 10:54:23 AM
I'm seeing a pool stale rate of 24% still....
December 03, 2012, 10:53:32 AM
Pool wide DOA drop under 5% but orphan rate in same time around 20%? See hourly stats now. Odd.
December 02, 2012, 11:59:42 PM
Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade
Upgrade
upgrading from 9.1 to 9.3 now...
December 02, 2012, 08:57:52 PM
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.
December 02, 2012, 05: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%) Upgrade
December 02, 2012, 05:46:59 PM
Pool wide DOA drop under 10%, looks like all troubles are gone.
Upgrade
Upgrade
December 02, 2012, 02:54:24 PM
nice i'll upgrade immediately
December 02, 2012, 01:08:46 PM
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
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
December 02, 2012, 08:16:40 AM
Quote
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
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...
December 02, 2012, 05: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.
December 02, 2012, 01: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.
December 02, 2012, 01: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.
December 01, 2012, 10:50:56 PM
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:
Not sure if it's worth worrying about or not but posting just in case.
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
December 01, 2012, 08:28:21 PM
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:
Not sure if it's worth worrying about or not but posting just in case.
Running the latest version as of 15 minutes ago from the GIT and I get the following:
Code:
2012-11-30 08:31:23.335637 > Traceback (most recent call last):
2012-11-30 08:31:23.336126 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:23.336928 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:25.159341 > in download_shares:
2012-11-30 08:31:25.159967 > Traceback (most recent call last):
2012-11-30 08:31:25.160453 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:25.161314 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:28.133602 > in download_shares:
2012-11-30 08:31:28.134254 > Traceback (most recent call last):
2012-11-30 08:31:28.134743 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:28.135574 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:28.166702 P2Pool: 0 shares in chain (0 verified/4565 total) Peers: 6 (0 incoming)
2012-11-30 08:31:28.167326 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2012-11-30 08:31:30.027398 > in download_shares:
2012-11-30 08:31:30.028164 > Traceback (most recent call last):
2012-11-30 08:31:30.028618 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:30.029446 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:31.816948 > in download_shares:
2012-11-30 08:31:31.817605 > Traceback (most recent call last):
2012-11-30 08:31:31.818093 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:31.818912 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:34.376080 > in download_shares:
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.
December 01, 2012, 05:36:28 PM
Oh? That's news. I've have symbols in my password & don't get any such errors....
I have not had time to understand what symbol brings problems. I just left the only letters and numbers, and the problem went away.
Yeah, I know some symbols can cause problems, but I like to use them when I can as an extra security layer.
I've noticed a steady lowering of the stale rate of late, as well as a lowering of users of the pool. Is there a general correlation with regards users v stales - or has Forrestv been doing some expert tweaking?
December 01, 2012, 01:18:38 PM
Oh? That's news. I've have symbols in my password & don't get any such errors....
I have not had time to understand what symbol brings problems. I just left the only letters and numbers, and the problem went away.
December 01, 2012, 09:58:33 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:
Not sure if it's worth worrying about or not but posting just in case.
Running the latest version as of 15 minutes ago from the GIT and I get the following:
Code:
2012-11-30 08:31:23.335637 > Traceback (most recent call last):
2012-11-30 08:31:23.336126 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:23.336928 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:25.159341 > in download_shares:
2012-11-30 08:31:25.159967 > Traceback (most recent call last):
2012-11-30 08:31:25.160453 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:25.161314 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:28.133602 > in download_shares:
2012-11-30 08:31:28.134254 > Traceback (most recent call last):
2012-11-30 08:31:28.134743 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:28.135574 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:28.166702 P2Pool: 0 shares in chain (0 verified/4565 total) Peers: 6 (0 incoming)
2012-11-30 08:31:28.167326 Local: 0H/s in last 0.0 seconds Local dead on arrival: ??? Expected time to share: ???
2012-11-30 08:31:30.027398 > in download_shares:
2012-11-30 08:31:30.028164 > Traceback (most recent call last):
2012-11-30 08:31:30.028618 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:30.029446 Requesting parent share b68a0d0b from 173.11.125.162:9333
2012-11-30 08:31:31.816948 > in download_shares:
2012-11-30 08:31:31.817605 > Traceback (most recent call last):
2012-11-30 08:31:31.818093 > Failure: twisted.python.failure.DefaultException: sharereply result: too long
2012-11-30 08:31:31.818912 Requesting parent share b68a0d0b from 83.161.255.174:9333
2012-11-30 08:31:34.376080 > in download_shares:
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.
December 01, 2012, 06:40:15 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.
December 01, 2012, 05:46:21 AM
I was in this boat. Password can`t contain any symbol. Try replace it. Use mixed-case letters and numbers.
Oh? That's news. I've have symbols in my password & don't get any such errors....
December 01, 2012, 02:58:35 AM
I was in this boat. Password can`t contain any symbol. Try replace it. Use mixed-case letters and numbers.
Jump to: