Install on CentOS/Red Hat with yum

This page describes the recommended instructions for installing the latest stable version of rippled on CentOS 7 or Red Hat Enterprise Linux 7, using Ripple's yum repository.

These instructions install a binary that has been compiled by Ripple.

Prerequisites

Before you install rippled, you must meet the System Requirements.

Installation Steps

  1. Install the Ripple RPM repository:

    Choose the appropriate RPM repository for the stability of releases you want:

    • stable for the latest production release (master branch)
    • unstable for pre-release builds (release branch)
    • nightly for experimental/development builds (develop branch)
    $ cat << REPOFILE | sudo tee /etc/yum.repos.d/ripple.repo
    [ripple-stable]
    name=XRP Ledger Packages
    baseurl=https://repos.ripple.com/repos/rippled-rpm/stable/
    enabled=1
    gpgcheck=0
    gpgkey=https://repos.ripple.com/repos/rippled-rpm/stable/repodata/repomd.xml.key
    repo_gpgcheck=1
    REPOFILE
    
    $ cat << REPOFILE | sudo tee /etc/yum.repos.d/ripple.repo
    [ripple-unstable]
    name=XRP Ledger Packages
    baseurl=https://repos.ripple.com/repos/rippled-rpm/unstable/
    enabled=1
    gpgcheck=0
    gpgkey=https://repos.ripple.com/repos/rippled-rpm/unstable/repodata/repomd.xml.key
    repo_gpgcheck=1
    REPOFILE
    
    $ cat << REPOFILE | sudo tee /etc/yum.repos.d/ripple.repo
    [ripple-nightly]
    name=XRP Ledger Packages
    baseurl=https://repos.ripple.com/repos/rippled-rpm/nightly/
    enabled=1
    gpgcheck=0
    gpgkey=https://repos.ripple.com/repos/rippled-rpm/nightly/repodata/repomd.xml.key
    repo_gpgcheck=1
    REPOFILE
    
    • Fetch the latest repo updates:

      $ sudo yum -y update
      
    • Install the new rippled package:

      $ sudo yum install rippled
      

      Version 1.3.1 does not require any changes to your config files (rippled.cfg and validators.txt). This update procedure leaves your existing config files in place.

    • Reload systemd unit files:

      $ sudo systemctl daemon-reload
      
    • Configure the rippled service to start on boot:

      $ sudo systemctl enable rippled.service
      
    • Start the rippled service:

      $ sudo systemctl start rippled.service
      

    Next Steps

    It can take several minutes for rippled to sync with the rest of the network, during which time it outputs warnings about missing ledgers.

    For information about rippled log messages, see Understanding Log Messages.

    After your rippled has synchronized with the rest of the network, you have a fully functional stock rippled server that you can use for local signing and API access to the XRP Ledger. Use rippled server states to tell whether your rippled server has synchronized with the network. You can use the rippled commandline interface to test this quickly:

    $ /opt/ripple/bin/rippled server_info
    

    For more information about communicating with your rippled server using the rippled APIs, see the rippled API reference.

    Once you have your stock rippled server running, you may want to consider running it as a validating server. For information about validating servers and why you might want to run one, see Run rippled as a Validator.

    Having trouble getting your rippled server started? See rippled Server Won't Start.

    Additional Configuration

    rippled should connect to the XRP Ledger with the default configuration. However, you can change your settings by editing the rippled.cfg file. For recommendations about configuration settings, see Capacity Planning.

    The recommended installation uses the config file /etc/opt/ripple/rippled.cfg by default. Other places you can put a config file include $HOME/.config/ripple/rippled.cfg (where $HOME is the home directory of the user running rippled), $HOME/.local/ripple/rippled.cfg, or the current working directory from where you start rippled.

    See the rippled GitHub repository for a description of all configuration options.

    You must restart rippled for any configuration changes to take effect:

    If you change the [debug_logfile] or [database_path] sections, you may need to grant ownership of the new configured path to the user you run rippled as.

    Updates

    You must update rippled regularly to remain synced with the rest of the XRP Ledger network. You can subscribe to the rippled Google Group to receive notifications of new rippled releases.

    The rippled package includes a script you can use to enable automatic updates on Linux. On other platforms, you must update manually.

    See Also