No new blocks, broken wallet

+1 vote


We have a "single node" Multichain running, but after a reboot we had to run the daemon with "-salvagewallet" because it say it has a broken wallet.

The main issue right now it that the networks is not creating new blocks, so new transactions get stuck on mempool

debug.log says something about mining, but we dont have mining at all, all the funds where send to an address on first block


2016-03-21 15:59:54 mapAddressBook.size() = 1
2016-03-21 15:59:54 init message: Loading addresses...
2016-03-21 15:59:54 Loaded 0 addresses from peers.dat  0ms
2016-03-21 15:59:54 init message: Done loading
2016-03-21 15:59:54 Node started
2016-03-21 15:59:54 dumpaddr thread start
2016-03-21 15:59:54 BitcoinMiner started
2016-03-21 15:59:54 mchn: Cannot find address having mining permission

2016-03-21 15:59:54 msghand thread start

How can we fix this?


asked Mar 21, 2016 by reiven

1 Answer

0 votes
It looks like this node does not have any addresses with mining permissions. If you still have a node with admin permissions you can use it to reassign mining permissions to one of this node's addresses.
answered Mar 21, 2016 by MultiChain
The server has changed his ip address, can this affect? Remember i only have 1 node
All permissioning is done by blockchain address rather than IP address, so this should not make a difference.
The address with mining permissions exists in the wallet and it has balance, and its a single-node server. Should i try to re-assign same permissions?
Could you please run listpermissions and see if it's shown there as a miner?
Yes, the "original" address exists and has the mining permissions, also admin .. and everything else.
Remember that i'm running the daemon with "-salvagewallet" or the daemon didnt start
OK, so the address is listed if you use getaddresses, and it's shown as having mining permission in listpermissions? So it's possible that the original problem you swaw is not the reason now why mining is not proceeding. The most common reason we find is "mining-requires-peers" being on by default, as set in the blockchain parameters, though you can override this using a runtime parameter.

I also want to confirm that you need to run salvagewallet every single time. If so it would be helpful for us to receive a copy of your wallet file, if you're willing (we can't connect to your blockchain anyway) to see in which way it's corrupted. If you're open to doing that I'll send you an email address.
We have mining-requires-peers = false configured, and yes, we need to always run the daemon with "salvagewallet" parameter, or the server did not start
Its ok to send you the wallet file, sure, thanks
Thanks I'll email you now.