Rewinding blockchain to block after v1.0.11 release

[bert2002]

System information

docker build of v1.0.11 with the official Dockerfile.

Expected behavior

After upgrading from v1.0.9 to v1.0.11 I am getting this error message on testnet:

Rewinding chain to upgrade configuration err="mismatching Shanghai fork timestamp in database (have timestamp 0, want timestamp 824638241048, rewindto timestamp 1702972799)"

and afterwards it starts rewinding:

...
Rewound to block with state              number=20,326,828 hash=0381f1..cab498
Rewound to block with state              number=20,173,744 hash=25c953..46d6a7
...

Is this an expected behavior?

Thanks,
bert

[charles2023wood]

Download the latest version, and have a try.

[bert2002]

Using the new .12 release now and downloading state. Will monitor the progress ⚡

[bert2002]

Hi,
it seems to be syncing, but it never finishes chain download and does repeatedly this:

Nov 12 02:17:32  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:32.330] Rewinding blockchain to block            target=24,901,289
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:32.648] Loaded most recent local header          number=24,901,289 hash=e9b6b3..935586 hash=778d19..0fced9 td=49,742,754 age=1h42m37s
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:32.648] Loaded most recent local block           number=0          hash=d90508..5c034a root=c5b395..466df8 td=1          age=3y1w4d
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:32.648] Loaded most recent local snap block      number=24,901,289 hash=e9b6b3..935586 root=778d19..0fced9 td=49,742,754 age=1h42m37s
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:32.648] Loaded last snap-sync pivot marker       number=24,903,273
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:32.648] Rolled back chain segment                header=24903338->24901289 snap=24903273->24901289 block=0->0 reason="syncing canceled (requested)"
Nov 12 02:17:32  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:32.648] Synchronisation failed, retrying         peer=fe5f8c66c2d325a6628d668cda11d18998b6e45c921563a8512732bf7ca20284 err="non existent state [6457f1eb..]"
Nov 12 02:17:46  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:46.461] Disabling direct-ancient mode            origin=24,901,289 ancient=24,669,169
Nov 12 02:17:46  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:46.461] Syncing: state healing in progress       accounts=634,[email protected] slots=600,[email protected] [email protected] nodes=9,269,[email protected]    pending=1
Nov 12 02:17:47  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:47.649] Syncing: chain download in progress      synced=99.99%  chain=35.19GiB headers=24,903,[email protected] bodies=24,901,[email protected] receipts=24,901,[email protected] eta=1h39m29.817s
Nov 12 02:17:48  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:48.650] Syncing: state healing in progress       accounts=634,[email protected] slots=600,[email protected] [email protected] nodes=9,269,[email protected]    pending=98
Nov 12 02:17:48  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:48.778] Unexpected trienode heal packet          peer=d565b56b reqid=7,159,287,470,360,294,334
Nov 12 02:17:51  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:51.938] Syncing: state healing in progress       accounts=634,[email protected] slots=600,[email protected] [email protected] nodes=9,269,[email protected]    pending=0
Nov 12 02:17:51  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:51.939] Rewinding blockchain to block            target=24,901,296
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:52.234] Loaded most recent local header          number=24,901,296 hash=a11909..ec79ae hash=9b6a8b..18fa91 td=49,742,768 age=1h42m36s
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:52.234] Loaded most recent local block           number=0          hash=d90508..5c034a root=c5b395..466df8 td=1          age=3y1w4d
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:52.234] Loaded most recent local snap block      number=24,901,296 hash=a11909..ec79ae root=9b6a8b..18fa91 td=49,742,768 age=1h42m36s
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | INFO [11-12|02:17:52.234] Loaded last snap-sync pivot marker       number=24,903,279
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:52.234] Rolled back chain segment                header=24903345->24901296 snap=24903279->24901296 block=0->0 reason="syncing canceled (requested)"
Nov 12 02:17:52  coredao[302690]: coredao-core-1  | WARN [11-12|02:17:52.234] Synchronisation failed, retrying         peer=3fa943726c913366a34cebef5606494c220d32b8503c75f02b784164c25163b9 err="non existent state [5709d1c9..]"
Nov 12 02:18:05  coredao[302690]: coredao-core-1  | INFO [11-12|02:18:05.433] Disabling direct-ancient mode            origin=24,901,296 ancient=24,669,169
Nov 12 02:18:05  coredao[302690]: coredao-core-1  | INFO [11-12|02:18:05.433] Syncing: state healing in progress       accounts=634,[email protected] slots=600,[email protected] [email protected] nodes=9,269,[email protected]    pending=1

Any idea why it would rollback?

Thanks,
bert

[charles2023wood]

Do you update the config file from mainnet.zip from https://github.com/coredao-org/core-chain/releases/tag/v1.0.12 Steffen ***@***.***> 于2024年11月12日周二 10:19写道：

…

Hi, it seems to be syncing, but it never finishes chain download and does repeatedly this: Nov 12 02:17:32 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:32.330] Rewinding blockchain to block target=24,901,289 Nov 12 02:17:32 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:32.648] Loaded most recent local header number=24,901,289 hash=e9b6b3..935586 hash=778d19..0fced9 td=49,742,754 age=1h42m37s Nov 12 02:17:32 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:32.648] Loaded most recent local block number=0 hash=d90508..5c034a root=c5b395..466df8 td=1 age=3y1w4d Nov 12 02:17:32 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:32.648] Loaded most recent local snap block number=24,901,289 hash=e9b6b3..935586 root=778d19..0fced9 td=49,742,754 age=1h42m37s Nov 12 02:17:32 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:32.648] Loaded last snap-sync pivot marker number=24,903,273 Nov 12 02:17:32 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:32.648] Rolled back chain segment header=24903338->24901289 snap=24903273->24901289 block=0->0 reason="syncing canceled (requested)" Nov 12 02:17:32 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:32.648] Synchronisation failed, retrying peer=fe5f8c66c2d325a6628d668cda11d18998b6e45c921563a8512732bf7ca20284 err="non existent state [6457f1eb..]" Nov 12 02:17:46 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:46.461] Disabling direct-ancient mode origin=24,901,289 ancient=24,669,169 Nov 12 02:17:46 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:46.461] Syncing: state healing in progress ***@***.*** ***@***.*** ***@***.*** ***@***.*** pending=1 Nov 12 02:17:47 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:47.649] Syncing: chain download in progress synced=99.99% chain=35.19GiB ***@***.*** ***@***.*** ***@***.*** eta=1h39m29.817s Nov 12 02:17:48 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:48.650] Syncing: state healing in progress ***@***.*** ***@***.*** ***@***.*** ***@***.*** pending=98 Nov 12 02:17:48 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:48.778] Unexpected trienode heal packet peer=d565b56b reqid=7,159,287,470,360,294,334 Nov 12 02:17:51 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:51.938] Syncing: state healing in progress ***@***.*** ***@***.*** ***@***.*** ***@***.*** pending=0 Nov 12 02:17:51 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:51.939] Rewinding blockchain to block target=24,901,296 Nov 12 02:17:52 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:52.234] Loaded most recent local header number=24,901,296 hash=a11909..ec79ae hash=9b6a8b..18fa91 td=49,742,768 age=1h42m36s Nov 12 02:17:52 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:52.234] Loaded most recent local block number=0 hash=d90508..5c034a root=c5b395..466df8 td=1 age=3y1w4d Nov 12 02:17:52 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:52.234] Loaded most recent local snap block number=24,901,296 hash=a11909..ec79ae root=9b6a8b..18fa91 td=49,742,768 age=1h42m36s Nov 12 02:17:52 coredao[302690]: coredao-core-1 | INFO [11-12|02:17:52.234] Loaded last snap-sync pivot marker number=24,903,279 Nov 12 02:17:52 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:52.234] Rolled back chain segment header=24903345->24901296 snap=24903279->24901296 block=0->0 reason="syncing canceled (requested)" Nov 12 02:17:52 coredao[302690]: coredao-core-1 | WARN [11-12|02:17:52.234] Synchronisation failed, retrying peer=3fa943726c913366a34cebef5606494c220d32b8503c75f02b784164c25163b9 err="non existent state [5709d1c9..]" Nov 12 02:18:05 coredao[302690]: coredao-core-1 | INFO [11-12|02:18:05.433] Disabling direct-ancient mode origin=24,901,296 ancient=24,669,169 Nov 12 02:18:05 coredao[302690]: coredao-core-1 | INFO [11-12|02:18:05.433] Syncing: state healing in progress ***@***.*** ***@***.*** ***@***.*** ***@***.*** pending=1 Any idea why it would rollback? Thanks, bert — Reply to this email directly, view it on GitHub <#39 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/A52Q2X2VVB7SGLJGS2J6HRL2AFQSNAVCNFSM6AAAAABP6DQWJKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINRZGQ2TKNZRGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[bert2002]

@charles2023wood this is testnet, but let me compare the configuration files.

Update: is identically, except logging we do to stdout

[bert2002]

Trying a full sync now, but it cant find an archive node I guess.

Nov 14 09:06:49 coredao[336701]: coredao-core-1  | WARN [11-14|09:06:49.343] Synchronisation failed, dropping peer    peer=d565b56b7033c544516797f163342e372a83cc0f524a858e8282005d55f77bd9 err="retrieved hash chain is invalid: missing parent"