Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 521. (Read 2591928 times)
The latest P2Pool commit fixes the LateEnd error with newer versions of Bitcoin.
Thank you for the pointers!
I actually had read those guides, but I think I feel victim to pre-mature optimization and applying without testing. Particularly in light of gyverlb's advice linked by GrapeApe which describes actually methodically testing and measuring the results of tuning to see what's working (sacrilege!). So... I disabled all the tweaks for now in bitcoin.conf and restarted bitcoind... But it turns out there was also a second "mistake" I made.
After restarting bitcoind without tweaks, getblocktemplate latency started out low but then would gradually and steadily build up to ~2sec(!) over the course of 30 minutes! So I decided to open 8333 for bitcoind to maybe get more connections. That didn't do much, either... That's when I noticed that I had been too clever and set "ufw limit" on the bitcoind and p2pool ports (linux kernel firewall rate limiting). When I deleted those rules and replaced them with the corresponding "ufw allow" unlimited rules my rate dropped considerably and seems to have stayed low over night (0.1-0.3s for the last six hours). So, I'll now work on tweaking more methodically.
Thanks for getting me pointed in the right direction!
I actually had read those guides, but I think I feel victim to pre-mature optimization and applying without testing. Particularly in light of gyverlb's advice linked by GrapeApe which describes actually methodically testing and measuring the results of tuning to see what's working (sacrilege!). So... I disabled all the tweaks for now in bitcoin.conf and restarted bitcoind... But it turns out there was also a second "mistake" I made.
After restarting bitcoind without tweaks, getblocktemplate latency started out low but then would gradually and steadily build up to ~2sec(!) over the course of 30 minutes! So I decided to open 8333 for bitcoind to maybe get more connections. That didn't do much, either... That's when I noticed that I had been too clever and set "ufw limit" on the bitcoind and p2pool ports (linux kernel firewall rate limiting). When I deleted those rules and replaced them with the corresponding "ufw allow" unlimited rules my rate dropped considerably and seems to have stayed low over night (0.1-0.3s for the last six hours). So, I'll now work on tweaking more methodically.
Thanks for getting me pointed in the right direction!
1. Try the guide posted above.
2. If you can't get your latency down, mine with a public node.
3. If you want to mine with a public node, and also want to reduce variance, give this a try: https://bitcointalksearch.org/topic/poolyrralnet-p2pool-backed-mining-pool-alpha-234841
2. If you can't get your latency down, mine with a public node.
3. If you want to mine with a public node, and also want to reduce variance, give this a try: https://bitcointalksearch.org/topic/poolyrralnet-p2pool-backed-mining-pool-alpha-234841
s
No incoming peers is not a problem and 1 share instead of expected 3 is caused by variance. A real problem is 1s latency and 9% DOA. It will decrease your income by 9%. Still better than 12% pps fee taken by some pools though)
Hi, sorry if this is the wrong place to ask. I'm new to p2pool.
I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
No incoming peers is not a problem and 1 share instead of expected 3 is caused by variance. A real problem is 1s latency and 9% DOA. It will decrease your income by 9%. Still better than 12% pps fee taken by some pools though)
Hi, sorry if this is the wrong place to ask. I'm new to p2pool.
I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
1 share in 15 hrs is rough but plausible. The thing that stands out to me would be the local 9.3% DOA. If you haven’t adjusted the difficulty level that seems high. As far as 0 incoming, they should start trickling in but you need to open port 9332 and 9333. I will tell you to read the guide gyverlb has posted at I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
https://bitcointalksearch.org/topic/m.1626156
edit: Yes 11.4 is the version you want yours just says unknown because you don't have it stored as a local git repository.
edit2: I didn’t see the 1s latency until the poster below mentioned it. Start here https://bitcointalksearch.org/topic/m.2256552 so you can get an idea of how to tune bitcoin (controversial subject). Also the guide I mentioned above covers this.
Hi, sorry if this is the wrong place to ask. I'm new to p2pool.
I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
I've got it setup and running (debian) and I just want to make sure things are looking OK. I have 330MH/s (AM USB eruptor). I've been running p2pool for 15 hrs, expected shares are ~5hrs, but I've only found 1 share. Is that something to be concerned about yet? Or is this amount of variance normal and I should sit tight? I don't have an issue letting it run longer waiting, but if it's already apparent that my setup is doing something wrong, that would be good to know if I need to roll my sleeves up. My getwork latency is ~1s. I apparently got 1 share so something is working...
Version: unknown 7032706f6f6c
Pool rate: 621GH/s (20% DOA+orphan) Share difficulty: 1190
Node uptime: 0.620 days Peers: 7 out, 0 in
Local rate: 308MH/s (9.3% DOA) Expected time to share: 4.60 hours
Shares: 1 total (0 orphaned, 0 dead) Efficiency: 124.7%
Payout if a block were found NOW: 0.00262778 BTC to xxx. Expected after mining for 24 hours: 0.0124 BTC per block.
Current block value: 25.28591 BTC Expected time to block: 37.2 hours
Also, I'm running the 11.4 release--is that recommended or do most people run the master branch from github?
Is peers in at 0 a problem? I can telnet to port 9333 from remote. Do I need more open ports?
Since newest bitcoind from git, I have errors on p2pool log:
Code:
2013-06-26 12:55:39.944779 p2pool (version 11.4-2-gf78a4e8)
2013-06-26 12:55:39.944959
2013-06-26 12:55:39.945105 Testing bitcoind RPC connection to 'http://127.0.0.1:8332/' with username 'bitcoinrpc'...
2013-06-26 12:55:40.068128 ...success!
2013-06-26 12:55:40.068220 Current block hash: d4710b27427c1d534bc78dac1c6863f3ebd04a55694b0ae4e8
2013-06-26 12:55:40.068277 Current block height: 243425
2013-06-26 12:55:40.068311
2013-06-26 12:55:40.068352 Testing bitcoind P2P connection to '127.0.0.1:8333'...
2013-06-26 12:55:40.100509 RECV version 71110100010000000000000039d6ca5100000000010000000000000000000000000000000000ffff000000000000010000000000000000000000000000000000ffff5869ab4b208dc9c543861df6eccf102f5361746f7368693a302e382e39392fe1b603...
2013-06-26 12:55:40.102466 > Error handling message: (see RECV line)
2013-06-26 12:55:40.102579 > Traceback (most recent call last):
2013-06-26 12:55:40.102732 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 215, in doRead
2013-06-26 12:55:40.102819 > return self._dataReceived(data)
2013-06-26 12:55:40.102904 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 221, in _dataReceived
2013-06-26 12:55:40.102984 > rval = self.protocol.dataReceived(data)
2013-06-26 12:55:40.103056 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 26, in dataReceived
2013-06-26 12:55:40.103129 > self.dataReceived2(data)
2013-06-26 12:55:40.103220 > File "/home/pioruns/p2pool/p2pool/util/datachunker.py", line 40, in _DataChunker
2013-06-26 12:55:40.103292 > wants = receiver.send(buf.get(wants))
2013-06-26 12:55:40.103362 > ------
2013-06-26 12:55:40.103448 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 54, in dataReceiver
2013-06-26 12:55:40.103536 > self.packetReceived(command, type_.unpack(payload))
2013-06-26 12:55:40.103624 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 63, in unpack
2013-06-26 12:55:40.103718 > obj = self._unpack(data)
2013-06-26 12:55:40.103821 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 47, in _unpack
2013-06-26 12:55:40.103912 > raise LateEnd()
2013-06-26 12:55:40.104000 > p2pool.util.pack.LateEnd:
2013-06-26 12:55:40.104559 ...success!
2013-06-26 12:55:40.104644
2013-06-26 12:55:40.104760 Determining payout address...
2013-06-26 12:55:40.105005 ...success! Payout address: 1Lenny8KpVhqKvxwQFdYh7UZ6LFF4atY6z
2013-06-26 12:55:40.105087
2013-06-26 12:55:40.105247 Loading shares...
2013-06-26 12:55:42.221859 1000
2013-06-26 12:55:44.645612 2000
2013-06-26 12:55:47.023718 3000
2013-06-26 12:55:48.818631 4000
2013-06-26 12:55:50.557296 5000
2013-06-26 12:55:52.394567 6000
2013-06-26 12:55:54.305045 7000
2013-06-26 12:55:56.497315 8000
2013-06-26 12:55:58.507793 9000
2013-06-26 12:56:00.165688 10000
2013-06-26 12:56:02.333371 11000
2013-06-26 12:56:04.012640 12000
2013-06-26 12:56:05.586501 13000
2013-06-26 12:56:07.423243 14000
2013-06-26 12:56:09.057284 15000
2013-06-26 12:56:10.626802 16000
2013-06-26 12:56:12.608668 17000
2013-06-26 12:56:14.359926 18000
2013-06-26 12:56:16.323359 19000
2013-06-26 12:56:17.903745 20000
2013-06-26 12:56:19.619935 21000
2013-06-26 12:56:19.794666 ...done loading 21090 shares (12454 verified)!
2013-06-26 12:56:19.794790
2013-06-26 12:56:19.794824 Initializing work...
2013-06-26 12:56:23.137975 ...success!
2013-06-26 12:56:23.138095
2013-06-26 12:56:23.138131 Joining p2pool network using port 9333...
2013-06-26 12:56:23.235745 RECV version 71110100010000000000000064d6ca5100000000010000000000000000000000000000000000ffff000000000000010000000000000000000000000000000000ffff5869ab4b208db68c30145ddbb828102f5361746f7368693a302e382e39392fe1b603...
2013-06-26 12:56:23.236284 > Error handling message: (see RECV line)
2013-06-26 12:56:23.236346 > Traceback (most recent call last):
2013-06-26 12:56:23.236385 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 215, in doRead
2013-06-26 12:56:23.236423 > return self._dataReceived(data)
2013-06-26 12:56:23.236459 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 221, in _dataReceived
2013-06-26 12:56:23.236495 > rval = self.protocol.dataReceived(data)
2013-06-26 12:56:23.236530 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 26, in dataReceived
2013-06-26 12:56:23.236566 > self.dataReceived2(data)
2013-06-26 12:56:23.236600 > File "/home/pioruns/p2pool/p2pool/util/datachunker.py", line 40, in _DataChunker
2013-06-26 12:56:23.236634 > wants = receiver.send(buf.get(wants))
2013-06-26 12:56:23.236667 > ------
2013-06-26 12:56:23.236700 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 54, in dataReceiver
2013-06-26 12:56:23.236736 > self.packetReceived(command, type_.unpack(payload))
2013-06-26 12:56:23.236769 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 63, in unpack
2013-06-26 12:56:23.236803 > obj = self._unpack(data)
2013-06-26 12:56:23.236836 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 47, in _unpack
2013-06-26 12:56:23.236870 > raise LateEnd()
2013-06-26 12:56:23.236904 > p2pool.util.pack.LateEnd:
2013-06-26 12:56:24.239385 RECV version 71110100010000000000000065d6ca5100000000010000000000000000000000000000000000ffff000000000000010000000000000000000000000000000000ffff5869ab4b208da170ba2446ed6ec1102f5361746f7368693a302e382e39392fe1b603...
2013-06-26 12:56:24.239831 > Error handling message: (see RECV line)
2013-06-26 12:56:24.239895 > Traceback (most recent call last):
2013-06-26 12:56:24.239951 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 215, in doRead
2013-06-26 12:56:24.240026 > return self._dataReceived(data)
2013-06-26 12:56:24.240080 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 221, in _dataReceived
2013-06-26 12:56:24.240138 > rval = self.protocol.dataReceived(data)
2013-06-26 12:56:24.240190 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 26, in dataReceived
2013-06-26 12:56:24.240245 > self.dataReceived2(data)
2013-06-26 12:56:24.240297 > File "/home/pioruns/p2pool/p2pool/util/datachunker.py", line 40, in _DataChunker
2013-06-26 12:56:24.240351 > wants = receiver.send(buf.get(wants))
2013-06-26 12:56:24.240402 > ------
2013-06-26 12:56:24.240452 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 54, in dataReceiver
2013-06-26 12:56:24.240506 > self.packetReceived(command, type_.unpack(payload))
2013-06-26 12:56:24.240558 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 63, in unpack
2013-06-26 12:56:24.240611 > obj = self._unpack(data)
2013-06-26 12:56:24.240662 > File "/home/pioruns/p2pool/p2pool/util/pack.py", line 47, in _unpack
2013-06-26 12:56:24.240716 > raise LateEnd()
2013-06-26 12:56:24.240766 > p2pool.util.pack.LateEnd:
2013-06-26 12:56:25.448685 RECV version 71110100010000000000000066d6ca5100000000010000000000000000000000000000000000ffff000000000000010000000000000000000000000000000000ffff5869ab4b208dcd1f4482073bdb78102f5361746f7368693a302e382e39392fe1b603...
2013-06-26 12:56:25.449088 > Error handling message: (see RECV line)
2013-06-26 12:56:25.449150 > Traceback (most recent call last):
2013-06-26 12:56:25.449207 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 215, in doRead
2013-06-26 12:56:25.449264 > return self._dataReceived(data)
2013-06-26 12:56:25.449318 > File "/usr/local/lib/python2.7/dist-packages/Twisted-13.0.0-py2.7-linux-x86_64.egg/twisted/internet/tcp.py", line 221, in _dataReceived
2013-06-26 12:56:25.449375 > rval = self.protocol.dataReceived(data)
2013-06-26 12:56:25.449428 > File "/home/pioruns/p2pool/p2pool/util/p2protocol.py", line 26, in dataReceived
2013-06-26 12:56:25.449491 > self.dataReceived2(data)
Code:
Linux 3.2.0-4-amd64 x86_64 GNU/Linux
Description: Debian GNU/Linux 7.1 (wheezy)
Python 2.7.3
Current p2pool version: 11.4-2-gf78a4e8
Code:
Current version: Bitcoin version v0.8.2-151-g4ad73c6-beta
commit 4ad73c6b080c46808b0c53b62ab6e4074e48dc75
so what the 8.3 does? i can't find the official topic, like the 8.2
http://bitcoin.org/en/release/v0.8.3
M
A couple of fixes.
https://bitcointalksearch.org/topic/bitcoin-qt-bitcoind-version-083-released-242848
so what the 8.3 does? i can't find the official topic, like the 8.2
http://bitcoin.org/en/release/v0.8.3
M
ok, seriously:
(...)
is this a bug?
Looks like your bitcoind is behind. (...)
is this a bug?
Your p2pool node know about new block but daemon still not got it.
Thats why you "jumping from...to..." and probably thats why your shares are orphaned when you jumping.
What would cause bitcoind to be behind p2pool? Could this be a result of limiting bitcoind connections?
zvs insists on having very large numbers of connections for both p2pool and bitcoind so it can't be it. In fact it could be the opposite if he hits another process latency problem by having more work to do broadcasting transactions, shares and blocks.
Edit: zvs often reacts on very small data samples, his configuration is interesting to study but I usually don't consider his early results to form an opinion as they are still within normal statistical error margin (the last I read was 2 orphans out of 8 shares for example).
so what the 8.3 does? i can't find the official topic, like the 8.2
ok, seriously:
(...)
is this a bug?
Looks like your bitcoind is behind. (...)
is this a bug?
Your p2pool node know about new block but daemon still not got it.
Thats why you "jumping from...to..." and probably thats why your shares are orphaned when you jumping.
What would cause bitcoind to be behind p2pool? Could this be a result of limiting bitcoind connections?
ok, seriously:
(...)
is this a bug?
Looks like your bitcoind is behind. (...)
is this a bug?
Your p2pool node know about new block but daemon still not got it.
Thats why you "jumping from...to..." and probably thats why your shares are orphaned when you jumping.
https://forum.litecoin.net/index.php/topic,4615.msg33811.html#msg33811
Read details of DoS attacks on the Litecoin network that has been going on since at least Friday, June 21st but stopped by Litecoin 0.6.9.2. Before the supernodes were patched it appears the attack was the cause for the spike in GBT latency experienced by p2pool LTC nodes. Individual nodes are still vulnerable to memory exhaustion DoS attack. Please upgrade to 0.6.9.2 ASAP to protect your node and the network.
Please follow the Litecoin Project on Google+ for the latest development news. We post stuff very often!
Read details of DoS attacks on the Litecoin network that has been going on since at least Friday, June 21st but stopped by Litecoin 0.6.9.2. Before the supernodes were patched it appears the attack was the cause for the spike in GBT latency experienced by p2pool LTC nodes. Individual nodes are still vulnerable to memory exhaustion DoS attack. Please upgrade to 0.6.9.2 ASAP to protect your node and the network.
Please follow the Litecoin Project on Google+ for the latest development news. We post stuff very often!
is this a bug?
Are the problems still being caused by the same payout address as posted earlier? If so regardless of how long they’ve been mining someone should say something, if I remember correctly you said 50% of them were linked uuhh submitted (lack of a better word) to his slow node.
Jump to: