<p>If you check in your <code>debug.log</code> you should be able to see if there is any error when you started the node. Probably when the node shutdown uncleanly some of the tables were in an inconsistent state.</p>

<p>Presuming everything is fine and it is not stuck, it is okay to just start with <code>bitcoind -daemon</code> and it will do what it needs to.</p>

CC BY-SA 4.0
2018-07-04T22:51:48.290Z
Awesome, thought that might be the case. Thanks a lot for your answer, really appreciate it!
S Psy
CC BY-SA 4.0
2018-07-03T21:15:54.803Z
2018-07-03T21:15:54.803Z
Willtech
<p>I am very new to this and apologies if it has been asked before but I can't seem to find a clear answer after looking extensively.</p>

<p>I am trying to run a full node. I started <code>bitcoind -daemon</code> and everything worked fine, the blockchain was syncing. It crashed the next day because I hadn't set my options for swap memory correctly.</p>

<p>After fixing that issue, I did <code>bitcoind -daemon</code> again and it looked like everything was being done from the start. Should I be doing <code>bitcoind -reindex-chainstate</code> from now on if the process stops? Or did I not understand correctly and simply doing <code>bitcoind</code> will resume syncing but requires some verification first?</p>

<p>Also, in any of the above cases, is it the same process once the blockchain has synced?</p>

<p>This is on a Raspberry Pi 3B+ with an external HDD for storage.</p>

<p>Thanks a lot in advance.</p>

<bitcoind><full-node><linux>
What is the right way to restart bitcoind if it crashes?
S Psy
# What is the right way to restart bitcoind if it crashes?

(Asked by: username_0 on 2018-07-03)

I am very new to this and apologies if it has been asked before but I can't seem to find a clear answer after looking extensively.

I am trying to run a full node. I started `bitcoind -daemon` and everything worked fine, the blockchain was syncing. It crashed the next day because I hadn't set my options for swap memory correctly.

After fixing that issue, I did `bitcoind -daemon` again and it looked like everything was being done from the start. Should I be doing `bitcoind -reindex-chainstate` from now on if the process stops? Or did I not understand correctly and simply doing `bitcoind` will resume syncing but requires some verification first?

Also, in any of the above cases, is it the same process once the blockchain has synced?

This is on a Raspberry Pi 3B+ with an external HDD for storage.

Thanks a lot in advance.

**Tags:** bitcoind, full-node, linux


---

## 1 answers

### Answer by username_1 on 2018-07-03. Score: 2

If you check in your `debug.log` you should be able to see if there is any error when you started the node. Probably when the node shutdown uncleanly some of the tables were in an inconsistent state.

Presuming everything is fine and it is not stuck, it is okay to just start with `bitcoind -daemon` and it will do what it needs to.

> **Comments:**
> **username_0**: Awesome, thought that might be the case. Thanks a lot for your answer, really appreciate it!  

---

