Bitcoin Forum
December 04, 2016, 10:28:21 PM *
News: To be able to use the next phase of the beta forum software, please ensure that your email address is correct/functional.
 
   Home   Help Search Donate Login Register  
Pages: « 1 ... 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 [295] 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 ... 744 »
  Print  
Author Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool  (Read 2029609 times)
GrapeApe
Sr. Member
****
Offline Offline

Activity: 477



View Profile
June 26, 2013, 04:50:52 PM
 #5881

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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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


here too

I downloaded the .tar.gz from the direct link at the top of  page (below login) and compiled from source. When I started bitcoin and p2pool I had an error in the p2pool log saying ports 9333 and 9332 are not open (not true) so I restarted ubuntu and that went away, all is working smoothly ( IT Crowd have you tried turning it off and back on again ). I see your version output says 0.8.2 the latest is now is 0.8.3. I also pulled the latest commits from p2pool as well. Other than my measly 200MH/s not finding shares fast enough all is good.
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
1480890501
Hero Member
*
Offline Offline

Posts: 1480890501

View Profile Personal Message (Offline)

Ignore
1480890501
Reply with quote  #2

1480890501
Report to moderator
GrapeApe
Sr. Member
****
Offline Offline

Activity: 477



View Profile
June 26, 2013, 05:05:28 PM
 #5882

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
https://bitcointalk.org/index.php?topic=153232.msg1626156#msg1626156

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://bitcointalk.org/index.php?topic=18313.msg2256552#msg2256552 so you can get an idea of how to tune bitcoin (controversial subject). Also the guide I mentioned above covers this.
baloo_kiev
Sr. Member
****
Offline Offline

Activity: 476


View Profile
June 26, 2013, 05:23:22 PM
 #5883

s
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?

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)

PGP: 6EC48BA7
Welcome to my p2pool: BTC
notme
Legendary
*
Offline Offline

Activity: 1526


View Profile
June 26, 2013, 09:58:07 PM
 #5884

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://bitcointalk.org/index.php?topic=234841.0

https://www.bitcoin.org/bitcoin.pdf
While no idea is perfect, some ideas are useful.
12jh3odyAAaR2XedPKZNCR4X4sebuotQzN
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 02:44:05 AM
 #5885

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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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

i had to edit some of the p2pool code to get it to work, afaik anyone with 0.8.3 will get the same repeating error

i may also try editing out the whole "punishing share" bit too later as some test,  that's 3/3 orphans right now, occur within 5s of that

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
GrapeApe
Sr. Member
****
Offline Offline

Activity: 477



View Profile
June 27, 2013, 04:14:39 AM
 #5886

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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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

i had to edit some of the p2pool code to get it to work, afaik anyone with 0.8.3 will get the same repeating error

i may also try editing out the whole "punishing share" bit too later as some test,  that's 3/3 orphans right now, occur within 5s of that

I didn't get those errors and this is the version I am running Bitcoin-Qt version v0.8.3.0-g40809ae-beta
I downloaded it from the link at top this page and complied from that src.

Keep me posted about what you do to the punishing share code...
iongchun
Member
**
Offline Offline

Activity: 76


View Profile
June 27, 2013, 04:44:33 AM
 #5887

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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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 > --- <exception caught here> ---
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

i had to edit some of the p2pool code to get it to work, afaik anyone with 0.8.3 will get the same repeating error

i may also try editing out the whole "punishing share" bit too later as some test,  that's 3/3 orphans right now, occur within 5s of that

I didn't get those errors and this is the version I am running Bitcoin-Qt version v0.8.3.0-g40809ae-beta
I downloaded it from the link at top this page and complied from that src.

Keep me posted about what you do to the punishing share code...

I also didn't get this error.
I build bitcoind from the commit tagged as "v0.8.3" (40809aed657502e9de158e2cfe2c659a316f2f90).
Maybe the latest git commit is already too new Smiley


