<p>I had a similar problem - it turned out that Bitcoin was running out of memory. (This happened when I was using one of DigitalOcean's 512MB VPS's.)</p>

<p>Here's what you can do to check if this is the problem:</p>

<ol>
<li><p>Run the command <code>watch free -m</code></p>

<p>You'll see something like this:</p>

<pre><code>             total       used       free     shared    buffers     cached  
Mem:           997        891        106          0        117        640
-/+ buffers/cache:        133        864
Swap:         4095          0       4095
</code></pre></li>
<li><p>Look at the intersection of <code>-/+ buffers/cache</code> and <code>free</code>. This is how much free memory you have. In this example, it's 864 MB.</p></li>
<li><p>If that number drops below 10 MB before the crash, that's probably the issue.</p></li>
</ol>

<p>Here's what you can do if this is the problem you're having:</p>

<ul>
<li><p>Get a larger VPS from your provider.</p></li>
<li><p><a href="https://unix.stackexchange.com/questions/48454/how-to-configure-swap-space-after-system-instalation">Enable swap</a></p></li>
<li><p>Try adding</p>

<pre><code>dbcache=50
maxconnections=4
rpcthreads=2
</code></pre>

<p>to your bitcoin.conf file.</p></li>
</ul>

CC BY-SA 3.0
2015-01-11T09:57:11.237Z
It seems to be the issue indeed. For some reasons I currently can't enlarge a swap file (which is only 512MB) but `bitcoind -disablewallet -dbcache=50 -maxorphanblocks=100 -maxconnections=4 -rpcthreads=2` did help so far.
src091
CC BY-SA 3.0
2015-01-11T09:12:08.210Z
2015-01-11T18:21:53.930Z
2017-04-13T12:37:20.883Z
Nick ODell
<p>I have an Ubuntu 14.04 512Mb RAM/100Gb HDD server which I use to host a remote bitcoin node. <code>bitcoind</code> currently catches up and for some reason it just stops working after 10-20 minutes or so every time I re-launch it. Nothing interesting in <code>debug.log</code>:</p>

<pre><code>2015-01-11 04:28:47 UpdateTip: new best=000000000000000027ce5c42b2e4b3e5cc51f441aaf3644a4fe8bf0215abae7c  height=306691  log2_work=79.261277  tx=41024325  date=2014-06-19 19:10:49 progress=0.488913
2015-01-11 04:28:47 ProcessBlock: ACCEPTED
2015-01-11 04:28:47 ProcessBlock: ORPHAN BLOCK 290, prev=00000000000000003de1051078cb951cadb90aad2e1a94019df07d431384934e
// nothing here, bitcoind not working anymore
</code></pre>

<p>What's going on and how can I fix it?</p>

<p>UPD here's the <code>bitcoin-cli getinfo</code> output:</p>

<pre><code>{
    "version" : 90300,
    "protocolversion" : 70002,
    "blocks" : 306754,
    "timeoffset" : 0,
    "connections" : 10,
    "proxy" : "",
    "difficulty" : 13462580114.52533913,
    "testnet" : false,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}
</code></pre>

<bitcoind><server>
bitcoind stops working
src091
# bitcoind stops working

(Asked by: username_0 on 2015-01-11)

I have an Ubuntu 14.04 512Mb RAM/100Gb HDD server which I use to host a remote bitcoin node. `bitcoind` currently catches up and for some reason it just stops working after 10-20 minutes or so every time I re-launch it. Nothing interesting in `debug.log`:

```
2015-01-11 04:28:47 UpdateTip: new best=000000000000000027ce5c42b2e4b3e5cc51f441aaf3644a4fe8bf0215abae7c  height=306691  log2_work=79.261277  tx=41024325  date=2014-06-19 19:10:49 progress=0.488913
2015-01-11 04:28:47 ProcessBlock: ACCEPTED
2015-01-11 04:28:47 ProcessBlock: ORPHAN BLOCK 290, prev=00000000000000003de1051078cb951cadb90aad2e1a94019df07d431384934e
// nothing here, bitcoind not working anymore

```

What's going on and how can I fix it?

UPD here's the `bitcoin-cli getinfo` output:

```
{
    "version" : 90300,
    "protocolversion" : 70002,
    "blocks" : 306754,
    "timeoffset" : 0,
    "connections" : 10,
    "proxy" : "",
    "difficulty" : 13462580114.52533913,
    "testnet" : false,
    "paytxfee" : 0.00000000,
    "relayfee" : 0.00001000,
    "errors" : ""
}

```

**Tags:** bitcoind, server


---

## 1 answers

### Answer by username_1 on 2015-01-11. Score: 3 | Accepted answer

I had a similar problem - it turned out that Bitcoin was running out of memory. (This happened when I was using one of DigitalOcean's 512MB VPS's.)

Here's what you can do to check if this is the problem:

1. Run the command `watch free -m`

   You'll see something like this:

   ```
                total       used       free     shared    buffers     cached  
   Mem:           997        891        106          0        117        640
   -/+ buffers/cache:        133        864
   Swap:         4095          0       4095

   ```
2. Look at the intersection of `-/+ buffers/cache` and `free`. This is how much free memory you have. In this example, it's 864 MB.
3. If that number drops below 10 MB before the crash, that's probably the issue.

Here's what you can do if this is the problem you're having:

* Get a larger VPS from your provider.
* [Enable swap](https://unix.stackexchange.com/questions/48454/how-to-configure-swap-space-after-system-instalation)
* Try adding

  ```
  dbcache=50
  maxconnections=4
  rpcthreads=2

  ```

  to your bitcoin.conf file.

> **Comments:**
> **username_0**: It seems to be the issue indeed. For some reasons I currently can't enlarge a swap file (which is only 512MB) but `bitcoind -disablewallet -dbcache=50 -maxorphanblocks=100 -maxconnections=4 -rpcthreads=2` did help so far.  

---

