Updating a node using the CLI

10st Okt 2023Radix Node v1.0.4 released

We renamed the binary filename from radixnode to babylonnode and changed the default file locations in order to prevent file clashes or unintentional overwrites when updating a node from Olympia to Babylon. Beware that despite effort to reduce friction, we highly recommend to do the migration using a new separate node instead of recycling the existing olympia node.

10st Okt 2023Radix Node v1.0.4 released

Use the babylonnode CLI to update your node or install a new node from scratch – or refer to the update instructions for Docker or systemd install methods.

Introduction

When updating your node, care should be taken to ensure the update goes smoothly. These instructions use the babylonnode CLI tool for an easy update process.

1. Prepare to update

First, if you haven’t already done so, ensure that you have backed up your node-keystore.ks key file. This key file contains the private key that determines your node’s unique address and (if you are running a validator node) validator ID. If anything goes wrong in the update process, if you have your key file, you can always reinstall the node from scratch and use it to recover access to your node.

Next, you may want to consider using a backup node to perform a switch to the updated node with minimal interruption (especially if running a validator node) – or to provide a quick recovery if something goes wrong during the update. See our recommendations for Maintaining Uptime for more.

2. Update your node

  • docker mode

  • systemd mode

To upgrade your node using CLI

babylonnode docker install --update
If upgrading to version 1.1.0, then install Java 17 either by running sudo apt install -y openjdk-17-jdk or run cli command babylonnode configure systemd

Run below command to upgrade your node.

babylonnode systemd install -u
  1. The -u option specifies that this launch of the node will be an update, causing babylonnode to create a backup of the current configuration file and ensure that the node has stopped before applying the changes.

  2. Optional - The -r specifies the release of the node software you wish to install. If not provided it will use the latest release from https://github.com/radixdlt/babylon-node/releases.

  3. Optional - The -i option is the external IP address of your server.

  4. Optional -The -t option is the IP address of a Radix node that you can use to join the network. On executing the command, the script will download the configuration file from the specified node and attempt to make a connection. Select any node IP from the closest region to your node from the list below:

  • Mainnet Seed Nodes

  • Stokenet Seed Nodes

radix://node_rdx1qf2x63qx4jdaxj83kkw2yytehvvmu6r2xll5gcp6c9rancmrfsgfw0vnc65@52.212.35.209,radix://node_rdx1qgxn3eeldj33kd98ha6wkjgk4k77z6xm0dv7mwnrkefknjcqsvhuu4gc609@54.79.136.139,radix://node_rdx1qwrrnhzfu99fg3yqgk3ut9vev2pdssv7hxhff80msjmmcj968487uugc0t2@43.204.226.50,radix://node_rdx1q0gnmwv0fmcp7ecq0znff7yzrt7ggwrp47sa9pssgyvrnl75tvxmvj78u7t@52.21.106.232
radix://node_tdx_2_1qv89yg0la2jt429vqp8sxtpg95hj637gards67gpgqy2vuvwe4s5ss0va2y@13.126.248.88,radix://node_tdx_2_1qvtd9ffdhxyg7meqggr2ezsdfgjre5aqs6jwk5amdhjg86xhurgn5c79t9t@13.210.209.103,radix://node_tdx_2_1qwfh2nn0zx8cut5fqfz6n7pau2f7vdyl89mypldnn4fwlhaeg2tvunp8s8h@54.229.126.97,radix://node_tdx_2_1qwz237kqdpct5l3yjhmna66uxja2ymrf3x6hh528ng3gtvnwndtn5rsrad4@3.210.187.161