BitShares Forum

Main => Technical Support => Topic started by: ElMato on October 20, 2014, 05:27:38 am

Title: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: ElMato on October 20, 2014, 05:27:38 am

Im connected to the network (network_get_connection_count between 1 and 5) but i cant go beyond block 728214.

(wallet closed) >>> about
{
  "blockchain_name": "BitShares X",
  "blockchain_description": "Decentralized Autonomous Exchange",
  "client_version": "v0.4.20",
  "bitshares_toolkit_revision": "ab40d8dc51cd4e54c0e05a2e9770fca3f03d6565",
  "bitshares_toolkit_revision_age": "18 days ago",
  "fc_revision": "c4e814d7ded6099dc4297aa843d4be7afa98b3ed",
  "fc_revision_age": "20 days ago",
  "compile_date": "compiled on Oct 10 2014 at 21:45:38",
  "boost_version": "1.56",
  "openssl_version": "OpenSSL 1.0.1i 6 Aug 2014",
  "build": "osx 64-bit"
}

(wallet closed) >>> blockchain_get_block_count
728214

(wallet closed) >>> blockchain_get_block 728214
{
  "previous": "65de54a989bbff9364f7de5eda59e04361950a3b",
  "block_num": 728214,
  "timestamp": "20141013T013800",
  "transaction_digest": "c8cf12fe3180ed901a58a0697a522f1217de72d04529bd255627a4ad6164f0f0",
  "next_secret_hash": "6796a4eb42517bba7bed76f5d4a617421837cbc5",
  "previous_secret": "6861922a10b235011fbdd9df9384d0c891dea065",
  "delegate_signature": "1fa445545cf7d186e61d35bf983fb2fd7d319ffb42ce1791a15d27b6ca56b37328aaced8b185b98e752c101201b0a76596b4bf5fbccbbbb259ce47ef596bc44d5c",
  "user_transaction_ids": []
}

Based on http://bitsharesblocks.com/blocks/block?id=728214, it seems that i'm not in a fork

I know that i can remove everything and start all over again, but i would like to diagnose whats happening.

Any hint?

Title: Re: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: xeroc on October 20, 2014, 06:53:58 am

"getinfo"

still showing connections?

Title: Re: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: ElMato on October 20, 2014, 07:41:29 am

Yes ...

(wallet closed) >>> get_info
{
  "blockchain_head_block_num": 728214,
  "blockchain_head_block_age": "7 days old",
  "blockchain_head_block_timestamp": "2014-10-13T01:38:00",
  "blockchain_average_delegate_participation": "0.16 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_delegate_pay_rate": "1.81292 BTSX",
  "blockchain_share_supply": "1,999,937,082.29552 BTSX",
  "blockchain_blocks_left_in_round": 97,
  "blockchain_next_round_time": "at least 16 minutes in the future",
  "blockchain_next_round_timestamp": "2014-10-20T07:56:00",
  "blockchain_random_seed": "a759ec9fa6857f2498f49f5ea9ab9fe3f4d1023d",
  "client_data_dir": "/Users/[edited]/Library/Application Support/BitShares X",
  "client_version": "v0.4.20",
  "network_num_connections": 2,
  "network_num_connections_max": 200,
  "ntp_time": "2014-10-20T07:39:55",
  "ntp_time_error": -0.065501000000000004,
  "wallet_open": false,
  "wallet_unlocked": null,
  "wallet_unlocked_until": null,
  "wallet_unlocked_until_timestamp": null,
  "wallet_last_scanned_block_timestamp": null,
  "wallet_scan_progress": null,
  "wallet_block_production_enabled": null,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}

Title: Re: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: xeroc on October 20, 2014, 07:55:52 am

odd ... I guess the other two parties are also stuck ... who knows why ..

maybe you can solve this be either manually connect to one of the seed nodes ..
or remove the known peers database and reconnect over to the network (by deleting the peers_leveldb folder in "/Users/[edited]/Library/Application Support/BitShares X")

Title: Re: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: ElMato on October 20, 2014, 07:30:40 pm

Thanks xerox, i deleted the peers db but nothing special happens.

This is my current situation..
...
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 4 active connections to the p2p network
--- there are now 3 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 2 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network
--- there are now 1 active connections to the p2p network
--- there are now 0 active connections to the p2p network

(wallet closed) >>> blockchain_is_synced
false

(wallet closed) >>> blockchain_get_block_count
728214

(wallet closed) >>> debug_list_errors_brief
[[
    "20140823T230420.868295",
    "unspecified"
  ],[
    "20140823T230802.872564",
    "unspecified"
  ],[
    "20140823T234202.589317",
    "unspecified"
  ],[
    "20140823T234312.493486",
    "unspecified"
  ],[
    "20140823T235051.270832",
    "unspecified"
  ],[
    "20140823T235727.272364",
    "unspecified"
  ],[
    "20140824T000410.802489",
    "unspecified"
  ],[
    "20140824T000413.969695",
    "unspecified"
  ],[
    "20140824T000650.043646",
    "unspecified"
  ],[
    "20140824T000833.202415",
    "unspecified"
  ],[
    "20140824T004241.059218",
    "Assert Exception"
  ],[
    "20140824T005409.639546",
    "block is older than our undo history allows us to process"
  ],[
    "20140825T203439.640586",
    "unspecified"
  ],[
    "20140825T213825.395229",
    "Assert Exception"
  ],[
    "20140825T213825.415806",
    "Assert Exception"
  ],[
    "20140825T213826.445013",
    "Assert Exception"
  ],[
    "20140825T213826.877497",
    "Assert Exception"
  ],[
    "20140825T213827.370234",
    "Assert Exception"
  ],[
    "20140825T213828.519711",
    "Assert Exception"
  ],[
    "20140826T010257.132931",
    "block is older than our undo history allows us to process"
  ]
]



I'm getting a lot of "key_not_found_exception" in p2p.log
"6 key_not_found_exception: Key Not Found\nunable to find key 728788\n"

what does it means?

Title: Re: Stuck at block 728214 - how to diagnose whats happening? (v0.4.20)
Post by: xeroc on October 20, 2014, 08:00:17 pm

What the ...?

I'm getting a lot of "key_not_found_exception" in p2p.log
"6 key_not_found_exception: Key Not Found\nunable to find key 728788\n"


could you make a copy of the "wallet" folder (or just rename it to something else .. and start your whole directory freshly ..
these is looking very strange ... and I might not be able to help you out ..
seems to be a yet undiscovered bug ..

could you add a bugreport at
https://github.com/BitShares/bitshares_toolkit/issues
pls?