BitShares Forum
Main => Technical Support => Topic started by: optictopic on May 11, 2015, 04:48:19 pm
-
I am running mac os 10.10.3 I had to reinstall the bitshares client. After opening the latest version 0.9.1 it took about an hour to make it to 68% sync. The client cycles between no connection and limited connection to the network. When it switches between being connected and not connected the 68% flashes to 100% for a fraction of a second. What should I do?
-
I am running mac os 10.10.3 I had to reinstall the bitshares client. After opening the latest version 0.9.1 it took about an hour to make it to 68% sync. The client cycles between no connection and limited connection to the network. When it switches between being connected and not connected the 68% flashes to 100% for a fraction of a second. What should I do?
wait until it catches up .. you may also delete the "peers_leveldb" folder in
~/Library/Application Support/BitShares
so that the client polls the seed nodes for new network nodes to download the chain from.
more advanced users may also try to download the chain from a chainserver
http://wiki.bitshares.org/index.php/BitShares/Chain-Server
-
The release 0.9.1 will also not sync for me on mac os x 10.9.4, it's stuck at block 1902795
I also enabled download from a chainserver too, and also reset the blockchain twice already, always stuck at about 75%
It says it has 10 network connections.
-
how long are you waiting? This is odd :(
do you get any other useful information from the CLI?
-
The cli is actually not even responding once it's stuck, I type get_info but I get no return. It looks like the server component has crashed. Very weird.
Need assistance :)
-
The cli is actually not even responding once it's stuck, I type get_info but I get no return. It looks like the server component has crashed. Very weird.
Need assistance :)
Ah .. ok .. I guess you can see heavy hard drive activity .. don't you?
The syncing progress is a computational expensive task that produces plenty of disk operations .. so you may just need more patients.
The CLI actually is the server component and when it is heavily syincing it may not respond to your commands quickly. Once the client is synced, you should restart it so that residual syncing data in the memory is wiped.
-
I left it running over night and it had no hard disk activity in the morning, but it was still stuck at about 73%
-
I left it running over night and it had no hard disk activity in the morning, but it was still stuck at about 73%
and you are still having connections?
could you run "about" and "info" and paste the results here?
-
I deleted the entire blockchain and let it resync from scratch. Stuck at block 1990812 for about an hour now. I tried restarting too, still stuck.
>> about
{
"blockchain_name": "BitShares",
"blockchain_description": "Decentralized Exchange",
"client_version": "0.9.1",
"bitshares_revision": "825aa724bb60564bd088a29101da96021613a9e9",
"bitshares_revision_age": "9 days ago",
"fc_revision": "e9824e174082d65117fd51d17377675d06bab7de",
"fc_revision_age": "9 days ago",
"compile_date": "compiled on May 4 2015 at 14:16:51",
"boost_version": "1.57",
"openssl_version": "OpenSSL 1.0.2a 19 Mar 2015",
"build": "osx 64-bit"
}
>> info
{
"blockchain_head_block_num": 1990812,
"blockchain_head_block_age": "64 days old",
"blockchain_head_block_timestamp": "2015-03-10T07:00:10",
"blockchain_head_block_id": "6a0e9a200a4fa1a6b8878949c8fb2835d20728bd",
"blockchain_average_delegate_participation": "0.02 %",
"blockchain_share_supply": "2,503,507,788.36221 BTS",
"blockchain_blocks_left_in_round": 100,
"blockchain_next_round_time": "at least 17 minutes in the future",
"blockchain_next_round_timestamp": "2015-05-13T07:36:30",
"blockchain_random_seed": "34d6bea4f06ff7e4d9b738d2fa9050e318819575",
"client_data_dir": "/Users/daniel/Library/Application Support/BitShares",
"client_version": "0.9.1",
"network_num_connections": 6,
"network_num_connections_max": 200,
"network_chain_downloader_running": false,
"network_chain_downloader_blocks_remaining": null,
"ntp_time": "2015-05-13T07:19:51",
"ntp_time_error": -0.085020999999999999,
"wallet_open": true,
"wallet_unlocked": true,
"wallet_unlocked_until": "12 days in the future",
"wallet_unlocked_until_timestamp": "2015-05-24T21:06:09",
"wallet_last_scanned_block_timestamp": "2014-07-22T16:58:50",
"wallet_scan_progress": "100.00 %",
"wallet_block_production_enabled": false,
"wallet_next_block_production_time": null,
"wallet_next_block_production_timestamp": null
}
-
It's doing SOMETHING since the cpu usage is 100-180%, but there's no hdd or network traffic to be seen.
-
Seems ok to me. You are definitely on the right fork. Try this to connect to other nodes directly:
network_add_node "107.170.211.129:1700" add
network_add_node "80.240.133.79:1776" add
network_add_node "188.226.195.137:60696" add
network_add_node "76.74.170.79:54200" add
network_add_node "176.9.234.166:1700" add
network_add_node "180.153.142.120:1777" add
network_add_node "162.243.220.142:1777" add
network_add_node "84.238.140.192:42577" add
network_add_node "5.101.106.138:1778" add
network_add_node "69.164.192.144:1700" add
network_add_node "192.168.0.14:1776" add
network_add_node "78.46.32.25:1776" add
network_add_node "192.168.0.12:44327" add
network_add_node "70.114.143.108:1776" add
network_add_node "106.187.91.24:38581" add
network_add_node "106.185.26.162:1981" add
network_add_node "188.138.107.159:1776" add
network_add_node "104.131.136.190:1776" add
network_add_node "95.85.33.16:8764" add
network_add_node "198.199.103.79:1776" add
network_add_node "104.131.234.136:8801" add
Maybe you are just connected to too many old nodes that have not been upgraded and have been disconnected from the rest of the network ..
-
It's doing SOMETHING since the cpu usage is 100-180%, but there's no hdd or network traffic to be seen.
that is a good sign .. if you run "getinfo" again, did "blockchain_head_block_num" increase?
-
Negative. I added the nodes in the console.
Still stuck at the very same block. I had 0.4-0.6 running just fine on this machine, this is very strange.
-
Negative. I added the nodes in the console.
Still stuck at the very same block. I had 0.4-0.6 running just fine on this machine, this is very strange.
Had another idea... could you please remove the checkpoints.json from the BitShares data directory in %APPDATA% and restart the client?
-
At least, its my network monitor is showing that its downloading data now.. but info shows that no block is being added.
Even after a restart, the block count did not changed.
I'll let it run for an hour and let you know
Thanks
-
Sorry for the inconveniences and thank you for the patience ..
-
I let it run for a while, and it produced about 250mb of traffic, but even after a restart the block count has NOT changed.
I'm at a loss here now.. This seems to be a bug.
-
You should also try a chain server http://wiki.bitshares.org/index.php/BitShares/Chain-Server
for downloading the blockchain. Try liondani's or wackou's servers for syncing ..
when you made the changes in the config and restarted the terminal client you will see something with "fast download" .. if you see "P2P" then the chain server might be offline ..
That's the last thing that may help here for syncing
-
I tried delegate.nathanhourt.com's chainserver yesterday, and it was fine until the client reached 70%, then it switched to p2p and was stuck there shortly after.
I setup 185.25.22.21:1375 (liondani) now, and will let you know if this works better. It's downloading from scratch now.
-
No luck. Still stuck. Doesn't seem to work on my iMac.
I'll try it on my laptop with my old wallet.
-
No luck. Still stuck. Doesn't seem to work on my iMac.
I'll try it on my laptop with my old wallet.
Can you show the output of the terminal .. from the startup until you see ">>>"?
-
I don't understand, but the client is sycned now.. I let it run for a few hours unattended and it did the job. However, the frontend it seemed stuck at this specific block.. very bad user experience.
Thank you xeroc!!
-
I don't understand, but the client is sycned now.. I let it run for a few hours unattended and it did the job. However, the frontend it seemed stuck at this specific block.. very bad user experience.
I see .. the status bar at the lower end of the GUI window is stuck although the client is synced (checked via console of the advanced menu?)
That may indeed be a bug ..
Thanks for taking the time to track it down!
-
Even the block count in "get_info" is stuck, and does not show progress. Suddenly, it was synced after hours.