search

XRPLF / rippled

Decentralized cryptocurrency blockchain daemon implementing the XRP Ledger protocol in C++
https://xrpl.org
ISC License
4.54k stars 1.47k forks source link

NetworkOPs:WRN We are not running on the consensus ledger #2351

Closed ghost closed 6 years ago

ghost commented 6 years ago

I am getting warning We are not running on the consensus ledger in ripple client. I have searched a lot but i am unable to resolve this issue. below is my logs

2018-Jan-24 09:49:25 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 09:49:25 LedgerConsensus:WRN Need consensus ledger 8FE90F36401DEBE3C3741A12D06D4548E5648C0FEE305108C592C93BFC77CF87
2018-Jan-24 09:49:25 InboundLedger:WRN 11 timeouts for ledger AD7F575B26BEE61F2C76728498EEDBAEF860F38AE9C84C7530321E1A8FB9DE51
...
2018-Jan-24 09:49:30 LedgerConsensus:WRN View of consensus changed during establish status=establish,  mode=wrongLedger
2018-Jan-24 09:49:30 LedgerConsensus:WRN 8FE90F36401DEBE3C3741A12D06D4548E5648C0FEE305108C592C93BFC77CF87 to B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13
2018-Jan-24 09:49:30 LedgerConsensus:WRN 
{
    "accepted" : true,
    "account_hash" : "6C94B5F6C2ACEB1D9648493793E7184C565E326239557F9AAC4D78059CAF9E87",
    "close_flags" : 0,
    "close_time" : 570102542,
    "close_time_human" : "2018-Jan-24 09:49:02",
    "close_time_resolution" : 10,
    "closed" : true,
    "hash" : "29AA78B5234C4002780C287BAC5BEA8CAD2E76032413267C6B96C9E62C6EF417",
    "ledger_hash" : "29AA78B5234C4002780C287BAC5BEA8CAD2E76032413267C6B96C9E62C6EF417",
    "ledger_index" : "1185",
    "parent_close_time" : 570102541,
    "parent_hash" : "200AF04EC1F739FFB72551569F93E4AD9615F1082B0B17079EA4B1870138F78F",
    "seqNum" : "1185",
    "totalCoins" : "100000000000000000",
    "total_coins" : "100000000000000000",
    "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000"
}

2018-Jan-24 09:49:30 LedgerConsensus:WRN Need consensus ledger B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13
2018-Jan-24 09:49:30 InboundLedger:WRN Want: B77EA831B80B670BFACE689B48DFEE1ED9973B057597DB6E83013B18F0A770C1
..
2018-Jan-24 09:49:31 TransactionAcquire:WRN Failed to acquire TX set 750A06D49CC9B64D5A4C5EFA868B52ACD668833604136DF2F8C2731F4CABFAE1
..
2018-Jan-24 09:49:33 InboundLedger:WRN 11 timeouts for ledger 72300CC6C24E8E7DEC6A5BA743555959C8D29FDC922DBBAF5E3A23E488FBED9B
2018-Jan-24 09:49:34 TransactionAcquire:WRN Failed to acquire TX set 55AEEEE0E7140F6C6CC6B2C684991F980074BD20BE9343C759D4BCB3BBF44F58
2018-Jan-24 09:49:34 InboundLedger:WRN 11 timeouts for ledger 02341A0334A7379736E87335ACDA218772132AD2AC393003579662F897143A9B
..
2018-Jan-24 09:49:42 Peer:WRN [9934] onReadMessage: Connection reset by peer
2018-Jan-24 09:49:42 Peer:WRN [9940] onReadMessage: Connection reset by peer
2018-Jan-24 09:49:43 LedgerConsensus:WRN We see no consensus, but 80% of nodes have moved on
2018-Jan-24 09:49:43 LedgerConsensus:ERR Unable to reach consensus
2018-Jan-24 09:49:43 LedgerConsensus:ERR 
{
    "acquired" : [ "0000000000000000000000000000000000000000000000000000000000000000" ],
    "close_resolution" : 10,
    "close_times" : 
    {
        "570102567" : 1,
        "570102568" : 3
    },
    "converge_percent" : 99,
    "current_ms" : 17999,
    "have_time_consensus" : true,
    "our_position" : 
    {
        "close_time" : "570102570",
        "previous_ledger" : "29AA78B5234C4002780C287BAC5BEA8CAD2E76032413267C6B96C9E62C6EF417",
        "propose_seq" : 3,
        "transaction_hash" : "0000000000000000000000000000000000000000000000000000000000000000"
    },
    "peer_positions" : 
    {
        "527AA0D411E2152B151FC3C79D2BFC5C039689C5" : 
        {
            "close_time" : "570102568",
            "peer_id" : "n9LwBhHaZ3BGMKJtzjJmhskemZfya99txPwbaVbkEu48YA5MuTNQ",
            "previous_ledger" : "B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13",
            "propose_seq" : 0,
            "transaction_hash" : "34457E873B92BF284BB6061A3CACE4998485F4CCC3219E85A80EA3EC8499AAD0"
        },
        "C3EC2D44DA7D7E50C437CC4964E79C1ECB4A8D0E" : 
        {
            "close_time" : "570102568",
            "peer_id" : "n9Jxzjh1mEFr83D4G6qAYRov2UzUiYXZwno2H4hjjygKJh4LJtwD",
            "previous_ledger" : "B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13",
            "propose_seq" : 0,
            "transaction_hash" : "34457E873B92BF284BB6061A3CACE4998485F4CCC3219E85A80EA3EC8499AAD0"
        },
        "E4FEEE12C7E87120DD4BD220E55ABDF710578ED9" : 
        {
            "close_time" : "570102568",
            "peer_id" : "n9MhLxPNQsVW34q9JK9j2zDuZ1qB1Yjt8cZ6cfdXwSkzaxXjvbQt",
            "previous_ledger" : "B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13",
            "propose_seq" : 0,
            "transaction_hash" : "34457E873B92BF284BB6061A3CACE4998485F4CCC3219E85A80EA3EC8499AAD0"
        },
        "E6C33D034038F579D52A1C046EC7D4662B0FBCD4" : 
        {
            "close_time" : "570102567",
            "peer_id" : "n9M6rLHLFssSjXnd4eagHFv954NJE64ApW2m4g1Xy2WWr3gNMHH6",
            "previous_ledger" : "B2AD5C4B30C62752D10F86323390898F3C0609E12DF0930AF83B0A7386C3CE13",
            "propose_seq" : 0,
            "transaction_hash" : "7863F494B0603CA4B6FCC7C9CCF78F0EF2A8FFD29BC57F302275DD5843DD9AF3"
        }
    },
    "phase" : "establish",
    "previous_mseconds" : 18000,
    "previous_proposers" : 5,
    "proposers" : 4,
    "proposing" : false,
    "synched" : false
}

