Hello,
I built rippled on a dev server, running ubuntu 16.04. Whatever I do, I can't seem to get rippled to sync the ledger.
I'm not sure what I'm missing but here are the environment specifics:
[server]
port_rpc_admin_local
port_peer
port_ws_admin_local
#port_ws_public
[port_rpc_admin_local]
port = 5005
ip = 0.0.0.0
admin = 0.0.0.0
protocol = http
[port_peer]
port = 51235
ip = 0.0.0.0
protocol = peer
[port_ws_admin_local]
port = 6006
ip = 127.0.0.1
admin = 127.0.0.1
protocol = ws
#[port_ws_public]
#port = 5005
#ip = 127.0.0.1
#protocol = wss
[ips]
54.84.21.230 51235
54.86.175.122 51235
54.186.248.91 51235
54.186.73.52 51235
184.173.45.38 51235
198.11.206.26 51235
169.55.164.29 51235
174.37.225.41 51235
[peer_private]
1
[node_size]
tiny
[ledger_history]
256
[validators_file]
/etc/rippled/validators.txt
[workers]
2
[ssl_verify]
0
[node_db]
type=nudb
path=/opt/data/ripple/nudb
advisory_delete=0
[database_path]
/opt/data/ripple/db
[debug_logfile]
/opt/data/ripple/debug.log
[signing_support]
true
[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org
[rpc_startup]
{ "command": "log_level", "severity": "info" }
[validators]
nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm
nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU
nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd
nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP
nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT
[validator_list_sites]
https://vl.ripple.com
[validator_list_keys]
ED2677ABFFD1B33AC6FBC3062B71F1E8397C1505E1C42C64D11AD1B28FF73F4734
{
"result" : {
"info" : {
"build_version" : "1.1.0",
"closed_ledger" : {
"age" : 4,
"base_fee_xrp" : 1e-05,
"hash" : "C87DABF3703AB169247097602F657809DD99D6268EC22E69DEAEF9879F38295C",
"reserve_base_xrp" : 200,
"reserve_inc_xrp" : 50,
"seq" : 85
},
"complete_ledgers" : "empty",
"hostid" : "dev",
"io_latency_ms" : 1,
"jq_trans_overflow" : "0",
"last_close" : {
"converge_time_s" : 2,
"proposers" : 0
},
"load" : {
"job_types" : [
{
"in_progress" : 1,
"job_type" : "clientCommand"
}
],
"threads" : 2
},
"load_factor" : 1,
"peer_disconnects" : "0",
"peer_disconnects_resources" : "0",
"peers" : 0,
"pubkey_node" : "n9Lg8CjCj2RNppWc9335m6pq9TR4aQPAGLofs95kEi55BbTUvtJQ",
"pubkey_validator" : "none",
"published_ledger" : "none",
"server_state" : "full",
"state_accounting" : {
"connected" : {
"duration_us" : "76368547",
"transitions" : 1
},
"disconnected" : {
"duration_us" : "1790027",
"transitions" : 1
},
"full" : {
"duration_us" : "2002195644",
"transitions" : 1
},
"syncing" : {
"duration_us" : "0",
"transitions" : 0
},
"tracking" : {
"duration_us" : "19",
"transitions" : 1
}
},
"time" : "2018-Sep-25 16:48:24.905404",
"uptime" : 2080,
"validation_quorum" : 22,
"validator_list_expires" : "2018-Oct-02 00:00:00.000000000"
},
"status" : "success"
}
}
You're coming very close to the minimum recommended amounts on your server. Please see the links below.
https://wiki.ripple.com/Latest_rippled_release_notes
https://developers.ripple.com/capacity-planning.html
This recommends 8 GB or more RAM.
The ledger grows at 5 GB per day as of Q4 2015, so you may also be pushing the edge of your storage space. In Ubuntu run
df -h
To see how much you're currently using.
@antechdemo, my machine has 16 GB of ram and the storage availability is 2.9T.
root@dev:/home/raul# df -h
Filesystem Size Used Avail Use% Mounted on
udev 7.8G 0 7.8G 0% /dev
tmpfs 1.6G 161M 1.5G 11% /run
/dev/sdb2 439G 18G 399G 5% /
tmpfs 7.8G 0 7.8G 0% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
tmpfs 7.8G 0 7.8G 0% /sys/fs/cgroup
/dev/sdb1 511M 3.4M 508M 1% /boot/efi
/dev/sda1 3.6T 604G 2.9T 18% /opt/data
tmpfs 1.6G 0 1.6G 0% /run/user/1000
root@dev:/home/raul#
root@dev:/home/raul# free -gh
total used free shared buff/cache available
Mem: 15G 4.7G 175M 101M 10G 10G
Swap: 976M 976M 0B
root@dev:/home/raul#
As for the average load, it is constantly under 4 ( my machine has 4 cores ).
You can try switching to RocksDB.
Stop the server (ctrl+c)
Edit rippled.cfg, updating the [node_db] stanza. Example:
[node_db]
type=RocksDB
path=/efs/.config/ripple/db/rocksdb
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
advisory_delete=0
You may notice that your server does not have _any_ peer connections. Without a connection to the network, it can't possibly sync.
The reason it has no peers is a consequence of your configuration (specifically, you have [peer_private] set to 1, which means your server won't attempt to establish any outgoing connections, which it warns you about on startup).
Unless you have a specific reason to limit the servers to which you connect, I would recommend removing the following lines from your config file:
[ips]
54.84.21.230 51235
54.86.175.122 51235
54.186.248.91 51235
54.186.73.52 51235
184.173.45.38 51235
198.11.206.26 51235
169.55.164.29 51235
174.37.225.41 51235
[peer_private]
1
Furthermore, you should remove the following lines from your validators.txt:
[validators]
nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm
nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU
nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd
nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP
nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT
If this continues to be an issue for you, please post an update here; otherwise please feel free to close this issue @antechdemo. If we don't hear back from you in the next 10 days, we'll probably end up closing this issue due to inactivity.
Most helpful comment
You may notice that your server does not have _any_ peer connections. Without a connection to the network, it can't possibly sync.
The reason it has no peers is a consequence of your configuration (specifically, you have
[peer_private]set to 1, which means your server won't attempt to establish any outgoing connections, which it warns you about on startup).Unless you have a specific reason to limit the servers to which you connect, I would recommend removing the following lines from your config file:
Furthermore, you should remove the following lines from your
validators.txt: