-
Notifications
You must be signed in to change notification settings - Fork 101
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Panic after enabling txindex #461
Comments
The error I'm getting with
This seems like another bug - why would it need so much RAM to delete something on the disk? |
Duplicate of #401? |
Brutal. We will debug this. Should be pretty easy to replicate. |
@infertux has this issue happened for you more than once? I haven't been able to reproduce on a testnet, and haven't had time to try it on mainnet. |
I am dropping indexes on my node, and recreating to see if I can replicate the issue. |
@jcramer It happened on a brand new node. My other bchd nodes are not experiencing this issue but they are running a stable release (as opposed to commit 71569b6).
@zquestz I'm doing this as well right now and will report back... |
@zquestz So |
To recap:
Looks like I need to resync the DB from scratch... |
I had no problems dropping the indexes, then rebuilding them from scratch. My node is happily running right now. Sorry, I couldn't reproduce. =\ |
Version: compiled at commit 71569b6
Steps to reproduce:
txindex=1
in config fileCrash after the index creation is complete:
Now it keeps crashing every time I start it. I tried to start it with
--reindexchainstate
but it's crashing as well.The text was updated successfully, but these errors were encountered: