You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
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:
To resolve it, I executed this command:
The node stabilized after several hours, but it soon started logging numerous warnings like this:
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=16to-rpcworkqueue=512 -rpcthreads=32, yet the warnings persist.Anyone else facing the same?
NOTE: I have also logged an issue for the same.
Beta Was this translation helpful? Give feedback.
All reactions