chain database is in an inconsistent state.

Started by Webber, September 13, 2014, 01:01:28 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

tonyk

#9
Quote from: vikram on September 14, 2014, 01:23:06 AM
In 0.4.15+ we have added some additionally database caching code. It is possible that this change could cause a problem like this; let us know if anyone continues to experience this.

Is this the official announcement for 0.4.15, that btw, will fork in less then 30 40h?
Lack of arbitrage is the problem, isn't it. And this 'should' solves it.

vikram

In 0.4.15+ we have added some additionally database caching code. It is possible that this change could cause a problem like this; let us know if anyone continues to experience this.

Webber

I add memory from 1G to 2G,then solved this issue.
Bitshares2.0 witness node:delegate.webber
Bitshares2.0 API:[url="ws://114.215.116.57:8090"]ws://114.215.116.57:8090[/url]

busygin

After --resync-blockchain in 0.4.15-RC1 the balance is correct but all recent transactions in GUI disappeared. Are they not "recent" anymore? I ran rescan but it didn't change anything. wallet_account_transaction_history output looks ok.

xeroc

Quote from: Webber on September 13, 2014, 02:41:59 PM
I deleted chain database ,same issue again. :-X :-X :-X

Can you delete the "chain" folder in %APDATA%\Roaming
manually and try again?

Webber

I deleted chain database ,same issue again. :-X :-X :-X
Bitshares2.0 witness node:delegate.webber
Bitshares2.0 API:[url="ws://114.215.116.57:8090"]ws://114.215.116.57:8090[/url]

Riverhead


xeroc

--resync-blockchain

had a similar issue and had to resync .. :-(

Webber

I build a new linux wallet today,but can't sync.Wallet version is 0.4.15-RC1.
--- there are now 13 active connections to the p2p network
I am disconnecting peer 80.240.133.79:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 104.131.35.149:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 178.62.50.61:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 178.62.50.61:1779 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 180.153.142.120:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 80.240.133.79:1778 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 95.85.33.16:8764 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 84.238.140.192:42577 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1778 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 5.101.106.138:1776 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 80.240.133.79:1777 for reason: You offered us a block that we reject as invalid
I am disconnecting peer 54.79.27.224:1776 for reason: You offered us a block that we reject as invalid
--- in sync with p2p network
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
--- there are now 0 active connections to the p2p network
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
Error: your chain database is in an inconsistent state.  Please shut down and relaunch using --rebuild-index or --resync-blockchain to repair the database
(wallet closed) >>>
(wallet closed) >>> info
{
  "blockchain_head_block_num": 451571,
  "blockchain_head_block_age": "66 hours old",
  "blockchain_head_block_timestamp": "2014-09-10T19:10:00",
  "blockchain_average_delegate_participation": "0.42 %",
  "blockchain_confirmation_requirement": 125,
  "blockchain_accumulated_fees": "209,705.88885 BTSX",
  "blockchain_delegate_pay_rate": "1.73367 BTSX",
  "blockchain_share_supply": "1,999,890,025.95776 BTSX",
  "blockchain_blocks_left_in_round": 101,
  "blockchain_next_round_time": "at least 17 minutes in the future",
  "blockchain_next_round_timestamp": "2014-09-13T13:17:50",
  "blockchain_random_seed": "b31cd4240040e986124f7235d2f8a4e6ae14b9ca",
  "client_data_dir": "/root/.BitSharesX",
  "client_version": "v0.4.15-RC1",
  "network_num_connections": 0,
  "network_num_connections_max": 200,
  "ntp_time": "2014-09-13T13:01:06",
  "ntp_time_error": -0.022821999999999999,
  "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
}
Bitshares2.0 witness node:delegate.webber
Bitshares2.0 API:[url="ws://114.215.116.57:8090"]ws://114.215.116.57:8090[/url]