<p>One way to solve this seems to be to disable and then reenable txindex. In other words, stop bitcoind, set txindex=0 in bitcoin.conf, start bitcoind, wait until fully started, stop bitcoind, set txindex=1, start bitcoind, wait until message "txindex is enabled at height xxx".</p>

<p>Unsure why this is necessary though.</p>

CC BY-SA 4.0
2024-11-01T18:36:48.710Z
I would be cautious of this advise. Restarting a `txindex`-synced node without `txindex` will essentially abandon `txindex` and you will need to re-index from scratch, should you want to enable `txindex` again
pokrovskyy
CC BY-SA 4.0
2024-11-01T18:57:13.023Z
and yes, it "helps" because there's no `txindex` anymore, so no warnings about it :) Maybe you did not notice this because you did not need `txindex` at the first place
pokrovskyy
CC BY-SA 4.0
2019-06-10T12:40:08.077Z
2019-06-10T12:40:08.077Z
Craig Raw
<p>For me it turned out that I had mempool.space running on my machine before bitcoind was done syncing the blockchain. I assume that mempool sends RPC calls to bitcoind in regular intervals, which then somehow causes this message to appear in the <code>debug.log</code> and often it seems that this message stops the blockchain syncing process and you have to restart bitcoind.</p>
<p>Simply shutting down mempool.space allowed bitcoind to then download the rest of the blockchain without any hickups, for me.</p>

CC BY-SA 4.0
2022-09-20T00:22:05.940Z
2022-09-20T00:22:05.940Z
mbrochh
<p>The warning message simply means that your node is indexing new block(s) at the moment, and thus RPC calls are blocked temporarily. Blocked here means they are waiting in the RPC request queue, not rejected or something. So once the indexing is done, they will be processed normally.</p>
<p>From the client side it may look like those requests take more time to execute. That is until there are too many requests in the RPC queue and further requests are rejected. then you would see different messages in the log explicitly stating this, which is a bigger concern (that's when your RPC clients will actually receive an error). Queue depth can be adjusted (default is 15, IIRC)</p>
<p>If you see a lot of messages like this - it may mean your node lacks resources to promptly index incoming blocks, check the node performance (disk IO / memory / CPU usage).</p>

CC BY-SA 4.0
2024-11-01T18:45:47.550Z
2024-11-01T18:45:47.550Z
pokrovskyy
<p>The message "BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications" is appearing regularly in my debug.log. When these messages appear, I can be sure that lnd will not be able to complete syncing to the chain and thus unable to fully start. </p>

<p>This message occurs after the "txindex thread exit" message, and can be triggered with a "bitcoin-cli getrawtransaction xxx" call. I don't know how to resolve this, or even to determine what state the txindex is in. Restarting bitcoind does not help.</p>

<p>I am running Bitcoin Core version v0.18.0 (release build).</p>

<bitcoin-core>
BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications
Craig Raw
# BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications

(Asked by: username_0 on 2019-06-10)

The message "BlockUntilSyncedToCurrentChain: txindex is catching up on block notifications" is appearing regularly in my debug.log. When these messages appear, I can be sure that lnd will not be able to complete syncing to the chain and thus unable to fully start.

This message occurs after the "txindex thread exit" message, and can be triggered with a "bitcoin-cli getrawtransaction xxx" call. I don't know how to resolve this, or even to determine what state the txindex is in. Restarting bitcoind does not help.

I am running Bitcoin Core version v0.18.0 (release build).

**Tags:** bitcoin-core


---

## 3 answers

### Answer by username_0 on 2019-06-10. Score: 1

One way to solve this seems to be to disable and then reenable txindex. In other words, stop bitcoind, set txindex=0 in bitcoin.conf, start bitcoind, wait until fully started, stop bitcoind, set txindex=1, start bitcoind, wait until message "txindex is enabled at height xxx".

Unsure why this is necessary though.

> **Comments:**
> **username_1**: I would be cautious of this advise. Restarting a `txindex`-synced node without `txindex` will essentially abandon `txindex` and you will need to re-index from scratch, should you want to enable `txindex` again  
> **username_1**: and yes, it "helps" because there's no `txindex` anymore, so no warnings about it :) Maybe you did not notice this because you did not need `txindex` at the first place  

---

### Answer by username_2 on 2022-09-20. Score: 0

For me it turned out that I had mempool.space running on my machine before bitcoind was done syncing the blockchain. I assume that mempool sends RPC calls to bitcoind in regular intervals, which then somehow causes this message to appear in the `debug.log` and often it seems that this message stops the blockchain syncing process and you have to restart bitcoind.

Simply shutting down mempool.space allowed bitcoind to then download the rest of the blockchain without any hickups, for me.


---

### Answer by username_1 on 2024-11-01. Score: 0

The warning message simply means that your node is indexing new block(s) at the moment, and thus RPC calls are blocked temporarily. Blocked here means they are waiting in the RPC request queue, not rejected or something. So once the indexing is done, they will be processed normally.

From the client side it may look like those requests take more time to execute. That is until there are too many requests in the RPC queue and further requests are rejected. then you would see different messages in the log explicitly stating this, which is a bigger concern (that's when your RPC clients will actually receive an error). Queue depth can be adjusted (default is 15, IIRC)

If you see a lot of messages like this - it may mean your node lacks resources to promptly index incoming blocks, check the node performance (disk IO / memory / CPU usage).


---

