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
  1. Tutorials
  2. Node

Running the node via binary file

PreviousMigrating the node to a new serverNextRunning a node cluster

Last updated 1 month ago

If you use the Node Auto-installer, this will set a service file that runs the node via the release_autorun.sh script This script is able to auto-update your node when there is a new version available. In some rare cases though, this file does not work as intended, and you will get an error in the node log, which won't be able to start. What you can do then is edit the service file and set it to run the node directly via binary file.

Stop the node if it's running and open the service file.

nano /lib/systemd/system/ceremonyclient.service

Change this line

ExecStart=/root/ceremonyclient/node/release_autorun.sh

With this one

ExecStart=/root/ceremonyclient/node/node-1.4.21.1-amd64

Please note that node-1.4.21.1-amd64 will be different depending on the node version and architecture. Look in your ceremonyclient/node folder and you should see the correct version you have downloaded. Now save the file and exit with CTRL+X and then Y

Update your daemon, run:

systemctl daemon-reload

Restart your node which at this point should work correctly.

If you make this change in the service file you will lose the ability to auto-update, and you will have to update manually.

Also, when updating via my script, you may face again the same issue, because that line will be set again to release_autorun.sh. You will have to manually make again the edit and set it to the new node binary version.

📌
â„šī¸
Cover

Want to say thank you?

CLICK TO DONATE