Quilibrium.one
SocialOfficial
Quilibrium Node Guide
Quilibrium Node Guide
  • 🖖Introduction
  • ✅Safety checks
  • đŸ“ŖAnnouncements
  • 🔗Links & Info
  • đŸ’ģBest server providers
  • đŸ’ģHardware requirements
  • 😎Q1 - Node Manager
  • ⚡Node Auto-installer
  • âŦ†ī¸Updating your node
  • âœ”ī¸Check your node info
  • 🔑Backup your private keys
  • đŸ“ĻBackup your node
  • 🔁Set up the gRPC calls
  • đŸ› ī¸Tools and scripts
  • 🔧Extra tools
  • 🔠Useful commands
  • â‰ī¸Troubleshooting
  • 📌Tutorials
    • Node
      • đŸ”ĸNode step by step installation
      • đŸŗInstalling the node on Docker
      • đŸĒŸInstalling the node and the qclient on Windows WSL
      • â†—ī¸Migrating the node to a new server
      • â„šī¸Running the node via binary file
      • Running a node cluster
      • ✅Reinstalling the node from scratch
      • âš™ī¸Managing your system resources
        • â˜‘ī¸Limiting your vCores usage
        • â˜‘ī¸Limiting your CPU usage
        • â˜‘ī¸Limiting the RAM assigned to each vCore
      • 🔄Switching from tmux to service
      • 💲Log your node balance every 1 hour
      • 🩷Escaping the "Pink Screen of Death"
      • 🔒Set up SSH keys
      • 🔒Creating a root login access
      • 👀Renting Servers Unveiled: Exploring Types and Processor Terminology
    • Qclient
      • Qclient commands
      • How to transfer QUIL
      • How to Bridge QUIL to WQUIL
      • How to retrieve your coin address after a failed bridging operation
  • 📂Archive
    • ⚡OLD - Node Auto-installer
    • đŸ”ĸOLD - Node step by step installation
    • 🔠OLD - Useful server commands
    • â‰ī¸OLD Troubleshooting
    • âŦ†ī¸OLD Updating your node
    • ⚡Importing an existing store folder for fast sync
    • â˜‘ī¸Changing the cpulimit value in release_autorun
  • âš ī¸Work in progress
  • 💜Want to say thank you?
Powered by GitBook
On this page
  • Check node info
  • Check node version
  • Check node peer ID
  • Console
  • Attach to existing tmux session
  • Create tmux session + run node + detach from session: 1 step command
  • Create cronjob to run the node automatically after a reboot
  • Kill node process
  • Empty "store" folder
  • Backup keys.yml and config.yml to a root/backup folder
  • Check total nodes connected to the network
  1. Archive

OLD - Useful server commands

PreviousOLD - Node step by step installationNextOLD Troubleshooting

Last updated 1 year ago

If you are looking for commands to transfer QUIL tokens, please

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 first. To go to the root folder, just type cd .

cd ~/ceremonyclient/node && GOEXPERIMENT=arenas go run ./... -node-info

Check node version

If the "Check node info" command above do not work, you can check the node version by running:

cat ~/ceremonyclient/node/config/version.go | grep -A 1 'func GetVersion() \[\]byte {' | grep -Eo '0x[0-9a-fA-F]+' | xargs printf '%d.%d.%d'

Check node peer ID

If the "Check node info" command above do not work, you can check the node peer ID by running:

cd ~/ceremonyclient/node && GOEXPERIMENT=arenas go run ./... -peer-id

Console

Similar to "Node info", this will show basic info about your node.

cd ~/ceremonyclient/node && GOEXPERIMENT=arenas go run ./... --db-console

Attach to existing tmux session

tmux a -t quil

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 ./...

tmux new-session -d -s quil 'export PATH=$PATH:/usr/local/go/bin && cd ~/ceremonyclient/node && ~/scripts/qnode_restart.sh'

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 ./...

echo "@reboot sleep 10 && tmux new-session -d -s quil 'export PATH=\$PATH:/usr/local/go/bin && cd ~/ceremonyclient/node && ~/scripts/qnode_restart.sh'" | crontab -

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

pkill node && pkill -f "go run ./..."

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.

sudo rm -r ~/ceremonyclient/node/.config/store

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

mkdir -p /root/backup && cp /root/ceremonyclient/node/.config/config.yml /root/backup && cp /root/ceremonyclient/node/.config/keys.yml /root/backup

Copy the files back from root/backup to your node folder (a copy will also remain in the root/backup folder)

cp /root/backup/{config.yml,keys.yml} /root/ceremonyclient/node/.config/

Check total nodes connected to the network

Install grpcURL

go install github.com/fullstorydev/grpcurl/cmd/grpcurl@latest

Run

/root/go/bin/grpcurl -plaintext -max-msg-sz 5000000 localhost:8337 quilibrium.node.node.pb.NodeService.GetPeerInfo | grep peerId | wc -l

📂
🔠
setup the gRPC calls
look here