ERROR: CheckBlockHeader() strikes again!

cryptogrinder

so I still see this in log ‘ERROR: CheckBlockHeader() : block with timestamp before last checkpoint’ and I’m on 0.9.6.1:

{
“version” : 90601,
“protocolversion” : 70005,
“walletversion” : 60000,
“balance” : 0.00000000,
“blocks” : 1876078,
“timeoffset” : 0,
“connections” : 17,
“proxy” : “”,
“difficulty” : 27.81805882,
“testnet” : false,
“keypoololdest” : 1504886606,
“keypoolsize” : 101,
“paytxfee” : 0.00000000,
“relayfee” : 0.01000000,
“errors” : “”
}

seems it was fully synced at that time (had blockchain from http://cryptochainer.com to sync faster) and also note that I’m using wellenreiter01’s PPA for debian

attaching logs: https://mega.nz/#!OE9kxDbL!Klw0y2LWZSbmBCkCNtizWrs1Mup16gQuZ6SoaEpMvtM

thanks for any help

Wellenreiter

This can happen, if a node connects and sends a block with an old timestamp.

Resons can be:

node from another coin connects and tries to send a block
- only if they use the message start strings, may happen, but rarely
a node on a shorter chain
- this will corrected automatically, as the other node will convert to the longer chain we are on later
badly coded other software

In general, these messages are seen and part of the protocol. As long as your node synchronizes correctly they can be ignored.

FlatBlack

@Wellenreiter said in ERROR: CheckBlockHeader() strikes again!:

node from another coin connects and tries to send a block
.
is this situation can be happened if running d ‘other coin’ mining-software n FTC-desktop wallet on d same computer on d same time…?
.
ex: Running d FTC-wallet while doing d Musicoin mining…
.
soori for askin this… :bow_tone1:

Wellenreiter

@FlatBlack said in ERROR: CheckBlockHeader() strikes again!:

is this situation can be happened if running d ‘other coin’ mining-software n FTC-desktop wallet on d same computer on d same time…?

ex: Running d FTC-wallet while doing d Musicoin mining…

soori for askin this…

No, it can’t be happen in that situation.
It only can happen, if another coins wallet uses the same TCP port and message start string as the Feathercoin wallet does, which means a very badly forked and implemented wallet.
The most common reason for this is a wallet sending a block while being on a side chain, which is shorter as the checkpointed chain your wallet is on. That client will be abandon the chain soon , that means the other client will detect the longer chain as part of the synchronization process and switch to that chain.

cryptogrinder

@Wellenreiter I still can not leave this error behind :[ the reason is that when I see this error in logs my node starts to act differently. I use it for mining. Had actually connected Nomp and also p2pool from your repo to it. So I turned off Nomp to be on a safe side since there is no more active development on it… recreated the node from scratch also rescanned couple times but logs are there again and my node acts strange. I also run other nodes from ltc, vtc in same environment (no problem with them). By strange I mean I got big reject ratio. The height of the block chain seems to be in sync when I checked against explorer. Here is output from nsgminer:

[13:45:35] Started at [2017-09-13 12:53:44]
[13:45:35] Pool: http://46.4.0.101:19327
[13:45:35] Run time: 0 hrs 51 mins 51 secs
[13:45:35] Average hash rate: 0.0112 MH/s
[13:45:35] Solved blocks: 0
[13:45:35] Best share difficulty: 443
[13:45:35] Queued work requests: 177
[13:45:35] Share submissions: 2
[13:45:35] Accepted shares: 2
[13:45:35] Rejected shares: 0
[13:45:35] Accepted diff1 shares: 38
[13:45:35] Rejected diff1 shares: 0
[13:45:35] Reject ratio: 0.0%
[13:45:35] Hardware errors: 0
[13:45:35] Efficiency (accepted shares * difficulty / 2 KB): 0.16
[13:45:35] Utility (accepted shares / min): 0.00/min
[13:45:35] Work Utility (diff1 shares accepted / min): 0.00/min

[13:45:35] Discarded work due to new blocks: 346
[13:45:35] Stale submissions discarded due to new blocks: 0
[13:45:35] Unable to get work from server occasions: 1
[13:45:35] Work items generated locally: 709
[13:45:35] Submitting work remotely delay occasions: 0
[13:45:35] New blocks detected on network: 51

[12:35:41] Started at [2017-09-13 12:21:56]
[12:35:41] Pool: stratum+tcp://cryptogrinder.com:19327
[12:35:41] Run time: 0 hrs 13 mins 45 secs

I’m also running other nodes like ltc, vtc on the same machine.
[12:35:41] Average hash rate: 0.0094 MH/s
[12:35:41] Solved blocks: 0
[12:35:41] Best share difficulty: 21
[12:35:41] Queued work requests: 42
[12:35:41] Share submissions: 560
[12:35:41] Accepted shares: 400
[12:35:41] Rejected shares: 160
[12:35:41] Accepted diff1 shares: 5
[12:35:41] Rejected diff1 shares: 2
[12:35:41] Reject ratio: 28.6%
[12:35:41] Hardware errors: 0
[12:35:41] Efficiency (accepted shares * difficulty / 2 KB): 0.04
[12:35:41] Utility (accepted shares / min): 0.01/min
[12:35:41] Work Utility (diff1 shares accepted / min): 0.00/min

[12:35:41] Discarded work due to new blocks: 16
[12:35:41] Stale submissions discarded due to new blocks: 1
[12:35:41] Unable to get work from server occasions: 32
[12:35:41] Work items generated locally: 195
[12:35:41] Submitting work remotely delay occasions: 0

Wellenreiter

The main difference I see is here:

you use http://46.4.0.101:19327

and on your node you use stratum+tcp://cryptogrinder.com:19327

This means, that you use different protocols between the p2pool server and your miner.

http://… means getblocktemplate is used

stratum+tcp:// means the stratum protocol is used.

The stratum protocol is newer, but also sometimes needs some tuning.
I don’t know nsgminer, so I can’t tell if it uses the extranonce extenion or not, but extranonce is not implemented on p2pool and therefore leads to errors.

Can you use http://cryptogrinder.com:19327 for a fast check, if the error rate goes down?

cryptogrinder

I tried without stratum+tcp:// but no help… actually I was mining with it before and was fine. Here’s the summary:

Summary of runtime statistics:

[12:53:25] Started at [2017-09-14 12:01:16]
[12:53:25] Pool: http://cryptogrinder.com:19327
[12:53:25] Run time: 0 hrs 52 mins 8 secs
[12:53:25] Average hash rate: 0.0094 MH/s
[12:53:25] Solved blocks: 0
[12:53:25] Best share difficulty: 14
[12:53:25] Queued work requests: 126
[12:53:25] Share submissions: 2860
[12:53:25] Accepted shares: 1897
[12:53:25] Rejected shares: 963
[12:53:25] Accepted diff1 shares: 19
[12:53:25] Rejected diff1 shares: 10
[12:53:25] Reject ratio: 33.7%
[12:53:25] Hardware errors: 0
[12:53:25] Efficiency (accepted shares * difficulty / 2 KB): 0.04
[12:53:25] Utility (accepted shares / min): 0.01/min
[12:53:25] Work Utility (diff1 shares accepted / min): 0.00/min

[12:53:25] Discarded work due to new blocks: 2
[12:53:25] Stale submissions discarded due to new blocks: 5
[12:53:25] Unable to get work from server occasions: 119
[12:53:25] Work items generated locally: 610
[12:53:25] Submitting work remotely delay occasions: 2
[12:53:25] New blocks detected on network: 42

running node locally at home seems fine… no checkblockheader at all…

cryptogrinder

can you try with ccminer or cgminer against my pool?.. maybe you could spot some weird stuff…

Wellenreiter

@cryptogrinder said in ERROR: CheckBlockHeader() strikes again!:

can you try with ccminer or cgminer against my pool?.. maybe you could spot some weird stuff…

Mining with sgminer now. No issues so far:

sgminer 5.1.0-dev-3-gfa9eb - Started: [2017-09-14 15:59:51] - [0 days 00:08:17]
--------------------------------------------------------------------------------
(4s):4.789K (avg):4.683Kh/s | A:46  R:0  HW:0  WU:0.852/m
ST: 0  SS: 0  NB: 8  LW: 496  GF: 0  RF: 0
Connected to cryptogrinder.com (stratum) diff 6.554 as user xxxxxxxxxxxxxxxxxx+0.0001
Block: 60deda4b...  Diff:1.82M  Started: [16:08:02]  Best share: 71

100% shares accepted so far (accepted 46 rejected 0)

Wellenreiter

I had my sgminer running for 39 minutes and no rejected shares at all.
Unfortunately I can’t get nsgminer working for neoscrypt on m system

update:

[17:18:44] Accepted 03da6390 Diff 0.260/0.153 GPU 0
[17:18:51] Accepted 02722cb1 Diff 0.409/0.153 GPU 0
[17:18:55] Accepted 014793ef Diff 0.781/0.153 GPU 0
[17:18:56] Accepted 039c1fed Diff 0.277/0.153 GPU 0
[17:18:57] Accepted 5510c1cb Diff 3.009/0.153 GPU 0
[17:19:02] Accepted 04d96299 Diff 0.206/0.153 GPU 0
[17:19:09] Accepted 05816d09 Diff 0.256/0.153 GPU 0
[17:19:13] Stratum connection to cryptogrinder.com interrupted
[17:19:13] cryptogrinder.com difficulty changed to 0.153
[17:19:18] Rejected 04bdd5b9 Diff 0.211/0.153 GPU 0
[17:19:20] Rejected 02651b9a Diff 0.418/0.153 GPU 0
[17:19:21] Rejected 03fd38c4 Diff 0.251/0.153 GPU 0
[17:19:23] Stratum connection to cryptogrinder.com interrupted
[17:19:23] cryptogrinder.com difficulty changed to 0.153
[17:19:28] Accepted 04fdf0b9 Diff 0.200/0.153 GPU 0
[17:19:34] Stratum connection to cryptogrinder.com interrupted
[17:19:34] cryptogrinder.com difficulty changed to 0.153
[17:19:42] Accepted 01a06e94 Diff 0.615/0.153 GPU 0
[17:19:42] Stratum connection to cryptogrinder.com interrupted
[17:19:42] cryptogrinder.com difficulty changed to 0.153

as you can see there are some rejected shares after an interrupted stratum connection.

My miner reports a rejection rate of 11.5% and your pool node reports a DOA of ~39%

Connection interruptions can be caused by the host you are running your p2pool node on, or connectivity problems to the pool node.

Wellenreiter

I just compared your p2pool version with the latest one on github, which is

v15.0-28-g6d59072

can you pull the latest version, do a ‘git checkout master’

and restart your pool?

There are some fixes in the latest version.

Wellenreiter

Stopped my miner now.

Final Statictics:

[17:33:32] Started at [2017-09-14 16:57:26]                    
[17:33:32] Pool: stratum+tcp://cryptogrinder.com:19327                    
[17:33:32] Runtime: 0 hrs : 36 mins : 6 secs                    
[17:33:32] Average hashrate: 2.4 Kilohash/s                    
[17:33:32] Solved blocks: 0                    
[17:33:32] Best share difficulty: 54                    
[17:33:32] Share submissions: 528                    
[17:33:32] Accepted shares: 434                    
[17:33:32] Rejected shares: 94                    
[17:33:32] Accepted difficulty shares: 67                    
[17:33:32] Rejected difficulty shares: 15                    
[17:33:32] Reject ratio: 17.8%                    
[17:33:32] Hardware errors: 0                    
[17:33:32] Utility (accepted shares / min): 12.03/min                    
[17:33:32] Work Utility (diff1 shares solved / min): 2.24/min
                
[17:33:32] Stale submissions discarded due to new blocks: 2                    
[17:33:32] Unable to get work from server occasions: 117                    
[17:33:32] Work items generated locally: 1823                    
[17:33:32] Submitting work remotely delay occasions: 2                    
[17:33:32] New blocks detected on network: 35

I think the reason for the high rejection rate are the interruptions miner to p2pool connection

cryptogrinder

pulled… restarted… here’s my output before restart:

[17:28:28] Stratum from pool 0 detected new block
[17:28:33] Rejected 64915371FFA30300x0 Diff 0.017/0.010 OCL 0
[17:28:35] Rejected 89FEF1681A1E0100x0 Diff 0.056/0.010 OCL 0
[17:28:36] The network difficulty has been set to 55348
[17:28:36] Stratum from pool 0 detected new block
[17:28:41] Rejected DB8E21281D3F0300x0 Diff 0.019/0.010 OCL 0
[17:28:42] Rejected B7D87F8A64E20500x0 Diff 0.011/0.010 OCL 0
[17:28:43] Rejected 2876E7D0C6F00000x0 Diff 0.066/0.010 OCL 0
[17:28:44] Rejected 8C5969D1C1200100x0 Diff 0.055/0.010 OCL 0
[17:28:44] Rejected 1D5183AA96410400x0 Diff 0.015/0.010 OCL 0
[17:28:45] Rejected 1BC0FD6F45F30300x0 Diff 0.016/0.010 OCL 0
[17:28:47] Rejected A1D2B7B2F4B20200x0 Diff 0.023/0.010 OCL 0
[17:28:47] Rejected CF5594B850070400x0 Diff 0.016/0.010 OCL 0
[17:28:48] Rejected D1100987CB250300x0 Diff 0.020/0.010 OCL 0
[17:28:48] Rejected 05052BE82C6C0100x0 Diff 0.044/0.010 OCL 0
[17:28:50] Rejected 04DE72E307800500x0 Diff 0.011/0.010 OCL 0
[17:28:50] Rejected E889072CFD9A0100x0 Diff 0.039/0.010 OCL 0
[17:28:52] Rejected 801262238E7B0500x0 Diff 0.011/0.010 OCL 0
[17:28:52] Rejected 8552131FF24A0000x0 Diff 0.213/0.010 OCL 0
[17:28:52] Rejected 1E43E92F84950400x0 Diff 0.014/0.010 OCL 0
[17:28:53] Rejected 1E1F61E97F1B0000x0 Diff 0.582/0.010 OCL 0
[17:28:53] Rejected 662F697BC92C0400x0 Diff 0.015/0.010 OCL 0
[17:28:54] Rejected 6ECAF47D541F0500x0 Diff 0.012/0.010 OCL 0
[17:28:54] Rejected F89EBF7D47BC0300x0 Diff 0.017/0.010 OCL 0
[17:28:55] Rejected DB862625BB020000x0 Diff 5.859/0.010 OCL 0
[17:28:55] Rejected 4424037FD01D0100x0 Diff 0.056/0.010 OCL 0
[17:28:57] Rejected 2FB7B6CB9EEB0500x0 Diff 0.011/0.010 OCL 0
[17:28:58] Rejected 98694B70E4200200x0 Diff 0.029/0.010 OCL 0
[17:28:58] Rejected 9047B9F2671C0000x0 Diff 0.563/0.010 OCL 0
[17:29:00] Rejected DC08286149C40100x0 Diff 0.035/0.010 OCL 0
[17:29:00] Rejected 9529270E5CB40200x0 Diff 0.023/0.010 OCL 0
[17:29:00] Rejected 563DE2657EB10300x0 Diff 0.017/0.010 OCL 0
[17:29:01] Rejected 553CF08427280400x0 Diff 0.015/0.010 OCL 0
[17:29:01] Rejected 52E92E4A92AE0300x0 Diff 0.017/0.010 OCL 0
[17:29:01] Rejected FB0A25159E480400x0 Diff 0.015/0.010 OCL 0
[17:29:02] Rejected DEE3E2C8683E0400x0 Diff 0.015/0.010 OCL 0
[17:29:02] Rejected B45C8DE51D6A0100x0 Diff 0.044/0.010 OCL 0
[17:29:02] Rejected 0EB30803A0CC0000x0 Diff 0.078/0.010 OCL 0
[17:29:02] Rejected AFA2AF7E0EF10300x0 Diff 0.016/0.010 OCL 0
[17:29:03] Rejected FE281D4A5EF30100x0 Diff 0.032/0.010 OCL 0
[17:29:03] Rejected 0AFBE293EB750400x0 Diff 0.014/0.010 OCL 0
[17:29:04] The network difficulty has been set to 63537
[17:29:04] Stratum from pool 0 detected new block
[17:29:10] Accepted 566A2FC054A10400x0 Diff 0.013/0.012 OCL 0
[17:29:10] Accepted 1A54F903102C0100x0 Diff 0.053/0.012 OCL 0
[17:29:10] Accepted 97951872BB360400x0 Diff 0.015/0.012 OCL 0
[17:29:11] Accepted EF5C70D3BC0E0200x0 Diff 0.030/0.012 OCL 0
[17:29:11] Accepted 5A4A97B8BCEF0300x0 Diff 0.016/0.012 OCL 0
[17:29:15] Pool 0 stale share detected, submitting as user requested
[17:29:15] Pool 0 stratum share submission failure
[17:29:15] The network difficulty has been set to 68076
[17:29:15] Stratum from pool 0 detected new block
[17:29:21] Pool 0 communication resumed, submitting work
[17:29:21] Rejected 5EFFC0A751EF0000x0 Diff 0.067/0.014 OCL 0
[17:29:21] Rejected 7BB750DF7FF60200x0 Diff 0.021/0.014 OCL 0
[17:29:23] Rejected EE9F27C7CC280300x0 Diff 0.020/0.014 OCL 0
[17:29:25] Rejected 1E7ED1DDEC440000x0 Diff 0.232/0.014 OCL 0
[17:29:27] Rejected D9CD224D743C0200x0 Diff 0.028/0.014 OCL 0
[17:29:28] Rejected A6CF638C84610400x0 Diff 0.014/0.014 OCL 0
[17:29:28] Rejected 581008EECD660400x0 Diff 0.014/0.014 OCL 0
[17:29:30] Rejected CD90DDA16E450000x0 Diff 0.230/0.014 OCL 0
[17:29:31] Rejected A456B62B00F70200x0 Diff 0.021/0.014 OCL 0
[17:29:35] Thread 0 being disabled U:0.03/m
[17:29:36]
Summary of runtime statistics:

[17:29:36] Started at [2017-09-14 17:26:55]
[17:29:36] Pool: http://cryptogrinder.com:19327
[17:29:36] Run time: 0 hrs 2 mins 40 secs
[17:29:36] Average hash rate: 0.0083 MH/s
[17:29:36] Solved blocks: 0
[17:29:36] Best share difficulty: 6
[17:29:36] Queued work requests: 11
[17:29:36] Share submissions: 139
[17:29:36] Accepted shares: 6
[17:29:36] Rejected shares: 133
[17:29:36] Accepted diff1 shares: 0
[17:29:36] Rejected diff1 shares: 1
[17:29:36] Reject ratio: 95.7%
[17:29:36] Hardware errors: 0
[17:29:36] Efficiency (accepted shares * difficulty / 2 KB): 0.00
[17:29:36] Utility (accepted shares / min): 0.00/min
[17:29:36] Work Utility (diff1 shares accepted / min): 0.00/min

[17:29:36] Discarded work due to new blocks: 0
[17:29:36] Stale submissions discarded due to new blocks: 1
[17:29:36] Unable to get work from server occasions: 9
[17:29:36] Work items generated locally: 50
[17:29:36] Submitting work remotely delay occasions: 1
[17:29:36] New blocks detected on network: 10

cryptogrinder

after restart and git pull the dao seems very low again

cryptogrinder

based on output it’s fine now… :) so thanks a lot. but not sure what was the problem… ?!

Summary of runtime statistics:

[12:39:24] Started at [2017-09-15 11:48:54]
[12:39:24] Pool: http://cryptogrinder.com:19327
[12:39:24] Run time: 0 hrs 50 mins 29 secs
[12:39:24] Average hash rate: 0.0117 MH/s
[12:39:24] Solved blocks: 0
[12:39:24] Best share difficulty: 28
[12:39:24] Queued work requests: 213
[12:39:24] Share submissions: 2981
[12:39:24] Accepted shares: 2963
[12:39:24] Rejected shares: 18
[12:39:24] Accepted diff1 shares: 33
[12:39:24] Rejected diff1 shares: 0
[12:39:24] Reject ratio: 0.6%
[12:39:24] Hardware errors: 0
[12:39:24] Efficiency (accepted shares * difficulty / 2 KB): 0.05
[12:39:24] Utility (accepted shares / min): 0.02/min
[12:39:24] Work Utility (diff1 shares accepted / min): 0.00/min

[12:39:24] Discarded work due to new blocks: 417
[12:39:24] Stale submissions discarded due to new blocks: 0
[12:39:24] Unable to get work from server occasions: 0
[12:39:24] Work items generated locally: 832
[12:39:24] Submitting work remotely delay occasions: 0
[12:39:24] New blocks detected on network: 47

Wellenreiter

@cryptogrinder said in ERROR: CheckBlockHeader() strikes again!:

but not sure what was the problem… ?!

It was a bug in the adaptive behavior of the p2pool software.

coutinho

This post is deleted!

cryptogrinder

@coutinho thanks for the info… very very helpful for ftc

@Wellenreiter just send you 100ftc as an appreciation… not much but at least smthng

Wellenreiter

@cryptogrinder

Many thanks :)

You also helped the community by bringing up the problem and verifying that the problem is fixed in the last p2pool code, so it’s on me to thank you.