[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[jtoomim]

We're having some trouble with our primary internet connection at our datacenter. ml.toom.im:9332, :9334, :9336, and :7903 will be unavailable probably for a few days. woff.toom.im:9348 and woff.toom.im:9327 should still be working, but our miners can't reach those ports any longer due to how our LAN and firewalls are currently configured during failover situations, so we will not be contributing any BCH or LTC hashrate until we get this issue resolved.

I lied about no errors....also, adding ANY +diff number and my miner always shows Diff of 8.04M

"'NoneType' object has no attribute 'expire'" messages can safely be ignored. They happen even when the node is working properly. That's just a cosmetic bug AFAIK. Not sure why address+XXXXX isn't working; I noticed that too on an earlier version of the code. That seems to be mostly cosmetic though, so I might not look into it for a while.

Only 2 submitted shares this whole time with 8GH on my node. It seems that the diff for each is going everywhere? ... *edit* no longer using 1mb_segwit fork.

1mb_segwit and p2pool/p2pool master should have the same litecoin share difficulty. They may have different pseudoshare difficulties, but pseudoshare difficulty is only used for statistics and does not affect revenue (unless it's so low that your CPU gets saturated, at least). Difficulty will be much higher than before due to the higher pool hashrate.

If those are the closest nodes to you, it all looks good.

Single-threaded CPU speed (including whether you're running pypy) is about 10x as important on Bitcoin p2pool as network latency is. It typically takes somewhere between 0.5 seconds and 3 seconds to process a share and issue new work on p2pool, depending on CPU speed, but it only takes between 0.001 seconds and 0.3 seconds to transmit stratum jobs to and from the miner and node.

Besides the invalid block this morning(im guessing invalid?)

As for the invalid LTC block from Wednesday Jan 24 at 12pm GMT, my litecoin debug.log says this:

Code:

2018-01-24 12:09:34 CreateNewBlock(): total size: 36290 block weight: 144287 txs: 95 fees: 10300975 sigops 1227
2018-01-24 12:09:49 CreateNewBlock(): total size: 38752 block weight: 154135 txs: 102 fees: 10740075 sigops 1283
2018-01-24 12:10:04 CreateNewBlock(): total size: 43993 block weight: 174106 txs: 113 fees: 11370458 sigops 1362
2018-01-24 12:10:19 CreateNewBlock(): total size: 61073 block weight: 242426 txs: 126 fees: 13213178 sigops 1482
2018-01-24 12:10:29 ERROR: ConnectBlock(): coinbase pays too much (actual=2511370458 vs limit=2511291614)
2018-01-24 12:10:29 InvalidChainFound: invalid block=496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28  height=1355999  log2_work=69.614049  date=2018-01-24 12:10:05
2018-01-24 12:10:29 InvalidChainFound:  current best=815e95cd59cdc16d20dc8add274fe3f5683174fdbe8c297eac5cfd3adfbd239f  height=1355998  log2_work=69.614023  date=2018-01-24 12:07:47
2018-01-24 12:10:29 ERROR: ConnectTip(): ConnectBlock 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 failed
2018-01-24 12:10:29 InvalidChainFound: invalid block=496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28  height=1355999  log2_work=69.614049  date=2018-01-24 12:10:05
2018-01-24 12:10:29 InvalidChainFound:  current best=815e95cd59cdc16d20dc8add274fe3f5683174fdbe8c297eac5cfd3adfbd239f  height=1355998  log2_work=69.614023  date=2018-01-24 12:07:47
2018-01-24 12:10:29 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:29 Peer 14 sent us invalid header via cmpctblock
2018-01-24 12:10:29 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:29 ERROR: ProcessNewBlock: AcceptBlock FAILED
2018-01-24 12:10:30 ERROR: AcceptBlockHeader: block 496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 is marked invalid
2018-01-24 12:10:30 Peer 18 sent us invalid header via cmpctblock
2018-01-24 12:10:34 CreateNewBlock(): total size: 64138 block weight: 254686 txs: 137 fees: 13520639 sigops 1562
2018-01-24 12:10:49 CreateNewBlock(): total size: 68992 block weight: 273439 txs: 152 fees: 15049509 sigops 1672
2018-01-24 12:11:05 CreateNewBlock(): total size: 75486 block weight: 298755 txs: 163 fees: 16182859 sigops 1750
2018-01-24 12:11:14 UpdateTip: new best=924b90b24a8003352e01c6e3bdb183466b718850e1da82ed1662d907e5e486de height=1355999 version=0x20000000 log2_work=69.614049 tx=20103178 date='2018-01-24 12:11:08' progress=1.000000 cache=22.9MiB(7817tx)
2018-01-24 12:11:14 CreateNewBlock(): total size: 1753 block weight: 6904 txs: 4 fees: 152800 sigops 432
2018-01-24 12:11:29 CreateNewBlock(): total size: 7627 block weight: 30400 txs: 15 fees: 1095648 sigops 576

The error is "coinbase pays too much (actual=2511370458 vs limit=2511291614)". Someone was trying to earn 0.00078844 LTC too much in that block. That invalid block was mined by LZzzELrQifCah5oafpNuCA6dLiyacVJNDa, and they were not using my code (they were voting for v17 shares). If anyone can find the node used by that miner, that would be helpful. You can sometimes get hints by browsing to (node IP:port)/static/share.html#496cf90d143d6ad706ec965d1fb2fabee62e6c493d32bc245384fc637d520c28 and seeing which peer it was received from, then repeating the process. This gets harder when nodes have non-standard UIs, though, and when I tried to do this on this share, the first node I ran into was running a non-standard UI. Someone else might have better luck.

It may be necessary to add some code to p2pool to check the coinbase payments to make sure that they don't violate rules like this, and punish (orphan) shares that are invalid in this way. But that sucks, because it means more code that I don't have time to write.

[Tornado_of_Coins]

So what happen to all the shares I had on that node?

[jtoomim]

It looks like we have resolved our networking problems. ml.toom.im:9332, :9334, and :7903 should be available again outside our LAN once again, and woff.toom.im:9348 and :9327 once again have hashrate on them.

So what happen to all the shares I had on that node?

Your shares were not on that node. They were on the p2pool network. When my nodes go down, they're no longer contributing to the p2pool network, but the shares that were mined before my nodes went down have been copied to all other nodes on the same network (i.e. jtoomimnet).

[jtoomim]

You get paid whenever a block is found. For Litecoin, that will average about once a day, but there may be no payouts at all on some days if we are unlucky. Your payments for the first few days will start smaller and will ramp up. After you stop mining, your payments will slowly ramp down over a few days.

[Tornado_of_Coins]

It looks like we have resolved our networking problems. ml.toom.im:9332, :9334, and :7903 should be available again outside our LAN once again, and woff.toom.im:9348 and :9327 once again have hashrate on them.

So what happen to all the shares I had on that node?

Your shares were not on that node. They were on the p2pool network. When my nodes go down, they're no longer contributing to the p2pool network, but the shares that were mined before my nodes went down have been copied to all other nodes on the same network (i.e. jtoomimnet).

Ahh, blockchain...Ii should have thought. Thanks JT

[Kiefff]

Hi, I have a few questions. 

1- I started mining with 20 "antminer" s9. I did not build my own Node. I'm mining for p2pool (http://p2pool.org/stats/node.php) It is stated that a payment will be made in 72 hours. If I do not find a block, can not I get this money?

2- Have you received money within 3 days of those who mining up until now? S9 or Bitcoin?

3- Do I receive a reward for the transfer fee from the scavenging I made in the P2pool pool or mining a block?

4- What do I understand when I see the following? Didn't find 6 daytime blocks?

https://image.ibb.co/cuHXgw/doa.png

Ps: I'm so sorry my english isn't good.

Thanks

1 - first you are mining on p2pool mainnet, I suggest Jtoomimnet for BTC mining. Or at least find a node that seems to be more efficient than the one you are on. If no block is found, there is no BTC to payout to the miners. This isnt a PAY PER SHARE pool. You get paid based on blocks found and shares you submitted into the sharechain. So that means whatever your PREDICTED PAYMENT is at the time of a found block, thats what you will get for your mining work.

2- you will receive BTC when a block is found by the pool. Everyone is paid almost immediately after found blocks. The coins are generated coins that no one touches but your wallet.

3- p2pool pays the miners the founds blocks and transaction fees of that block. So normal BTC block = 12.5 BTC + extra transfer fees. Same with LTC network, just block reward is 25 LTC + transaction fees. Sometimes transfer fees almost make the block reward DOUBLE. p2pool, Kano.is, and Slushpool are the only pools that I know payout the transaction fee, in the BTC world. I could be wrong..

4- what you are highlighting is found blocks, but im pretty sure those are invalid? Not 100%, I mostly follow LTC p2pool. Like i said before, get off mainnet p2pool btc and join jtoomim net. More hash and smoother network.

Hope I answered your questions...and again, get off mainnet p2pool and join a Jtoomimnet node. ~80day est BLOCK time vs ~15-20days is a big difference. Not to mention the difference in block sizes between the two... LETS CRUSH BLOCKS!

-Keith

[kbirand]

Hi, I have a few questions. 

1- I started mining with 20 "antminer" s9. I did not build my own Node. I'm mining for p2pool (http://p2pool.org/stats/node.php) It is stated that a payment will be made in 72 hours. If I do not find a block, can not I get this money?

2- Have you received money within 3 days of those who mining up until now? S9 or Bitcoin?

3- Do I receive a reward for the transfer fee from the scavenging I made in the P2pool pool or mining a block?

4- What do I understand when I see the following? Didn't find 6 daytime blocks?

https://image.ibb.co/cuHXgw/doa.png

Ps: I'm so sorry my english isn't good.

Thanks

1 - first you are mining on p2pool mainnet, I suggest Jtoomimnet for BTC mining. Or at least find a node that seems to be more efficient than the one you are on. If no block is found, there is no BTC to payout to the miners. This isnt a PAY PER SHARE pool. You get paid based on blocks found and shares you submitted into the sharechain. So that means whatever your PREDICTED PAYMENT is at the time of a found block, thats what you will get for your mining work.

2- you will receive BTC when a block is found by the pool. Everyone is paid almost immediately after found blocks. The coins are generated coins that no one touches but your wallet.

3- p2pool pays the miners the founds blocks and transaction fees of that block. So normal BTC block = 12.5 BTC + extra transfer fees. Same with LTC network, just block reward is 25 LTC + transaction fees. Sometimes transfer fees almost make the block reward DOUBLE. p2pool, Kano.is, and Slushpool are the only pools that I know payout the transaction fee, in the BTC world. I could be wrong..

4- what you are highlighting is found blocks, but im pretty sure those are invalid? Not 100%, I mostly follow LTC p2pool. Like i said before, get off mainnet p2pool btc and join jtoomim net. More hash and smoother network.

Hope I answered your questions...and again, get off mainnet p2pool and join a Jtoomimnet node. ~80day est BLOCK time vs ~15-20days is a big difference. Not to mention the difference in block sizes between the two... LETS CRUSH BLOCKS!

-Keith

I was about to ask exactly the same questions as Momentmc.. Thank you for your kind answers Keith.

I myself have few questions as well.

1- So what I understand that I have to wait 15-20 days to get paid.. But  while checking this node: http://212.45.19.162:9332/static/ I have found that this wallet is
https://blockchain.info/address/1EntfMRTWee7oGYfDf4vNRE62frXrmCT8a getting roughly 0.01 per day for 35 to 40TH... He/she gets paid every 5 to 7 days...  This is mainnet.. If Mainnet is getting blocks every 70 days what is this payment ?

2- With my limited blockchain knowledge I thought that to solve a block you need the previous block to hash.. If we are solving blocks how do we know the previous block since giants like btc.com, antpool etc etc solve blocks every 10 minutes.. Then this means that once we start hashing a block the previous block is obsolete since these giants have already finds blocks..

3- jtoomim is it an other fork of p2pool. I have tried installing it on my mac.. had a lot of difficulty ..

Thanks...

[Kiefff]

I was about to ask exactly the same questions as Momentmc.. Thank you for your kind answers Keith.

I myself have few questions as well.

1- So what I understand that I have to wait 15-20 days to get paid.. But  while checking this node: http://212.45.19.162:9332/static/ I have found that this wallet is
https://blockchain.info/address/1EntfMRTWee7oGYfDf4vNRE62frXrmCT8a getting roughly 0.01 per day for 35 to 40TH... He/she gets paid every 5 to 7 days...  This is mainnet.. If Mainnet is getting blocks every 70 days what is this payment ?

2- With my limited blockchain knowledge I thought that to solve a block you need the previous block to hash.. If we are solving blocks how do we know the previous block since giants like btc.com, antpool etc etc solve blocks every 10 minutes.. Then this means that once we start hashing a block the previous block is obsolete since these giants have already finds blocks..

3- jtoomim is it an other fork of p2pool. I have tried installing it on my mac.. had a lot of difficulty ..

Thanks...

No problem.

1- you are just looking at the blockchain explorer, pretty much just all the transaction of his wallets. Not everything that shows up there is from mining. If you send or receive any BTC, the explorer with show it ALL. But the link you provided appears to be another p2pool BTC mainnet node. That wallet ID you pointed out will only get paid when p2pool MAINNET finds a block. Predicted payout = payout at time of block finding by the pool.

2- Confused ? =D The bigger pools do smash blocks. There are work restarts, but I dont have any answer for ya. Im sure, one of the super smart guys can answer it tho im sure.

3- yes so there are two forks of p2pool BTC nets to mine on. One is the mainnet, which to me seems out dated. The other is Jtoomimnet(1mb_segwit), which seems to be smoother. I personally always tell people to join Jtoomimnet. His code seems to be superior, but thats just me from a miners standpoint and knowing what I know. Im no programmer by the way, but I know a tad bit of code to get by, barely. Jtoomim just implemented his 1mb_segwit fork to the p2pool LTC network and I will say it has improved the network dramatically.

Here are the two different nets. Not sure of the location of these nodes, but just to give an example.

http://crypto.office-on-the.net:9334/static/ <--Jtoomimnet node
http://crypto.office-on-the.net:9332/static/ <--Mainnet node

[jtoomim]

If you are trying to mine Vertcoin, you need to install vertcoind, not bitcoind. bitcoind is for mining bitcoin or bitcoin cash.

[jtoomim]

2- With my limited blockchain knowledge I thought that to solve a block you need the previous block to hash.. If we are solving blocks how do we know the previous block since giants like btc.com, antpool etc etc solve blocks every 10 minutes.. Then this means that once we start hashing a block the previous block is obsolete since these giants have already finds blocks..

You need the hash of the previous block, yes. But there is no progress to abandon. It's not like after 1 day, we're 10% of the way to mining a block, and can predict that we'll mine a block in 9 more days. Mining is like rolling a die with 1,000,000,000,000,000 sides. If the die comes up with a 1, then you've mined a valid block. If the die comes up with any other number, then you have not mined a block and need to try again. When someone else publishes a new block, that forces us to roll a die at a different table. When you switch tables, you don't bring anything with you from the old table, and you abandon the roll in progress. But it doesn't matter, because each round of the game only lasts a billionth of a second and is independent from all other rounds.

[Kiefff]

You get paid whenever a block is found. For Litecoin, that will average about once a day, but there may be no payouts at all on some days if we are unlucky. Your payments for the first few days will start smaller and will ramp up. After you stop mining, your payments will slowly ramp down over a few days.

I set mooncoin wallet address to bleutrade mooncoin address. Is this a problem? It has passed 24 hours. The p2pool site has a hash speed of 1.8g hash. Help

Mining dashboard : https://moonchain.net/a/2T2xx8srAQ

yes, you shouldnt of used an exchange wallet id. Contact bleutrade...sometimes exchanges have problems with generated coins. They should be able to help you.


**edit** also that is not the mining dashboard...that is just simple a blockchain explorer, which shows wallet balances and transactions. Looks like a balance of 34k mooncoins currently, with some other transactions that took place as well.

[kbirand]

2- With my limited blockchain knowledge I thought that to solve a block you need the previous block to hash.. If we are solving blocks how do we know the previous block since giants like btc.com, antpool etc etc solve blocks every 10 minutes.. Then this means that once we start hashing a block the previous block is obsolete since these giants have already finds blocks..

You need the hash of the previous block, yes. But there is no progress to abandon. It's not like after 1 day, we're 10% of the way to mining a block, and can predict that we'll mine a block in 9 more days. Mining is like rolling a die with 1,000,000,000,000,000 sides. If the die comes up with a 1, then you've mined a valid block. If the die comes up with any other number, then you have not mined a block and need to try again. When someone else publishes a new block, that forces us to roll a die at a different table. When you switch tables, you don't bring anything with you from the old table, and you abandon the roll in progress. But it doesn't matter, because each round of the game only lasts a billionth of a second and is independent from all other rounds.

Thank you Jtoomim,

I still have not clearly understood .. the total Hashing power of p2pool is around 1.5ph where as btc poll is around 4.290eh.. So they will crush the blocks every time we start hashing. And also our expected time on finding a block on your fork is around 10-15 days (87 days on p2pool)... Until we find a block they will find one and every time we have to start from the beginning, so how do we ever get one...

Thanks..

[jtoomim]

First, I don't know where you're getting your numbers. The BTC network hashrate is about 19.5 EH/s, not 4.29 EH/s.

https://blockchain.info/charts/hash-rate

Also, jtoomimnet p2pool's hashrate is about 5.6 PH/s, which is a lot better than mainnet's 1.5 PH/s

If mainnet p2pool's hashrate is 1.5 PH/s, and BTC's total hashrate is 19.5 EH/s = 19500 PH/s, then mainnet p2pool has a 1.5 / 19500 = 1 in 13,000 chance to mine each block. Each day we get 144 blocks, so mainnet should see on average one block every 13000/144. = 90 days.

Until we find a block they will find one and every time we have to start from the beginning, so how do we ever get one...

"The beginning" isn't the right way to think about it, because there is nothing except "the beginning". There is no progress to abandon. Every hash you do is starting from the beginning, and you finish a nanosecond later. Most attempts are failures. Each time someone has a successful 1-nanosecond-long attempt, they get the block reward.

Everyone is rolling dice. Some people have more dice than others, but it doesn't matter. The first person to roll a 1 on a 1,000,000,000,000-sided die wins that round, and then everyone walks to a new table and starts again. Your chance of winning is proportional to the number of dice rolls you make.

[seavey87]

First, I don't know where you're getting your numbers. The BTC network hashrate is about 19.5 EH/s, not 4.29 EH/s.

https://blockchain.info/charts/hash-rate

Also, jtoomimnet p2pool's hashrate is about 5.6 PH/s, which is a lot better than mainnet's 1.5 PH/s

If mainnet p2pool's hashrate is 1.5 PH/s, and BTC's total hashrate is 19.5 EH/s = 19500 PH/s, then mainnet p2pool has a 1.5 / 19500 = 1 in 13,000 chance to mine each block. Each day we get 144 blocks, so mainnet should see on average one block every 13000/144. = 90 days.

Until we find a block they will find one and every time we have to start from the beginning, so how do we ever get one...

"The beginning" isn't the right way to think about it, because there is nothing except "the beginning". There is no progress to abandon. Every hash you do is starting from the beginning, and you finish a nanosecond later. Most attempts are failures. Each time someone has a successful 1-nanosecond-long attempt, they get the block reward.

Everyone is rolling dice. Some people have more dice than others, but it doesn't matter. The first person to roll a 1 on a 1,000,000,000,000-sided die wins that round, and then everyone walks to a new table and starts again. Your chance of winning is proportional to the number of dice rolls you make.

Do you have a link to your p2pool node with 5.6 PH/s?

[kr1z1s]

First, I don't know where you're getting your numbers. The BTC network hashrate is about 19.5 EH/s, not 4.29 EH/s.

https://blockchain.info/charts/hash-rate

Also, jtoomimnet p2pool's hashrate is about 5.6 PH/s, which is a lot better than mainnet's 1.5 PH/s

If mainnet p2pool's hashrate is 1.5 PH/s, and BTC's total hashrate is 19.5 EH/s = 19500 PH/s, then mainnet p2pool has a 1.5 / 19500 = 1 in 13,000 chance to mine each block. Each day we get 144 blocks, so mainnet should see on average one block every 13000/144. = 90 days.

Until we find a block they will find one and every time we have to start from the beginning, so how do we ever get one...

"The beginning" isn't the right way to think about it, because there is nothing except "the beginning". There is no progress to abandon. Every hash you do is starting from the beginning, and you finish a nanosecond later. Most attempts are failures. Each time someone has a successful 1-nanosecond-long attempt, they get the block reward.

Everyone is rolling dice. Some people have more dice than others, but it doesn't matter. The first person to roll a 1 on a 1,000,000,000,000-sided die wins that round, and then everyone walks to a new table and starts again. Your chance of winning is proportional to the number of dice rolls you make.

Periodically an error occurs

Code:

2018-01-27 12:29:00.936674 Generating a share with 748899 bytes, 2907033 WU (new: 719273 B, 2789186 WU) in 485 tx (385 new), plus est gentx of 2552 bytes/10244 WU
2018-01-27 12:29:00.936831 Total block stripped size=722010 B, full size=751531 B,  weight: 2917517 WU
2018-01-27 12:29:00.997316 Generating a share with 748899 bytes, 2907033 WU (new: 719273 B, 2789186 WU) in 485 tx (385 new), plus est gentx of 2552 bytes/10244 WU
2018-01-27 12:29:00.997447 Total block stripped size=722010 B, full size=751531 B,  weight: 2917517 WU
in handle_share_hashes:
Traceback (most recent call last):
Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer

Sometimes once a minute, sometimes less.

[jtoomim]

kr1z1s, you seem to be missing most of the error message traceback. The next 10 or 20 lines will contain most of the useful information.

I cannot find any similar errors on my node.

[kr1z1s]

kr1z1s, you seem to be missing most of the error message traceback. The next 10 or 20 lines will contain most of the useful information.

I cannot find any similar errors on my node.

On http://p2p-spb.xyz:9334/static/

Code:

2018-01-27 15:00:18.531633  Pool: 7838TH/s Stale rate: 8.4% Expected time to block: 16.5 days
in handle_share_hashes:
Traceback (most recent call last):
Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer

2018-01-27 15:00:20.801093 Lost peer 188.0.182.10:34872 - Connection was aborted locally, using.
2018-01-27 15:00:22.723872 Peer sent entire transaction 25e973de5fea05cf9d148ab717cdc78b3459129de7f8c591ff4c548a400d0cce that was already received
2018-01-27 15:00:23.619997 Got new merged mining work!
2018-01-27 15:00:23.672125 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 15:00:23.672267 Total block stripped size=656968 B, full size=751377 B,  weight: 2722237 WU
2018-01-27 15:00:23.742487 New work for 149eGg3gsZ3zdE4E7PmnWJZSqeeFrnGFVb! Diff: 9840.12 Share diff: 41190634.56 Block value: 13.75 BTC (1304 tx, 749 kB)
2018-01-27 15:00:23.844060 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 15:00:23.844248 Total block stripped size=656968 B, full size=751377 B,  weight: 2722237 WU
2018-01-27 15:00:24.043136 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 15:00:24.043281 Total block stripped size=656968 B, full size=751377 B,  weight: 2722237 WU
2018-01-27 15:00:24.171487 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 15:00:24.171679 Total block stripped size=656968 B, full size=751377 B,  weight: 2722237 WU
2018-01-27 15:00:24.288891 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 15:00:24.289031 Total block stripped size=656968 B, full size=751377 B,  weight: 2722237 WU
2018-01-27 15:00:24.388557 Generating a share with 748813 bytes, 2712025 WU (new: 71842 B, 243739 WU) in 1304 tx (78 new)

That's all there is.

[sawa]

I have a similar error on my nodes:

On http://crypto.mine.nu:9334

Code:

2018-01-27 19:05:03.529457 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.529558 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:03.599891 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.599979 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:03.671132 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.671222 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:03.742918 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.743010 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:03.815214 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.815307 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:03.892442 Generating a share with 633206 bytes, 2420801 WU (new: 54100 B, 200392 WU) in 1191 tx (113 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 19:05:03.892529 Total block stripped size=598384 B, full size=635725 B,  weight: 2430833 WU
2018-01-27 19:05:05.053899 GOT SHARE! 1KGPJ95Ag2BG5ScGPPntHQiRJswqqHSz5x a7d86b95 prev 13050939 age 1.35s
2018-01-27 19:05:05.185550 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.185679 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:05.257983 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.258077 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:05.328909 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.328995 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:05.400739 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.400826 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:05.471392 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.471481 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:05.545372 Generating a share with 633206 bytes, 2420801 WU (new: 0 B, 0 WU) in 1191 tx (0 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 19:05:05.545466 Total block stripped size=598429 B, full size=635770 B,  weight: 2431013 WU
2018-01-27 19:05:07.275101 Peer 188.0.182.10:57134 says protocol version is 3301, client version 15.0-84-g4a0332c
2018-01-27 19:05:07.275255 Incoming connection from peer 188.0.182.10:57134 established. p2pool version: 3301 '15.0-84-g4a0332c'
2018-01-27 19:05:07.709601 Sending 1 shares to 188.0.182.10:57134
2018-01-27 19:05:07.895025 Peer sent entire transaction 39478c1bd43272a3c144c9a96f32068984263ad9c110c7ade63d69eb49685aee that was already received
2018-01-27 19:05:11.602308 Peer sent entire transaction 31f953330507776f033215fc62512d3e7e2070bd26db3ce82eebff0dc81ca37f that was already received
2018-01-27 19:05:12.218424 Peer sent entire transaction 59fa82e5ccf35ea61351b3c11eabd7a399c73e8b40a2a84a9217e37fbaaa077a that was already received
2018-01-27 19:05:13.028446 Peer sent entire transaction 59fa82e5ccf35ea61351b3c11eabd7a399c73e8b40a2a84a9217e37fbaaa077a that was already received
2018-01-27 19:05:13.440721 Peer sent entire transaction 340f407826819fe4fed739c055ebc285b75b088eda444529fd823361e40ca198 that was already received
2018-01-27 19:05:14.214497 Peer sent entire transaction 59fa82e5ccf35ea61351b3c11eabd7a399c73e8b40a2a84a9217e37fbaaa077a that was already received
2018-01-27 19:05:15.037561 P2Pool: 17546 shares in chain (17550 verified/17550 total) Peers: 17 (11 incoming)
2018-01-27 19:05:15.037703  Local: 206TH/s in last 10.0 minutes Local dead on arrival: ~4.9% (3-8%) Expected time to share: 5.6 minutes
2018-01-27 19:05:15.037767  Shares: 2859 (237 orphan, 74 dead) Stale rate: ~10.9% (9-13%) Efficiency: ~96.5% (95-98%) Current payout: (0.0034)=0.0034 BTC
2018-01-27 19:05:15.037822  Pool: 7174TH/s Stale rate: 7.7% Expected time to block: 18.0 days
2018-01-27 19:05:16.794886 Peer sent entire transaction e7c6e2c52ecd6a342468229408f76815ce247a3f2989ff72c4c04450a97e9642 that was already received
2018-01-27 19:05:22.009249 Peer sent entire transaction 59fa82e5ccf35ea61351b3c11eabd7a399c73e8b40a2a84a9217e37fbaaa077a that was already received
in handle_share_hashes:
Traceback (most recent call last):
Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer

2018-01-27 19:05:22.276760 Lost peer 188.0.182.10:57134 - Connection was aborted locally, using.
2018-01-27 19:05:27.017590 Peer sent entire transaction 1c3199e706993ea34d784d9a806a95dabfd6b3a3a3cdf1a1027d2f14e10348a3 that was already received
2018-01-27 19:05:27.052279 Peer sent entire transaction 473d459ec84b30ca44e0916329aa67dba3fa81e4af7f09db49d9a06cf56d0683 that was already received
2018-01-27 19:05:27.549058 Peer sent entire transaction 7a64691098b63f656572ce5f1bea96de3aaadea8d12d070913a0cfdb0c228b5a that was already received
2018-01-27 19:05:28.785815 Peer sent entire transaction 9f65f9b8b3e17085dcef7d2e90e27c8c8c910d223fc722c818af11c2c1b0bd30 that was already received
2018-01-27 19:05:28.788962 Peer sent entire transaction 7a64691098b63f656572ce5f1bea96de3aaadea8d12d070913a0cfdb0c228b5a that was already received
2018-01-27 19:05:28.991084 Peer sent entire transaction 9f65f9b8b3e17085dcef7d2e90e27c8c8c910d223fc722c818af11c2c1b0bd30 that was already received
2018-01-27 19:05:29.640548 Peer sent entire transaction d24cb82eda8237004107abf1ad1e8b37a55e596910feec559a4b21a229960993 that was already received
2018-01-27 19:05:30.016216 Peer sent entire transaction f52d7cb758daebc3a9edfc29c8539954b8130fd30b2f67b69d458c0bc6f23939 that was already received
2018-01-27 19:05:37.428183 Peer sent entire transaction d24cb82eda8237004107abf1ad1e8b37a55e596910feec559a4b21a229960993 that was already received
2018-01-27 19:05:39.761200 Peer sent entire transaction e26c3d34888fb80a53fee1e4f3c3187c8fa16379622dd1f870838d860b2abcbd that was already received
2018-01-27 19:05:42.168714 Peer sent entire transaction 93b5e355ec7798507d2a58f0517d4057ffa0080b848f860a4bbe9feba7bc0c68 that was already received
2018-01-27 19:05:42.214920 Peer sent entire transaction 93b5e355ec7798507d2a58f0517d4057ffa0080b848f860a4bbe9feba7bc0c68 that was already received
2018-01-27 19:05:42.838171 Peer sent entire transaction d24cb82eda8237004107abf1ad1e8b37a55e596910feec559a4b21a229960993 that was already received
2018-01-27 19:05:43.414838 Peer sent entire transaction d24cb82eda8237004107abf1ad1e8b37a55e596910feec559a4b21a229960993 that was already received
2018-01-27 19:05:43.714485 Lost peer 5.19.171.173:9333 - Connection to the other side was lost in a non-clean fashion.
2018-01-27 19:05:45.076199 Peer sent entire transaction d076fbfbb0116789e0495c59a53f13d75b053e12ada89e990e962a98c6be9664 that was already received
2018-01-27 19:05:45.090113 P2Pool: 17546 shares in chain (17550 verified/17550 total) Peers: 15 (10 incoming)
2018-01-27 19:05:45.090189  Local: 206TH/s in last 10.0 minutes Local dead on arrival: ~4.7% (3-7%) Expected time to share: 5.9 minutes
2018-01-27 19:05:45.090226  Shares: 2859 (237 orphan, 74 dead) Stale rate: ~10.9% (9-13%) Efficiency: ~96.5% (95-98%) Current payout: (0.0034)=0.0034 BTC
2018-01-27 19:05:45.090266  Pool: 7174TH/s Stale rate: 7.7% Expected time to block: 18.0 days
2018-01-27 19:05:47.037909 Peer 192.168.0.104:9333 says protocol version is 3301, client version 15.0-84-g4a0332c-dirty
2018-01-27 19:05:47.038096 Outgoing connection to peer 5.19.171.173:9333 established. p2pool version: 3301 '15.0-84-g4a0332c-dirty'
2018-01-27 19:05:47.430649 Peer sent entire transaction 0daf07544069ab9fba66e5779f2b605f180ac50780f0854422cc2b34b8047762 that was already received
2018-01-27 19:05:53.450488 Peer sent entire transaction cfae83fcab2585fec2d18ea19bde796ab88cff4201f57e31e88e761446a68ef8 that was already received
2018-01-27 19:05:57.517437 Peer sent entire transaction ea90c01cdc1b934285f7ae5e768a807b205913d102b42f91b2ff7a23f2a39fc9 that was already received
2018-01-27 19:05:58.450992 Peer sent entire transaction 51764c51827b60b566f10ceee2ca8ca26a2a0334c688ab90340c136555b82ca4 that was already received
2018-01-27 19:05:58.627012 Peer sent entire transaction 51764c51827b60b566f10ceee2ca8ca26a2a0334c688ab90340c136555b82ca4 that was already received
2018-01-27 19:06:00.213119 > Peer referenced unknown transaction f3e7345456ccbf4b8e1cc546cc5b33349d3e380f7f83606ae40c3d7f1a426cb6, disconnecting
2018-01-27 19:06:00.213797 Lost peer 94.54.173.36:52503 - Connection was aborted locally, using.
2018-01-27 19:06:00.456656 Peer sent entire transaction 51764c51827b60b566f10ceee2ca8ca26a2a0334c688ab90340c136555b82ca4 that was already received

On http://crypto.mine.nu:9334

Code:

2018-01-27 17:59:40.971156 Generating a share with 455309 bytes, 1744865 WU (new: 38925 B, 140610 WU) in 871 tx (78 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 17:59:40.971284 Total block stripped size=432371 B, full size=457828 B,  weight: 1754897 WU
2018-01-27 17:59:41.019366 Generating a share with 455309 bytes, 1744865 WU (new: 38925 B, 140610 WU) in 871 tx (78 new), plus est gentx of 2439 bytes/9792 WU
2018-01-27 17:59:41.019476 Total block stripped size=432371 B, full size=457828 B,  weight: 1754897 WU
2018-01-27 17:59:42.056340 Peer sent entire transaction 943fbf2928c40a971dbde69f46fa3cda3d952aa496f805467b0763b320a11e83 that was already received
2018-01-27 17:59:42.927545 Peer sent entire transaction 943fbf2928c40a971dbde69f46fa3cda3d952aa496f805467b0763b320a11e83 that was already received
in handle_share_hashes:
Traceback (most recent call last):
Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer

2018-01-27 17:59:44.637027 Lost peer 188.0.182.10:47302 - Connection was aborted locally, using.
2018-01-27 17:59:47.169099 Peer sent entire transaction 102230d68f1d235ea73d3bd3053d7e4491728ab188e1f67c5c8c853422ea3c2a that was already received
2018-01-27 17:59:48.084086 Peer sent entire transaction 102230d68f1d235ea73d3bd3053d7e4491728ab188e1f67c5c8c853422ea3c2a that was already received
2018-01-27 17:59:50.119290 Peer sent entire transaction 102230d68f1d235ea73d3bd3053d7e4491728ab188e1f67c5c8c853422ea3c2a that was already received
2018-01-27 17:59:51.798927 Peer sent entire transaction 102230d68f1d235ea73d3bd3053d7e4491728ab188e1f67c5c8c853422ea3c2a that was already received
2018-01-27 17:59:51.826240 Peer sent entire transaction f4a475ecf1f6f7e131da3f9ca28c3a747d0436b243bb8c28dda7580f88e50a2b that was already received
2018-01-27 17:59:52.010552 Lost peer 208.84.223.121:9337 - Connection to the other side was lost in a non-clean fashion.
2018-01-27 17:59:52.448633 Peer sent entire transaction 102230d68f1d235ea73d3bd3053d7e4491728ab188e1f67c5c8c853422ea3c2a that was already received
2018-01-27 17:59:54.695016 Peer 178.63.18.3:9333 says protocol version is 3301, client version 15.0-84-g4a0332c-dirty
2018-01-27 17:59:54.695237 Outgoing connection to peer 178.63.18.3:9333 established. p2pool version: 3301 '15.0-84-g4a0332c-dirty'
2018-01-27 17:59:58.006062 Peer sent entire transaction 8f5e2a7f0ceaa93de1783ad537485c1ed86a8959d51d06a9dc58a26fea795e83 that was already received
2018-01-27 17:59:58.435182 Peer sent entire transaction 7b41b134b12e7e675950aa452fd6a972738c0dc0f7c95791a2ac7514342b7bda that was already received
2018-01-27 17:59:58.564615 Generating a share with 459107 bytes, 1759076 WU (new: 4464 B, 16875 WU) in 882 tx (12 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 17:59:58.564726 Total block stripped size=435887 B, full size=461671 B,  weight: 1769288 WU
2018-01-27 17:59:58.594474 New work for 1LRAff8qeMz4L4EoatmyQRLYhMMRm8TGvB! Diff: 711.47 Share diff: 2274696.14 Block value: 13.60 BTC (882 tx, 459 kB)
2018-01-27 17:59:58.623969 Generating a share with 459107 bytes, 1759076 WU (new: 4464 B, 16875 WU) in 882 tx (12 new), plus est gentx of 2484 bytes/9972 WU
2018-01-27 17:59:58.624102 Total block stripped size=435887 B, full size=461671 B,  weight: 1769288 WU
2018-01-27 17:59:58.648694 Peer sent entire transaction 8f5e2a7f0ceaa93de1783ad537485c1ed86a8959d51d06a9dc58a26fea795e83 that was already received
2018-01-27 18:00:00.562606 Peer sent entire transaction 9a13c5c1054600658313f7feb482c9ede9c806bcbaead27a8a9134494085e5aa that was already received
2018-01-27 18:00:00.826043 Peer sent entire transaction 0daf07544069ab9fba66e5779f2b605f180ac50780f0854422cc2b34b8047762 that was already received
2018-01-27 18:00:01.292218 Peer sent entire transaction dbf2281bb0311cc354b35927108f500b56c61b3cd2fb13ee4f4177201658c587 that was already received
2018-01-27 18:00:01.906429 P2Pool: 17545 shares in chain (17549 verified/17549 total) Peers: 18 (12 incoming)
2018-01-27 18:00:01.906612  Local: 2879GH/s in last 10.0 minutes Local dead on arrival: ~3.8% (2-6%) Expected time to share: 58.3 minutes
2018-01-27 18:00:01.906700  Shares: 262 (34 orphan, 12 dead) Stale rate: ~17.6% (13-23%) Efficiency: ~90.0% (84-95%) Current payout: (0.0033)=0.0033 BTC
2018-01-27 18:00:01.906790  Pool: 7838TH/s Stale rate: 8.4% Expected time to block: 16.5 days

[Staim]

Similar errors.
http://213.110.128.16:9332

Code:

2018-01-27 20:03:39.456000 Peer sent entire transaction 888d9c4b738cf8742c2f9883
048ae3bf6e452abf8afe6703414c648a7e145daf that was already received
2018-01-27 20:03:39.472000 Peer sent entire transaction 7a18ff69ba3db169aaeb5fd4
839b756b4cd080d64abe96ac8f4cdc8b6818cc3e that was already received
2018-01-27 20:03:39.472000 Peer 188.0.182.10:34400 says protocol version is 3301
, client version 15.0-84-g4a0332c
2018-01-27 20:03:39.472000 Incoming connection from peer 188.0.182.10:34400 esta
blished. p2pool version: 3301 '15.0-84-g4a0332c'
2018-01-27 20:03:40.065000 Peer sent entire transaction 7a18ff69ba3db169aaeb5fd4
839b756b4cd080d64abe96ac8f4cdc8b6818cc3e that was already received
2018-01-27 20:03:40.472000 Sending 1 shares to 188.0.182.10:34400
2018-01-27 20:03:42.097000 Peer sent entire transaction 888d9c4b738cf8742c2f9883
048ae3bf6e452abf8afe6703414c648a7e145daf that was already received
2018-01-27 20:03:49.988000 Peer sent entire transaction 3c1dade8e5c07e69313694f0
badf93af9670bad23974f46011705b0dfb2cf148 that was already received
2018-01-27 20:03:50.035000 Peer sent entire transaction 402df8669eeaf9720798c693
c5acc198665ffdc44d5d4960928b309aab48459d that was already received
2018-01-27 20:03:50.129000 Peer sent entire transaction acb63af8e6f5a19e7e076ef6
7c3a7884814c848f32d6ffff419fac8d73032cd0 that was already received
2018-01-27 20:03:53.504000 Peer sent entire transaction d0a4c3f4cb5e4c31009fb0a8
eeef809186a23e332cd0a43fcaad3b0a899bfb64 that was already received
2018-01-27 20:03:53.583000 Lost peer 91.121.95.32:9333 - Connection to the other
 side was lost in a non-clean fashion.
2018-01-27 20:03:53.598000 Lost peer 91.176.125.54:9333 - Connection to the othe
r side was lost in a non-clean fashion.
2018-01-27 20:03:53.708000 Lost peer 69.27.173.226:9333 - Connection to the othe
r side was lost in a non-clean fashion.
2018-01-27 20:03:53.895000 Lost peer 212.58.112.196:9333 - Connection was closed
 cleanly.
in handle_share_hashes:
Traceback (most recent call last):
Failure: twisted.internet.defer.TimeoutError: in GenericDeferrer

2018-01-27 20:03:54.489000 Lost peer 188.0.182.10:34400 - Connection was aborted
 locally, using.
2018-01-27 20:03:59.286000 Peer sent entire transaction f10f9efa3c78407160d9f44f
846970999f614fb5025b08db1cbab3257dd94cd1 that was already received
2018-01-27 20:03:59.380000 P2Pool: 17359 shares in chain (10986 verified/17363 t
otal) Peers: 3 (0 incoming)
2018-01-27 20:03:59.380000  Local: 0H/s in last 0.0 seconds Local dead on arriva
l: ??? Expected time to share: ???
2018-01-27 20:03:59.396000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficie
ncy: ??? Current payout: (0.0000)=0.0000 BTC
2018-01-27 20:03:59.396000  Pool: 4603TH/s Stale rate: 7.7% Expected time to blo
ck: 28.1 days
2018-01-27 20:03:59.880000 Peer 188.0.182.10:9333 says protocol version is 3301,
 client version 15.0-84-g4a0332c
2018-01-27 20:03:59.880000 Outgoing connection to peer 188.0.182.10:9333 establi
shed. p2pool version: 3301 '15.0-84-g4a0332c'
2018-01-27 20:04:00.458000 Sending 1 shares to 188.0.182.10:9333
2018-01-27 20:04:01.005000 Peer 192.168.15.43:9335 says protocol version is 3301
, client version 15.0-84-g4a0332c
2018-01-27 20:04:01.005000 Outgoing connection to peer 37.194.10.30:9335 establi
shed. p2pool version: 3301 '15.0-84-g4a0332c'
2018-01-27 20:04:02.349000 Peer sent entire transaction a9149de67b53c270f7a04816
0cb0424682c28e7c08db02901335ab89fa00e0e2 that was already received
2018-01-27 20:04:03.021000 Peer sent entire transaction 818a4ef9bf5a6d0011726667
fdbdf882c99520768cff769ca9564dabd9a2aa74 that was already received
2018-01-27 20:04:03.959000 Peer sent entire transaction fd3e54fa7c71ba47a8da56bc
00883c9aff9d474da320380725536a4e4fdcd060 that was already received
2018-01-27 20:04:14.069000 Peer sent entire transaction fd3e54fa7c71ba47a8da56bc
00883c9aff9d474da320380725536a4e4fdcd060 that was already received
2018-01-27 20:04:18.648000 Peer sent entire transaction 7e993cf538694f971c2d8719
80a48536a9146759753c3b8f875cfd39c9e06eea that was already received

And a little different:

Code:

2018-01-27 20:07:54.564000 Peer sent entire transaction b83ee31d3b084065a25dc833
b7fbada8175d0bfd7a14fdf6f7e708d456440af7 that was already received
2018-01-27 20:07:54.626000 Peer sent entire transaction 269536ab6d4607784e22af15
7ddb86614d991e65bc9d30f06d2f2e14f051ce78 that was already received
2018-01-27 20:07:54.689000 Peer sent entire transaction 05edbd703433153f2dd96877
ce3728e3a015f80259c17506b18ed3be0a3dadc3 that was already received
2018-01-27 20:07:54.892000 Peer sent entire transaction 77626d6edcf878b4d54a2b29
d5023eb7a15fdced99f50846d9dc47d379f8e5d0 that was already received
2018-01-27 20:07:56.189000 Requesting parent share 117eacb2 from 37.194.10.30:93
35
2018-01-27 20:08:01.705000 Peer sent entire transaction a734b29c17743cc124a6f2da
7455b08b15703529fe05c4e51d715e92c9cde7a8 that was already received
2018-01-27 20:08:04.065000 P2Pool: 17339 shares in chain (11002 verified/17343 t
otal) Peers: 6 (0 incoming)
2018-01-27 20:08:04.065000  Local: 0H/s in last 0.0 seconds Local dead on arriva
l: ??? Expected time to share: ???
2018-01-27 20:08:04.065000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficie
ncy: ??? Current payout: (0.0000)=0.0000 BTC
2018-01-27 20:08:04.065000  Pool: 4722TH/s Stale rate: 7.0% Expected time to blo
ck: 27.4 days
2018-01-27 20:08:10.503000 Peer sent entire transaction dbc6fb53b5d15d58702b2d0b
fb65fc5140a34674afe6ea18e02a3aff0043231e that was already received
2018-01-27 20:08:10.534000 Peer sent entire transaction d972de2e8f11f1aaf683bd6f
779bdcf43e9af5efd9607e6cc4857d37684a5e97 that was already received
Unhandled error in Deferred:

2018-01-27 20:08:19.317000 Peer sent entire transaction 0cf9cd2c9e53de5da0110e4b
465f0c99597b5578a43d855826f9073e40d9b716 that was already received
2018-01-27 20:08:24.255000 Peer sent entire transaction 96ba9601f799a17fd74abf61
f9091bec6bf999bc611793c9311f043316c4c612 that was already received
2018-01-27 20:08:24.270000 Peer sent entire transaction da1ab9f2d023d0169a2886ab
1fb73b4e12def8915cefa51d622b2795a76e6ede that was already received
2018-01-27 20:08:37.084000 Peer sent entire transaction f59f8b1e486cd0f749806564
183a37859c5d3cee85e95a361cd01507a7733f6f that was already received
2018-01-27 20:08:37.100000 Peer sent entire transaction 2fcf5ba98d77553e55a2a23d
3a9fc0a6852166e734ca5b8aabe2dc4f022e565f that was already received
2018-01-27 20:08:37.116000 P2Pool: 17339 shares in chain (11002 verified/17343 t
otal) Peers: 6 (0 incoming)
2018-01-27 20:08:37.116000  Local: 0H/s in last 0.0 seconds Local dead on arriva
l: ??? Expected time to share: ???
2018-01-27 20:08:37.116000  Shares: 0 (0 orphan, 0 dead) Stale rate: ??? Efficie
ncy: ??? Current payout: (0.0000)=0.0000 BTC
2018-01-27 20:08:37.116000  Pool: 4722TH/s Stale rate: 7.0% Expected time to blo
ck: 27.4 days

[jtoomim]

Oh, this is on Bitcoin. I was looking on my Litecoin node. I see the error now.

Taking a brief glance at the code (node.py:53 and p2p.py:71), it looks like the "in handle_share_hashes: ... twisted.internet.defer.TimeoutError"  error happens when a peer takes longer than 15 seconds to reply to a request for a share and its parents. This will happen e.g. when one of your peers is saturating its CPU at 100% on one core. It does not mean there's a problem on your node. It just means that someone else has a problem.