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.. |
|
|
|
|
I think the cheapest I've seen a 7850 including the rebate is $132 on Newegg.... after selling games, that would have been about $110 at the time (5-24, tomb raider + bioshock were worth more then, etc)..
They're regularly up there for $140, including rebate... and the games.
Though some are better than others (re: 2GB vs 1GB, etc). I think the cheapest I've seen a 2GB is $160. I bought an MSI Twin Frozr 2GB for $170, after rebate, on May 12th... back then it was worth it to take it out of the box and mine with it.
I don't think so now. If you're going for pure profit... you'd just buy it, do the rebate, sell the games, then sell the card as 'new in box'.
I think the 7790's on newegg are a better deal, though. I wish I had bought more a few months ago... they use like 70 watts for 300-320mhash and you could get them for about $75 after selling the games..
(re: i got about $80 each for my sapphire 5830's on amazon after fees, was replacing those cards with 7xxx series)
|
|
|
|
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 |
|
|
|
|
I'm going to be shutting down nogleg.com p2pool sometime in the next 12-24 hrs, just to give fair warning to other ppl using it atm
|
|
|
|
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/logadded www.nogleg.com/log.2which 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 |
|
|
|
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) |
|
|
|
|
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
|
|
|
|
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 |
|
|
|
Since newest bitcoind from git, I have errors on p2pool log: 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)
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 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 had to change the nonstandard transaction to a 1 DoS amount, as someone was sending me thousands of nonstandard transactions, raising system load to >5
|
|
|
|
|
ok, seriously:
2013-06-25 19:07:09.184546 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.187304 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:09.950242 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:09.950321 Local: 5970MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.7 minutes
2013-06-25 19:07:09.950354 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:09.950396 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:14.203573 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:14.206408 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:17.955598 P2Pool: 17368 shares in chain (17373 verified/17373 total) Peers: 58 (4 incoming)
2013-06-25 19:07:17.955675 Local: 6076MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.5 minutes
2013-06-25 19:07:17.955715 Shares: 7 (1 orphan, 0 dead) Stale rate: ~14.3% (2-52%) Efficiency: ~100.5% (57-115%) Current payout: 0.2505 BTC
2013-06-25 19:07:17.955759 Pool: 552GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:19.184574 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:19.187462 Punishing share for 'Block-stale detected! 6dd42c5d83567ac74ee79dd224864a71f2b6f1b0a9d28f7e6f < cd03f48c5345acfc88bcaff1f81f4fa125c18df73fdb6f792f'! Jumping from 062aec7c to
a3c6c045!
2013-06-25 19:07:21.728450 GOT SHARE! Drizztztzzztztzzzzztzz 1c29e828 prev a3c6c045 age 14.17s
2013-06-25 19:07:21.775027 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.778033 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.780870 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.783816 New work for worker! Difficulty: 1.430048 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:21.788586 New work for worker! Difficulty: 5.000000 Share difficulty: 1048.780971 Total block value: 25.000500 BTC including 1 transactions
2013-06-25 19:07:24.523397 Peer sent entire transaction c046b6219388a196710f6df1542ba8b2f8bc9e5ff8cd413644e141bb3a80b254 that was already received
2013-06-25 19:07:25.961603 P2Pool: 17347 shares in chain (17351 verified/17351 total) Peers: 58 (4 incoming)
2013-06-25 19:07:25.961688 Local: 6137MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.3 minutes
2013-06-25 19:07:25.961730 Shares: 8 (1 orphan, 0 dead) Stale rate: ~12.5% (2-48%) Efficiency: ~102.6% (62-115%) Current payout: 0.2532 BTC
2013-06-25 19:07:25.961757 Pool: 551GH/s Stale rate: 14.7% Expected time to block: 1.7 days
2013-06-25 19:07:27.725795 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.728756 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.731579 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.734343 New work for worker! Difficulty: 1.401363 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:27.737214 New work for worker! Difficulty: 5.000000 Share difficulty: 1039.385193 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.898191 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.901337 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.906160 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.909223 New work for worker! Difficulty: 1.432098 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:32.912061 New work for worker! Difficulty: 5.000000 Share difficulty: 1043.302225 Total block value: 25.001500 BTC including 3 transactions
2013-06-25 19:07:33.963725 P2Pool: 17349 shares in chain (17353 verified/17353 total) Peers: 58 (4 incoming)
2013-06-25 19:07:33.963799 Local: 6126MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.1 minutes
2013-06-25 19:07:33.963832 Shares: 8 (2 orphan, 0 dead) Stale rate: ~25.0% (7-60%) Efficiency: ~88.3% (48-110%) Current payout: 0.2505 BTC
2013-06-25 19:07:33.963876 Pool: 553GH/s Stale rate: 15.1% Expected time to block: 1.7 days
is this a bug?
|
|
|
|
|
ok, had 3 orphans in 170 shares or something as i recall
so, i restart server with bitcoind 0.8.3
and on share 4:
2013-06-25 18:02:03.554832 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:03.557871 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.560598 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.563201 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.565803 New work for worker! Difficulty: 1.772574 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:03.568432 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.088180 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:07.416689 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:07.634945 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.146924 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:08.147316 Skipping from block 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab to block aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719!
2013-06-25 18:02:09.185104 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.191632 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 8aa0ee38 to 287fcce9!
2013-06-25 18:02:09.659806 GOT SHARE! Crazed Hookers 5183904d prev 287fcce9 age 6.09s
2013-06-25 18:02:09.707200 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.710064 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.712893 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.715610 New work for worker! Difficulty: 1.898801 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:09.718332 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:10.466509 P2Pool: 17327 shares in chain (17332 verified/17332 total) Peers: 57 (3 incoming)
2013-06-25 18:02:10.466586 Local: 6324MH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-7%) Expected time to share: 12.0 minutes
2013-06-25 18:02:10.466617 Shares: 4 (0 orphan, 0 dead) Stale rate: ~0.0% (0-49%) Efficiency: ~120.3% (61-121%) Current payout: 0.2596 BTC
2013-06-25 18:02:10.466645 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:13.322844 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:13.359771 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.362627 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.367018 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.369778 New work for worker! Difficulty: 2.061223 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:13.372481 New work for worker! Difficulty: 5.000000 Share difficulty: 1063.852358 Total block value: 25.000000 BTC including 0 transactions
2013-06-25 18:02:14.206935 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:14.212014 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:18.472999 P2Pool: 17321 shares in chain (17326 verified/17326 total) Peers: 57 (3 incoming)
2013-06-25 18:02:18.473077 Local: 6244MH/s in last 10.0 minutes Local dead on arrival: ~3.9% (2-7%) Expected time to share: 12.2 minutes
2013-06-25 18:02:18.473107 Shares: 4 (1 orphan, 0 dead) Stale rate: ~25.0% (4-70%) Efficiency: ~90.2% (36-115%) Current payout: 0.2569 BTC
2013-06-25 18:02:18.473150 Pool: 578GH/s Stale rate: 16.9% Expected time to block: 1.7 days
2013-06-25 18:02:19.185085 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
2013-06-25 18:02:19.188387 Punishing share for 'Block-stale detected! aab5fe4319dba59006ca9ff6a55c7edf822892ffda854cf719 < 10a65f5818d8bcb9438ac0ee53701061984b36bdb5cc331cab'! Jumping from 4af26ed4 to 8aa0ee38!
so, I've submitted a share based on the new block, but I get orphaned again, and I'm still 'punishing' other shares
|
|
|
|
|
so, is this fixed in the latest version?
it wasn't very nice to get 10GB used up in 5 minutes, some modifications would be good to remove
that wasnt a 'small memory leak', it was some huge 'memory storage' exploit
|
|
|
|
It just seems that with asics coming on line and hash rates increasing, that its overall a redistribution of bitcoin mining. So the network is really no better off than we were mining with 5770s last year... and the last block to be mined will still be around the same time it was predicted to be mathematically. We've just tipped the same tables in favor of the few who have large amounts of asic hash power. The network is now safer because the entry cost is higher for someone who would want to perform a 51% attack (let's say Obama lol). It is / it is going to be impossible to do that with GPUs and a limited availability of ASICs further helps to diminish the chances of someone being able to purchase enough hardware for a 51% attack. Or, is there a ceiling limitation to difficulty? And once we hit that, we can mine the block chain faster than originally though possible?
No. the 1st part is BS the main benefit is that there will (presumably) be less cpu bot miners it gets tiresome hearing this 51% attack over and over, but that whole statement is just wrong. the specialized equipment = less people mining = more chance for one entity to gain a majority of hashing power. the limited # of ASICs doesnt help diminish the chances at all, it increases it. if asicminer wanted to, they probably could have done a 51% attack, simply by using all the junk they have been selling... but why would you do such a thing and undermine your own profit? the only offsetting factor would be that setting up large GPU farms required some bit of computer knowledge and technical expertise (not to mention setting up the mining software, etc), thus limiting the # of people that could mine somewhat. ASICs : bitcoins :: AOL : internet You aren't seeing the big picture. ASICs always existed. If the "good miners" aren't using them it doesn't result in a gentlemans agreement where attackers won't use them either. At one point it would have taken $20M to $40M worth of GPUs to attack the Bitcoin network ... one problem with that. No serious attacker would have spent $20M on GPUs. They would have spent $1M and produced enough ASICs to 99.9999999999% the network. The threat always existed. The "good guys" using ASICs removes that cheat card. An attacker can still use ASICs but the hashrate will be much higher and without a "cheating advantage" it becomes a pure brute force attack. You seem to think of only the "economic 51% attack" where an attacker looks to directly benefit from their hashing power by reversing transactions. That has probably never been a threat even a $1M investment would be significantly larger than any potential revenue from such a scheme. However the "non-economic 51% attack" where an attacker sees the cost as simply the price to destroy Bitcoin isn't subject to limits of "showing a profit". IF (and it remains an if) over the next couple years the usage, exchange rate, and hashing power all grow the cost to attack the network will rise significantly. In theory someday it may requires hundreds of millions of dollars or possibly even a billion dollars worth of single purpose hardware. That limits the number of potential attackers to only the largest of nation states. All (no POS) alt-coins on the other hand could be 51% attacked by the Central Bank of Somolia. all this stuff is irrelevant (or agrees) with what I said? you are saying that a 51% attack is more likely with ASICs than with GPUs ("they always existed") i doubt you disagree that the limited # of ASICs right now *increases the chance (edited to reflect what I said). do you disagree with the asicminer comment? argh. less asics = higher chance. |
|
|
|
get some 7790s, it has currently the best price/hashrate ratio and best power consumption/hashrate ratio: https://suryarpraveen.wordpress.com/2013/04/23/amd-destroys-nvidia-at-bitcoin-mining-can-the-gap-ever-be-bridged/If you have more money then go for 7950s. The CPU I would use is an AMD Trinity or Richland APU. They are cheap and they can be used as an extra GPU. The A10-5800K gives about 114 MHash/s for Bitcoin mining, and about 70 kHash/s for Litecoin Mining with a TDP of 120 Watt. The new A10-6700 should be at same level or a bit above, but consumes less power. The A10-6800K should be even better but power consumption should be close to the A10-5800K. ^^ that is correct 7790's are the best thing to buy right now, if you aren't taking pci-e slots into consideration 7950's will drop in price a lot more than 7790's. 7790's can do 300mhash on about 70 watts. you can get some of the brands for less than $100 on newegg if you do the rebates and sell the games. i've purchased a few (7790, 7850), mined for a month, then resold the card for profit even after ebay fee. but that was about ... 6 weeks ago, when it was worth the effort |
|
|
|
Greetings-
I'm mining LTC with a Sapphire 7870XT (Tahiti). I was wondering what some options might be for helping cool the card down.
Ironically, I find I get the best hashrate (400kH/s or so) when the card is underclocked (850 Mhz). My case is small, though, so even with good fans and such my temps were constantly around 85C - which as the absolute maximum I want to be at (and I don't want to be in the "red zone" all the time). So I took the side of the case off and I am now at 80C. That's better, but I'd still prefer to be lower than that.
I figure I have a few options. What do you guys think of:
1. Is it worth re-seating the cooler with Arctic Silver 5 (AS5)? I have heard that because of its conductivity, AS5 may not be my best bet for a GPU, but I already own it.
2. What about a third-party cooler to replace the stock cooler? I know these things are not cheap - I've seen some units at $150 or more! Unless I can get a big drop in temps, I'd prefer not to outlay so much cash.
3. Is there a water/liquid cooled solution? If so, how risky do you think it is and how much would it cost?
Thanks for any and all ideas!
the best option would be to remove the case entirely and get a $15-$20 floor fan (honeywell, lasko, w/e). the other option is to keep the case on and just put the fan in front of it angled slightly so it exhausts out the back of the case (assuming that you have fans in front that are intake etc) oh, the answer to #1 = yes, if it doesn't void your warranty |
|
|
|
still in stock for me.  haha, says discontinued now. that's lame. it said out of stock when i looked. i guess someone that had an order cancelled it. i would have bought one for $212 |
|
|
|
Alright so I recently bought a $20 plastic box fan from Home Depot to cool down my rig. Only problem is, after like 5 days of continuous running, a melting plastic smell begins to come out of the fan. I think the wiring is getting so hot that some of the plastic is melting. Do you guys have any suggestions on a box fan that can run 24/7 without burning my house down? Thanks  uh, I have five of those cheap $15-$20 honeywell fans, only one has stopped working, and it was just from being in 100% use for over a year, I guess. melted? wtf. this is with ambient temps over 110oF sometimes |
|
|
|
It just seems that with asics coming on line and hash rates increasing, that its overall a redistribution of bitcoin mining. So the network is really no better off than we were mining with 5770s last year... and the last block to be mined will still be around the same time it was predicted to be mathematically. We've just tipped the same tables in favor of the few who have large amounts of asic hash power. The network is now safer because the entry cost is higher for someone who would want to perform a 51% attack (let's say Obama lol). It is / it is going to be impossible to do that with GPUs and a limited availability of ASICs further helps to diminish the chances of someone being able to purchase enough hardware for a 51% attack. Or, is there a ceiling limitation to difficulty? And once we hit that, we can mine the block chain faster than originally though possible?
No. the 1st part is BS the main benefit is that there will (presumably) be less cpu bot miners it gets tiresome hearing this 51% attack over and over, but that whole statement is just wrong. the specialized equipment = less people mining = more chance for one entity to gain a majority of hashing power. the limited # of ASICs doesnt help diminish the chances at all, it increases it. if asicminer wanted to, they probably could have done a 51% attack, simply by using all the junk they have been selling... but why would you do such a thing and undermine your own profit? the only offsetting factor would be that setting up large GPU farms required some bit of computer knowledge and technical expertise (not to mention setting up the mining software, etc), thus limiting the # of people that could mine somewhat. ASICs : bitcoins :: AOL : internet |
|
|
|
OK, so I've been looking at my orphans for the last 10 days or so.... about 33% of them occur after a block solve.
i guess i should also mention that 50% of them are orphaned by 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe and i know he isnt using an asic, so why so slow? How do you know it was that address, and is it wrong to assume that you have his ip address? If so ban him don't send any more work his way. Not that it matters but that address has a huge balance by the way... nah, he's a major contributor to p2pool. i think he's been mining it for years. i'm just whining and wish he had a faster setup. =p I don't even know what IP he mines to, which I guess is part of the problem. I think he's on a private node, probably with just 6 outgoing connections. oh, I know it was that address since my orphan showed up in the 'headers' list... then I go to the parent share and click on child, and it shows what replaced your orphaned share (if it works the way I think it does, that replacement is actually dictated by the share that comes after it) Here's another good example (not my shares): (presumably two would have been orphaned, anyway, but..) These three shares, in order of time my server saw them: Share 5573d59d Parent: f923ec04 Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.021445) Share d0a23adf Parent: f923ec04 Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.186212) Share 22d14440 Parent: f923ec04 Time first seen: Tue Jun 25 2013 03:26:34 GMT-0500 (Central Daylight Time) (1372148794.205658) (183ms apart) got orphaned by this one: Share 7cb9dbd5 Parent: f923ec04 Time first seen: Tue Jun 25 2013 03:26:48 GMT-0500 (Central Daylight Time) (1372148808.8004) Payout address: 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe 14780ms late it got orphaned because the next share was: Share 5ccfc4c1 Parent: 7cb9dbd5 Time first seen: Tue Jun 25 2013 03:26:51 GMT-0500 (Central Daylight Time) (1372148811.190973) Payout address: 1CTgYxMTY5j6SLytKeMsBWAXuUc6yNKcAe ....... that's a really long lag time.. I was thinking he must have been working on a different parent share, but that says they all have the same one.... *scratch* oh! I bet it was caused by this: http://blockchain.info/block-index/394604/0000000000000099ea7426c7e7289e03c25caebe329b5f0b7f10696d20626879the same thing I was whining about =p ---------------------------- 1 orphan in 107 shares (107 now, 101 then), this: 2013-06-25 08:58:19.715307 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from f5e744ca to aea3ccc9! 2013-06-25 08:58:19.749535 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions 2013-06-25 08:58:19.753518 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions 2013-06-25 08:58:19.757446 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions 2013-06-25 08:58:19.761187 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions 2013-06-25 08:58:19.766552 New work for worker! Difficulty: 5.000000 Share difficulty: 1075.192002 Total block value: 25.008000 BTC including 4 transactions 2013-06-25 08:58:19.796149 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:19.800348 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:19.804610 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:19.809372 New work for worker! Difficulty: 1.351312 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.000072 New work for worker! Difficulty: 5.000000 Share difficulty: 1075.192002 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.802166 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to f5e744ca! 2013-06-25 08:58:20.844785 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.850027 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.856650 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.861682 New work for worker! Difficulty: 1.351312 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:20.866957 New work for worker! Difficulty: 5.000000 Share difficulty: 1076.726276 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:23.376789 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to f5e744ca! 2013-06-25 08:58:23.379542 Punishing share for 'Block-stale detected! ed82da82bd35e7059f84ff75721bdc5e2ed51e5a5bb801a6c < 32205ef944185696477f67f3081b9d0812403497f4cc931cd9'! Jumping from 541b96e9 to f5e744ca! 2013-06-25 08:58:24.442380 GOT SHARE! Crazed Hookers 4380a491 prev f5e744ca age 3.58s 2013-06-25 08:58:24.490625 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.494000 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.497168 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.501941 New work for worker! Difficulty: 1.268760 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.505167 New work for worker! Difficulty: 5.000000 Share difficulty: 1069.919469 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.599258 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.602612 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.605772 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.608983 New work for worker! Difficulty: 1.294867 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:24.703523 New work for worker! Difficulty: 5.000000 Share difficulty: 1076.474487 Total block value: 25.002000 BTC including 4 transactions 2013-06-25 08:58:25.710917 P2Pool: 17337 shares in chain (17342 verified/17342 total) Peers: 68 (14 incoming) 2013-06-25 08:58:25.711003 Local: 6319MH/s in last 10.0 minutes Local dead on arrival: ~7.3% (4-11%) Expected time to share: 12.2 minutes 2013-06-25 08:58:25.711045 Shares: 101 (1 orphan, 9 dead) Stale rate: ~9.9% (5-18%) Efficiency: ~110.4% (101-116%) Current payout: 0.2833 BTC 2013-06-25 08:58:25.711082 Pool: 583GH/s Stale rate: 18.4% Expected time to block: 1.6 days maybe it's more like 50% of the orphans |
|
|
|
|
Show Posts
