Replies: 1 comment
-
Hi, if those are the only logs you're seeing on startup, it's very likely that your disk is bottlenecked/slow, so truncating is taking a long time. I'd recommend double checking your node hardware specs to make sure you meet the required hardware (i.e., see here: https://aptos.dev/network/nodes/full-node/pfn-requirements), and try provisioning more IOPS for your disk. Can you give it a try and follow up? 😄 |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Discord user ID
darin6559
Describe your question in detail.
Hey team,
My Aptos mainnet archive node has stopped syncing and is failing to serve any requests. The logs show repeated messages like:
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
I'm already running version v1.32.2.
Any idea how to fix this?
What error, if any, are you getting?
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
Truncating State Merkle DB.: current: 3105741380, target: 3105734073
What have you tried or looked at? Or how can we reproduce the error?
i have restart the nodes multiple times, its still the same
Which operating system are you using?
Linux (Ubuntu, Fedora, Windows WSL, etc.)
Which SDK or tool are you using? (if any)
Python SDK
Describe your environment or tooling in detail
using official docker image from https://github.com/aptos-labs/aptos-core/releases/tag/aptos-node-v1.32.2
Beta Was this translation helpful? Give feedback.
All reactions