-
Notifications
You must be signed in to change notification settings - Fork 983
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Genesis File Corruption in Namada Dry Run Node #4073
Comments
Seem to actually be due to running out of disk space, although I have another 57G of free space on that partition:
|
its probably due to rocksdb compaction. It requires double the amount of storage used. So if namada is using 100gb for db, it requires another 100gb to be free. |
Looks like this could be it |
Bug Report: Genesis File Corruption in Namada Dry Run Node
Description:
Genesis file at
/nvme/namada_dryrun/namada-dryrun.abaaeaf7b78cb3ac/cometbft/config/genesis.json
is truncated mid-line, causing node crash with deserialization error.Symptoms:
Couldn't deserialize the genesis file: Error("EOF while parsing a string", line: 30
"value": "AAECAwQ
ERROR namada_node::abortable: Abortable spawner error: task 64 panicked
Context:
System Info:
Impact:
Node cannot start, preventing network participation and balance queries.
namada-debug-20241121_140726.zip
Attached logs collected with the Debug Collector
The text was updated successfully, but these errors were encountered: