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

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password

Need help to recover blpckchain.info wallet, my wife forgot her password and the brute force with btcrecover is not catching the password I used btcrecover to extract the wallet file (wallet.aes.json) from a blockchain account and I have been running btcrecover with dictionaries of my making but it has been going on for weeks and I am running out of ideas on how to permutate what my wife and I think the password could have been. Is there a way to just manually transfer the btc from the old wallet into a new wallet we do have access to or is there any way to extract the password or private keys directly from the wallet file? We have: the phone with the original wallet app installed, the wallet file pulled using btcrecover, access to the email to allow authorization to access, the wallet identifier that was sent to her email when she first signed up, the phone which has the wallet, the pin that was used for the wallet, and we know how much btc is in the account. We do not have: The pri...
Read more

When downloading the blockchain my application is become unusable, is there an issue with my code or am I using the BitcoinJ library incorrectly?

When downloading the blockchain my application is become unusable, is there an issue with my code or am I using the BitcoinJ library incorrectly? I am building a Bitcoin wallet with the BitcoinJ Library, after looking at the example of fetching a transaction that they have shown on their github it shows that you need to download the blockchain however. When attempting to download the blockchain to view the balance of my wallet, it begins to lock up and become unusable. I have even tried downloading the blockchain in an async task like so, but still the app becomes completely unusable and the UI doesn't even load. What am I missing? I thought that the download wouldn't be that large as I am attempting to create an SPV wallet which from what I understand doesn't download the entire blockchain, or is this something I need to configure seperately? class MainActivity : AppCompatActivity() { override fun onCreate(savedInstanceState: Bundle?) { DownloadBlockchain(...
Read more

Mistakenly sent BTC from my personal wallet back to one of the exchange wallet addresses that I had received BTC from before - help recovering!

Mistakenly sent BTC from my personal wallet back to one of the exchange wallet addresses that I had received BTC from before - help recovering! TDLR: I sent BTC from an exchange to a personal wallet. Several months later I mistakenly sent BTC from my personal wallet back to one of the exchange wallet addresses that I had received BTC from. The exchange is saying that they do not own the wallet ID. Can someone please look at this sequence of events and help me clarify the situation or more effectively communicate this situation to the exchange? Here's a chronological order of events Exchange Transaction (sent from Exchange to personal wallet) Jul 23, 2017 https://blockchain.info/tx/8541cdf82b99f9ff87092cbf6109b972c520f59087471d58ff4e171e130f5ff1 I transfer 0.0072780 BTC to wallet ID 12QWuHYViDzaW3R4ksrTYR9xuhDhgJc9nK (lets call this wallet-A) Jul 25, 2017 https://blockchain.info/tx/73ef9cdd28e2a22a81d28421b4f9b44afd364813df85a4404226261c555c754d I transfer 2.13505777 BTC to wa...
Read more