Node stops syncing

[Ajaiswal2610]

Describe the bug
Node automatically stopped Syncing for no reason

:24:55.967] retaining ability to lookup full transaction history as archive mode is enabled
INFO [10-04|07:24:55.967] using existing jwt file filename=/home/user/.arbitrum/jwtsecret
INFO [10-04|07:24:55.967] Running Arbitrum nitro node revision=v3.2.1-d81324d vcs.time=2024-09-24T10:12:36-05:00
TRACE[10-04|07:24:55.967] sending RPC request method=eth_chainId logId=1 args=[]
INFO [10-04|07:24:55.968] rpc response method=eth_chainId logId=1 err="Post "http://localhost:8544\": dial tcp
INFO [10-04|07:25:01.975] retaining ability to lookup full transaction history as archive mode is enabled
INFO [10-04|07:25:01.975] using existing jwt file filename=/home/user/.arbitrum/jwtsecret
INFO [10-04|07:25:01.975] Running Arbitrum nitro node revision=v3.2.1-d81324d vcs.time=2024-09-24T10:12:36-05:00
TRACE[10-04|07:25:01.975] sending RPC request method=eth_chainId logId=1 args=[]
TRACE[10-04|07:25:01.977] rpc response method=eth_chainId logId=1 err= result=""0x1"" attempt=0 args=[]
INFO [10-04|07:25:01.977] connected to l1 chain l1url=http://localhost:8544 l1chainid=1
TRACE[10-04|07:25:01.977] sending RPC request method=eth_getCode logId=2 args="["0x0000000000000000000000000000000000000064", "latest"]"
TRACE[10-04|07:25:01.996] rpc response method=eth_getCode logId=2 err= result=""0x"" attempt=0 args="["0x0000000000000000000000000000000000000064", "latest"]"
INFO [10-04|07:25:01.997] Starting metrics server addr=http://127.0.0.1:6070/debug/metrics
TRACE[10-04|07:25:01.997] sending RPC request method=eth_call logId=3 args="[{"from":"0x0000000000000000000000000000000000000000","input":"0x8ee1a126","to":"0x5ef0d09d1e6204141b4d37530808ed19f60fba35"}, "latest"]"
TRACE[10-04|07:25:02.018] rpc response method=eth_call logId=3 err= result=""0x184884e1eb9fefdc158f6c8ac912bb183bf3cf83f0090317e0bc4ac5860baa39"" attempt=0 args="[{"from":"0x0000000000000000000000000000000000000000","input":"0x8ee1a126","to":"0x5ef0d09d1e6204141b4d37530808ed19f60fba35"}, "latest"]"
INFO [10-04|07:25:18.216] Using leveldb as the backing database
INFO [10-04|07:25:18.216] Allocated cache and file handles database=/home/user/.arbitrum/arb1/nitro/l2chaindata cache=16.00MiB handles=16 readonly=true
INFO [10-04|07:26:18.346] Using LevelDB as the backing database
INFO [10-04|07:26:18.346] Found legacy ancient chain path location=/home/user/.arbitrum/arb1/nitro/l2chaindata/ancient
DEBUG[10-04|07:26:18.371] Chain freezer table opened database=/home/user/.arbitrum/arb1/nitro/l2chaindata/ancient table=headers items=259,840,932 size=1.79GiB
Chain metadata
databaseVersion:
headBlockHash: 0x90f9efc6f3e66815e848de628437f33a31d36839c13112d9e926e5edd1b20b44
headFastBlockHash: 0x90f9efc6f3e66815e848de628437f33a31d36839c13112d9e926e5edd1b20b44
headHeaderHash: 0x90f9efc6f3e66815e848de628437f33a31d36839c13112d9e926e5edd1b20b44
lastPivotNumber:
len(snapshotSyncStatus): 0 bytes
snapshotDisabled: false
snapshotJournal: 888080 bytes
snapshotRecoveryNumber:
snapshotRoot: 0x9ae9fc50d2d8644c5f9136aefb1743be049973650cce51f1d2afc36fc4d24ed0
txIndexTail: 0 (0x0)

Usage of /usr/local/bin/nitro:
ERROR[10-04|07:26:18.668] error initializing database err="Failed to open database: freezer table(path: /home/user/.arbitrum/arb1/nitro/l2chaindata/ancient, name: hashes, num: 4) is corrupted"

[yorickdowne]

“Is corrupted” - did you have an unclean shutdown?

wipe the DB and start over. If it keeps happening you have a hardware issue most likely. On consumer gear I’d say RAM, in which case it’s a memtest86+ in continuous loop for 5 days to rule that out; but if this is a server with ECC the more likely culprit is failing storage, check smartctl -x