Node Maintenance
Stopping the Node
To temporarily stop your validator node, select option 7 "Stop validator node" from the menu.
This will stop all containers but preserve your data.
You can start the node again using option 6.
Shutting Down the Node
Select option 8 "Shutdown validator node" from the menu to shut down your node.
This effectively does the same as stopping but is used when you want to emphasize a full shutdown.
Cleaning Up Node Data
Select option 9 "Cleanup validator node" from the menu to completely remove all node data.
β οΈ WARNING: This will delete all blockchain data and you will need to sync from scratch again! This operation cannot be undone.
Your validator keys will be preserved, but all sync progress and blockchain data will be deleted.
After cleaning, you will need to reinitialize the node before starting it again.
How to Restart and Resync Your BLOCX Node from Zero
Follow these steps to completely restart your node and resync it from scratch:
Step 0: Stop the Node
Before making any changes, make sure your node is stopped.
Step 1: Edit the Docker Compose File
Open this file in a text editor:
Find the line starting with command: and add the following line directly after line 50:
--purge-db-force
This line forces the node to delete all existing blockchain data and restart syncing from zero.
Step 2: Restart the Node
Run the following command to restart your node:
./initExecution.sh
This will start your node and begin resyncing from the very beginning.
Step 3: Remove the Purge Command
β οΈ Important: After the node has started syncing successfully, remove the --purge-db-force line from the compose-validator.yaml file.
If you leave it in, your node will always reset and resync from scratch every time it restarts, which you donβt want.
Last updated