Open joltcan opened 1 year ago
Running Fulcrum also in a VM (ESXi 7.01) 6vCPU 16GB RAM. BitcoinCore is running too. I installed Fulcrum 1.9.1, and after 5 days syncing (99%) I got the massage that the database has been corrupted. After deleting the fulcrum_db I started again. After another day (66%) I got the same message.
LOG.txt
LOG_old_1692207067861514.txt
Any idea what I can do?
Don't use fast-sync. it is experimental and doesn't always work ok and may eat memory. Also max open files .. just leave it at default.
If worried maybe enabling swap would help avoid OOMs..
Thank you for your quick response. I try it with disabled fast-sync again.
Hello cculianu, syncing just finished. Without fast-sync. Thanks
Yay!
Running Fulcrum in a VM (esx 6.7) with 32 GB RAM and 8 cores (also has bitcoind running). The other day Fulcrum stopped with the infamous
The following settings are non-standard, based on various googling to see if we can get it to do the initial sync faster:
Any guesses or anything we can do. It was running for a few months without any hickups.