I have updated ripple server from the version from 0.90.1 to 1.0.0 and after that, It is not showing server state as full

I have updated ripple server from the version from 0.90.1 to 1.0.0 and after that, It is not showing server state as full

I have updated ripple server from the version from 0.90.1 to 1.0.0 and after that, It is not showing server state as full any time and at time of the transaction, it shows error as no network.

server_state command result as

Loading: "/etc/opt/ripple/rippled.cfg" 2018-May-29 12:04:11.486921582 HTTPClient:NFO Connecting to 127.0.0.1:5005

{ "result" : { "state" : { "build_version" : "1.0.0", "closed_ledger" : { "base_fee" : 10, "close_time" : 580910650, "hash" : "0C4B9474F937617748A9E30431FA39EF0868148C6DC4E52CE8065E999096AD9F", "reserve_base" : 200000000, "reserve_inc" : 50000000, "seq" : 246 }, "complete_ledgers" : "empty", "fetch_pack" : 10131, "io_latency_ms" : 1, "jq_trans_overflow" : "0", "last_close" : { "converge_time" : 3000, "proposers" : 0 }, "load" : { "job_types" : [ { "job_type" : "untrustedProposal", "peak_time" : 15, "per_second" : 47 }, { "in_progress" : 2, "job_type" : "ledgerData", "waiting" : 29 }, { "in_progress" : 1, "job_type" : "clientCommand" }, { "job_type" : "transaction", "per_second" : 11 }, { "job_type" : "advanceLedger", "peak_time" : 12, "per_second" : 7 }, { "job_type" : "fetchTxnData", "per_second" : 15 }, { "avg_time" : 2, "job_type" : "trustedValidation", "peak_time" : 17, "per_second" : 3 }, { "avg_time" : 1, "job_type" : "writeObjects", "peak_time" : 16, "per_second" : 3 }, { "job_type" : "trustedProposal", "peak_time" : 16, "per_second" : 6 }, { "job_type" : "peerCommand", "per_second" : 745 }, { "job_type" : "diskAccess", "peak_time" : 11, "per_second" : 2 }, { "job_type" : "AsyncReadNode", "peak_time" : 14, "per_second" : 996 } ], "threads" : 4 }, "load_base" : 256, "load_factor" : 256, "network_ledger" : "waiting", "peer_disconnects" : "2", "peer_disconnects_resources" : "0", "peers" : 10, "pubkey_node" : "n9MuzdNGGMcof5i2gtHaDkP8bwNHbCSyX8stM1vqJf4wVT3AB9WN", "pubkey_validator" : "none", "published_ledger" : "none", "server_state" : "connected", "state_accounting" : { "connected" : { "duration_us" : "1166488476", "transitions" : 1 }, "disconnected" : { "duration_us" : "1501687", "transitions" : 1 }, "full" : { "duration_us" : "0", "transitions" : 0 }, "syncing" : { "duration_us" : "0", "transitions" : 0 }, "tracking" : { "duration_us" : "0", "transitions" : 0 } }, "time" : "2018-May-29 12:04:11.487299", "uptime" : 1168, "validation_quorum" : 11, "validator_list_expires" : 581385600 }, "status" : "success" } }

https://ift.tt/2IUXQwP

Comments

Post a Comment

Popular posts from this blog

The Importance Of Owning Crypto

Image
The Importance Of Owning Crypto 😀 Thank You For Watching! :D 🚩 Remember to subscribe and hit the bell "🔔" icon! ►Need certified & professional help with your crypto taxes? Taxbit is here to help! Use this link to receive 10% off of their services: https://ift.tt/2GUy4uv ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ SUPPORT THE CHANNEL ► Patreon Sponsors (Private Telegram Group) - https://goo.gl/vpX5sW ► YouTube Sponsors - https://www.youtube.com/channel/UCdUSSt-IEUg2eq46rD7lu_g/join -~-~~-~~~-~~-~- 💓Crypto Donations Are Really Appreciated!💓 💎►Donate Ether and Ethereum-Based Tokens: 0x1466032B4F0F13910DA35B16371807428CB40714 💎►Donate Bitcoin: 3JKQycXHdD5yqSRTf5VabM28Ff9AfXYcJD 💎►Donate Bitcoin Cash: qrsq45lsrumctyu98mgjgc0qjaleng2jdgau3qz90x 💎►Donate Dash Xn1sUfFDkZAwArJ6mtJUYVLndnmXctxA1L 💎►Donate Monero 463EDu2cqU4ASxLVVKYkVMbk1Nz6TQyy9Wt8b3D5CdJjZh9JukZNGUyLvbJnXoJNRXTN98cSpLSRVN2bYoDTmsxkJSUKtmy 💎►Donate Using Paypal: https://goo.gl/7m1X4Z -~-~~-~~~-~~-~- MUS...
Read more

Activation of SegWit v1

Activation of SegWit v1 The segregated witness soft fork of August 2017 included a versioning field which would allow for future incrementation. Anthony Towns has recently posted an early draft of the proposal for the SegWit v1 upgrade to the mailing list . Although the devil is of course in the details, how could such an upgrade process look like? What are the different upgrade mechanism for the major [v1 - v16] and minor [v1.0 - v1.127] version changes? How is the soft fork signaled? How is the consensus change enforced? Is the v1 change as "contentious" and time consuming as v0 was? What are the tasks of node operators and miners? Thank you in advance for the answer! https://ift.tt/2VrPDpG
Read more

Nonce usage in ECDSA signing algorithm

Nonce usage in ECDSA signing algorithm I'm trying to understand the signing function secp256k1_ecdsa_sig_sign(), and I'm curious about the nonce usage here. static int secp256k1_ecdsa_sig_sign(const secp256k1_ecmult_gen_context *ctx, secp256k1_scalar *sigr, secp256k1_scalar *sigs, const secp256k1_scalar *seckey, const secp256k1_scalar *message, const secp256k1_scalar *nonce, int *recid) { unsigned char b[32]; secp256k1_gej rp; secp256k1_ge r; secp256k1_scalar n; int overflow = 0; secp256k1_ecmult_gen(ctx, &rp, nonce); secp256k1_ge_set_gej(&r, &rp); secp256k1_fe_normalize(&r.x); secp256k1_fe_normalize(&r.y); secp256k1_fe_get_b32(b, &r.x); secp256k1_scalar_set_b32(sigr, b, &overflow); /* These two conditions should be checked before calling */ VERIFY_CHECK(!secp256k1_scalar_is_zero(sigr)); VERIFY_CHECK(overflow == 0); if (recid) { /* The overflow condition is cryptographically unreachable as hitting it requires f...
Read more