2018-Jan-24 09:49:43 NetworkOPs:WRN We are not running on the consensus ledger

And this is my server info:

Loading: "/etc/opt/ripple/rippled.cfg"
2018-Jan-24 09:37:21 HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "id" : 1,
   "result" : {
      "info" : {
         "build_version" : "0.81.0",
         "closed_ledger" : {
            "age" : 11,
            "base_fee_xrp" : 1e-05,
            "hash" : "C4204421EE92790F2AB6CE39C67255A5DD8AA175F6387730E3A6069657810CBE",
            "reserve_base_xrp" : 200,
            "reserve_inc_xrp" : 50,
            "seq" : 1075
         },
         "complete_ledgers" : "empty",
         "fetch_pack" : 53,
         "hostid" : "AjitSoman",
         "io_latency_ms" : 1,
         "last_close" : {
            "converge_time_s" : 21,
            "proposers" : 6
         },
         "load" : {
            "job_types" : [
               {
                  "job_type" : "untrustedProposal",
                  "peak_time" : 7,
                  "per_second" : 25
               },
               {
                  "avg_time" : 1,
                  "job_type" : "ledgerData",
                  "peak_time" : 27,
                  "per_second" : 6
               },
               {
                  "in_progress" : 1,
                  "job_type" : "clientCommand"
               },
               {
                  "avg_time" : 1,
                  "job_type" : "transaction",
                  "peak_time" : 10,
                  "per_second" : 2
               },
               {
                  "job_type" : "fetchTxnData",
                  "peak_time" : 3,
                  "per_second" : 68
               },
               {
                  "avg_time" : 1,
                  "job_type" : "trustedValidation",
                  "peak_time" : 18
               },
               {
                  "job_type" : "writeObjects",
                  "peak_time" : 6,
                  "per_second" : 11
               },
               {
                  "job_type" : "trustedProposal",
                  "peak_time" : 2,
                  "per_second" : 1
               },
               {
                  "job_type" : "peerCommand",
                  "peak_time" : 3,
                  "per_second" : 252
               },
               {
                  "avg_time" : 2,
                  "job_type" : "diskAccess",
                  "peak_time" : 46
               },
               {
                  "job_type" : "SyncReadNode",
                  "per_second" : 27
               },
               {
                  "job_type" : "AsyncReadNode",
                  "peak_time" : 5,
                  "per_second" : 864
               },
               {
                  "job_type" : "WriteNode",
                  "per_second" : 32
               }
            ],
            "threads" : 4
         },
         "load_factor" : 1,
         "peers" : 10,
         "pubkey_node" : "n9MXQr1KYpDo2V8BgXLzLsLksmVugNHYFbTi7JQjRXxe6iG71mwM",
         "pubkey_validator" : "none",
         "published_ledger" : "none",
         "server_state" : "connected",
         "state_accounting" : {
            "connected" : {
               "duration_us" : "6577916946",
               "transitions" : 1
            },
            "disconnected" : {
               "duration_us" : "2079480",
               "transitions" : 1
            },
            "full" : {
               "duration_us" : "0",
               "transitions" : 0
            },
            "syncing" : {
               "duration_us" : "0",
               "transitions" : 0
            },
            "tracking" : {
               "duration_us" : "0",
               "transitions" : 0
            }
         },
         "uptime" : 6579,
         "validation_quorum" : 4,
         "validator_list_expires" : "2018-Feb-01 00:00:00"
      },
      "status" : "success"
   }
}

When i am checking account info i am getting InsufficientNetworkMode message

ajit@AjitSoman:/opt/ripple/bin$ ./rippled account_info rww9KRNZ7mEHNAXEeLdVreiuk4bimtmbiS
Loading: "/etc/opt/ripple/rippled.cfg"
2018-Jan-24 09:55:06 HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "id" : 1,
   "result" : {
      "error" : "noNetwork",
      "error_code" : 17,
      "error_message" : "InsufficientNetworkMode",
      "request" : {
         "account" : "rww9KRNZ7mEHNAXEeLdVreiuk4bimtmbiS",
         "command" : "account_info"
      },
      "status" : "error"
   }
}
ajit@AjitSoman:/opt/ripple/bin$

Can anybody suggest how to resolve this issue

MarkusTeufelberger commented 6 years ago

What's the content of your rippled.cfg file and the specs of your machine (RAM, CPU, HDD/SSD, Network uplink speed)?

ghost commented 6 years ago

This is my rippled.cfg

[server]
port_rpc_admin_local
port_peer
port_ws_admin_local
#port_ws_public
#ssl_key = /etc/ssl/private/server.key
#ssl_cert = /etc/ssl/certs/server.crt

[port_rpc_admin_local]
port = 5005
ip = 127.0.0.1
admin = 127.0.0.1
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

#-------------------------------------------------------------------------------

[node_size]
medium

# This is primary persistent datastore for rippled.  This includes transaction
# metadata, account states, and ledger headers.  Helpful information can be
# found here: https://ripple.com/wiki/NodeBackEnd
# delete old ledgers while maintaining at least 2000. Do not require an
# external administrative command to initiate deletion.
[node_db]
type=RocksDB
path=/var/lib/rippled/db/rocksdb
open_files=2000
filter_bits=12
cache_mb=256
file_size_mb=8
file_size_mult=2
online_delete=2000
advisory_delete=0

[database_path]
/var/lib/rippled/db

# This needs to be an absolute directory reference, not a relative one.
# Modify this value as required.
[debug_logfile]
/var/log/rippled/debug.log

[sntp_servers]
time.windows.com
time.apple.com
time.nist.gov
pool.ntp.org