Bitcoin: 1NFMpJUW7sTKmnVKj12MxhPvCvzAKQ5gUV
Namecoin: N5Tnt3JyMeizsoAFAZDr7CSxjzDtPSisK8
Mining with P2Pool. Graph. Blocks.
chanson
Member
**
Offline Offline

Activity: 84


View Profile
June 27, 2013, 02:44:48 PM
 #5888

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!
forrestv
Hero Member
*****
Offline Offline

Activity: 510


View Profile
June 27, 2013, 03:26:06 PM
 #5889

The latest P2Pool commit fixes the LateEnd error with newer versions of Bitcoin.

1J1zegkNSbwX4smvTdoHSanUfwvXFeuV23
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 03:58:24 PM
 #5890

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!
that shouldn't have had any impact, the getblocktemplate latency will increase mainly because 1) you build up a lot of transactions in storage, that'll show up on bitcoind getmininginfo, 2) your system is overloaded

more connections would probably make the second case more likely

no blocks within the last 30 minutes or so makes #1 a problem, for some people

rate limiting, connections, all this is totally different area

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 04:11:33 PM
 #5891

it's really simple to set up p2pool to have a low getblocktemplate latency

in bitcoin.conf,

blockprioritysize=0
blockmaxsize=3000
minrelaytxfee=100000  (or maybe 0.001)

i'm not sure which one of those is the proper way to put it in conf, my guess is the 1st

that's all you need to do



    // Fee-per-kilobyte amount considered the same as "free"
    // If you are mining, be careful setting this:
    // if you set it to zero then
    // a transaction spammer can cheaply fill blocks using
    // 1-satoshi-fee transactions. It should be set above the real
    // cost to you of processing a transaction.

oh, the getblocktemplate latency doesnt have a huge effect, really

just when blocks are solved.  so then some ppl are penalized that have faster bitcoind, if some ppl with slow getblocktemplate latencies get off a couple shares in a row

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
chanson
Member
**
Offline Offline

Activity: 84


View Profile
June 27, 2013, 05:16:37 PM
 #5892

Isn't this JSON-RPC thing for getblocktemplate completely stupid? Why aren't we using a shared memory segment with bitcoind?
bitpop
Legendary
*
Offline Offline

Activity: 1918


https://keybase.io/bitpop


View Profile WWW
June 27, 2013, 05:20:51 PM
 #5893

I don't think latency in those terms is the problem

Reputation  |  PGP  |  DigitalOcean  |  OpenVPN 2GB Free  |  TorGuard  |  Ethereum Classic
Bitcoin: 3DSh6AnmvBpDJFUz2mnLirMLmTMcFs9nDm
Bitmessage: BM-2cXN9j8NFT2n1FxDVQ6HQq4D4MZuuaBFyb
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 06:32:16 PM
 #5894

I don't think latency in those terms is the problem
Well, you didn't make it clear who you were replying to

but, yeah, getblocktemplate latency has nothing to do with having more or less peers, it has to do with your local machine

(ed: well, i suppose if you had a max of 1 connection in bitcoind, then that one connection didn't relay any transactions, you'd have a really low getblocktemplate time)

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 08:08:51 PM
 #5895

p2pool falsely claiming share is "dead on arrival" after block solved, orphaning valid shares over invalid shares, claiming "Dead on arrival" shares that become undead

first time, it became undead, and valid

second time, it remained dead

2013-06-27 14:59:35.699635  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.5% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:36.885926 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:36.888536 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:37.338727 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:40.485636 New work for worker! Difficulty: 5.000000 Share difficulty: 1115.669886 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:40.701845  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.2% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:41.640140 GOT SHARE! Tempbastard 115dabec prev 82d3447f age 17.21s DEAD ON ARRIVAL
2013-06-27 14:59:45.449055 New work for worker! Difficulty: 5.000000 Share difficulty: 1107.910003 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:45.704697  Shares: 59 (2 orphan, 4 dead) Stale rate: ~10.2% (4-21%) Efficiency: ~112.3% (99-120%) Current payout: 0.2480 BTC

