synchronization problems

[chlorocryptos]

Describe the issue

blockchain synchronization does not start/proceed when the client version 1.3.1 starts up.

synchronization can be triggered to start, when the command 'reconsiderblock ' is issued, using the block hash marked active from 'getchaintips' . once the synchronization reachs a certain point (endpoint of pre-loaded headers ?) it hangs again. according to the log the chain becomes regarded as invalid and the connecting nodes marked as misbehaving, although the blocks are valid in the block explorer. then only a restart of the client and repetition of the above commands will facilitate further synchronization. neither a reindex, nor a full download of the blockchain was able to change this behaviour...

Log file snippet

2019-09-12 15:54:59 UpdateTip: new best=2f3fab8eb25017ca575f7420a721b79c00fc476ab9e56b706b3c73cc3da4cd0f height=1477910 log2_trust=52.576683 tx=2956056 date=2019-09-12 15:23:02 progress=0.999985 cache=8.2MiB(26569tx) moneysupply=46938708.11896718 2019-09-12 15:54:59 uint256HashMap:Set(1251/2048) data=64 sz=131072 2019-09-12 15:54:59 ERROR: GetKernelStakeModifier() : reached best block 2f3fab8eb25017ca575f7420a721b79c00fc476ab9e56b706b3c73cc3da4cd0f at height 1477910 from block 9876a81174a603c4076f040a51c8045a46d86b64763dc9ebe47fc627207c0ec2 2019-09-12 15:54:59 ERROR: CheckProofOfStake() : INFO: check kernel failed on coinstake 2ffd9445334e8ea70d364a697e26e13042666c4f2c7d9b88abfcd14fd782c2b9, hashProof=0000000000000000000000000000000000000000000000000000000000000000 2019-09-12 15:54:59 WARNING: ppcoinContextualBlockChecks: check proof-of-stake failed for block 61bac36357043a75848aef6f91b0a4fc03382961b9bf195e803f8f66586229a9 2019-09-12 15:54:59 ERROR: ConnectBlock: Consensus::ppcoinContextualBlockChecks failed: (code 0) 2019-09-12 15:54:59 Misbehaving: 51.15.120.57:16662 (0 -> 1) 2019-09-12 15:54:59 InvalidChainFound: invalid block=61bac36357043a75848aef6f91b0a4fc03382961b9bf195e803f8f66586229a9 height=1477911 log2_trust=52.576683 date=2019-09-12 15:26:17 moneysupply=0.00 2019-09-12 15:54:59 InvalidChainFound: current best=2f3fab8eb25017ca575f7420a721b79c00fc476ab9e56b706b3c73cc3da4cd0f height=1477910 log2_trust=52.576683 date=2019-09-12 15:23:02 moneysupply=0.00 2019-09-12 15:54:59 ERROR: ConnectTip() : ConnectBlock 61bac36357043a75848aef6f91b0a4fc03382961b9bf195e803f8f66586229a9 failed 2019-09-12 15:54:59 InvalidChainFound: invalid block=61bac36357043a75848aef6f91b0a4fc03382961b9bf195e803f8f66586229a9 height=1477911 log2_trust=52.576683 date=2019-09-12 15:26:17 moneysupply=0.00 2019-09-12 15:54:59 InvalidChainFound: current best=2f3fab8eb25017ca575f7420a721b79c00fc476ab9e56b706b3c73cc3da4cd0f height=1477910 log2_trust=52.576683 date=2019-09-12 15:23:02 moneysupply=0.00 2019-09-12 15:55:13 ERROR: AcceptBlockHeader : prev block invalid 2019-09-12 15:55:13 Misbehaving: 95.216.169.129:16662 (0 -> 100) BAN THRESHOLD EXCEEDED 2019-09-12 15:55:13 ERROR: invalid header received 2019-09-12 15:55:13 ProcessMessage(headers, 87 bytes) FAILED peer=2 2019-09-12 15:55:14 ThreadSocketHandler -- removing node: peer=2 addr=95.216.169.129:16662 nRefCount=1 fNetworkNode=1 fInbound=0ERROR: AcceptBlockHeader : prev block invalid 2019-09-12 15:55:14 Misbehaving: [2a01:4f9:c010:2187::1]:16662 (0 -> 100) BAN THRESHOLD EXCEEDED 2019-09-12 15:55:14 ERROR: invalid header received 2019-09-12 15:55:14 ProcessMessage(headers, 87 bytes) FAILED peer=1 2019-09-12 15:55:14 ThreadSocketHandler -- removing node: peer=1 addr=[2a01:4f9:c010:2187::1]:16662 nRefCount=1 fNetworkNode=1 fInbound=0ERROR: AcceptBlockHeader : prev block invalid 2019-09-12 15:55:14 Misbehaving: 51.15.120.57:16662 (1 -> 101) BAN THRESHOLD EXCEEDED 2019-09-12 15:55:14 ERROR: invalid header received

What platform are you using (Linux, Windows, Mac)

Windows 7, 64 bit

[chlorocryptos]

ok, this issue seems to be resolved with version 1.3.2. the 1.3.2 client syncs and stakes without problems. thanks

[AmirAbrams]

Thanks for reporting back.