Problems with 8.26.1 upgrade

[vikas027]

We recently upgraded our DigiByte node from version 8.22.2 to 8.26.1, after which we began seeing the following error in the logs:

digibyte-0 digibyte 2025-11-06T03:15:37Z Opened LevelDB successfully
digibyte-0 digibyte 2025-11-06T03:15:37Z Using obfuscation key for /home/digibyte/data/indexes/txindex: 0000000000000000
digibyte-0 digibyte 2025-11-06T03:15:37Z Error: txindex: best block of the index not found. Please rebuild the index.
digibyte-0 digibyte Error: txindex: best block of the index not found. Please rebuild the index.
digibyte-0 digibyte 2025-11-06T03:15:37Z Shutdown: In progress...
digibyte-0 digibyte 2025-11-06T03:15:37Z scheduler thread exit
digibyte-0 digibyte 2025-11-06T03:15:37Z Flushed fee estimates to fee_estimates.dat.

To resolve it, I executed this command:

digibyted -disablewallet -reindex -datadir=/home/digibyte/data

The node stabilized after several hours, but it soon started logging numerous warnings like this:

WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting

At present, we're performing a complete resync. We've scaled up the CPU and RAM resources and adjusted the configuration from -rpcworkqueue=128 -rpcthreads=16 to -rpcworkqueue=512 -rpcthreads=32, yet the warnings persist.

Anyone else facing the same?

[JaredTate]

Hi there — thanks for opening this issue and for providing the detailed logs. We really appreciate you taking the time to report it.

Before we go further: are you still experiencing this issue, or did the full resync resolve things on your node? Please let us know so we can track it accurately.

After further investigation, here are a few things you can try right away while we continue looking into this further.

---

Quick Follow-Up Questions

1. Have you ever seen this same issue when running Bitcoin Core v26 or later?
DigiByte v8.26 includes the changes from Bitcoin Core v22 → v26. Knowing whether this behavior appears upstream helps determine if the issue is DigiByte-specific or inherited.

2. Did the error appear immediately on first startup after upgrading to 8.26.1, or only after running the reindex?
This will help us determine whether the stored block locator or the rebuild path is involved.

---

What We Know So Far

In v8.26, the index system now requires the first block hash in the stored block locator to exist in the active chain during initialization. This is stricter than earlier behavior (which could fall back to genesis). If that first hash is missing — for example due to a minor reorg or outdated locator — the index fails with:

txindex: best block of the index not found. Please rebuild the index.

Your use of -reindex was the correct immediate action.

---

Immediate Suggestions

For the txindex Error

If others encounter this error:

Delete only the txindex (recommended)

# Stop the node
digibyte-cli stop

Delete only the txindex database (preserves blockchain data)

rm -rf ~/.digibyte/indexes/txindex/

Restart — index will rebuild automatically

• Reduce heavy RPC usage while the index is rebuilding.
Even with high -rpcworkqueue and -rpcthreads values, heavy RPC calls during initial sync can saturate the queue and trigger warnings.

• Let the node run quietly after a clean reindex until the txindex fully completes.

• If warnings persist after the full sync finishes, please share updated logs.
This will help us confirm whether it's related to locator handling, RPC contention, or something else in the upgrade path.

---

Next Steps

We are continuing to review the upgrade path from v8.22.2 → v8.26.1 and how older locator data interacts with the stricter initialization rules in v8.26. Your report is very helpful in confirming this behavior.

Please let us know:

• Whether the issue persists after the full resync
• Whether you've seen similar behavior on Bitcoin Core v26+
• Any new logs once the index completes syncing

Thanks again for reporting this — we’ll keep digging and will update this issue as we learn more.

[exodus-justinz]

@JaredTate thanks for the quick response!

are you still experiencing this issue, or did the full resync resolve things on your node?

Yes, we are still experiencing this, and a full resync didn't solve the issue

Have you ever seen this same issue when running Bitcoin Core v26 or later?

I don't remember seeing any issues with our Bitcoin instance. It's running smoothly, and no slowness was observed

Did the error appear immediately on first startup after upgrading to 8.26.1, or only after running the reindex?

Immediately after upgrading to 8.26.1. We also see higher resource usage compared to the previous version - if that helps.

Immediate Suggestions

let me try this out and revert back here with the results. thank you for this!

[exodus-justinz]

reindex finished

2025-12-03T04:56:37Z ReadBlockFromDisk: Called with pos=FlatFilePos(nFile=221, nPos=40286294)
2025-12-03T04:56:37Z ReadBlockFromDisk: Called with pos=FlatFilePos(nFile=221, nPos=40286583)
2025-12-03T04:56:37Z txindex is enabled at height 22553196
2025-12-03T04:56:37Z txindex thread exit
2025-12-03T04:56:57Z Saw new header hash=00000000000000024e085d387e35b592e06c4bc4337d89de5652bb3b6ac47f8d height=22553197
2025-12-03T04:56:57Z [net] Saw new cmpctblock header hash=00000000000000024e085d387e35b592e06c4bc4337d89de5652bb3b6ac47f8d peer=30
2025-12-03T04:56:57Z UpdateTip: new best=00000000000000024e085d387e35b592e06c4bc4337d89de5652bb3b6ac47f8d height=22553197 version=0x2009a202 log2_work=84.755099 tx=52207862 date='2025-12-03T04:56:56Z' progress=1.000000 cache=12.3MiB(108664txo)

i'll reenable traffic and monitor it for a while

[exodus-justinz]

@JaredTate i'm seeing network timeouts after enabling traffic. i added -debug=rpc and let me paste the output below

2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=help user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getnetworkinfo user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getmempoolinfo user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getpeerinfo user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=estimatesmartfee user=bitcoinrpc
2025-12-03T06:53:40Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:41Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:43Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:44Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:47Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:49Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:51Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc
2025-12-03T06:53:52Z [rpc] ThreadRPCServer method=getblockchaininfo user=bitcoinrpc

i stumbled upon this issue, do you think the threads are getting occupied by getblockchaininfo which causes the network timeouts? we run our node with the following

-dbcache=450 -rpcworkqueue=128 -rpcthreads=16

[exodus-justinz]

node got corrupted again after 2 days

Error: txindex: best block of the index not found. Please rebuild the index.

[JaredTate]

T

node got corrupted again after 2 days

Error: txindex: best block of the index not found. Please rebuild the index.

Thank you @exodus-justinz for the feedback. I will take a deeper look in to this this morning and try to help get this resolved quickly.

Also if you were to compile latest from develop we fixed the getblockchaininfo timeout issue with this PR recently merged: #349

[exodus-justinz]

@JaredTate, any ideas on when it'll be rolled out on a stable release? just need to reindexing after using the develop branch but it looks fine now.

[JaredTate]

@JaredTate, any ideas on when it'll be rolled out on a stable release? just need to reindexing after using the develop branch but it looks fine now.

Thanks for the feedback. So, to confirm our develop branch is stable for you guys since our getblockchaininfo fix?

We have a handful of other small improvements to add ot anoher rekease but we would like to get to the bottom of this issue before another release. We will shoot for another small update release in a week or two. But if the develo branch is stable for you guys it would make sense to run it till our next major release.

Thanks again for supporting DGB & thank you for reporting your issue!