dumpwallet "filename"
Dumps all wallet keys in a human-readable format.
Dumps all wallet keys in a human-readable format.
cool! i was looking at outdated api documentation. will try dumpwallet command
Topic: EXCEPTION: St9bad_alloc std::bad_alloc bitcoin in ProcessMessages() (Read 1838 times)
January 17, 2016, 11:34:39 PM
cool! i was looking at outdated api documentation. will try dumpwallet command
January 17, 2016, 12:44:26 PM
as far as i know exporting privatekey can only be done one by one through API.
Cant you use bumpwallet?
Code:
dumpwallet "filename"
Dumps all wallet keys in a human-readable format.
Arguments:
1. "filename" (string, required) The filename
Examples:
> bitcoin-cli dumpwallet "test"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "dumpwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
Dumps all wallet keys in a human-readable format.
Arguments:
1. "filename" (string, required) The filename
Examples:
> bitcoin-cli dumpwallet "test"
> curl --user myusername --data-binary '{"jsonrpc": "1.0", "id":"curltest", "method": "dumpwallet", "params": ["test"] }' -H 'content-type: text/plain;' http://127.0.0.1:8332/
It would give you a nice file that you can split by # of lines (mind the header though) and reimport into different wallet files via a short script.
January 17, 2016, 12:34:12 PM
as far as i know exporting privatekey can only be done one by one through API.
It might not be too hard to whip up a script that iterates the addresses and then dumps the private keys for them.
January 17, 2016, 12:32:46 PM
as far as i know exporting privatekey can only be done one by one through API.
January 17, 2016, 12:30:12 PM
and this wallet will not grow, i will leave it as it is because i don't have idea how to split the wallet.dat easily
You can export and then later import the private keys (am not sure if the exporting can be done in one go though - you'd need to check that).
January 17, 2016, 12:23:41 PM
yes i already built a load balancer for few bitcoind wallets, and of course they will be separated into fewer addresses.
and this wallet will not grow, i will leave it as it is because i don't have idea how to split the wallet.dat easily
and this wallet will not grow, i will leave it as it is because i don't have idea how to split the wallet.dat easily
January 17, 2016, 12:11:02 PM
Glad to know that you fixed your problem but I would recommend that you reconsider the idea of having such a huge wallet (especially if it is going to grow much bigger).
Many of the RPC functions will perform poorly because of that (and the problem will just get worse and worse).
Many of the RPC functions will perform poorly because of that (and the problem will just get worse and worse).
January 17, 2016, 12:05:13 PM
hahaha yes it is very silly, it turns out I was using 32bit box 
no wonder bitcoind crashes when reach 4gb and ignore the rest of the memory
i already moved it to 64bit and everything seems to work fine.
thanks for the help
anyway, for anyone have similar issue but with limited RAM, using -dbcache=16 really do the trick. it works even for 100k+ addresses but every command become very slow.
no wonder bitcoind crashes when reach 4gb and ignore the rest of the memory
i already moved it to 64bit and everything seems to work fine.
thanks for the help
anyway, for anyone have similar issue but with limited RAM, using -dbcache=16 really do the trick. it works even for 100k+ addresses but every command become very slow.
January 17, 2016, 10:36:43 AM
Did you use a 32-bit version by any chance? That would explain the 3GB limit.
I was guessing the same thing but wanted to make sure exactly what was causing the crash first (if the super large wallet is causing blockchain corruption then perhaps that is a bug that should be reported).
OP should note that if they are using Windows then they are using a 32 bit version (so a possible fix might be to change to a 64 bit Linux version).
January 17, 2016, 09:58:01 AM
i'm installing fresh bitcoind on new server now.
Did you use a 32-bit version by any chance? That would explain the 3GB limit.
January 17, 2016, 02:02:14 AM
i'm installing fresh bitcoind on new server now.
January 17, 2016, 01:38:19 AM
corrupted block database detected.
Then your problem is a corrupted blockchain (whether or not your wallet has anything to do with it) so unfortunately you are simply going to have to repair that before trying to use your original wallet again.
I would suggest you consider setting up a separate machine (or VM) for working on this and keep a copy of the blockchain (once you have the full uncorrupted version) somewhere handy.
The point being that if it was due to your wallet's size that somehow the blockchain got corrupted (unlikely but I guess possible) then you might find that as soon as you put back your big wallet and restart it might corrupt the blockchain again (putting you back to square one).
So once you have a clean blockchain (with an empty wallet) back that up (the whole thing) before trying to put back in you big wallet.
January 17, 2016, 01:35:54 AM
or did you mean to backup whole .bitcoin directory?
January 17, 2016, 01:34:47 AM
is it possible to create a new wallet without resync?
tried to move the wallet.dat, starting bitcoind gave me
tried to move the wallet.dat, starting bitcoind gave me
Code:
Corrupted block database detected.
Do you want to rebuild the block database now?
January 17, 2016, 01:15:45 AM
i was trying to avoid resync the whole blockchain if possible (it already takes 1 day to reach 32xxxx).
I didn't suggest that you resync the whole blockchain at all - backup your wallet and then delete it is all I suggested (after first stopping bitcoind).
That shouldn't take you more than a minute to do (after you restart bitcoind it will create a new empty wallet which is done almost instantly).
January 17, 2016, 01:14:35 AM
i was trying to avoid resync the whole blockchain if possible (it already takes 1 day to reach 34xxxx).
but I will do it anyway. and see what happen. will update later.
thanks for your help.
but I will do it anyway. and see what happen. will update later.
thanks for your help.
January 17, 2016, 12:26:13 AM
what i'm really confused is the server doesn't seem to run out of memory. only 3gb being used.
Firstly, have you verified that it is the wallet that is causing your problem?
(if you haven't then there is very little point in my continuing to offer any advice)
January 17, 2016, 12:20:54 AM
what i'm really confused is the server doesn't seem to run out of memory. only 3gb being used.
January 16, 2016, 10:36:12 PM
i know it is not a good idea, but i need to get this wallet up. any ideas?
Well first I'd suggest you work out whether the problem is your wallet - assuming that it is then I hope for your sake you have a backup that still works (if not you are going to have a very hard time especially if the wallet is encrypted).
January 16, 2016, 10:31:14 PM
the wallet has 100k of addresses
^ That is not a good idea.
The wallet doesn't scale well at all and despite the large amount of RAM you might be hitting a limit that is causing the bad alloc (although a bad alloc could also be caused through passing an invalid value for allocation).
To work out whether the problem is your wallet's size back it up and then delete it and re-start Bitcoin (it will create a new empty wallet). If no crashes happen with the empty wallet then I would assume your problem is the huge wallet.
i know it is not a good idea, but i need to get this wallet up. any ideas?
Jump to: