BitShares Forum
Main => Technical Support => Topic started by: kingslanding on November 17, 2014, 02:54:53 pm
-
I installed 0.2.24 and it syncs most of the way but it slows down at the very end. It gets to the point where as soon as a block is synced, a new block comes along. So it never finishes.
I tried reinstalling, removing the bitshares dir except the wallet dir, resetting the database (via killing the process), and still get the same thing. I'm running on Windows 8.
Any suggestions on how to fix this?
-
I installed 0.2.24 and it syncs most of the way but it slows down at the very end. It gets to the point where as soon as a block is synced, a new block comes along. So it never finishes.
do you get these info from the GUI .. or from typing "getinfo" in the console?
have you tried "getinfo" in the console?
-
I installed 0.2.24 and it syncs most of the way but it slows down at the very end. It gets to the point where as soon as a block is synced, a new block comes along. So it never finishes.
do you get these info from the GUI .. or from typing "getinfo" in the console?
have you tried "getinfo" in the console?
I was getting it from the GUI at first. When I type get_info in the console, the blockchain_head_block_num matches the latest block processed so far shown in the GUI. It's always about 15 blocks away from finishing.
> get_info
{
"blockchain_head_block_num": 1034155,
"blockchain_head_block_age": "7 seconds old",
"blockchain_head_block_timestamp": "2014-11-17T15:41:10",
"blockchain_average_delegate_participation": "100.00 %",
"blockchain_confirmation_requirement": 1,
"blockchain_share_supply": "2,498,103,908.06907 BTS",
"blockchain_blocks_left_in_round": 85,
"blockchain_next_round_time": "at least 14 minutes in the future",
"blockchain_next_round_timestamp": "2014-11-17T15:55:20",
"blockchain_random_seed": "ff4e8cc3b55c49b7a10177613b4e093c41a3c5ec",
"client_data_dir": "C:/Users/xxxxxx/AppData/Roaming/BitShares",
"client_version": "v0.4.24",
"network_num_connections": 8,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2014-11-17T15:41:17",
"ntp_time_error": -156.319625,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2014-11-29T05:21:50",
"wallet_last_scanned_block_timestamp": "2014-11-17T15:41:10",
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
-
You are totally fine ... you latest block age (second line) shows a number in the seconds
You can also try
blockchain_is_synched
-
You are totally fine ... you latest block age (second line) shows a number in the seconds
You can also try
blockchain_is_synched
I tried blockchain_is_synced and it came back true, so you're correct. Thanks for the help. I'll ignore the GUI output.