Oddbean new post about | logout
▲ ▼
BlackCoffee | 5 months ago (raw) | root | parent | reply | flag 
 Do you know the cause? I got a UPS for my dojo but still haven't gone back to Fulcrum.
▲ ▼
greenart7c3 | 5 months ago (raw) | root | parent | reply | flag +1 
 For me it was power loss and one time the SSD was overheating
▲ ▼
sommerfeld | 5 months ago (raw) | root | parent | reply | flag +2 
 I honestly don't know. This happened by just rebooting...
My theory is that when you reboot, it kills all processes "nicely" with SIGTERM but if they don't stop after some time, it kills them forcefully with SIGKILL. I think Fulcrum can take a while to shutdown if it gets killed while writing to the DB, so when it gets SIGKILLed later, DB gets corrupted.
▲ ▼
cloud fodder | 5 months ago (raw) | root | parent | reply | flag +1 
 Do you have timeoutstopseconds set? I guess I should ask if you're using a systemd unit first 😁

It should wait for it on a reboot if you have the settings set and it's running in the system.slice
▲ ▼
c2e5c5cb | 5 months ago (raw) | root | parent | reply | flag +2 
 Use the latest version. The problem is not Fulcrum, but the underlying rocksdb, which was very shaky <v8. Now it’s really stable, I love Fulcrum. It’s great software. 

However, I regularly make rsync backups of the database directory, just in case. But I do that with the Bitcoin blockchain as well because I don’t want to wait weeks for it to resync/reindex.