Well, the thing is that last week, I got home from work and I find my bitcoin node shut down due to data corurption. So, I started reindexing the chainstate a shortly after bitcoin core seg faulted! Then, I think it was here in the forum that I opened a thread about this and someone told me it could be the cpu overheating. So, I went to check and yes, it was overheating. It was like 102ºC.
Check the data sheet for your processor and look for something called the Tjmax temperature. It's the highest temperature your CPU can operate at without overheating, and if it crosses this value there's going to be a few seconds of grace period where the OS hibernates if that's possible. If not then the system actually runs normally during that grace period and then abruptly powers off. Most processors have it at 100C but some powerful CPUs can go up to 105C. Just some overheating 101 from someone who had to deal with this too
If you continue to have problems with the CPU overheating and you're using Linux then you need to underclock it from software using
cpupower.
But, this
anchor.dat file cannot be found in my blockcahin dir.
However, I can see this in my debug file:
2021-02-10T18:39:16Z Loaded 2 addresses from "anchors.dat"
Bitcoin Core creates an anchors.dat file with the two peers when it shuts down normally, and when it starts again, it deletes this file after reading the peers from it (
addrdb.cpp). Perhaps the log entry you are seeing was made at the time you started Core
before it shut down abnormally. In that case no anchors.dat existed because one wasn't created at shutdown, so when Core sees that anchors.dat doesn't exist at startup, it skips reading those addresses, and it will not create this file right after that check fails (but will still write this file next time it shuts down normally).
