MC 2.0 alpha 3 cannot be started anymore

+1 vote

MC 2.0 stopped working (don't know what was done before, but it was not running for a long time).

I am not able to start. The following error message is provided:

Error on starting daemon: multichaind: core/main.cpp:2213: bool DisconnectBlock(CBlock&, CValidationState&, CBlockIndex*, CCoinsViewCache&, bool*): Assertion `pindex->GetBlockHash() == view.GetBestBlock()' failed.

 Debug.log

2018-07-10 11:45:28 mchn: Permission DB is behind current chain tip. Permission DB: 27, Chain tip: 28
2018-07-10 11:45:28 mchn: Entities DB is behind current chain tip. Entities DB: 27, Chain tip: 28
2018-07-10 11:45:28 mchn: Wallet Tx DB is behind current chain tip. Wallet Tx DB: 27, Chain tip: 28
2018-07-10 11:45:28 mchn: Permission/Entities/WalletTx DB is behind current chain tip. Shifting chain tip to 27
2018-07-10 11:45:28 mchn: Disconnecting block 001422d7776de6a61a09dd99705c81272f3d7d8733deae16e5f2498cf4b650b3 (height 28) from permission DB (0 transactions in mempool)
2018-07-10 11:45:28 wtxs: AddTx  Error: 6
2018-07-10 11:45:28 ERROR: AcceptToMemoryPool: : AcceptMultiChainTransaction failed fc0e001ee7251a11265d85eacf3970dc973420acbbab391e46406bc1a4f76330 : Wallet error 6
2018-07-10 11:45:28 mchn: Replaying memory pool (0 new transactions, total 2)
2018-07-10 11:45:28 UpdateTip:            new best=0067e9e9151dce452ae8008889eaf2371a7c3fc51f9ef549e4d4892ef7650f85  height=27  log2_work=12.807355  tx=30  date=2018-07-10 10:53:29 progress=1.000000  cache=1
2018-07-10 11:45:28 mchn: Replaying memory pool (0 new transactions, total 0)
2018-07-10 11:45:28 ReacceptWalletTransactions: 0 txs in unconfirmed pool
2018-07-10 11:45:28 Set active chain tip: 0067e9e9151dce452ae8008889eaf2371a7c3fc51f9ef549e4d4892ef7650f85
2018-07-10 11:45:28 VerifyBlockMiner: Block: 28, Fork: 27, Chain: 27
2018-07-10 11:45:28 VerifyBlockMiner: Rolled back to block 27
2018-07-10 11:45:28 VerifyBlockMiner: Verifying block 28
2018-07-10 11:45:28 VerifyBlockMiner: New block 001422d7776de6a61a09dd99705c81272f3d7d8733deae16e5f2498cf4b650b3 (height 28)
2018-07-10 11:45:28 VerifyBlockMiner: Restoring chain, block 28
2018-07-10 11:45:28 VerifyBlockMiner: Restored on block 27
2018-07-10 11:45:28 mchn: Connecting block 001422d7776de6a61a09dd99705c81272f3d7d8733deae16e5f2498cf4b650b3 (height 28) ...
2018-07-10 11:45:28 mchn: Checking block signature and miner permissions...
2018-07-10 11:45:28 mchn: Committing permission changes for block 28...
2018-07-10 11:45:28 wtxs: AddTx  Error: 6
2018-07-10 11:45:28 ERROR: ConnectTip() : ConnectBlock 001422d7776de6a61a09dd99705c81272f3d7d8733deae16e5f2498cf4b650b3 failed, Wtxs AddTx fc0e001ee7251a11265d85eacf3970dc973420acbbab391e46406bc1a4f76330, error: 6
2018-07-10 11:45:28 mchn: Rolling back permission DB to height 27
2018-07-10 11:45:28 mchn: Rolling back asset DB to height 27
2018-07-10 11:45:28 mchn: Rolling back wallet txs DB to height 27
2018-07-10 11:45:28 LoadBlockIndexDB(): hashBestChain=0067e9e9151dce452ae8008889eaf2371a7c3fc51f9ef549e4d4892ef7650f85 height=27 date=2018-07-10 10:53:29 progress=1.000000
2018-07-10 11:45:28 init message: Verifying blocks...
2018-07-10 11:45:28 Verifying last 27 blocks at level 3

Any idea? 

asked Jul 10 by Alexoid

2 Answers

0 votes

If you used off-chain stream items, and also the autosubscribe runtime parameter, then we're aware of this bug and will be releasing a fix shortly.

answered Jul 10 by MultiChain
Thanks for the (fast) information. :-)

Alex
0 votes
MultiChain 2.0 alpha 4, just released, should fix this.
answered Aug 9 by MultiChain
...