search

mantlenetworkio / mantle

Mantle | Mass adoption of decentralized & token-governed technologies. With Mantle Network, Mantle Treasury, and token holder-governed products initiatives.
https://www.mantle.xyz
MIT License
226 stars 101 forks source link

Crash at block 49402524 #1403

Closed fafrd closed 7 months ago

fafrd commented 8 months ago

I followed the v2 setup guide here: https://github.com/mantlenetworkio/networks/blob/main/run-node-mainnetv2.md. I'm using mantle-archive.20240315.tar.zst downloaded from s3.

My node always seems to crash at mantle block 49402524 (mainnet ethereum block 19062054)

I've tried against both a local Erigon ethereum node and Alchemy public eth node.

Node with docker-compose -f docker-compose-mainnetv2.yml up -d

replica_1  | INFO [03-14|01:38:33.837] indexed transaction                      index=49402521 next=49402521
replica_1  | INFO [03-14|01:38:33.837] CheckUpgrade                             chain id=5000
replica_1  | INFO [03-14|01:38:33.838] New block                                index=49402521 l1-timestamp=1705924537 l1-blocknumber=19062054 tx-hash=0x97bd9b57333edb10d126233c6bd0e4c4ae5f8012a766f64887819ee3c37daab8 queue-orign=sequencer gas=117148   fees=5.8574e-06      elapsed=1.279ms
replica_1  | INFO [03-14|01:38:33.910] indexed transaction                      index=49402522 next=49402522
replica_1  | INFO [03-14|01:38:33.911] CheckUpgrade                             chain id=5000
replica_1  | INFO [03-14|01:38:33.912] New block                                index=49402522 l1-timestamp=1705924542 l1-blocknumber=19062054 tx-hash=0xb770e3ffe29c2a5a0acf36381dc33dc965d02d662ec734c8d528b1ca3bd12561 queue-orign=sequencer gas=116748   fees=5.8374e-06      elapsed=1.402ms
replica_1  | INFO [03-14|01:38:33.983] indexed transaction                      index=49402523 next=49402523
replica_1  | INFO [03-14|01:38:33.983] CheckUpgrade                             chain id=5000
replica_1  | INFO [03-14|01:38:33.984] New block                                index=49402523 l1-timestamp=1705924542 l1-blocknumber=19062054 tx-hash=0xddd3f14e7cf74d330e8cc25fd9b17c99fa7a8c1669118a8e75b1829c3edf788e queue-orign=sequencer gas=117491   fees=5.87455e-06     elapsed=1.370ms
replica_1  | INFO [03-14|01:38:34.056] indexed transaction                      index=49402524 next=49402524
replica_1  | INFO [03-14|01:38:34.056] CheckUpgrade                             chain id=5000
replica_1  | INFO [03-14|01:38:34.057] New block                                index=49402524 l1-timestamp=1705924542 l1-blocknumber=19062054 tx-hash=0x934dea3850de4c8db1c3694c6f53d4d2b0d914124f2364ee229850f97aefee9b queue-orign=sequencer gas=139964   fees=6.9982e-06      elapsed=1.384ms
replica_1  | INFO [03-14|01:38:34.062] Got interrupt, shutting down...
replica_1  | INFO [03-14|01:38:34.065] WebSocket endpoint closed                url=ws://0.0.0.0:8546
replica_1  | INFO [03-14|01:38:34.066] HTTP endpoint closed                     url=http://0.0.0.0:8545
replica_1  | INFO [03-14|01:38:34.068] Blockchain manager stopped
replica_1  | INFO [03-14|01:38:34.068] Transaction pool stopped
replica_1  | INFO [03-14|01:38:34.129] indexed transaction                      index=49402525 next=0
replica_1  | ERROR[03-14|01:38:34.133] Could not verify                         error="Verifier cannot sync transactions with BackendL2: Verifier cannot sync transactions with backend l2: Cannot sync transactions with backend l2: Cannot apply transaction: Received tx at index 49402525 when looking for 0"
replica_1  | INFO [03-14|01:38:34.203] SyncService sync                         nextIndex=0        latestIndex=60985434
replica_1  | INFO [03-14|01:38:34.203] Syncing transaction range                start=0        end=60985434 backend=l2
replica_1  | INFO [03-14|01:38:34.273] indexed transaction                      index=0        next=0
replica_1  | ERROR[03-14|01:38:34.273] Timestamp monotonicity violation         hash=0x628dfc1672ce02095ff53e2b2a6337ac1605bc850b1fc2889f591d71de07f851 latest=1705924542 tx=1688314886
replica_1  | ERROR[03-14|01:38:34.273] Blocknumber monotonicity violation       hash=0x628dfc1672ce02095ff53e2b2a6337ac1605bc850b1fc2889f591d71de07f851 new=17607410 old=19062054
replica_1  | CRIT [03-14|01:38:34.273] Failed to store index                    err="leveldb: closed"
fafrd commented 7 months ago

This was because I was still running the v1 node without realizing, oops. Closing