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:
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.