Author Topic: Stuck in block 381500  (Read 3683 times)

0 Members and 1 Guest are viewing this topic.

Offline kokojie

  • Sr. Member
  • ****
  • Posts: 286
    • View Profile
Yes, same here, if I start from scratch, I end up stuck on 381500.

I actually backed up my blocks previously, and if I load from backup, I'm stuck on 468912.

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Vikram and I ran into this issue late Friday, it appears to be due to some flooding of transactions by Toast while doing sharedrop testing. Vikram was investigating this further, not sure what else he may have discovered about it.

It is our luck to have this issue in Devshares. Nice test bed. I hope the problem resolved soon and will get NOTE on Bitshares.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline dannotestein

  • Hero Member
  • *****
  • Posts: 760
    • View Profile
    • BlockTrades International
  • BitShares: btsnow
Vikram and I ran into this issue late Friday, it appears to be due to some flooding of transactions by Toast while doing sharedrop testing. Vikram was investigating this further, not sure what else he may have discovered about it.
http://blocktrades.us Fast/Safe/High-Liquidity Crypto Coin Converter

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Have you tried:
./btshares_client  --rebuild-index

Have you deleted all folds and files (except "wallets" of course) ?

PS even "checkpoints.json", "config.json", node_config.json"

Did it several times but still have the same issue.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline xeroc

  • Board Moderator
  • Hero Member
  • *****
  • Posts: 12920
  • ChainSquad GmbH
    • View Profile
    • ChainSquad GmbH
  • BitShares: xeroc
  • GitHub: xeroc
Code: [Select]
  ],[
    "2015-01-22T20:45:34",
    "block is older than our undo history allows us to process"
  ],[
    "2015-01-22T20:45:34",
    "block is older than our undo history allows us to process"
  ]

Offline liondani

  • Hero Member
  • *****
  • Posts: 3737
  • Inch by inch, play by play
    • View Profile
    • My detailed info
  • BitShares: liondani
  • GitHub: liondani
Have you tried:
./btshares_client  --rebuild-index

Have you deleted all folds and files (except "wallets" of course) ?

PS even "checkpoints.json", "config.json", node_config.json"

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
There were a large scale of UIA issuance (Testnote) around blocks we stuck in. Devs please look at it
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline wackou

Weirder even, I resynced the blockchain from scratch and got stuck again, but this time on block 381471...
Please vote for witness wackou! More info at http://digitalgaia.io

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
same issue, but I'm stuck on 381464. Weird... What's even weirder is that delegate participation is shown at 1.4%, but it doesn't look like I'm on a fork because the hash of block 381464 is 296636ff24de0725a8efcd85a54330ee4896a505, which is the same as I the one I get from my delegate which is fully synchronized... I will try to resync the entire blockchain see if it helps.

Some people also stuck in 381464 too. Weird...

Here's my getinfo result.

Code: [Select]
{
  "blockchain_head_block_num": 381500,
  "blockchain_head_block_age": "21 hours old",
  "blockchain_head_block_timestamp": "2015-02-20T21:58:20",
  "blockchain_average_delegate_participation": "1.35 %",
  "blockchain_confirmation_requirement": 1,
  "blockchain_share_supply": "2,633,214,502.49841 DVS",
  "blockchain_blocks_left_in_round": 78,
  "blockchain_next_round_time": "at least 13 minutes in the future",
  "blockchain_next_round_timestamp": "2015-02-21T18:42:00",
  "blockchain_random_seed": "d13d75cb125980304a655b93951c4086a7d77bab",
  "client_data_dir": "C:/Users/Administrator/AppData/Roaming/DevShares",
  "client_version": "0.6.3",
  "network_num_connections": 11,
  "network_num_connections_max": 200,
  "network_chain_downloader_running": false,
  "network_chain_downloader_blocks_remaining": null,
  "ntp_time": "2015-02-21T18:29:01",
  "ntp_time_error": 0.45690199999999997,
  "wallet_open": true,
  "wallet_unlocked": true,
  "wallet_unlocked_until": "12 days in the future",
  "wallet_unlocked_until_timestamp": "2015-03-05T08:15:30",
  "wallet_last_scanned_block_timestamp": "2015-02-20T18:59:20",
  "wallet_scan_progress": "100.00 %",
  "wallet_block_production_enabled": false,
  "wallet_next_block_production_time": null,
  "wallet_next_block_production_timestamp": null
}
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline wackou

same issue, but I'm stuck on 381464. Weird... What's even weirder is that delegate participation is shown at 1.4%, but it doesn't look like I'm on a fork because the hash of block 381464 is 296636ff24de0725a8efcd85a54330ee4896a505, which is the same as I the one I get from my delegate which is fully synchronized... I will try to resync the entire blockchain see if it helps.
Please vote for witness wackou! More info at http://digitalgaia.io

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Try quit, delete peers.leveldb folder, start.

Did it several times but didn't work. Same issue occured.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop

Offline abit

  • Committee member
  • Hero Member
  • *
  • Posts: 4572
    • View Profile
    • Abit's Hive Blog
  • BitShares: abit
  • GitHub: abitmore
Try quit, delete peers.leveldb folder, start.
BitShares committee member: abit
BitShares witness: in.abit

Offline clayop

  • Hero Member
  • *****
  • Posts: 2033
    • View Profile
    • Bitshares Korea
  • BitShares: clayop
Anyone have the same situation? I deleted chain files two time but it did not work.
Bitshares Korea - http://www.bitshares.kr
Vote for me and see Korean Bitshares community grows
delegate-clayop