🔠OLD - Useful server commands
Check node info
After your node has been running for at least 30 minutes, run this command from your root folder to check the node info (Node version, Peer ID, Quil balance). For this to work, you need to setup the gRPC calls first. To go to the root folder, just type cd .
Check node version
If the "Check node info" command above do not work, you can check the node version by running:
Check node peer ID
If the "Check node info" command above do not work, you can check the node peer ID by running:
Console
Similar to "Node info", this will show basic info about your node.
Attach to existing tmux session
To detach from tmux press CTRL+B then release both keys and press D
Create tmux session + run node + detach from session: 1 step command
This is useful to quickly run then node in a session AFTER you have rebooted your server. Only RUN this after a reboot and if you have no tmux session already active.
The last part ~/scripts/qnode_restart.sh
will only work if you have run the auto-installer in this guide. Otherwise, you have to use GOEXPERIMENT=arenas go run ./...
Create cronjob to run the node automatically after a reboot
You only have to run this command once. This will set up a cronjob that will create your tmux session and run the node automatically after every reboot of your server. Shoutout to Peter Jameson (Quilibrium Discord community creator) for the script.
The last part ~/scripts/qnode_restart.sh
will only work if you have run the auto-installer in this guide. Otherwise, you have to use GOEXPERIMENT=arenas go run ./...
If you need to delete the crontab:
Open the crontab file for editing with crontab -e
Locate the line corresponding to the cron job you want to delete and delete it. Press CTRL+X, then Y to save, then ENTER
Kill node process
Use this in case you need to stop the node and kill the process
Empty "store" folder
CAREFUL: this will empty your "store" folder, only use it if you know what you are doing. Sometimes when you receive errors that you cannot debug, you can solve by killing the node process, emptying the store folder and starting the node again from scratch.
Backup keys.yml and config.yml to a root/backup folder
This may be useful if you have to clean up your ceremonyclient folder and don't want to download locally your config.yml and keys.yml. You can just back up them remotely on a root/backup folder and copy them again in the node folder later on.
Copy the files from your node folder to the root/backup folder
Copy the files back from root/backup to your node folder (a copy will also remain in the root/backup folder)
Check total nodes connected to the network
Install grpcURL
Run
Last updated