TaylorWarden Posted November 10, 2020 Share Posted November 10, 2020 I have rented a new dedicated server to host a rippled validator. Right now it is operating in stock mode. I have made no changes to the default rippled.cfg file. The server_info command returns the following output: [root@server1 html]# /opt/ripple/bin/rippled server_info Loading: "/etc/opt/ripple/rippled.cfg" 2020-Nov-10 17:20:39.368218366 UTC HTTPClient:NFO Connecting to 127.0.0.1:5005 { "result" : { "info" : { "build_version" : "1.6.0", "closed_ledger" : { "age" : 1869, "base_fee_xrp" : 1e-05, "hash" : "68E96E053752C27711CFF028FD624EA4A136B1C46E192172AC31C5C40049C052", "reserve_base_xrp" : 200, "reserve_inc_xrp" : 50, "seq" : 2 }, "complete_ledgers" : "empty", "hostid" : "server1.streetsofsilver.ca", "io_latency_ms" : 1, "jq_trans_overflow" : "0", "last_close" : { "converge_time_s" : 0, "proposers" : 0 }, "load" : { "job_types" : [ { "in_progress" : 1, "job_type" : "clientCommand" } ], "threads" : 6 }, "load_factor" : 1, "network_ledger" : "waiting", "peer_disconnects" : "0", "peer_disconnects_resources" : "0", "peers" : 0, "pubkey_node" : "n9LUWV65Zbsq5GvCRLS6vEWBy8B6WSafdggAKBkKY2heFyy3vLui", "pubkey_validator" : "none", "published_ledger" : "none", "server_state" : "disconnected", "server_state_duration_us" : "1867022647", "state_accounting" : { "connected" : { "duration_us" : "0", "transitions" : 0 }, "disconnected" : { "duration_us" : "1867022647", "transitions" : 1 }, "full" : { "duration_us" : "0", "transitions" : 0 }, "syncing" : { "duration_us" : "0", "transitions" : 0 }, "tracking" : { "duration_us" : "0", "transitions" : 0 } }, "time" : "2020-Nov-10 17:20:39.369265 UTC", "uptime" : 1867, "validation_quorum" : 4294967295, "validator_list" : { "count" : 1, "expiration" : "2020-Nov-21 00:00:00.000000000 UTC", "status" : "active" } }, "status" : "success" } } Why is the validation_quorum so astronomically high and what could be causing the server to remain disconnected from the network? The server specs are as follows: Quote CentOS (installed via yum) 240 GB SSD 16G GB DDR3 RAM Quad core processors Link to comment Share on other sites More sharing options...
TaylorWarden Posted November 14, 2020 Author Share Posted November 14, 2020 (edited) If you also experience the problem that I was encountering, this is the solution that worked for me. The problem is that the default firewall settings for CentOS 7.9 pervert the connection to the RCL network. If you have WHM installed on your server, navigate to Plugins > ConfigServer Security > Firewall > Firewall configuration and add the following ports to TCP_IN and TCP_OUT: 5005,2459,51235,6006,6005,50051. You can also do it manually via the command line, the configuration file is located at /etc/csf/csf.conf. You will need to restart csf+lfd as well as the rippled service for the daemon to properly function. Here is the output that I recently received after successfully editing the firewall configuration: [root@server1 home]# /opt/ripple/bin/rippled server_info Loading: "/etc/opt/ripple/rippled.cfg" 2020-Nov-14 01:04:53.403840263 UTC HTTPClient:NFO Connecting to 127.0.0.1:5005 { "result" : { "info" : { "build_version" : "1.6.0", "complete_ledgers" : "59534066-59534495", "fetch_pack" : 80624, "hostid" : "server1.streetsofsilver.ca", "io_latency_ms" : 1, "jq_trans_overflow" : "0", "last_close" : { "converge_time_s" : 2, "proposers" : 38 }, "load" : { "job_types" : [ { "avg_time" : 2, "job_type" : "publishAcqLedger", "peak_time" : 26, "per_second" : 4 }, { "job_type" : "untrustedValidation", "peak_time" : 2, "per_second" : 19 }, { "job_type" : "ledgerRequest", "per_second" : 1 }, { "job_type" : "ledgerData", "peak_time" : 20, "per_second" : 80 }, { "in_progress" : 1, "job_type" : "clientCommand", "per_second" : 6 }, { "job_type" : "transaction", "peak_time" : 3, "per_second" : 6 }, { "job_type" : "batch", "per_second" : 4 }, { "job_type" : "advanceLedger", "peak_time" : 7, "per_second" : 5 }, { "job_type" : "fetchTxnData", "per_second" : 4 }, { "avg_time" : 23, "job_type" : "writeAhead", "peak_time" : 102 }, { "job_type" : "trustedValidation", "peak_time" : 3, "per_second" : 4 }, { "job_type" : "trustedProposal", "peak_time" : 1, "per_second" : 12 }, { "job_type" : "peerCommand", "per_second" : 488 }, { "job_type" : "processTransaction", "per_second" : 6 }, { "job_type" : "SyncReadNode", "peak_time" : 18, "per_second" : 2086 }, { "job_type" : "AsyncReadNode", "peak_time" : 18, "per_second" : 890 }, { "job_type" : "WriteNode", "peak_time" : 14, "per_second" : 3477 } ], "threads" : 6 }, "load_factor" : 1, "peer_disconnects" : "6", "peer_disconnects_resources" : "0", "peers" : 10, "pubkey_node" : "n9LUWV65Zbsq5GvCRLS6vEWBy8B6WSafdggAKBkKY2heFyy3vLui", "pubkey_validator" : "none", "server_state" : "full", "server_state_duration_us" : "102728633", "state_accounting" : { "connected" : { "duration_us" : "101043367", "transitions" : 1 }, "disconnected" : { "duration_us" : "2252737", "transitions" : 1 }, "full" : { "duration_us" : "102728633", "transitions" : 1 }, "syncing" : { "duration_us" : "2026163", "transitions" : 1 }, "tracking" : { "duration_us" : "0", "transitions" : 1 } }, "time" : "2020-Nov-14 01:04:53.404284 UTC", "uptime" : 208, "validated_ledger" : { "age" : 4, "base_fee_xrp" : 1e-05, "hash" : "74A04E8DE8B1A3AB39A0174A516E38A7731FE7F59E6A87840CF2C0B12074F213", "reserve_base_xrp" : 20, "reserve_inc_xrp" : 5, "seq" : 59534495 }, "validation_quorum" : 31, "validator_list" : { "count" : 1, "expiration" : "2020-Nov-21 00:00:00.000000000 UTC", "status" : "active" } }, "status" : "success" } } Kudos to the technians at Namecheap.com for assisting with this issue! Your team is the best! Edited November 14, 2020 by TaylorWarden Thanks jargoman 1 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