simaqiaoxi
commented
6 years ago Another server_info where the state is connected instead of full, complete_ledgers now empty and the closed leger is... seq 422, the start of rippled history? Still reporting noNetwork for hours.
{
"result": {
"info": {
"build_version": "0.90.0",
"closed_ledger": {
"age": 0,
"base_fee_xrp": 0.00001,
"hash": "24E533C0BA598B577F67CAE77E883721338F6120A559F83DB60602A86D00963A",
"reserve_base_xrp": 200,
"reserve_inc_xrp": 50,
"seq": 422
},
"complete_ledgers": "empty",
"fetch_pack": 21082,
"hostid": "72e6212c021f",
"io_latency_ms": 1,
"jq_trans_overflow": "0",
"last_close": {
"converge_time_s": 1.999,
"proposers": 16
},
"load": {
"job_types": [
{
"job_type": "untrustedProposal",
"peak_time": 2,
"per_second": 54
},
{
"avg_time": 16,
"in_progress": 2,
"job_type": "ledgerData",
"peak_time": 287,
"per_second": 13,
"waiting": 7
},
{
"in_progress": 1,
"job_type": "clientCommand"
},
{
"job_type": "transaction",
"peak_time": 2,
"per_second": 18
},
{
"job_type": "batch",
"per_second": 5
},
{
"job_type": "advanceLedger",
"per_second": 10
},
{
"job_type": "fetchTxnData",
"peak_time": 1,
"per_second": 45
},
{
"avg_time": 1,
"job_type": "trustedValidation",
"peak_time": 34,
"per_second": 3
},
{
"job_type": "writeObjects",
"peak_time": 1,
"per_second": 253
},
{
"avg_time": 1,
"job_type": "acceptLedger",
"peak_time": 3
},
{
"job_type": "trustedProposal",
"per_second": 7
},
{
"avg_time": 1,
"job_type": "heartbeat",
"peak_time": 2
},
{
"job_type": "peerCommand",
"per_second": 706
},
{
"job_type": "diskAccess",
"peak_time": 1,
"per_second": 3
},
{
"job_type": "processTransaction",
"per_second": 9
},
{
"job_type": "SyncReadNode",
"peak_time": 13,
"per_second": 374
},
{
"job_type": "AsyncReadNode",
"peak_time": 80,
"per_second": 1054
},
{
"job_type": "WriteNode",
"per_second": 400
}
],
"threads": 6
},
"load_factor": 1,
"peer_disconnects": "337",
"peer_disconnects_resources": "0",
"peers": 9,
"pubkey_node": "n9Kd572TQTiF6xaDtu4DBugXpZMHxm7gcGVd4q9bHvcvnsLVHeNQ",
"pubkey_validator": "none",
"published_ledger": "none",
"server_state": "connected",
"state_accounting": {
"connected": {
"duration_us": "2293891912",
"transitions": 2
},
"disconnected": {
"duration_us": "1545861",
"transitions": 1
},
"full": {
"duration_us": "69015070",
"transitions": 1
},
"syncing": {
"duration_us": "0",
"transitions": 0
},
"tracking": {
"duration_us": "29",
"transitions": 1
}
},
"uptime": 2364,
"validation_quorum": 11,
"validator_list_expires": "2018-Apr-09 00:00:00"
},
"status": "success"
}
}
nbougalis
After seeing a noNetwork event should we expect for complete_ledgers to reset? On a few occasions we have had a 'noNetwork' outage spanning anywhere from 10mins-2hours from our ripple node. This morning managed to grab a few server_info's while it was occurring, could you please inform if anything is unusual in this state? Was surprised to see complete-ledgers cleared out. (ledger_history is set to 16)
Also noted the low uptime although this is running in a docker container currently reporting 47hrs uptime (after a reset the last time it was stuck reporting noNetwork too long).
Any advice much appreciated. Also looking for notes on how we can encourage rippled to fill the gaps in these ledgers? We don't want a full history, but would like to have say... a full history since ledger 37541387