Describe the bug
I started the node with nitro-pruned snapshot, after compacting database log the node has been stacked with message.
Head state missing, repairing number=205,131,834 hash=146360..8773da snaproot=b97cfc..c48be4
This message not goes away, more then 2-4 hours. And node does not accept calls.
nmap 10.1.0.5 -p 8547
Starting Nmap 7.93 ( https://nmap.org ) at 2024-05-07 16:25 +04
Nmap scan report for 10.1.0.5
Host is up (0.00012s latency).
PORT STATE SERVICE
8547/tcp closed unknown
Nmap done: 1 IP address (1 host up) scanned in 0.41 seconds
But if using archive mode thats works fine. Without errors.
To Reproduce
Get the snapshot from docs, prepare docker-compose.yml
Pruning takes a lot of time, even on a recently pruned database. Archive mode doesn't prune, so doesn't have the delay. Node cannot serve calls during pruning
Describe the bug I started the node with nitro-pruned snapshot, after compacting database log the node has been stacked with message.
Head state missing, repairing number=205,131,834 hash=146360..8773da snaproot=b97cfc..c48be4
This message not goes away, more then 2-4 hours. And node does not accept calls.
But if using archive mode thats works fine. Without errors.
To Reproduce Get the snapshot from docs, prepare docker-compose.yml
mkdir -p ./volumes/arbitrum
chmod -R 777 ./volumes/arbitrum
docker-compose up -d && docker-compose logs -f
Expected behavior I am expecting the correct sync of node and starts to accept calls.
Additional context Logs here arb-node-log.txt