<p><code>transaction index disabled</code> is logged when the <code>txindex=1</code> or <code>-txindex</code> flag is not set. If it was once indexed, and you don't pass that flag, then bitcoind will prevent you from accidentally rebuilding the database without the indexes unless you explicitly tell it to with <code>-reindex</code>. Check your <code>bitcoin.conf</code> file and the startup script. Alternatively, try adding <code>-txindex</code> to <code>/etc/systemd/system/bitcoind.service</code> where <code>bitcoind</code> is called:</p>

<p><code>ExecStart=/usr/local/bin/bitcoind -txindex -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid</code></p>

CC BY-SA 4.0
2018-10-11T07:43:57.643Z
Thanks, unfortunately it didn't solved it. When calling this command I get: `Bitcoin server starting`. But when calling the debug file, it still gives "LoadBlockIndexDB: transaction index disabled". Could it be something with RPC connections because this also doesn't work when calling for `bitcoin-cli' commands
Jeans5
CC BY-SA 4.0
2018-10-11T14:27:24.963Z
I don't think it is running at all anymore (it says Exiting), you can check with `ps | aux grep bitcoind`, so RPC commands won't work either.
JBaczuk
CC BY-SA 4.0
2018-10-11T14:34:35.493Z
Thanks, this gives me "admin     7651  0.0  0.0   4372   568 pts/0    S+   16:32   0:00 grep --color=auto bitcoind".  
     When asking for the command `systemctl status bitcoind.service`, I get a green message `Active (running)`. So I assume it's running?
Jeans5
CC BY-SA 4.0
2018-10-11T14:37:48.277Z
Did you try restarting the service? `sudo systemctl restart bitcoind.service`? You can try running it directly (not as a service) until you get it working. `bitcoind -txindex -daemon`
JBaczuk
CC BY-SA 4.0
2018-10-11T14:48:41.087Z
Also this gives me the same error as above. I can't get my head around, because the same blockchain (same bitcoin folder with index and chainstate) works perfectly on my laptop with the UI. Do you think, it has something to do with the RPC credentials?
Jeans5
CC BY-SA 4.0
2018-10-11T14:53:58.013Z
No, I don't think so. If you copied the entire .bitcoin folder over, and run the same version of `bitcoind` with `txindex` flag, it *should* work, unless I'm missing something
JBaczuk
CC BY-SA 4.0
2018-10-10T20:12:52.520Z
2018-10-11T14:30:14.623Z
2018-10-11T14:30:14.623Z
JBaczuk
<p>I'm trying to run bitcoind on a Raspberry Pi 3 but I'm stuck on an error. The raspberry has a Hdd for storage with a fully indexed blockchain that was synced on my laptop and than copied to the Hdd (txindex=1).</p>

<p>When calling the log file I get this message:</p>

<p><a href="https://i.sstatic.net/Xj6fN.png" rel="nofollow noreferrer"><img src="https://i.sstatic.net/Xj6fN.png" alt="enter image description here"></a></p>

<p>Side note: I also did a reindex-chainstate=1 afterwords, but I still got this issue.</p>

CC BY-SA 4.0
2018-10-10T18:46:47.213Z
why does it say transaction index disabled? are you using `-txindex` on the pi?
JBaczuk
CC BY-SA 4.0
2018-10-10T19:26:23.883Z
I have no idea. Yes, it runs with `txindex=1`
Jeans5
CC BY-SA 4.0
2018-10-10T19:56:16.580Z
which version of `bitcoind` is the pi running?
JBaczuk
CC BY-SA 4.0
2018-10-10T20:01:26.110Z
Version 0.16.3. I followed these steps for LND ==> https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_30_bitcoin.md
Jeans5
<bitcoind><raspberry-pi><reindex><txindex>
LoadBlockIndexDB: transaction index disabled
Jeans5
# LoadBlockIndexDB: transaction index disabled

(Asked by: username_0 on 2018-10-10)

I'm trying to run bitcoind on a Raspberry Pi 3 but I'm stuck on an error. The raspberry has a Hdd for storage with a fully indexed blockchain that was synced on my laptop and than copied to the Hdd (txindex=1).

When calling the log file I get this message:

[![enter image description here](https://i.sstatic.net/Xj6fN.png)](https://i.sstatic.net/Xj6fN.png)

Side note: I also did a reindex-chainstate=1 afterwords, but I still got this issue.

**Tags:** bitcoind, raspberry-pi, reindex, txindex

> **Comments:**
> **username_1**: why does it say transaction index disabled? are you using `-txindex` on the pi?  
> **username_0**: I have no idea. Yes, it runs with `txindex=1`  
> **username_1**: which version of `bitcoind` is the pi running?  
> **username_0**: Version 0.16.3. I followed these steps for LND ==> https://github.com/Stadicus/guides/blob/master/raspibolt/raspibolt_30_bitcoin.md  

---

## 1 answers

### Answer by username_1 on 2018-10-10. Score: 0

`transaction index disabled` is logged when the `txindex=1` or `-txindex` flag is not set. If it was once indexed, and you don't pass that flag, then bitcoind will prevent you from accidentally rebuilding the database without the indexes unless you explicitly tell it to with `-reindex`. Check your `bitcoin.conf` file and the startup script. Alternatively, try adding `-txindex` to `/etc/systemd/system/bitcoind.service` where `bitcoind` is called:

`ExecStart=/usr/local/bin/bitcoind -txindex -daemon -conf=/home/bitcoin/.bitcoin/bitcoin.conf -pid=/home/bitcoin/.bitcoin/bitcoind.pid`

> **Comments:**
> **username_0**: Thanks, unfortunately it didn't solved it. When calling this command I get: `Bitcoin server starting`. But when calling the debug file, it still gives "LoadBlockIndexDB: transaction index disabled". Could it be something with RPC connections because this also doesn't work when calling for `bitcoin-cli' commands  
> **username_1**: I don't think it is running at all anymore (it says Exiting), you can check with `ps | aux grep bitcoind`, so RPC commands won't work either.  
> **username_0**: Thanks, this gives me "admin     7651  0.0  0.0   4372   568 pts/0    S+   16:32   0:00 grep --color=auto bitcoind".        When asking for the command `systemctl status bitcoind.service`, I get a green message `Active (running)`. So I assume it's running?  
> **username_1**: Did you try restarting the service? `sudo systemctl restart bitcoind.service`? You can try running it directly (not as a service) until you get it working. `bitcoind -txindex -daemon`  
> **username_0**: Also this gives me the same error as above. I can't get my head around, because the same blockchain (same bitcoin folder with index and chainstate) works perfectly on my laptop with the UI. Do you think, it has something to do with the RPC credentials?  
> **username_1**: No, I don't think so. If you copied the entire .bitcoin folder over, and run the same version of `bitcoind` with `txindex` flag, it *should* work, unless I'm missing something  

---