# Where to find some other servers speaking the Ripple protocol.
#
[ips]
r.ripple.com 51235

# File containing trusted validator keys or validator list publishers.
# Unless an absolute path is specified, it will be considered relative to the
# folder in which the rippled.cfg file is located.
[validators_file]
validators.txt

# Turn down default logging to save disk space in the long run.
# Valid values here are trace, debug, info, warning, error, and fatal
[rpc_startup]
{ "command": "log_level", "severity": "warning" }

# If ssl_verify is 1, certificates will be validated.
# To allow the use of self-signed certificates for development or internal use,
# set to ssl_verify to 0.
[ssl_verify]
1

And this is my System configuration

RAM: 8 GB CPU: Intel core i3 2.30 GHz HDD: 500 GB Network Speed : 1 Mb/sec

MarkusTeufelberger commented 6 years ago

1 Mbit per second is FAR too low unfortunately, that's just ~100 kB/s. Even if you actually meant 1 MB/s that's also probably not enough. Try setting your [node_size] to tiny so rippled fetches a little less data at once.

Realistically though you'll need to upgrade your internet connection significantly.

ghost commented 6 years ago

I have set [node_size] to tiny and i am getting same logs:

Loading: "/etc/opt/ripple/rippled.cfg"
Watchdog: Launching child 1
2018-Jan-24 13:27:02 JobQueue:NFO Auto-tuning to 4 validation/transaction/proposal threads.
2018-Jan-24 13:27:03 Amendments:DBG Amendment C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1 is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D is supported.
2018-Jan-24 13:27:03 Amendments:DBG Amendment 1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454 is supported.
2018-Jan-24 13:27:03 OrderBookDB:DBG Advancing from 0 to 3
2018-Jan-24 13:27:03 OrderBookDB:DBG OrderBookDB::update>
2018-Jan-24 13:27:03 OrderBookDB:DBG OrderBookDB::update< 0 books found
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT;Seq: 2;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU;Seq: 2;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHBtzeujejMTAWCymPjcaQUjLgxnfxDGTGoZnP3PvHRkR24hVgjw;Seq: 1;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP;Seq: 2;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd;Seq: 4;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm;Seq: 2;
2018-Jan-24 13:27:03 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHBe4vqSAzjpPRLKwSFzRFtmvzXaf5wPPmuVrQCAoJoS1zskgDA4;Seq: 1;
2018-Jan-24 13:27:03 ValidatorList:DBG Loading configured trusted validator list publisher keys
2018-Jan-24 13:27:03 ValidatorList:DBG Loaded 1 keys
2018-Jan-24 13:27:03 ValidatorList:DBG Loading configured validator keys
2018-Jan-24 13:27:03 ValidatorList:DBG Loaded 0 entries
2018-Jan-24 13:27:03 ValidatorSite:DBG Loading configured validator list sites
2018-Jan-24 13:27:03 ValidatorSite:DBG Loaded 1 sites
2018-Jan-24 13:27:03 NodeObject:DBG NodeStore target size set to 16384
2018-Jan-24 13:27:03 NodeObject:DBG NodeStore target age set to 60000000000
2018-Jan-24 13:27:03 TaggedCache:DBG LedgerCache target size set to 32
2018-Jan-24 13:27:03 TaggedCache:DBG LedgerCache target age set to 30000000000
2018-Jan-24 13:27:03 TaggedCache:DBG TreeNodeCache target size set to 128000
2018-Jan-24 13:27:03 TaggedCache:DBG TreeNodeCache target age set to 30000000000
2018-Jan-24 13:27:03 NetworkOPs:NFO Consensus time for #3 with LCL 29977E976F4C6331758B657DAB604F7DFB936F854AFF3280E8993DDB72F87F38
2018-Jan-24 13:27:03 ValidatorList:DBG 0  of 0 listed validators eligible for inclusion in the trusted set
2018-Jan-24 13:27:03 ValidatorList:DBG Using quorum of 18446744073709551615 for new set of 0 trusted validators
2018-Jan-24 13:27:03 ValidatorList:WRN New quorum of 18446744073709551615 exceeds the number of trusted validators (0)
2018-Jan-24 13:27:03 LedgerConsensus:NFO Entering consensus process, watching, synced=no
2018-Jan-24 13:27:03 LedgerConsensus:NFO Consensus mode change before=observing, after=observing
2018-Jan-24 13:27:03 NetworkOPs:DBG Initiating consensus engine
2018-Jan-24 13:27:03 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http)
2018-Jan-24 13:27:03 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer)
2018-Jan-24 13:27:03 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws)
2018-Jan-24 13:27:03 Application:FTL Startup RPC: 
{
    "command" : "log_level",
    "severity" : "warning"
}

2018-Jan-24 13:27:03 Application:FTL Result: {}

2018-Jan-24 13:28:02 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 13:28:02 LedgerConsensus:WRN Need consensus ledger 477C7A70A8B420D34E5E4AB03853F96B5F26820CF0494D229A612C9442490225
2018-Jan-24 13:28:06 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 13:28:06 LedgerConsensus:WRN Need consensus ledger 9BB1BBDC0CBD06D6CE56083171CFB051408CB96539609E81AF017E8BA2BDA560
2018-Jan-24 13:28:09 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 13:28:11 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 13:28:11 LedgerConsensus:WRN Need consensus ledger D0CCC59AE5EF9B947E12B7AC54C501107BC947DB30A1CF74A135DF8B33368473
2018-Jan-24 13:28:13 LedgerConsensus:WRN By the time we got D313324BC8A7FAB4CDED2E66BCFAE43FC097A434FF934DF433952F23A7118F92 no peers were proposing it
2018-Jan-24 13:28:13 LedgerConsensus:WRN By the time we got 607A6EC758B91EFF7110823ABC010F9C8A16396C0F596A4928F6BC86E8AEBF68 no peers were proposing it
2018-Jan-24 13:28:13 LedgerConsensus:WRN By the time we got F9893E967EDFC3147119EB8DA8A4816139699C64BDE2F7C771A0987ABA28CF8F no peers were proposing it
2018-Jan-24 13:28:13 LedgerConsensus:WRN By the time we got 0D07E1A39C3A7CF2ECA1AC2723993A9006793C7C9507EF99DA44FC3E9869BEFD no peers were proposing it
2018-Jan-24 13:28:13 LedgerConsensus:WRN By the time we got A0338DC197DC20835A0C830D9A34D14BAAEF7C8748C5444E308F7C5BDB4C7B13 no peers were proposing it
2018-Jan-24 13:28:14 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-24 13:28:14 LedgerConsensus:WRN Need consensus ledger A97376A95D9673592DF3A26F5950343F7034CABF2E01772978D0DE427B10F35B
2018-Jan-24 13:28:17 NetworkOPs:WRN Submitted transaction invalid: Cannot both single- and multi-sign.
2018-Jan-24 13:28:20 NetworkOPs:WRN We are not running on the consensus ledger

Can you tell me the reason why i am getting this warning:We are not running on the consensus ledger

Also i have seen size of rocksdb . it has download around 900 MB

ajit@AjitSoman:/var/lib/rippled/db$ du . -h
909M    ./rocksdb/rippledb.e0cf
40K ./rocksdb/rippledb.4ab1
909M    ./rocksdb
916M    .
MarkusTeufelberger commented 6 years ago

You are likely running with the --net switch. This means your node is starting its own ledger (you got to over 1000 ledgers already, see "seq" : 1075) and tries to gradually pull data from other nodes until it has the same state as the rest of the network at which point it would switch over to the ledger chain that the network uses instead of its own private fork. However, while pulling the network state also changes over time (By the time we got ... no peers were proposing it), so it needs to play catch-up multiple times until it finally reaches the tip.

With 1 Mb or 1 MB per second this is going to be a difficult problem, since the other peers might move forward faster than you are able to catch up.

ghost commented 6 years ago

I have installed ripple client on AWS server which has these configuration: RAM: 4 GB CPU: Intel(R) Xeon(R) CPU E5-2676 v3 @ 2.40GHz HDD: 500 GB Network Speed : 332.70 Mbit/s

But still getting same logs

Loading: "/etc/opt/ripple/rippled.cfg"
Watchdog: Launching child 1
2018-Jan-25 06:57:30 JobQueue:NFO Auto-tuning to 4 validation/transaction/proposal threads.
2018-Jan-25 06:57:30 Amendments:DBG Amendment C6970A8B603D8778783B61C0D445C23D1633CCFAEF0D43E7DBCD1521D34BD7C3 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 4C97EBA926031A7CF7D7B36FDE3ED66DDA5421192D63DE53FFB46E43B9DC8373 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment C1B8D934087225F509BEB5A8EC24447854713EE447D277F69545ABFA0E0FD490 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 6781F8368C4771B83E8B821D88F580202BCB4228075297B19E4FDC5233F1EFDC is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 42426C4D4F1009EE67080A9B7965B44656D7714D104A72F9B4369F97ABF044EE is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 08DE7D96082187F6E6578530258C77FAABABE4C20474BDB82F04B021F1A68647 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 740352F2412A9909880C23A559FCECEDA3BE2126FED62FC7660D628A06927F11 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 1562511F573A19AE9BD103B5D6B9E01B3B46805AEC5D3C4805C902B514399146 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 532651B4FD58DF8922A49BA101AB3E996E5BFBF95A913B3E392504863E63B164 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment E2E6F2866106419B88C50045ACE96368558C345566AC8F2BDF5A5B5587F0E6FA is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 07D43DCE529B15A10827E5E04943B496762F9A88E3268269D69C44BE49E21104 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 86E83A7D2ECE3AD5FA87AB2195AE015C950469ABF0B72EAACED318F74886AE90 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 42EEA5E28A97824821D4EF97081FE36A54E9593C6E4F20CBAE098C69D2E072DC is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment DC9CA96AEA1DCF83E527D1AFC916EFAF5D27388ECA4060A88817C1238CAEE0BF is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 3012E8230864E95A58C60FD61430D7E1B4D3353195F2981DC12B0C7C0950FFAC is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment CC5ABAE4F3EC92E94A59B1908C2BE82D2228B6485C00AFF8F22DF930D89C194E is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment B4D44CC3111ADD964E846FC57760C8B50FFCD5A82C86A72756F6B058DDDF96AD is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 6C92211186613F9647A89DFFBAB8F94C99D4C7E956D495270789128569177DA1 is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment B9E739B8296B4A1BB29BE990B17D66E21B62A300A909F25AC55C22D6C72E1F9D is supported.
2018-Jan-25 06:57:30 Amendments:DBG Amendment 1D3463A5891F9E589C5AE839FFAC4A917CE96197098A1EF22304E1BC5B98A454 is supported.
2018-Jan-25 06:57:30 OrderBookDB:DBG Advancing from 0 to 3
2018-Jan-25 06:57:30 OrderBookDB:DBG OrderBookDB::update>
2018-Jan-25 06:57:30 OrderBookDB:DBG OrderBookDB::update< 0 books found
2018-Jan-25 06:57:30 ValidatorList:DBG Loading configured trusted validator list publisher keys
2018-Jan-25 06:57:30 ValidatorList:DBG Loaded 1 keys
2018-Jan-25 06:57:30 ValidatorList:DBG Loading configured validator keys
2018-Jan-25 06:57:30 ValidatorList:DBG Loaded 0 entries
2018-Jan-25 06:57:30 ValidatorSite:DBG Loading configured validator list sites
2018-Jan-25 06:57:30 ValidatorSite:DBG Loaded 1 sites
2018-Jan-25 06:57:30 NodeObject:DBG NodeStore target size set to 131072
2018-Jan-25 06:57:30 NodeObject:DBG NodeStore target age set to 120000000000
2018-Jan-25 06:57:30 TaggedCache:DBG LedgerCache target size set to 256
2018-Jan-25 06:57:30 TaggedCache:DBG LedgerCache target age set to 180000000000
2018-Jan-25 06:57:30 TaggedCache:DBG TreeNodeCache target size set to 512000
2018-Jan-25 06:57:30 TaggedCache:DBG TreeNodeCache target age set to 90000000000
2018-Jan-25 06:57:30 NetworkOPs:NFO Consensus time for #3 with LCL 722A990D5070AA2CF1A9AA5A125C836508989569D729AC48194BEB2CD02DAD22
2018-Jan-25 06:57:30 ValidatorList:DBG 0  of 0 listed validators eligible for inclusion in the trusted set
2018-Jan-25 06:57:30 ValidatorList:DBG Using quorum of 18446744073709551615 for new set of 0 trusted validators
2018-Jan-25 06:57:30 ValidatorList:WRN New quorum of 18446744073709551615 exceeds the number of trusted validators (0)
2018-Jan-25 06:57:30 LedgerConsensus:NFO Entering consensus process, watching, synced=no
2018-Jan-25 06:57:30 LedgerConsensus:NFO Consensus mode change before=observing, after=observing
2018-Jan-25 06:57:30 NetworkOPs:DBG Initiating consensus engine
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHBe4vqSAzjpPRLKwSFzRFtmvzXaf5wPPmuVrQCAoJoS1zskgDA4;Seq: 1;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUBGitjsiaiMJBWKYsJBHU2shmYt9m29hRqoh8AS5bSAjXoHmdd;Seq: 4;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHB1FqfBpNg7UTpiqEUkKcAiWqC2PFuoGY7FPWtCcXAxSkhpqDkm;Seq: 2;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUpwrafS45zmi6eT72XS5ijpkW5JwfL5mLdPhEibrqUvtRcMAjU;Seq: 2;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUgoJvpqXZMZwxh8ZoFseFJEVF8ryup9r2mFYchX7ftMdNn3jLT;Seq: 2;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHUXh1ELizQ5QLLqtNaVEbbbfMdq3wMkh14aJo5xi83xzzaatWWP;Seq: 2;
2018-Jan-25 06:57:30 ManifestCache:NFO Manifest: AcceptedNew;Pk: nHBtzeujejMTAWCymPjcaQUjLgxnfxDGTGoZnP3PvHRkR24hVgjw;Seq: 1;
2018-Jan-25 06:57:30 ValidatorSite:DBG Applied new validator list from https://vl.ripple.com
2018-Jan-25 06:57:30 Server:NFO Opened 'port_rpc_admin_local' (ip=127.0.0.1:5005, admin IPs:127.0.0.1, http)
2018-Jan-25 06:57:30 Server:NFO Opened 'port_peer' (ip=0.0.0.0:51235, peer)
2018-Jan-25 06:57:30 Server:NFO Opened 'port_ws_admin_local' (ip=127.0.0.1:6006, admin IPs:127.0.0.1, ws)
2018-Jan-25 06:57:30 Application:FTL Startup RPC: 
{
    "command" : "log_level",
    "severity" : "warning"
}

2018-Jan-25 06:57:30 Application:FTL Result: {}

2018-Jan-25 06:58:32 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:32 LedgerConsensus:WRN Need consensus ledger 62CC1CC02AFDDE9E3E4EDA8EA30BEC142A181FF5BBE60F60C0B72B0B06496540
2018-Jan-25 06:58:33 NetworkOPs:WRN Submitted transaction invalid: Cannot both single- and multi-sign.
2018-Jan-25 06:58:35 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:35 LedgerConsensus:WRN Need consensus ledger 2DEC5B4ECD083C63B57F47059308A172DB2A7470673E89FD080B119E25907494
2018-Jan-25 06:58:35 NetworkOPs:WRN Submitted transaction invalid: Cannot both single- and multi-sign.
2018-Jan-25 06:58:38 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:38 LedgerConsensus:WRN Need consensus ledger 81BEB8692AB51D1EA21048320E6E729C013A9A5E777CB5B09D1C0AB8ADCD65F1
2018-Jan-25 06:58:41 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:43 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:43 LedgerConsensus:WRN Need consensus ledger 058FFB5171A42B6D491ACD51F5DE00A92D7DEDD86B3F2C60F703217911DF6F76
2018-Jan-25 06:58:45 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:45 LedgerConsensus:WRN Need consensus ledger 832BE837B8A66F6188D8EB6ABDE909A794B179336CEF7F8B8A962CB2B7AB5915
2018-Jan-25 06:58:48 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:50 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:50 LedgerConsensus:WRN Need consensus ledger 55BE7C3F23FBB64601BA8DD7C6FDA5D7FD7600B265F5BD2BECB953CB04B7E908
2018-Jan-25 06:58:52 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:52 LedgerConsensus:WRN Need consensus ledger C466F4E05E492A2B926C043F40A3366DD49191C9A388FEB7EBDA10B07659BF6D
2018-Jan-25 06:58:55 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:57 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:57 LedgerConsensus:WRN Need consensus ledger B4BB4BDDC7174DA241313BA73E4F8451DAE12939CC3417599BB8FA78E679CBE9
2018-Jan-25 06:58:59 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:58:59 LedgerConsensus:WRN Need consensus ledger 458DFDC7E6D8D76455F5C82BCF8B8FA1F11B59A514856606483F6D08A1184AD5
2018-Jan-25 06:59:02 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:02 LedgerConsensus:WRN Need consensus ledger 9DDC394B2C14405F838925BF278C956A6F700B68C35B05BB04D09FAACC91CBB0
2018-Jan-25 06:59:05 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:05 LedgerConsensus:WRN Need consensus ledger AA7A4BB0D9CF88014ED382EBB7381C2F8A8EFA048337A801FCF1C8475C8E5E8F
2018-Jan-25 06:59:06 NetworkOPs:WRN Submitted transaction invalid: Cannot both single- and multi-sign.
2018-Jan-25 06:59:08 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:10 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:10 LedgerConsensus:WRN Need consensus ledger 87B27328A524944923339465081D76FC5FC549BB06CFBAE3009303F2AD719995
2018-Jan-25 06:59:12 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:12 LedgerConsensus:WRN Need consensus ledger 9CC564282E50A0F30AC09ED58C6D61A33B345B915EF6D264BCDE999642A9F214
2018-Jan-25 06:59:15 Peer:WRN [012] onReadMessage: short read
2018-Jan-25 06:59:15 Peer:WRN [014] onReadMessage: short read
2018-Jan-25 06:59:15 Peer:WRN [008] onReadMessage: short read
2018-Jan-25 06:59:15 Peer:WRN [005] onReadMessage: short read
2018-Jan-25 06:59:16 Peer:WRN [004] onReadMessage: short read
2018-Jan-25 06:59:16 Peer:WRN [006] onReadMessage: short read
2018-Jan-25 06:59:16 Peer:WRN [003] onReadMessage: short read
2018-Jan-25 06:59:16 Peer:WRN [007] onReadMessage: short read
2018-Jan-25 06:59:16 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:16 LedgerConsensus:WRN Need consensus ledger 59BC9FF1FD033121F40DAA88DD416504D020053EFD2EA694228D1F4111E07AD6
2018-Jan-25 06:59:19 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:19 LedgerConsensus:WRN Need consensus ledger EDD67EB0BDCF31D8E8780D9784B0D19C210DAF4B9EF9631FCB306417CC861029
2018-Jan-25 06:59:22 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:22 LedgerConsensus:WRN Need consensus ledger 6952E1C28F2967C84FF657AC9954B497427191A644BBF3FE30F47187F9ACDEA3
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 543ms wait: 604ms
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 977ms wait: 201ms
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 35ms wait: 1174ms
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 19ms wait: 1183ms
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 15ms wait: 1188ms
2018-Jan-25 06:59:25 LoadMonitor:WRN Job: processLedgerData run: 18ms wait: 1194ms
2018-Jan-25 06:59:26 LoadMonitor:WRN Job: processLedgerData run: 124ms wait: 904ms
2018-Jan-25 06:59:26 LoadMonitor:WRN Job: processLedgerData run: 124ms wait: 892ms
2018-Jan-25 06:59:26 LoadMonitor:WRN Job: processLedgerData run: 121ms wait: 1125ms
2018-Jan-25 06:59:26 LoadMonitor:WRN Job: processLedgerData run: 121ms wait: 1109ms
2018-Jan-25 06:59:27 LoadMonitor:WRN Job: recvValidation->checkValidation run: 1404ms wait: 0ms
2018-Jan-25 06:59:28 LoadMonitor:WRN Job: recvPropose->checkPropose run: 1323ms wait: 708ms
2018-Jan-25 06:59:28 LoadMonitor:WRN Job: NetOPs.heartbeat run: 1861ms wait: 34ms
2018-Jan-25 06:59:28 LoadMonitor:WRN Job: recvPropose->checkPropose run: 544ms wait: 1486ms
2018-Jan-25 06:59:28 LoadMonitor:WRN Job: recvPropose->checkPropose run: 2019ms wait: 17ms
2018-Jan-25 06:59:29 LoadMonitor:WRN Job: recvPropose->checkPropose run: 388ms wait: 2166ms
2018-Jan-25 06:59:29 LoadMonitor:WRN Job: recvPropose->checkPropose run: 388ms wait: 2166ms
2018-Jan-25 06:59:29 LoadMonitor:WRN Job: recvPropose->checkPropose run: 388ms wait: 2166ms
2018-Jan-25 06:59:29 LoadMonitor:WRN Job: NodeObject::store run: 116ms wait: 3285ms
2018-Jan-25 06:59:30 LoadMonitor:WRN Job: recvValidation->checkValidation run: 945ms wait: 3231ms
2018-Jan-25 06:59:30 LoadMonitor:WRN Job: recvValidation->checkValidation run: 982ms wait: 3247ms
2018-Jan-25 06:59:31 LoadMonitor:WRN Job: WAL run: 50ms wait: 4495ms
2018-Jan-25 06:59:31 LoadMonitor:WRN Job: reportFeeChange->pubServer run: 14ms wait: 2225ms
2018-Jan-25 06:59:32 LoadMonitor:WRN Job: reportFeeChange->pubServer run: 6ms wait: 1620ms
2018-Jan-25 06:59:32 LoadMonitor:WRN Job: reportFeeChange->pubServer run: 7ms wait: 1017ms
2018-Jan-25 06:59:33 LoadMonitor:WRN Job: ValidationWrite run: 3067ms wait: 0ms
2018-Jan-25 06:59:33 LoadMonitor:WRN Job: Validations::doStaleWrite run: 3219ms wait: 57ms
2018-Jan-25 06:59:34 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-25 06:59:34 LoadMonitor:WRN Job: processLedgerData run: 1322ms wait: 7532ms
2018-Jan-25 06:59:34 LoadMonitor:WRN Job: sweep run: 2959ms wait: 671ms
2018-Jan-25 06:59:34 LedgerConsensus:WRN Need consensus ledger BB359CC8214E047F077596A67E79280D21BEEAD5104D083D2DA3F068C3D632B8
2018-Jan-25 06:59:35 LoadMonitor:WRN Job: reportFeeChange->pubServer run: 8ms wait: 1263ms
2018-Jan-25 06:59:35 LoadMonitor:WRN Job: processLedgerData run: 1595ms wait: 8916ms
2018-Jan-25 06:59:35 LoadMonitor:WRN Job: processLedgerData run: 1581ms wait: 8389ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: processLedgerData run: 258ms wait: 9515ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: acceptLedger run: 7736ms wait: 669ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: recvPropose->checkPropose run: 778ms wait: 9351ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: processLedgerData run: 2ms wait: 10182ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: processLedgerData run: 262ms wait: 10064ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: NetOPs.heartbeat run: 927ms wait: 74ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: recvPropose->checkPropose run: 134ms wait: 10194ms
2018-Jan-25 06:59:36 LoadMonitor:WRN Job: processLedgerData run: 140ms wait: 10181ms
2018-Jan-25 06:59:37 LoadMonitor:WRN Job: recvPropose->checkPropose run: 134ms wait: 10409ms
2018-Jan-25 06:59:37 LoadMonitor:WRN Job: recvPropose->checkPropose run: 179ms wait: 10559ms
2018-Jan-25 06:59:37 LoadMonitor:WRN Job: recvPropose->checkPropose run: 190ms wait: 10825ms
2018-Jan-25 06:59:37 LoadMonitor:WRN Job: recvPropose->checkPropose run: 205ms wait: 11112ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 121ms wait: 11457ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 129ms wait: 11449ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: processLedgerData run: 1285ms wait: 3137ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: processLedgerData run: 1285ms wait: 5086ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 199ms wait: 11787ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 199ms wait: 11787ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 199ms wait: 11787ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 72ms wait: 11976ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12058ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 0ms wait: 12047ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvPropose->checkPropose run: 2ms wait: 12059ms
2018-Jan-25 06:59:38 LoadMonitor:WRN Job: recvValidation->checkValidation run: 30ms wait: 12100ms
2018-Jan-25 06:59:39 LoadMonitor:WRN Job: recvValidation->checkValidation run: 763ms wait: 280ms
2018-Jan-25 06:59:39 LoadMonitor:WRN Job: recvValidation->checkValidation run: 765ms wait: 281ms
2018-Jan-25 06:59:39 LoadMonitor:WRN Job: recvPropose->checkPropose run: 124ms wait: 932ms
2018-Jan-25 06:59:40 LoadMonitor:WRN Job: recvValidation->checkValidation run: 1167ms wait: 281ms
2018-Jan-25 06:59:40 LoadMonitor:WRN Job: recvValidation->checkValidation run: 1394ms wait: 281ms
2018-Jan-25 06:59:43 LedgerConsensus:WRN We see no consensus, but 80% of nodes have moved on
2018-Jan-25 06:59:43 LedgerConsensus:ERR Unable to reach consensus
2018-Jan-25 06:59:43 LedgerConsensus:ERR
bachase commented 6 years ago

