bitcoin: bitcoind crash
Is there an existing issue for this?
- I have searched the existing issues
Current behaviour
My bitcoin node is crashing quite frequently. And after the crash you can’t recover anymore. It seems that the files become inaccessible and you cannot start again. Because I can’t even read the debug.log file. Everything only works again after restarting the system.
The problem started after I updated to version 27.0.0. Before I had version 25.0.0
Expected behaviour
Don’t crash
Steps to reproduce
I didn’t identify any steps to reproduce. It happens at random times every 3 or 4 days.
Relevant log output
Jan 21 09:38:57 freedom-server systemd[1]: Started bitcoind.service - Bitcoin daemon.
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Main process exited, code=dumped, status=6/ABRT
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Failed with result 'core-dump'.
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Consumed 2h 53min 32.054s CPU time, 648.0M memory peak, 0B memory swap peak.
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Scheduled restart job, restart counter is at 1.
Jan 22 18:27:11 freedom-server systemd[1]: Starting bitcoind.service - Bitcoin daemon...
Jan 22 18:27:11 freedom-server bitcoind[58682]: Error: Settings file could not be read:
Jan 22 18:27:11 freedom-server bitcoind[58682]: - /hdd/bitcoin/settings.json. Please check permissions.
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Control process exited, code=exited, status=1/FAILURE
Jan 22 18:27:11 freedom-server systemd[1]: bitcoind.service: Failed with result 'exit-code'.
Jan 22 18:27:11 freedom-server systemd[1]: Failed to start bitcoind.service - Bitcoin daemon.
How did you obtain Bitcoin Core
Pre-built binaries
What version of Bitcoin Core are you using?
27.0.0
Operating system and version
Ubuntu 24.04 LTS
Machine specifications
Intel® Core™ i5-4200M CPU @ 2.50GHz 8GB RAM
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 25 (10 by maintainers)
@frbitten Bitcoin Core, as a user-level application, is simply incapable of corrupting a filesystem, as it has no access to the raw disk. Corruption is a sign of either a hardware issue (likely) or an operation system issue (unlikely).
Bitcoin Core makes heavy use of CPU, RAM and storage IO. Hardware defects might only become visible when running Bitcoin Core. You might want to check your hardware for defects.
Source: https://bitcoin.stackexchange.com/a/12206
Usually the issue tracker is used to track technical issues related to the Bitcoin Core code base.
General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange or the
#bitcoinIRC channel on Libera Chat, or one of the Bitcoin subreddits, or any other place that you feel is well suited.+1
Disks from every brand have failed at every age, and it is reasonable that some examples of a generally reliable drive will fail after 2 years, it’s possible that the manufacturer of your drive will replace it under warranty if it has failed before its advertised lifetime. (https://www.crucial.com/ssd/bx500)
You might want to check the SMART data of the drive, doing something like:
This article: https://www.linuxjournal.com/article/6983 has helpful information about how to interpret the output of
smartctl -A /dev/sdXIf you had to fsck / repair your filesystem, it may be unavoidable, you may need new storage device(s). System error logs at the times /var/log/syslog, might help you shed light on on this. Also, 90% capacity seems (to me) kind of high for one SDD that has to do everything – OS, swap, tmp, apps, blockchain data, etc. Also, you did not mention AV software… You might at least benefit from cheap external storage at least, especially if you are not running pruned. That, or switch to running pruned if you are not already.
This will not do anything; shutdown is the same whether you send the
stopcommand or not.While this might prevent certain problems, it is unrelated to disk corruption.