Skip to main content

Troubleshooting

Validator Recovery In Case Of Database Corruption:​

By following these steps, you can quickly recover your validator node, minimizing downtime and maintaining your participation in the consensus.

Stop the failed validator node​

sudo systemctl stop iota-node

Delete the database folders​

There are two database folders to delete, specified in your validator.yaml under the keys db-path: and consensus-config -> db-path:.

If you used default values for these folders, run this command to delete both folders at once:

rm -rf /opt/iota/db/*

If you customized them at setup, replace the previous paths with the ones you specified in validator.yaml under db-path: and consensus-config -> db-path:.

Restore from formal snapshot​

Follow the steps in this document:
https://docs.iota.org/operator/validator-node/configs/snapshots#restoring-from-formal-snapshots

Start the validator node​

sudo systemctl start iota-node

Let the validator sync all databases (including consensus_db) and monitor recovery progress:​

sudo journalctl -fu iota-node

See also https://docs.iota.org/operator/validator-node/monitoring.