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
Bitcoin Core 27 crash at sync - Ubuntu - No error in logs #30001
Comments
What filesystem is the storage? Is it attached via USB? Is the datadir on the storage, or only the blocksdir? What is the full bitcoin config file? Can you run it in gdb again for a traceback? Does |
Thanks for taking the time answering @maflcko. The external HDD is mounted as a GUID Partition Table and is connected via USB3 to the motherboard's input. Only blocksdir is stored in the HDD. Attached the gdb output when running bitcoin-qt in the debugger: gdb.txt Please also find the |
The gdb txt is empty. You can also post it in a comment, if it is shorter than 100 lines. |
@maflcko apologies, here is the dgb extract https://pastebin.com/LQri1rtg |
I mean it doesn't contain the crash information. Are you sure this is a crash and not a normal shutdown or someone initiating a shutdown? In any case, if this really is a crash, you can get the traceback with something like:
Then recreate the crash and check the output in the terminal. |
Closing for now due to inactivity, but please leave a comment if you have more details or information. |
Is there an existing issue for this?
Current behaviour
Bitcoin Core launches and starts syncing with the blockchain. After a variable amount of time (20 minutes to 2 hours), Bitcoin Core crashes (app closed) with no error in the logs
Expected behaviour
Bitcoin Core is expected to sync without crashing
Steps to reproduce
Relevant log output
No response
How did you obtain Bitcoin Core
Pre-built binaries
What version of Bitcoin Core are you using?
v27.0.0
Operating system and version
Ubuntu 22.04.4
Machine specifications
-Extract from the latest debug log (can't upload the full file):
The text was updated successfully, but these errors were encountered: