-
Notifications
You must be signed in to change notification settings - Fork 1.5k
server_state stuck in connected or syncing
Elliot Lee edited this page Sep 24, 2018
·
1 revision
To check the status of your server, run server_info
:
> ./rippled server_info
If the output contains one of the following:
"server_state" : "connected",
"server_state" : "syncing",
and this persists for a long period of time (more than 10 minutes), and
- you are using SSDs
- you are currently using RocksDB
Then you should try switching to NuDB.
- Stop the server (ctrl+c)
- Edit
rippled.cfg
, updating the[node_db]
and (optionally)[database_path]
stanzas
Example:
[node_db]
type=nudb
path=/var/lib/rippled/dbnudb/nudb
advisory_delete=0
[database_path]
/var/lib/rippled/dbnudb
Ensure that rippled has permission to write to the path (e.g. /var/lib/rippled/dbnudb
) and that there is no existing data there (to prevent conflicts).
- Start the server
Under typical conditions, rippled should reach "server_state" : "full",
within a few minutes.