Hi @ajit-soman,

What type of storage is your AWS instance using? Maximum IOPS?

We are working on updating specifications for running rippled, both locally and on cloud providers and appreciate your feedback.

MarkusTeufelberger commented 6 years ago

You might want to wait longer than just 2 minutes...

4 GB RAM is also rather on the lower end - did you set your node_size to tiny?

JoelKatz commented 6 years ago

It's pretty difficult to catch up the network, a moving target, in just 2 minutes. I'd wait at least ten before getting concerned.

jmozah commented 6 years ago

I get the same issue for the past few days "We are not running on the consensus ledger". On increasing the log level to info i get " LedgerConsensus:NFO Consensus mode change before=wrongLedger, after=wrongLedger".

This setup was working until Jan19th and suddenly on that day morning my ledger sync stopped. I deleted the entire db and started fresh now. Seeing the same problem and it has been running for 10 hours now.

I am on 0.81 version, size tiny on a 4 core , 8 GB RAM, 2000 Mbps bandwidth.

wilsonianb commented 6 years ago

Hi @jmozah The keys on Ripple-operated validators were changed around that time. Please confirm that your rippled.cfg and validators.txt files have been updated accordingly. https://groups.google.com/forum/#!topic/ripple-server/4EJyLZZUu4o

jmozah commented 6 years ago

