zbwdaa Posted November 13, 2018 Share Posted November 13, 2018 Our nodes are always inexplicably interrupted and here is my config: [server] port_rpc_admin_local port_peer port_ws_admin_local [port_rpc_admin_local] port = 5005 ip = 172.18.19.33 admin = 172.18.19.33 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 [node_size] huge [node_db] type=RocksDB path=/mnt/ripple/db/rocksdb open_files=2000 filter_bits=12 cache_mb=256 file_size_mb=8 file_size_mult=2 online_delete=10000000 advisory_delete=0 [ledger_history] 10000000 [database_path] /mnt/ripple/db [debug_logfile] /var/log/rippled/debug.log [sntp_servers] time.windows.com time.apple.com time.nist.gov pool.ntp.org [ips] r.ripple.com 51235 169.55.164.20 51235 169.54.2.154 51235 s2.ripple.com 51235 [validators_file] validators.txt [rpc_startup] { "command": "log_level", "severity": "warning" } [ssl_verify] 0 There is no problem with our network and server. The host and the server perform ssh communication, and after starting the ripple file in my_build, it is always inexplicable. Link to comment Share on other sites More sharing options...
karlos Posted November 13, 2018 Share Posted November 13, 2018 Are you using a SSD? You need good IOPS Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now