You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Check the logs/console for this error: panic: Value missing for key ...
Expected behavior:
The node should restart without errors.
Actual behavior:
The node cannot restart due to this error: "panic: Value missing for key [...] corresponding to nodeKey ..." when the pruning settings are either pruning = default or pruning = everything. If you set pruning = nothing, the node succesfully restarts without any errors. Tested with both goleveldb and rocksdb db backends.
Hi @alienc0der, I get similar stack trace when replay blocks but Value missing for key [0 0 0 0 0 0 0 1 0 0 0 1] error hasn't occurred yet, would you mind share the app.toml and config.toml for reference?
I'm using rocksdb, but I get the same error when switching to goleveldb. The problem is the IAVL implementation because when I've switched to memiavl the issue didn't appear anymore.
System info:
Cronos version 1.4.0-rc3
Ubuntu
22.04
with8 cores
and16GB RAM
Ethermint commit e4d00df
Steps to reproduce:
pruning = default
orpruning = everything
panic: Value missing for key ...
Expected behavior:
The node should restart without errors.
Actual behavior:
The node cannot restart due to this error:
"panic: Value missing for key [...] corresponding to nodeKey ..."
when the pruning settings are eitherpruning = default
orpruning = everything
. If you setpruning = nothing
, the node succesfully restarts without any errors. Tested with bothgoleveldb
androcksdb
db backends.Additional info:
Full stack trace:
The text was updated successfully, but these errors were encountered: