frequent new node setup needed

[marcelkb]

Summary

Since the v4 release i had it 2 times already, that i needed to completly setup my node again (corrupted) with snapshot. months before it was stable and only be needed by node upgrade.
both nodes on win11 and linux (rasp) had the problem on the same timeframe. last one yesterday morning (Saturday, 16.12. in the night in german time). the one before on 7.12

Maybe it connects to the futureswap handling?

Environment

• Node Version: 4.0.0 (win), 4.0.3 (linux, raspberry 4 with ubuntu, 4 GB, (GB Swap file)

Logs

2023-12-07T13:10:24Z ERROR: ConnectBlock: Incorrect EVM block hash in coinbase output
2023-12-07T13:10:25Z ERROR: AcceptBlockHeader: block 75f9cd4634614e590c8ca447f0ed7f08f55ebf3374cf4e1746956f84a0eb085b is marked invalid
2023-12-07T15:59:26Z ERROR: AcceptBlockHeader: block a0c46385f56d678a8a7be27a0bad79438618f1aef8307fc83739e5337894550c is marked invalid

2023-12-16T09:40:52Z ERROR: ConnectBlock: Incorrect EVM block hash in coinbase output
2023-12-16T09:40:52Z InvalidChainFound: invalid block=462966d2f463cf4d7aad26c2d0f3a82d0e64ef2a66fd8861781f5edba04edacc height=3547281 log2_work=88.003427 date=2023-12-15T14:57:08Z
2023-12-16T09:40:52Z InvalidChainFound: current best=02b3b7b95b849f34de063535f4c7c2c40ce38ac23fd0113055dabd38f5813777 height=3547280 log2_work=88.003427 date=2023-12-15T14:58:18Z
2023-12-16T09:40:52Z ERROR: ConnectBlock 462966d2f463cf4d7aad26c2d0f3a82d0e64ef2a66fd8861781f5edba04edacc failed, (code 16)
2023-12-16T09:40:52Z InvalidChainFound: invalid block=f92e842dad33b68210b6930c8abfb49be828bb305abdc268274bcf8de1355edd height=3547312 log2_work=88.003454 date=2023-12-15T15:14:27Z
2023-12-16T09:40:52Z InvalidChainFound: current best=02b3b7b95b849f34de063535f4c7c2c40ce38ac23fd0113055dabd38f5813777 height=3547280 log2_work=88.003427 date=2023-12-15T14:58:18Z

2023-12-16T09:40:53Z ERROR: AcceptBlockHeader: prev block invalid
2023-12-16T09:40:53Z ERROR: AcceptBlockHeader: block 0c8595fc2740d9783eb9a15ea4f5cf46398be51ef2c774e9f5fab4e2a66b5117 is marked invalid

[prasannavl]

I expect this was probably related to corrupt data / snapshots. EVM dataset corruption was in particular not integrity checked by the node in earlier versions to fail early indicating data corruption, which would result in block being invalidated. Later versions should be smarter to detect this on startup.

Please feel free to open re-open the issue in-case you continue to experience these in later versions.