Here is some snapshots of the system as it runs via the "sensors" command.
coretemp-isa-0000
Adapter: ISA adapter
Package id 0: +52.0°C (high = +86.0°C, crit = +100.0°C)
Core 0: +52.0°C (high = +86.0°C, crit = +100.0°C)
Core 1: +46.0°C (high = +86.0°C, crit = +100.0°C)
Core 2: +45.0°C (high = +86.0°C, crit = +100.0°C)
Core 3: +43.0°C (high = +86.0°C, crit = +100.0°C)
acpitz-acpi-0
Adapter: ACPI interface
temp1: +50.0°C (crit = +98.0°C)
temp2: +50.0°C (crit = +98.0°C)
I hope it helps.
Your CPU seems to be fine. Lets check if bitcoind is throwing a fatal C++ exception.
Go to github.com/bitcoin/bitcoin, and go to the Releases page. We are going to download the source code for Bitcoin 24.0 and compile it, then have it run under a debugger.
Under "Bitcoin Core 24.0" download the one that ends with "x86_64-linux-gnu.tar.gz", Extract it to any download folder.
Now, open a terminal and run:
sudo apt-get install -y build-essential libtool autotools-dev automake pkg-config bsdmainutils python3 libevent-dev libboost-dev libsqlite3-dev libqt5gui5 libqt5core5a libqt5dbus5 qttools5-dev qttools5-dev-tools qtwayland5
This will install the compiler and other dependencies needed to build Bitcoin Core.
Next, go to the root folder of the bitcoin core source code and run:
./contrib/install_db4.sh $(pwd)
export BDB_PREFIX=$(pwd)/db4 # This is supposed to be the db4 folder in the current die. If you get mysterious compile errors related to Berkeley DB, you probably forgot to run this command.
./autogen.sh
./configure BDB_LIBS="-L${BDB_PREFIX}/lib -ldb_cxx-4.8" BDB_CFLAGS="-I${BDB_PREFIX}/include" CXXFLAGS="-O0 -g" CFLAGS="-O0 -g"
make
OK, now we have built Bitcoin Core 24 from source. Now we are ready to debug it. You can open the debugger with this command:
gdb src/bitcoind
(If that says command not found, you need to install gdb using "sudo apt-get install gdb")
This will open up a debugger.
Now all you have to do is run:
run -nodaemon
This will start Bitcoind and pass it the -nodaemon option, so it doesn't fork and escape from the debugger.
At this point, just monitor the debugger. If Core crashes or mysteriously disappears again, its going to show up on the debugger. Just copy and paste the entire output here so we can inspect it.
