Search code examples
ripplerippled

Did anyone succeded with running 'rippled'?

I made an attempt to run rippled both versions 1.1.2 and 1.2.4 on Ubuntu 18.04 and I would not say it does not work at all, because it utilizes CPU and Disk, creates database of 3GB size, and I even was able to create a wallet from the command line, but if I do

./rippled account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true

I always get

Loading: "/home/xrp/.config/ripple/rippled.cfg"
2019-May-29 10:04:10.273909186 HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "result" : {
      "error" : "lgrNotFound",
      "error_code" : 21,
      "error_message" : "ledgerNotFound",
      "request" : {
         "account" : "r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59",
         "command" : "account_info",
         "ledger_index" : 0
      },
      "status" : "error"
   }
}

What can be wrong?

See Building and running rippled on Ubuntu for more information on what steps I did.

EDIT1:

I tried the same account_info command with s1.ripple.com and s2.ripple.com and got the same "lgrNotFound" error:

./rippled -v --rpc_ip 34.213.185.56:51234 account_info r9cZA1mLK5R5Am25ArfXFmqgNwjZgnfk59 true

Solution

  • It looks like you are successfully running rippled. What you haven't done yet is successfully get rippled up-to-date or "synchronized" to the rest of the nodes on the network.

    There are several possible reasons why, but these are the most common that I've seen:

    1. Inability to connect to other peers. If your firewall or other network issue is making it impossible to connect to other peers, you're never going to sync. Run rippled server_info, and look for the number of peers. It should be at least 10 after rippled has been running for a few minutes. (The command rippled peers will give a lot more detail, but usually the number is sufficient to know if you're ok or not.)
    2. Insufficient time. It can take several minutes for a node to sync, because it has to download the state of the ledger at some given time, then catch up to the changes from that time. If you've been waiting over 15 minutes or so, this is probably not your problem.
    3. Insufficient machine resources. Most often this takes the form of a slow network connection, or a slow hard drive. These pages will give more details and current recommendations:
    4. Inability to download the validator list. Less common in general is a problem connecting to the cofigured [validator_list_sites] (https://vl.ripple.com) by default. Run rippled validators. You should get a result that includes a bunch (31 currently) of validator node IDs (50-odd character strings starting with "n"), and a JSON object labelled validator_list. That object should indicate an expiration date in the future, and a status of "active". Anything else usually indicates a problem. rippled validator_list_sites may give you more of an explanation of what the problem is, if any.