mirror of
https://github.com/XRPLF/xrpl-dev-portal.git
synced 2025-11-20 19:55:54 +00:00
more 1.3.0 update/install/migration work
This commit is contained in:
mDuo13
@@ -25,20 +25,36 @@ Before you install `rippled`, you must meet the [System Requirements](system-req
|
||||
$ wget -q -O - "https://repos.ripple.com/repos/api/gpg/key/public" | \
|
||||
sudo apt-key add -
|
||||
|
||||
The key should match the following fingerprint:
|
||||
4. Check the fingerprint of the newly-added key:
|
||||
|
||||
C001 0EC2 05B3 5A33 10DC 90DE 395F 97FF CCAF D9A2
|
||||
$ apt-key finger
|
||||
|
||||
The output should include an entry for Ripple such as the following:
|
||||
|
||||
pub rsa3072 2019-02-14 [SC] [expires: 2012-02-13]
|
||||
C001 0EC2 05B3 5A33 10DC 90DE 395F 97FF CCAF D9A2
|
||||
uid [ unknown] TechOps Team at Ripple <techops+rippled@ripple.com>
|
||||
sub rsa3072 2019-02-14 [E] [expires: 2021-02-13]
|
||||
|
||||
In particular, make sure that the fingerprint matches. (In the above example, the fingerprint is on the second line, starting with `C001`.)
|
||||
|
||||
4. Add the appropriate Ripple repository for your operating system version:
|
||||
|
||||
$ sudo echo "deb https://repos.ripple.com/repos/rippled-deb bionic stable" > \
|
||||
/etc/apt/sources.list.d/ripple.list
|
||||
$ echo "deb https://repos.ripple.com/repos/rippled-deb bionic stable" | \
|
||||
sudo tee -a /etc/apt/sources.list.d/ripple.list
|
||||
|
||||
The above example is appropriate for **Ubuntu 18.04 Bionic Beaver**. For other operating systems, replace the word `bionic` with one of the following:
|
||||
|
||||
- `xenial` for **Ubuntu 16.04 Xenial Xerus**
|
||||
- `stretch` for **Debian 9 Stretch**
|
||||
|
||||
If you want access to development or pre-release versions of `rippled`, use one of the following instead of `stable`:
|
||||
|
||||
- `unstable` - Pre-release builds ([`release` branch](https://github.com/ripple/rippled/tree/release))
|
||||
- `nightly` - Experimental/development builds ([`develop` branch](https://github.com/ripple/rippled/tree/develop))
|
||||
|
||||
**Warning:** Unstable and nightly builds may be broken at any time. Do not use these builds for production servers.
|
||||
|
||||
5. Fetch the Ripple repository.
|
||||
|
||||
$ sudo apt -y update
|
||||
@@ -51,7 +67,6 @@ Before you install `rippled`, you must meet the [System Requirements](system-req
|
||||
|
||||
$ systemctl status rippled.service
|
||||
|
||||
***TODO: confirm it starts automatically***
|
||||
The `rippled` service should start automatically. If not, you can start it manually:
|
||||
|
||||
$ sudo systemctl start rippled.service
|
||||
|
||||
@@ -1,14 +1,49 @@
|
||||
# rippled v1.3.0 Migration Instructions
|
||||
|
||||
The install and upgrade process on supported platforms has changed for `rippled` v1.3.0. If you have `rippled` v1.2.4 or lower installed, follow the instructions for upgrading on your platform:
|
||||
This document describes the migration process for upgrading from `rippled` 1.2.4 or earlier to `rippled` v1.3.0 or later. This is necessary because the `rippled` install process has changed as of version 1.3.0.
|
||||
|
||||
This document provides migration steps for upgrading on supported platforms:
|
||||
|
||||
- [CentOS or Red Hat Enterprise Linux (RHEL)](#migration-on-centos-or-red-hat-enterprise-linux-rhel)
|
||||
- [Ubuntu Linux](#migration-on-ubuntu-linux)
|
||||
|
||||
For other platforms, see the updated instructions for compiling from source.
|
||||
For other platforms, see the updated instructions for compiling from source. ([Ubuntu](build-run-rippled-ubuntu.html), [macOS](build-run-rippled-macos.html), or [Windows](https://github.com/ripple/rippled/tree/develop/Builds/VisualStudio2017))
|
||||
|
||||
# Migration on CentOS or Red Hat Enterprise Linux (RHEL)
|
||||
|
||||
***TODO: Test. Might be same as manual install steps***
|
||||
|
||||
Ripple's official RPM repository and instructions for using it have changed. To migrate from the old repository to the new one, complete the following steps:
|
||||
|
||||
1. Stop the `rippled` server.
|
||||
|
||||
$ sudo systemctl stop rippled.service
|
||||
|
||||
2. Back up your configuration files.
|
||||
|
||||
Copy your configuration files to a temporary directory. For example:
|
||||
|
||||
$ mkdir ~/rippled_config_backup
|
||||
$ cp /opt/ripple/etc/rippled.cfg ~/rippled_config_backup
|
||||
$ cp /opt/ripple/etc/validators.txt ~/rippled_config_backup
|
||||
|
||||
You may need to adjust the paths to the `rippled.cfg` and `validators.txt` files to match your configuration.
|
||||
|
||||
3. Back up your data files.
|
||||
|
||||
Copy your rippled server's database files to a temporary directory. For example:
|
||||
|
||||
$ mkdir ~/rippled_data_backup
|
||||
$ cp -r /var/lib/rippled/db/ ~/rippled_data_backup
|
||||
|
||||
You may need to adjust the path to your database files to match your configuration. You should be sure to copy all database files, including SQLite databases (`.sqlite` and `.db` files), NuDB or RocksDB files for the [ledger store](ledger-history.html), and the [shard store](history-sharding.html) if you have history sharding enabled.
|
||||
|
||||
This process may take a long time, depending on how much data you have stored.
|
||||
|
||||
**Caution:** You can choose to skip this step if you do not need the ledger history data. Your server can download the necessary amount of ledger data from the peer-to-peer network after it comes back online. Validators and simple stock servers do not need large amounts of historical data to keep up with the progress of the XRP Ledger.
|
||||
|
||||
4. Update the
|
||||
|
||||
***TODO: instructions per https://github.com/ripple/ripple-dev-portal/issues/544***
|
||||
|
||||
Roughly:
|
||||
@@ -24,15 +59,21 @@ Roughly:
|
||||
|
||||
# Migration on Ubuntu Linux
|
||||
|
||||
***TODO: instructions per https://github.com/ripple/ripple-dev-portal/issues/544***
|
||||
Prior to version 1.3.0, the supported way to install `rippled` on Ubuntu Linux was using Alien to install the RPM package. Starting with `rippled` v1.3.0, Ripple provides a native package for Ubuntu and Debian Linux, which is the recommended way of installing it. If you already have the RPM package installed, complete the [installation steps](install-rippled-on-ubuntu.html) to upgrade the package and switch over to the native APT (`.deb`) package.
|
||||
|
||||
Roughly:
|
||||
If you have made any changes to your config files (`/opt/ripple/etc/rippled.cfg` and `/opt/ripple/etc/validators.txt`), `apt` may prompt you during installation asking if you want to overwrite your config files with the newest versions from the packages. Version 1.3.0 does not require any changes to the config file, so you can safely keep your existing config files unchanged.
|
||||
|
||||
- stop rippled
|
||||
- backup data & config
|
||||
- uninstall package w/ alien
|
||||
- install 1.3 the standard way (now w/ `apt`)
|
||||
- stop rippled
|
||||
- restore config & data files
|
||||
- start rippled, check status
|
||||
- optionally remove alien itself
|
||||
After installing the new package, if you no longer need Alien for any other packages, you may optionally uninstall it and its dependencies using the following steps:
|
||||
|
||||
1. Uninstall Alien:
|
||||
|
||||
$ sudo apt -y remove alien
|
||||
|
||||
2. Uninstall unused dependencies:
|
||||
|
||||
$ sudo apt -y autoremove
|
||||
|
||||
|
||||
## Automatic Updates
|
||||
|
||||
The `rippled` v1.3.0 package includes an updated auto-update script that works on Ubuntu and Debian Linux. For more information, see [Update `rippled` Automatically on Linux](update-rippled-automatically-on-linux.html).
|
||||
|
||||
Reference in New Issue
Block a user