3.0 KiB
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:
{% if currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-ubuntu.md" or currentpage.md == "tutorials/manage-the-rippled-server/installation/build-run-rippled-macos.md" %} $ ./rippled server_info {% else %} $ /opt/ripple/bin/rippled server_info {% endif %}
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.
{% include '_snippets/conf-file-location.md' %}
See the rippled GitHub repository for a description of all configuration options.
{% if currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-ubuntu-with-alien.md" or
currentpage.md == "tutorials/manage-the-rippled-server/installation/install-rippled-on-centos-rhel-with-yum" %}
If you change the [debug_logfile] or [database_path] sections, you may need to grant the rippled user and group ownership to your new configured path:
$ chown -R rippled:rippled <configured path>
Restart rippled for any configuration changes to take effect:
$ sudo service rippled restart
{% endif %}
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 for Red Hat Enterprise Linux and CentOS includes a script you can use to enable automatic updates on those platforms. On other platforms, you must update manually.