Jump to content

rippled stock node failing to download ledgers


Recommended Posts

I tried setting up a stock node on a virtual machine this afternoon and it seems like rippled is failing to download ledgers as the complete_ledgers field reports empty.  Here is the output of server_info:

Quote

tw@tw-VirtualBox:~/Downloads/my_ripple_experiment$ /opt/ripple/bin/rippled server_info
Loading: "/etc/opt/ripple/rippled.cfg"
2020-Oct-25 18:35:10.895048660 UTC HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "result" : {
      "info" : {
         "build_version" : "1.6.0",
         "closed_ledger" : {
            "age" : 20,
            "base_fee_xrp" : 1e-05,
            "hash" : "B8FF18E9C85617BBB569145491B3FA5C0CEDBA413144A341E654122E7395D20E",
            "reserve_base_xrp" : 200,
            "reserve_inc_xrp" : 50,
            "seq" : 744
         },
         "complete_ledgers" : "empty",
         "fetch_pack" : 4,
         "hostid" : "tw-VirtualBox",
         "io_latency_ms" : 1,
         "jq_trans_overflow" : "0",
         "last_close" : {
            "converge_time_s" : 26.013,
            "proposers" : 0
         },
         "load" : {
            "job_types" : [
               {
                  "job_type" : "untrustedValidation",
                  "peak_time" : 5,
                  "per_second" : 6
               },
               {
                  "job_type" : "ledgerData",
                  "per_second" : 2
               },
               {
                  "in_progress" : 1,
                  "job_type" : "clientCommand"
               },
               {
                  "job_type" : "advanceLedger",
                  "per_second" : 4
               },
               {
                  "job_type" : "fetchTxnData",
                  "per_second" : 21
               },
               {
                  "job_type" : "trustedValidation",
                  "peak_time" : 5,
                  "per_second" : 1
               },
               {
                  "job_type" : "trustedProposal",
                  "peak_time" : 2,
                  "per_second" : 3
               },
               {
                  "job_type" : "peerCommand",
                  "peak_time" : 1,
                  "per_second" : 73
               },
               {
                  "job_type" : "AsyncReadNode",
                  "per_second" : 1
               }
            ],
            "threads" : 3
         },
         "load_factor" : 1,
         "network_ledger" : "waiting",
         "peer_disconnects" : "1282",
         "peer_disconnects_resources" : "0",
         "peers" : 10,
         "pubkey_node" : "n94NoNZgDYvquzTb3cLcTzrmY6ucNTGAHxWwzwphyNCvTdkBZXA7",
         "pubkey_validator" : "none",
         "published_ledger" : "none",
         "server_state" : "connected",
         "server_state_duration_us" : "674323758",
         "state_accounting" : {
            "connected" : {
               "duration_us" : "6860652880",
               "transitions" : 14
            },
            "disconnected" : {
               "duration_us" : "721519581",
               "transitions" : 14
            },
            "full" : {
               "duration_us" : "0",
               "transitions" : 0
            },
            "syncing" : {
               "duration_us" : "0",
               "transitions" : 0
            },
            "tracking" : {
               "duration_us" : "0",
               "transitions" : 0
            }
         },
         "time" : "2020-Oct-25 18:35:10.895522 UTC",
         "uptime" : 7582,
         "validation_quorum" : 31,
         "validator_list" : {
            "count" : 1,
            "expiration" : "2020-Nov-21 00:00:00.000000000 UTC",
            "status" : "active"
         }
      },
      "status" : "success"
   }
}

 

Link to post
Share on other sites
Quote

Storing full history is expensive. As of 2018-12-11, the full history of the XRP Ledger occupies approximately 9 terabytes of disk space, which must be entirely stored on fast solid state disk drives for proper server performance. Such a large amount of solid state storage is not cheap, and the total amount of history you must store increases by approximately 12 GB per day.

Acquiring full history from the peer-to-peer network takes a long time (several months) and requires that your server has sufficient system and network resources to acquire older history while keeping up with new ledger progress. To get a faster start on acquiring ledger history, you may want to find another server operator who has a large amount of history already downloaded, who can give you a database dump or at least allow your server to explicitly peer with theirs for a long time to acquire history. The server can load ledger history from a file and verify the integrity of the historical ledgers it imports.

The above is from xrpl.org. 

Try setting online deletion to a lower value. 
https://xrpl.org/configure-online-deletion.html

I'm not sure exactly what your error is but the first thing I would check is that you have enough disk space and enough ram. I see that you're running in vm ware. This may not be possible due to required system specs. 
https://xrpl.org/server-doesnt-sync.html



You may also be blocked by a firewall.

Link to post
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.