this is the case of the DOA share remaining DOA, despite:

the parent share:

Share 82d3447f
Time first seen: Thu Jun 27 2013 14:59:17 GMT-0500 (Central Daylight Time) (1372363157.042115)
Payout address: 1GL7mM8ZA69WXQcSLu69WYTHGXgXajjSPT

the "non-DOA" child share:

Share b684ab9e (<--- as you can see, my log repeatedly "punished" this share, for being "block-stale")
Time first seen: Thu Jun 27 2013 14:59:24 GMT-0500 (Central Daylight Time) (1372363164.357247)
Payout address: 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV


please fix this crap.  thanks



ed: oh, oops, here's the earlier part:

2013-06-27 14:59:24.375464 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:24.425505 New work for worker! Difficulty: 5.000000 Share difficulty: 1110.049880 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:25.689527  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.5% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:26.885891 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:26.888480 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!

log is always linked at www.nogleg.com/log

added www.nogleg.com/log.2

which shows

2013-06-27 11:37:27.023558 GOT SHARE! Tempbastard 18fae184 prev 1a0e47a0 age 4.15s

a share being orphaned right before a block, presumably because of the same slow nodes that cause ^^^

the cause of about 1/2 of my orphans and maybe 1/5th of the DOAs

ed: next begins here

2013-06-27 16:05:17.479788 GOT SHARE! Crazed Hookers 9436d28f prev ce2367af age 0.48s
2013-06-27 16:05:22.517996 Skipping from block a4bd5a28f726c27f813cd0657b354f81f79855d4752de4ba56 to block bb36b7e2cba69a75d33f4f16c564690540869c98abcebd3a7a!

******************************

also, I'm going to be shutting down my p2pool sometime in the next 12-24 hrs, giving the ppl mining there some fair warning if you dont have a backup set

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
GrapeApe
Sr. Member
****
Offline Offline

Activity: 477



View Profile
June 27, 2013, 10:15:17 PM
 #5896

p2pool falsely claiming share is "dead on arrival" after block solved, orphaning valid shares over invalid shares, claiming "Dead on arrival" shares that become undead

first time, it became undead, and valid

second time, it remained dead

2013-06-27 14:59:35.699635  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.5% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:36.885926 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:36.888536 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:37.338727 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:40.485636 New work for worker! Difficulty: 5.000000 Share difficulty: 1115.669886 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:40.701845  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.2% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:41.640140 GOT SHARE! Tempbastard 115dabec prev 82d3447f age 17.21s DEAD ON ARRIVAL
2013-06-27 14:59:45.449055 New work for worker! Difficulty: 5.000000 Share difficulty: 1107.910003 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:45.704697  Shares: 59 (2 orphan, 4 dead) Stale rate: ~10.2% (4-21%) Efficiency: ~112.3% (99-120%) Current payout: 0.2480 BTC

this is the case of the DOA share remaining DOA, despite:

the parent share:

Share 82d3447f
Time first seen: Thu Jun 27 2013 14:59:17 GMT-0500 (Central Daylight Time) (1372363157.042115)
Payout address: 1GL7mM8ZA69WXQcSLu69WYTHGXgXajjSPT

the "non-DOA" child share:

Share b684ab9e (<--- as you can see, my log repeatedly "punished" this share, for being "block-stale")
Time first seen: Thu Jun 27 2013 14:59:24 GMT-0500 (Central Daylight Time) (1372363164.357247)
Payout address: 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV




While trying to wrap my head around this I was going through your log and found this.....

