<p>I am trying to initialize a fully functional working mainnet node. The initial download with
<code>bitcoind</code> works fine until the cache reaches around 600MiB. After which it crashes. The entire 600MiB is disposed of, and I need to start again. I checked debug.log, but there were no inconsistencies that could have been suggested for the occurrence of the crash. I am setting up this system on Oracle VMWare, with around 650 GB of disk space.</p>
<p>Is there any way by which, after 600MiB of cached data, I can flush it to disk and resume with the download again? Also, any knowledge of what is causing this problem will be helpful.</p>

CC BY-SA 4.0
2023-08-17T19:22:12.213Z
How much (available) RAM do you have? My best guess is that your node is crashing exactly when it's trying to flush to disk, at which time it temporarily uses a bit more memory.
Pieter Wuille
CC BY-SA 4.0
2023-08-18T17:54:56.643Z
For this machine I have allocated around 6GB.
Sumitava Biswas
<bitcoin-core><bitcoind><full-node><synchronization><cache>
Bitcoin Mainnet Initialization Crash
Sumitava Biswas
# Bitcoin Mainnet Initialization Crash

(Asked by: username_0 on 2023-08-17)

I am trying to initialize a fully functional working mainnet node. The initial download with
`bitcoind` works fine until the cache reaches around 600MiB. After which it crashes. The entire 600MiB is disposed of, and I need to start again. I checked debug.log, but there were no inconsistencies that could have been suggested for the occurrence of the crash. I am setting up this system on Oracle VMWare, with around 650 GB of disk space.

Is there any way by which, after 600MiB of cached data, I can flush it to disk and resume with the download again? Also, any knowledge of what is causing this problem will be helpful.

**Tags:** bitcoin-core, bitcoind, full-node, synchronization, cache

> **Comments:**
> **username_1**: How much (available) RAM do you have? My best guess is that your node is crashing exactly when it's trying to flush to disk, at which time it temporarily uses a bit more memory.  
> **username_0**: For this machine I have allocated around 6GB.  

---

## 0 answers

