Bitcoin core error after disabling block chain pruning and then restarting the application, error:opening block database #23816

issue nuketown3 opened this issue on December 19, 2021
  1. nuketown3 commented at 9:50 AM on December 19, 2021: none

    <!-- This issue tracker is only for technical issues related to Bitcoin Core. General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com. For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/. If the node is "stuck" during sync or giving "block checksum mismatch" errors, please ensure your hardware is stable by running memtest and observe CPU temperature with a load-test tool such as linpack before creating an issue! Any report, issue or feature request related to the GUI should be reported at https://github.com/bitcoin-core/gui/issues/ -->

    <!-- Describe the issue -->

    I have attempted to turn of block chain pruning in the options menu, which has required the application to restart. When I have restarted the application I'm faced with this error message and then the program closes.

    This now happens every time I open the application and wont load to the wallet, It also persists even after I uninstall the entire bitcoin core and re install the bit coin core program and when I go to initial launch the program this again pops up.

    Was working previous but with a pruned block chain and had no problems, but as soon as I went to options and disabled block chain pruning this was the resulting error I received.

    "you need to rebuild the data base using -reindex to go back to unpruned mode. This will redownload the entire blockchain. do you want to rebuild the block database now?

    ok

    error:opening block database

    ok

    program closes"

    If someone knows what I can do to fix this, many thanks

    <!--- What behavior did you expect? -->

    <!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->

    <!--- How reliably can you reproduce the issue, what are the steps to do so? -->

    <!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->

    <!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->

    <!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop enviro ![Core error2](https://user-images.githubusercontent.com/95224812/146670460-710c0765-940f-4455-b37d-2727b7eff253.png) ![Core error1](https://user-images.githubusercontent.com/95224812/146670458-ecfd58a6-f21e-42c6-be17-f77827e8f9aa.png) nment and graphical shell? -->

    <!-- Any extra information that might be useful in the debugging process. -->

    <!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->

  2. nuketown3 renamed this:
    Bitcoin core error after disabling block chain pruning and then restarting the application
    Bitcoin core error after disabling block chain pruning and then restarting the application, error:opening block database
    on Dec 19, 2021
  3. Davidson-Souza commented at 1:51 PM on December 23, 2021: none

    Did you start core with -reindex=1?

  4. hebasto commented at 2:56 PM on January 3, 2022: member

    Is it the same as #22964?

  5. Dog-Pack commented at 3:42 PM on January 22, 2022: none

    Did you start core with -reindex=1?

    I had the same issue goggled, it found this thread tried the above and then it started ok.

    and yes i believe its the same as 22964

  6. hebasto commented at 11:24 AM on October 24, 2022: member

    yes i believe its the same as 22964

    Could be closed as #22964 has been resolved.

  7. hebasto closed this on Oct 24, 2022

  8. bitcoin locked this on Oct 24, 2023

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-05-20 06:53 UTC