Author Topic: Latest client release will not completely sync  (Read 4406 times)

0 Members and 1 Guest are viewing this topic.

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
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
}
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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?

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
I left it running over night and it had no hard disk activity in the morning, but it was still stuck at about 73%
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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.

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
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 :)
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
how long are you waiting? This is odd :(

do you get any other useful information from the CLI?

Offline mindphlux

  • Sr. Member
  • ****
  • Posts: 232
    • View Profile
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.
Please consider voting for my witness mindphlux.witness and my committee user mindphlux. I will not vote for changes that affect witness pay.

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12922
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
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

Offline optictopic

  • Jr. Member
  • **
  • Posts: 32
    • View Profile
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?