@wilsonianb Thanks for the info. Really appreciate it. I missed it completely. Where can i get the updated validators list for testnet?

wilsonianb commented 6 years ago

For the testnet, you can instead add the following to your validators.txt

[validator_list_sites]
https://vl.altnet.rippletest.net

[validator_list_keys]
ED264807102805220DA0F312E71FC2C69E1552C9C5790F6C25E3729DEB573D5860
jmozah commented 6 years ago

@wilsonianb Thanks a ton

ghost commented 6 years ago

@bachase
This is the iostat of server

Linux 3.13.0-116-generic (ip----)   01/26/2018  _x86_64_    (2 CPU)

avg-cpu:  %user   %nice %system %iowait  %steal   %idle
           0.33    0.00    0.07    0.03    0.15   99.42

Device:            tps    kB_read/s    kB_wrtn/s    kB_read    kB_wrtn
xvda              1.50        16.70        28.64  302792226  519284204

Storage type is c1.medium

@MarkusTeufelberger and @JoelKatz

Here is the ripple client logs after 20 min 

2018-Jan-26 09:18:11 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-26 09:18:11 LedgerConsensus:WRN Need consensus ledger B923D03681E4304E04618D3978B5981971863833FEF090958F8794249A9401B0
2018-Jan-26 09:18:11 LoadMonitor:WRN Job: processLedgerData run: 2753ms wait: 2030ms
2018-Jan-26 09:18:11 LoadMonitor:WRN Job: processLedgerData run: 2513ms wait: 665ms
2018-Jan-26 09:18:11 LoadMonitor:WRN Job: processLedgerData run: 135ms wait: 3005ms
2018-Jan-26 09:18:11 LoadMonitor:WRN Job: processLedgerData run: 175ms wait: 2997ms
2018-Jan-26 09:18:11 LoadMonitor:WRN Job: processLedgerData run: 221ms wait: 2930ms
2018-Jan-26 09:18:12 LoadMonitor:WRN Job: processLedgerData run: 258ms wait: 2584ms
2018-Jan-26 09:18:12 LoadMonitor:WRN Job: processLedgerData run: 60ms wait: 2415ms
2018-Jan-26 09:18:12 LoadMonitor:WRN Job: processLedgerData run: 340ms wait: 2472ms
2018-Jan-26 09:18:14 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-26 09:18:15 LoadMonitor:WRN Job: processLedgerData run: 3660ms wait: 1286ms
2018-Jan-26 09:18:15 LoadMonitor:WRN Job: processLedgerData run: 132ms wait: 3630ms
2018-Jan-26 09:18:15 LoadMonitor:WRN Job: processLedgerData run: 51ms wait: 3383ms
2018-Jan-26 09:18:15 LoadMonitor:WRN Job: processLedgerData run: 46ms wait: 3422ms
2018-Jan-26 09:18:16 LoadMonitor:WRN Job: processLedgerData run: 335ms wait: 3238ms
2018-Jan-26 09:18:16 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-26 09:18:16 LedgerConsensus:WRN Need consensus ledger B2838B737CD88993EE35451CF5D7B4676114540B9888BA3C1CA67B8E47814655
2018-Jan-26 09:18:16 LoadMonitor:WRN Job: processLedgerData run: 204ms wait: 2714ms
2018-Jan-26 09:18:16 LoadMonitor:WRN Job: processLedgerData run: 111ms wait: 2897ms
2018-Jan-26 09:18:17 LoadMonitor:WRN Job: processLedgerData run: 251ms wait: 880ms
2018-Jan-26 09:18:17 LoadMonitor:WRN Job: processLedgerData run: 100ms wait: 1068ms
2018-Jan-26 09:18:18 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-26 09:18:19 LoadMonitor:WRN Job: processLedgerData run: 7178ms wait: 514ms
2018-Jan-26 09:18:20 NetworkOPs:WRN We are not running on the consensus ledger
2018-Jan-26 09:18:20 LedgerConsensus:WRN Need consensus ledger 98C281D93B5BF5FFC4D52ACB3E50A56E791EC09907ED1524CEEB79044EE50759
2018-Jan-26 09:18:21 LoadMonitor:WRN Job: processLedgerData run: 4252ms wait: 703ms
2018-Jan-26 09:18:21 LoadMonitor:WRN Job: processLedgerData run: 1843ms wait: 3110ms
2018-Jan-26 09:18:21 LoadMonitor:WRN Job: processLedgerData run: 64ms wait: 4831ms
2018-Jan-26 09:18:21 LoadMonitor:WRN Job: processLedgerData run: 119ms wait: 4742ms
2018-Jan-26 09:18:21 LoadMonitor:WRN Job: processLedgerData run: 227ms wait: 4530ms
jmozah commented 6 years ago

