2

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).

Improve this question

3 Answers 3

Reset to default
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.

Improve this answer
2
  • 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
    Commented Nov 1 at 18:36
  • 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
    Commented Nov 1 at 18:57
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.

Improve this answer
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).

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.