ReserveKeyFromKeyPool(): read failed #2397

issue rebroad opened this issue on March 21, 2013
  1. rebroad commented at 2:13 PM on March 21, 2013: contributor

    This happens when unlocking the wallet to create a new receive address. Happens every time, so unable to create new receive addresses currently.

    (Bitcoin version v0.8.0-62-gb5ec091-beta (2013-03-21 10:08:32 +0700))

    Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there.

    Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there.


    EXCEPTION: St13runtime_error
    ReserveKeyFromKeyPool() : read failed
    bitcoin in Runaway exception

    [Thread 0x7fffdd5b2700 (LWP 6673) exited] bitcoin-qt.master: /usr/include/boost/thread/pthread/recursive_mutex.hpp:101: void boost::recursive_mutex::lock(): Assertion `!pthread_mutex_lock(&m)' failed.

    Program received signal SIGABRT, Aborted. [Switching to Thread 0x7fffba7fc700 (LWP 6688)] 0x00007ffff46fe425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 (gdb) bt #0 0x00007ffff46fe425 in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x00007ffff4701b8b in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x00007ffff46f70ee in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #3 0x00007ffff46f7192 in __assert_fail () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x0000000000450d4d in boost::unique_lock<AnnotatedMixinboost::recursive_mutex >::lock() () #5 0x000000000050cfc4 in ThreadSocketHandler2(void) () #6 0x000000000050e6f1 in ThreadSocketHandler(void) () #7 0x00007ffff69866c9 in ?? () from /usr/lib/libboost_thread.so.1.49.0 #8 0x00007ffff6761e9a in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0 #9 0x00007ffff47bbcbd in clone () from /lib/x86_64-linux-gnu/libc.so.6 #10 0x0000000000000000 in ?? ()

  2. laanwj commented at 12:18 PM on November 7, 2013: member

    Should be fixed with master / newer 0.8.x. If not please comment here or open a new issue.

  3. laanwj closed this on Nov 7, 2013

  4. FourthDr commented at 1:11 AM on February 15, 2016: none

    I'm getting this same error ever since upgrading from 0.9x to 10+ now at 11.2. I get this error when trying to send bitcoins after entering my wallet password and when trying to create a new receive address. Both operations fail with this error and then bitcoin core crashes.

  5. dcousens commented at 1:13 AM on February 15, 2016: contributor

    @FourthDr can you outline the exact steps that lead to your crash? Is it consistent?

  6. FourthDr commented at 1:15 AM on February 15, 2016: none

    Yes, it is consistent. I start bitcoin and wait over an hour for it to verify blocks, then scan. Once the client opens and I try to send bitcoin by clicking send, I get a password prompt, enter password click ok, then the client freezes and finally I get the error. With creating a new address, I get the error immediately after clicking create new address. :-( My last successful send was with 0.9 client.

  7. FourthDr commented at 1:23 AM on February 15, 2016: none

    error

  8. FourthDr commented at 1:31 AM on February 15, 2016: none

    I also tried installing bitcoin core 11.2 on a brand new install of Windows 7 that never had bitcoin installed on it. And It will never completely sync up. It gets to within 2 weeks, then starts crashing immediately upon starting the client. So I am at a loss as to what to do. I am dead in the water as far as bitcoin core is concerned. What was changed in the 10x & 11x client that has gone so hideously wrong??

  9. FourthDr commented at 9:35 PM on February 17, 2016: none

    So is there a dedicated support site for bitcoin core problems? Need this resolved asap! My coins are being held hostage!

  10. laanwj commented at 10:18 AM on February 18, 2016: member

    As far as I know, no. Like for any open source project, support, if available at all, is provided by the community (or service contracts).

    Anyhow: Looks like a corrupted wallet. What you could try is to backup wallet.dat carefully, and then run bitcoind/qt with the command line argument -salvagewallet. This will try to repair it as far as automatically possible.

  11. raymliu commented at 7:50 AM on April 26, 2020: none

    maybe the dat file problem ?

  12. DrahtBot locked this on Feb 15, 2022

github-metadata-mirror

This is a metadata mirror of the GitHub repository bitcoin/bitcoin. This site is not affiliated with GitHub. Content is generated from a GitHub metadata backup.
generated: 2026-04-13 18:16 UTC

This site is hosted by @0xB10C
More mirrored repositories can be found on mirror.b10c.me