2013-06-27 14:59:22.200435 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from 82d3447f to f619b3c1!
2013-06-27 14:59:22.243440 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.246420 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.249283 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.252093 New work for worker! Difficulty: 5.000000 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.255850 New work for worker! Difficulty: 5.000000 Share difficulty: 5000.002049 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.327728 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.330796 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.333631 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.522117 New work for worker! Difficulty: 5.000000 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.705084 New work for worker! Difficulty: 5.000000 Share difficulty: 5000.002049 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:24.375464 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!

I don't understand how  82d3447f can be the parent share if we jumped from 82d3447f to f619b3c1. How do we jump  back to  82d3447f what happened to f619b3c1??? I am confused by this....
baloo_kiev
Sr. Member
****
Offline Offline

Activity: 476


View Profile
June 27, 2013, 10:24:09 PM
 #5897

p2pool falsely claiming share is "dead on arrival" after block solved, orphaning valid shares over invalid shares, claiming "Dead on arrival" shares that become undead

...

also, I'm going to be shutting down my p2pool sometime in the next 12-24 hrs, giving the ppl mining there some fair warning if you dont have a backup set

Please run with -debug command line option for verbose logging. Thanks.

PGP: 6EC48BA7
Welcome to my p2pool: BTC
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 10:41:44 PM
 #5898

p2pool falsely claiming share is "dead on arrival" after block solved, orphaning valid shares over invalid shares, claiming "Dead on arrival" shares that become undead

first time, it became undead, and valid

second time, it remained dead

2013-06-27 14:59:35.699635  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.5% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:36.885926 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:36.888536 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:37.338727 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!
2013-06-27 14:59:40.485636 New work for worker! Difficulty: 5.000000 Share difficulty: 1115.669886 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:40.701845  Shares: 58 (2 orphan, 3 dead) Stale rate: ~8.6% (3-19%) Efficiency: ~114.2% (101-121%) Current payout: 0.2480 BTC
2013-06-27 14:59:41.640140 GOT SHARE! Tempbastard 115dabec prev 82d3447f age 17.21s DEAD ON ARRIVAL
2013-06-27 14:59:45.449055 New work for worker! Difficulty: 5.000000 Share difficulty: 1107.910003 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:45.704697  Shares: 59 (2 orphan, 4 dead) Stale rate: ~10.2% (4-21%) Efficiency: ~112.3% (99-120%) Current payout: 0.2480 BTC

this is the case of the DOA share remaining DOA, despite:

the parent share:

Share 82d3447f
Time first seen: Thu Jun 27 2013 14:59:17 GMT-0500 (Central Daylight Time) (1372363157.042115)
Payout address: 1GL7mM8ZA69WXQcSLu69WYTHGXgXajjSPT

the "non-DOA" child share:

Share b684ab9e (<--- as you can see, my log repeatedly "punished" this share, for being "block-stale")
Time first seen: Thu Jun 27 2013 14:59:24 GMT-0500 (Central Daylight Time) (1372363164.357247)
Payout address: 185Kip6odGYs4eSHD6DYsWVDJBg2DNLfiV




While trying to wrap my head around this I was going through your log and found this.....

2013-06-27 14:59:22.200435 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from 82d3447f to f619b3c1!
2013-06-27 14:59:22.243440 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.246420 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.249283 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.252093 New work for worker! Difficulty: 5.000000 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.255850 New work for worker! Difficulty: 5.000000 Share difficulty: 5000.002049 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.327728 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.330796 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.333631 New work for worker! Difficulty: 1.560562 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.522117 New work for worker! Difficulty: 5.000000 Share difficulty: 1112.553271 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:22.705084 New work for worker! Difficulty: 5.000000 Share difficulty: 5000.002049 Total block value: 25.003000 BTC including 3 transactions
2013-06-27 14:59:24.375464 Punishing share for 'Block-stale detected! 5eb5fbbee222c57983d44064121839f36a6b9ade5728c6bee6 < 994e796a55e58076e851ee356cc6cdae297b0ecebb41bb651d'! Jumping from b684ab9e to 82d3447f!

I don't understand how  82d3447f can be the parent share if we jumped from 82d3447f to f619b3c1. How do we jump  back to  82d3447f what happened to f619b3c1??? I am confused by this....


Yeah, there are all sorts of weird anomalies like that.  I think that was the case for my DOA that became undead, wasn't it?   I remember we both mentioned something about having no clue wtf happened to xxxxxxx share that it said it was jumping to, haha.

re: debug mode, I have no more mhash on the pool and it may not happen again with ~1500-2000mhash or so that's on it now.  I wish I had saved all my old logs, tho

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
baloo_kiev
Sr. Member
****
Offline Offline

Activity: 476


View Profile
June 27, 2013, 11:19:46 PM
 #5899

It would be nice if forrestv commented on this!

This is what I see after looking into the code. If a share C is based on a stale block (usually shortly after a block was found), it gets "punished" and nodes start working on top of its parent share P, so C is forced to orphan. However, if a node does not follow this rule (may be a result of code modification or high bitcoind latency), it works on top of C (while others are working on P!) and may eventually find a share, "save" C from orphanage and (easily since it is 1 share ahead by total work!) orphan all P's children found before it. Looks like a bug to me.

PGP: 6EC48BA7
Welcome to my p2pool: BTC
zvs
Legendary
*
Offline Offline

Activity: 1386



View Profile WWW
June 27, 2013, 11:32:08 PM
 #5900

It would be nice if forrestv commented on this!

This is what I see after looking into the code. If a share C is based on a stale block (usually shortly after a block was found), it gets "punished" and nodes start working on top of its parent share P, so C is forced to orphan. However, if a node does not follow this rule (may be a result of code modification or high bitcoind latency), it works on top of C (while others are working on P!) and may eventually find a share, "save" C from orphanage and (easily since it is 1 share ahead by total work!) orphan all P's children found before it. Looks like a bug to me.

Yeah, that is exactly what I think is happening.  I think it's the result of latency (internet) + bitcoind getblocktemplate latency.  It doesn't help that some of the highest hash power miners on p2pool seem to be behind firewalls & are on slow connections/machines.  Miner X finds a share, say, 1-3 seconds after a new block, Miner X's client thinks it is a legit share and passes it around, some of the other p2pool nodes relay it as legit....  another share is then built off of that one, and then that's it for anyone that (ed: has found a share off of) the parent of the 'punished' share...  the two shares > one share, so everyone switches over.

I didn't keep my old logs, but I've had a few times where I've found a share, gotten a new work (not just from the sleep time deferral, +1 to verified shares, etc), then the next work, it'll become an orphan... so then that means that some other nodes had some 3 share chain vs the 2 share chain.  The 3rd share on that chain might not even necessarily be from a slow node..

Dacentec, best deals for US dedicated servers. They regularly restock $20-$25 Opterons with 8-16GB RAM & 2x1-2TB HDD's (ofc, usually lots of other good stuff to choose from).  I did a Serverbear benchmark of one of my $20/mo Opteron (June last year), it's here.  Have had about a half dozen different servers with Dacentec, & none have failed to sustain at least 40MB/s (burst higher). My favorite is a 12-month rent-to-own ZT Systems 2XL5520 16GB 2x2TB SATA for $40/month (got lucky with the 'off-brand', haven't seen a RTO 2xL5520 for under $50/mo since -- at least for monthly contracts).  wholesaleinternet.com has some ancient 2-core intel CPUs @ $10/mo sometimes (I got an Intel Core 2 6300 @ 1.86GHz, with a 250GB HDD with 46000 hours on it, LOL. $20 @ Dacentec is much better, if you can grab one). joesdatacenter.com (same location as Wholesale Internet) also occasionally has specials (or if you don't want to wait, it has an AMD Opteron 170 @ $16/mo).
Pages: « 1 ... 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 [295] 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 ... 744 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!