@wilsonianb I am getting "Unsupported amendment" after i updated the validators list for testnet.

Amendments:ERR Unsupported amendment 157D2D480E006395B76F948E3E07A45A05FE10230D88A7993C71F97AE4B1F2D1 activated.
Amendments:ERR Unsupported amendment 67A34F2CF55BFC0F93AACD5B281413176FEE195269FA6D95219A2DF738671172 activated.
Amendments:ERR Unsupported amendment F64E1EABBE79D55B3BB82020516CEC2C582A98A6BFE20FBE9BB6A0D233418064 activated.
LedgerMaster:ERR One or more unsupported amendments activated: server blocked.

I am running rippled version 0.81.0.

PS: Is GH issues the right place to ask questions like this .. or do ripple devs hangout in discord or something.

jmozah commented 6 years ago

looks like for testnet we need 0.90.0-b2 atleast.

wilsonianb commented 6 years ago

The Checks amendment (introduced in 0.90.0-b4) is enabled on the testnet, so that's the version you'll need.

ghost commented 6 years ago

I run rippled ledger current command yesterday. I got this output on aws server:

ubuntu@ip-xxx:~$ /opt/ripple/bin/rippled ledger current
Loading: "/etc/opt/ripple/rippled.cfg"
2018-Feb-01 14:14:33 HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "id" : 1,
   "result" : {
      "ledger" : {
         "closed" : false,
         "ledger_index" : "36263704",
         "parent_hash" : "615560C970DB9F230B2E77294C6E65800D372ADEF23C7E89E927EEDC43B14A22",
         "seqNum" : "36263704"
      },
      "ledger_current_index" : 36263704,
      "status" : "success",
      "validated" : false
   }
}
ubuntu@ip-xxx:~$

But now I am running the same command i am getting this output 

ubuntu@ip-xxx:~$ /opt/ripple/bin/rippled ledger current
Loading: "/etc/opt/ripple/rippled.cfg"
2018-Feb-02 04:56:37 HTTPClient:NFO Connecting to 127.0.0.1:5005

{
   "id" : 1,
   "result" : {
      "error" : "noNetwork",
      "error_code" : 17,
      "error_message" : "InsufficientNetworkMode",
      "request" : {
         "command" : "ledger",
         "ledger_index" : "current"
      },
      "status" : "error"
   }
}
ubuntu@ip-xxx:~$

I haven't changed anything . Can anybody give some suggestion how to fix this issue.

ghost commented 6 years ago

This is a system dependent issue . To run a ripple client you will need a system with good hardware configuration along with high speed internet

DaveWK commented 6 years ago

it seems even with good hardware it ignores attempts to catch up without manual intervention... why can't it just attempt to fetch missing ledgers without me using ledger_cleaner by hand?

songjim commented 6 years ago

hi，guys how long does the test network sync? my server_info: `Loading: "/home/ubuntu/.config/ripple/rippled.cfg" 2018-May-10 06:48:13 HTTPClient:NFO Connecting to 127.0.0.1:5005

{ "result" : { "info" : { "build_version" : "0.90.1", "closed_ledger" : { "age" : 13, "base_fee_xrp" : 1e-05, "hash" : "447A93ADBBA8B24A7B4D403D6AFC60F5617347B92BA4A0DB72E81B68E1223177", "reserve_base_xrp" : 200, "reserve_inc_xrp" : 50, "seq" : 3 }, "complete_ledgers" : "empty", "hostid" : "songjian", "io_latency_ms" : 1, "jq_trans_overflow" : "0", "last_close" : { "converge_time_s" : 1.999, "proposers" : 0 }, "load" : { "job_types" : [ { "job_type" : "untrustedValidation", "per_second" : 2 }, { "job_type" : "untrustedProposal", "per_second" : 53 }, { "in_progress" : 2, "job_type" : "ledgerData" }, { "in_progress" : 1, "job_type" : "clientCommand" }, { "job_type" : "writeObjects", "per_second" : 20 }, { "job_type" : "peerCommand", "per_second" : 692 }, { "job_type" : "SyncReadNode", "peak_time" : 7, "per_second" : 84 }, { "job_type" : "AsyncReadNode", "peak_time" : 40, "per_second" : 65667 }, { "job_type" : "WriteNode", "per_second" : 23 } ], "threads" : 6 }, "load_factor" : 1, "network_ledger" : "waiting", "peer_disconnects" : "0", "peer_disconnects_resources" : "0", "peers" : 10, "pubkey_node" : "n9L35pCohrTuT2dYBB3yePw3uoEjxGbyAV7iLXnDu1FFszgPTSeu", "pubkey_validator" : "none", "published_ledger" : "none", "server_state" : "connected", "state_accounting" : { "connected" : { "duration_us" : "83797501", "transitions" : 1 }, "disconnected" : { "duration_us" : "1254960", "transitions" : 1 }, "full" : { "duration_us" : "0", "transitions" : 0 }, "syncing" : { "duration_us" : "0", "transitions" : 0 }, "tracking" : { "duration_us" : "0", "transitions" : 0 } }, "uptime" : 85, "validation_quorum" : 11, "validator_list_expires" : "2018-May-20 00:00:00" }, "status" : "success" } }` i can use websocket API just after complete the testnet sync ?