Topic: Runaway exception (Read 2761 times)
Thank you both for your answers. I didn't have to go that far, I (pretty much accidentally) stumbled on uncorrupted backup so all is fine and dandy now. Phew.
Well it actually wasn't trivial after all. I tried (yeah, 2 weeks later) to send money and got this:
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Did you back up the wallet.dat file? (just checking as you can always decrypt it from that).
AChow is right, contact jackjack if the salvagewallet command doesn't work (he has a more powerful script).
If you can get the private keys you can then load them into another wallet and be able to use them.
Yeah I hear you. This is getting hard to handle.
Salvage didn't help, unfortunately.
At this point, I don't think there is much that can be done through Core. You can use a tool like PyWallet (https://bitcointalksearch.org/topic/pywallet-22-manage-your-wallet-update-required-34028) to get as many of the private keys as you can from the wallet. Then take those private keys and import them to a new wallet. One caveat though, pywallet has not been updated in a while so it may not fully work with your wallet. You can contact the author of pywallet, JackJack (https://bitcointalksearch.org/user/jackjack-21053) if you need help with it as he has been more active recently. Salvage didn't help, unfortunately.
Yeah I hear you. This is getting hard to handle.
Salvage didn't help, unfortunately.
Salvage didn't help, unfortunately.
Well it actually wasn't trivial after all. I tried (yeah, 2 weeks later) to send money and got this:
-img snip-
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Try adding -salvagewallet to the command. You should really get your Bitcoin out of that wallet ASAP. -img snip-
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Well it actually wasn't trivial after all. I tried (yeah, 2 weeks later) to send money and got this:
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Debug.log had entry 2 hours prior to this and it said: "The wallet is probably corrupted: Some keys decrypt but not all." I guess this has something to do with that, but what?
Well that was trivial.. thanks again.
You were spot on with that one! Thanks a million. Had to rescan but works indeed.
No problem!Is there any advantages upgrading to HD wallet
An HD wallet allows you to only have to backup once (if you encrypt, you have to backup again) to have all of the private keys that you will ever make. It means that you don't have to backup every 100 transactions to keep all of your private keys, although backing up regularly is a good practice anyways.and how do I do that if that's even possible?
First you need to create a new wallet by moving your current wallet.dat file to a safe location and then starting Bitcoin Core without the -usehd option (or -usehd=1, but that is the default). Then encrypt that wallet, back it up, and get some addresses from it. Then you have to move the new wallet.dat file to a safe place and put the old wallet.dat back in. Start up Bitcoin Core with whatever you need to do to make it work, and send all of your Bitcoin to the addresses that you got from the new wallet. Once the Bitcoin is sent and confirmed, you can replace your old wallet.dat with the new one and you will be using a HD wallet. It seems that Bitcoin Core is trying to generate a HD master key, but it should not as your wallet is not a HD wallet. Try starting Bitcoin Core with -usehd=0.
You were spot on with that one! Thanks a million. Had to rescan but works indeed.
Is there any advantages upgrading to HD wallet and how do I do that if that's even possible?
It seems that Bitcoin Core is trying to generate a HD master key, but it should not as your wallet is not a HD wallet. Try starting Bitcoin Core with -usehd=0.
The issue is right at the bottom:
This error means that Bitcoin Core was unable to write something to the wallet. So double check the permissions on the wallet.dat file inside of the datadir. Make sure that your user account is able to both read and write to the file.
Quote
************************
EXCEPTION: St13runtime_error
GenerateNewHDMasterKey: AddKeyPubKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-01-15 11:26:42 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
EXCEPTION: St13runtime_error
GenerateNewHDMasterKey: AddKeyPubKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-01-15 11:26:42 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
This error means that Bitcoin Core was unable to write something to the wallet. So double check the permissions on the wallet.dat file inside of the datadir. Make sure that your user account is able to both read and write to the file.
Yeah, user has all rights and running as administrator doesn't help. It can't be anything else than this current wallet because with generating new wallet client starts just fine. I just don't see what it can be. I've tried to start with -upgradewallet and -salvagewallet but those do nothing.
The issue is right at the bottom:
This error means that Bitcoin Core was unable to write something to the wallet. So double check the permissions on the wallet.dat file inside of the datadir. Make sure that your user account is able to both read and write to the file.
Quote
************************
EXCEPTION: St13runtime_error
GenerateNewHDMasterKey: AddKeyPubKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-01-15 11:26:42 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
EXCEPTION: St13runtime_error
GenerateNewHDMasterKey: AddKeyPubKey failed
C:\Program Files\Bitcoin\bitcoin-qt.exe in Runaway exception
2017-01-15 11:26:42 CDBEnv::EnvShutdown: Error 22 shutting down database environment: Invalid argument
This error means that Bitcoin Core was unable to write something to the wallet. So double check the permissions on the wallet.dat file inside of the datadir. Make sure that your user account is able to both read and write to the file.
I've tried 13.1. too. It was the first version that didn't work. Install folder (and every folder) is the same as previous versions. I don't know if 12.2 had any abnormalities. Debug.log has no entry for that version.
Edit 16th, Jan. : Works.
Edit 16th, Jan. : Works.
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
The new version should be able to use your existing wallet file without an issue as far as I know. I'd be more concerned with getting the new wallet working with your wallet file if I were you. It should load your existing wallet by default I think. Was it not doing this?
No, using my old wallet with the coins gives runaway exception and the client won't start.
You mean when using the new version of Bitcoin Core with your old wallet, you are also seeing the exception error?
First off, I would make a backup of your wallet file for safety purposes. It is possible your wallet file is corrupted and causing this error.
Then, I would try running bitcoin application with the -salvagewallet parameter via command line. This command attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat
Yes, that's what i meant. Clearly I wasn't expressing myself too well.
Anyway, I've tried -salvagewallet, but it did nothing. I tried downgrading client to 0.12.1 and wallet did work (so I guess it's not corrupt), but again, after upgrading to 13.2 it results in fatal error.
Try 0.13.1 and see if that works.
There are many nodes running that or below so there couldn't have been too many bug fixes in the new release.
Otherwise, did you put 0.13.2 bitcoin core in the same place as the previous bitcoin core executable, it may just be a location issue (as in it can't find your wallet.dat file or the config file)?
Is there anything in the debug.log file after running the 0.12.2 executable that is abnormal?
Yes, that's what i meant. Clearly I wasn't expressing myself too well.
Anyway, I've tried -salvagewallet, but it did nothing. I tried downgrading client to 0.12.1 and wallet did work (so I guess it's not corrupt), but again, after upgrading to 13.2 it results in fatal error.
Please post your debug.log file. Anyway, I've tried -salvagewallet, but it did nothing. I tried downgrading client to 0.12.1 and wallet did work (so I guess it's not corrupt), but again, after upgrading to 13.2 it results in fatal error.
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
The new version should be able to use your existing wallet file without an issue as far as I know. I'd be more concerned with getting the new wallet working with your wallet file if I were you. It should load your existing wallet by default I think. Was it not doing this?
No, using my old wallet with the coins gives runaway exception and the client won't start.
You mean when using the new version of Bitcoin Core with your old wallet, you are also seeing the exception error?
First off, I would make a backup of your wallet file for safety purposes. It is possible your wallet file is corrupted and causing this error.
Then, I would try running bitcoin application with the -salvagewallet parameter via command line. This command attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat
Yes, that's what i meant. Clearly I wasn't expressing myself too well.
Anyway, I've tried -salvagewallet, but it did nothing. I tried downgrading client to 0.12.1 and wallet did work (so I guess it's not corrupt), but again, after upgrading to 13.2 it results in fatal error.
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
The new version should be able to use your existing wallet file without an issue as far as I know. I'd be more concerned with getting the new wallet working with your wallet file if I were you. It should load your existing wallet by default I think. Was it not doing this?
No, using my old wallet with the coins gives runaway exception and the client won't start.
You mean when using the new version of Bitcoin Core with your old wallet, you are also seeing the exception error?
First off, I would make a backup of your wallet file for safety purposes. It is possible your wallet file is corrupted and causing this error.
Then, I would try running bitcoin application with the -salvagewallet parameter via command line. This command attempts to salvage public/private keys and master encryption keys (if the wallet is encrypted) into a new wallet.dat
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
The new version should be able to use your existing wallet file without an issue as far as I know. I'd be more concerned with getting the new wallet working with your wallet file if I were you. It should load your existing wallet by default I think. Was it not doing this?
No, using my old wallet with the coins gives runaway exception and the client won't start.
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
The new version should be able to use your existing wallet file without an issue as far as I know. I'd be more concerned with getting the new wallet working with your wallet file if I were you. It should load your existing wallet by default I think. Was it not doing this?
What operating system are you using? Did you recently upgrade the OS or install any updates, etc?
If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
Windows 10. Bitcoin 0.12.1 was installed on this and it did work.If the new version works, I'm not sure there is really a need to get the old one working again to be honest.
I think there is need to get the old one working again since it has my coins.
Jump to: