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

[Soily]

Hi there,

I’m not able to sync my node anymore or it’s soo slow that it will take ages to reach the 100%. At the moment it’s on 97.24%. Also I’m not able to see Peers connecting. I had a look in the log and I think it has something to do with the message written in the title.

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

I’m on Raspberry Pi5 with SSD connected but using the OS on a high quality SD card for booting.

Any ideas how to solve it? Yesterday when I re-installed the os from scratch, I could only once connect to peers. After that and after several restarts, no connection at all. The Bitcoin Node App UI also doesn’t show any block numbers or connections.

Kind Regards
Paddy

[Soily]

A couple of more observations so far.
Changing the -rpcworkqueue setting to 64 didn’t change anything. I still get the warning as written in the title.

[Soily]

These are my logs from the last startup slightly after it was finishing the verification. Shortly after many of the warnings appeared (didn’t include them at the end because they are too many).

umbrel@umbrel:~$ cat ~/umbrel/app-data/bitcoin/data/bitcoin/debug.log | tail -n 100

2025-08-13T05:26:56Z Config file arg: chain=“main”

2025-08-13T05:26:56Z Config file arg: datacarrier=“1”

2025-08-13T05:26:56Z Config file arg: datacarriersize=“83”

2025-08-13T05:26:56Z Config file arg: dbcache=“1000”

2025-08-13T05:26:56Z Config file arg: dbcache=“450”

2025-08-13T05:26:56Z Config file arg: i2pacceptincoming=“0”

2025-08-13T05:26:56Z Config file arg: i2psam=“10.21.22.11:7656”

2025-08-13T05:26:56Z Config file arg: includeconf=“umbrel-bitcoin.conf”

2025-08-13T05:26:56Z Config file arg: listen=“1”

2025-08-13T05:26:56Z Config file arg: listenonion=“0”

2025-08-13T05:26:56Z Config file arg: maxconnections=“125”

2025-08-13T05:26:56Z Config file arg: maxmempool=“300”

2025-08-13T05:26:56Z Config file arg: maxorphantx=“100”

2025-08-13T05:26:56Z Config file arg: maxreceivebuffer=“5000”

2025-08-13T05:26:56Z Config file arg: maxsendbuffer=“1000”

2025-08-13T05:26:56Z Config file arg: maxuploadtarget=“0”

2025-08-13T05:26:56Z Config file arg: mempoolexpiry=“336”

2025-08-13T05:26:56Z Config file arg: onion=“10.21.22.10:9050”

2025-08-13T05:26:56Z Config file arg: onlynet=“ipv4”

2025-08-13T05:26:56Z Config file arg: onlynet=“ipv6”

2025-08-13T05:26:56Z Config file arg: onlynet=“onion”

2025-08-13T05:26:56Z Config file arg: onlynet=“i2p”

2025-08-13T05:26:56Z Config file arg: peerblockfilters=“1”

2025-08-13T05:26:56Z Config file arg: peerbloomfilters=“0”

2025-08-13T05:26:56Z Config file arg: peertimeout=“60”

2025-08-13T05:26:56Z Config file arg: permitbaremultisig=“1”

2025-08-13T05:26:56Z Config file arg: persistmempool=“1”

2025-08-13T05:26:56Z Config file arg: printtoconsole=“0”

2025-08-13T05:26:56Z Config file arg: prune=“0”

2025-08-13T05:26:56Z Config file arg: rest=“0”

2025-08-13T05:26:56Z Config file arg: rpcallowip=“10.21.0.0/16”

2025-08-13T05:26:56Z Config file arg: rpcallowip=“127.0.0.1”

2025-08-13T05:26:56Z Config file arg: rpcauth=****

2025-08-13T05:26:56Z Config file arg: rpcworkqueue=“64”

2025-08-13T05:26:56Z Config file arg: rpcworkqueue=“128”

2025-08-13T05:26:56Z Config file arg: timeout=“5000”

2025-08-13T05:26:56Z Config file arg: txindex=“1”

2025-08-13T05:26:56Z Config file arg: whitelist=“10.21.0.0/16”

2025-08-13T05:26:56Z Config file arg: whitelist=“127.0.0.1”

2025-08-13T05:26:56Z Config file arg: zmqpubhashblock=“tcp://0.0.0.0:28334”

2025-08-13T05:26:56Z Config file arg: zmqpubhashtx=“tcp://0.0.0.0:28336”

2025-08-13T05:26:56Z Config file arg: zmqpubrawblock=“tcp://0.0.0.0:28332”

2025-08-13T05:26:56Z Config file arg: zmqpubrawtx=“tcp://0.0.0.0:28333”

2025-08-13T05:26:56Z Config file arg: zmqpubsequence=“tcp://0.0.0.0:28335”

2025-08-13T05:26:56Z Config file arg: [main] bind=“0.0.0.0:8333”

2025-08-13T05:26:56Z Config file arg: [main] bind=“10.21.21.8:8334=onion”

2025-08-13T05:26:56Z Config file arg: [main] port=“8333”

2025-08-13T05:26:56Z Config file arg: [main] rpcbind=“10.21.21.8”

2025-08-13T05:26:56Z Config file arg: [main] rpcbind=“127.0.0.1”

2025-08-13T05:26:56Z Config file arg: [main] rpcport=“8332”

2025-08-13T05:26:56Z Command-line arg: datadir=“/data/bitcoin”

2025-08-13T05:26:56Z Command-line arg: deprecatedrpc=“create_bdb”

2025-08-13T05:26:56Z Using at most 125 automatic connections (1048576 file descriptors available)

2025-08-13T05:26:56Z scheduler thread start

2025-08-13T05:26:56Z Binding RPC on address 10.21.21.8 port 8332

2025-08-13T05:26:56Z Binding RPC on address 127.0.0.1 port 8332

2025-08-13T05:26:56Z Generated RPC authentication cookie /data/bitcoin/.cookie

2025-08-13T05:26:56Z Permissions used for cookie: rw-------

2025-08-13T05:26:56Z Using random cookie authentication.

2025-08-13T05:26:56Z Using rpcauth authentication.

2025-08-13T05:26:56Z Starting HTTP server with 16 worker threads

2025-08-13T05:26:56Z Using wallet directory /data/bitcoin

2025-08-13T05:26:56Z init message: Verifying wallet(s)…

2025-08-13T05:26:56Z Using SQLite Version 3.46.1

2025-08-13T05:26:56Z Using wallet /data/bitcoin

2025-08-13T05:26:56Z Using SQLite Version 3.46.1

2025-08-13T05:26:56Z Using wallet /data/bitcoin

2025-08-13T05:26:56Z Using /16 prefix for IP bucketing

2025-08-13T05:26:56Z init message: Loading P2P addresses…

2025-08-13T05:26:56Z Loaded 11220 addresses from peers.dat 41ms

2025-08-13T05:26:56Z init message: Loading banlist…

2025-08-13T05:26:56Z SetNetworkActive: true

2025-08-13T05:26:56Z Cache configuration:

2025-08-13T05:26:56Z * Using 2.0 MiB for block index database

2025-08-13T05:26:56Z * Using 125.0 MiB for transaction index database

2025-08-13T05:26:56Z * Using 109.4 MiB for basic block filter index database

2025-08-13T05:26:56Z * Using 8.0 MiB for chain state database

2025-08-13T05:26:56Z * Using 755.6 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)

2025-08-13T05:26:56Z Script verification uses 3 additional threads

2025-08-13T05:26:56Z Using obfuscation key for blocksdir *.dat files (/data/bitcoin/blocks): ‘0000000000000000’

2025-08-13T05:26:56Z Opening LevelDB in /data/bitcoin/blocks/index

2025-08-13T05:26:56Z Opened LevelDB successfully

2025-08-13T05:26:56Z Using obfuscation key for /data/bitcoin/blocks/index: 0000000000000000

2025-08-13T05:26:56Z Using 16 MiB out of 16 MiB requested for signature cache, able to store 524288 elements

2025-08-13T05:26:56Z Using 16 MiB out of 16 MiB requested for script execution cache, able to store 524288 elements

2025-08-13T05:26:56Z init message: Loading block index…

2025-08-13T05:26:56Z Assuming ancestors of block 00000000000000000001b658dd1120e82e66d2790811f89ede9742ada3ed6d77 have valid signatures.

2025-08-13T05:26:56Z Setting nMinimumChainWork=0000000000000000000000000000000000000000b1f3b93b65b16d035a82be84

2025-08-13T05:27:01Z LoadBlockIndexDB: last block file = 4952

2025-08-13T05:27:01Z LoadBlockIndexDB: last block file info: CBlockFileInfo(blocks=71, size=128009116, heights=897145…898169, time=2025-05-17…2025-05-24)

2025-08-13T05:27:01Z Checking all blk files are present…

2025-08-13T05:27:04Z Initializing chainstate Chainstate [ibd] @ height -1 (null)

2025-08-13T05:27:04Z Opening LevelDB in /data/bitcoin/chainstate

2025-08-13T05:27:04Z Opened LevelDB successfully

2025-08-13T05:27:04Z Using obfuscation key for /data/bitcoin/chainstate: 951427f74b2a688d

2025-08-13T05:27:04Z Loaded best chain: hashBestChain=0000000000000000000039787262a18f04c2c3be7a71292f8bde3772e0e603b5 height=897604 date=2025-05-20T20:27:35Z progress=0.972544

2025-08-13T05:27:04Z init message: Verifying blocks…

2025-08-13T05:27:04Z Verifying last 6 blocks at level 3

2025-08-13T05:27:04Z Verification progress: 0%

2025-08-13T05:28:47Z Verification progress: 16%

2025-08-13T05:40:22Z Verification progress: 50%

2025-08-13T05:50:33Z Verification progress: 66%

2025-08-13T06:00:35Z Verification progress: 83%

2025-08-13T06:09:40Z Verification progress: 99%

2025-08-13T06:09:40Z Verification: No coin database inconsistencies in last 6 blocks (14736 transactions)

2025-08-13T06:09:40Z Block index and chainstate loaded

2025-08-13T06:09:40Z Opening LevelDB in /data/bitcoin/indexes/txindex

2025-08-13T06:09:43Z Opened LevelDB successfully

2025-08-13T06:09:43Z Using obfuscation key for /data/bitcoin/indexes/txindex: 0000000000000000

2025-08-13T06:09:43Z Opening LevelDB in /data/bitcoin/indexes/blockfilter/basic/db

2025-08-13T06:09:43Z Opened LevelDB successfully

2025-08-13T06:09:43Z Using obfuscation key for /data/bitcoin/indexes/blockfilter/basic/db: 0000000000000000

2025-08-13T06:09:43Z Using SQLite Version 3.46.1

2025-08-13T06:09:43Z Using wallet /data/bitcoin

2025-08-13T06:09:43Z init message: Loading wallet…

2025-08-13T06:09:43Z [default wallet] Wallet file version = 10500, last client version = 290000

2025-08-13T06:09:43Z [default wallet] Descriptors: 0, Descriptor Keys: 0 plaintext, 0 encrypted, 0 total.

2025-08-13T06:09:43Z [default wallet] Wallet completed loading in 0ms

2025-08-13T06:09:43Z [default wallet] setKeyPool.size() = 0

2025-08-13T06:09:43Z [default wallet] mapWallet.size() = 0

2025-08-13T06:09:43Z [default wallet] m_address_book.size() = 0

2025-08-13T06:09:43Z Setting NODE_NETWORK on non-prune mode

2025-08-13T06:09:43Z block tree size = 909758

2025-08-13T06:09:43Z nBestHeight = 897604

2025-08-13T06:09:43Z initload thread start

2025-08-13T06:09:43Z Bound to 0.0.0.0:8333

2025-08-13T06:09:43Z Bound to 10.21.21.8:8334

2025-08-13T06:09:43Z Loaded 0 addresses from “anchors.dat”

2025-08-13T06:09:43Z 0 block-relay-only anchors will be tried for connections.

2025-08-13T06:09:43Z init message: Starting network threads…

2025-08-13T06:09:43Z net thread start

2025-08-13T06:09:43Z dnsseed thread start

2025-08-13T06:09:43Z Waiting 300 seconds before querying DNS seeds.

2025-08-13T06:09:43Z init message: Done loading

2025-08-13T06:09:43Z addcon thread start

2025-08-13T06:09:43Z msghand thread start

2025-08-13T06:09:43Z opencon thread start

2025-08-13T06:14:43Z Loading addresses from DNS seed dnsseed.emzy.de.

2025-08-13T06:14:44Z Loading addresses from DNS seed seed.bitcoin.wiz.biz.

2025-08-13T06:14:44Z Loading addresses from DNS seed dnsseed.bitcoin.dashjr-list-of-p2p-nodes.us.

2025-08-13T06:14:45Z Waiting 300 seconds before querying DNS seeds.

2025-08-13T06:15:37Z UpdateTip: new best=0000000000000000000162d5c01459c1bef4f1180610d108090482d956370901 height=897605 version=0x20024000 log2_work=95.619314 tx=1193169030 date=‘2025-05-20T20:47:23Z’ progress=0.972537 cache=2.2MiB(15642txo)

[Soily]

What I find strange, that it has two rpcworkqueue settings shown in the log. I only set =32 once but he is getting from somewhere another rpcworkqueue which is 128.

I could imagine that this has an impact on this bad behavior. I want to start with the 32, to see if this stops the overloading or something. How can I remove the 128 setting from where?

[Soily]

I started yesterday the node with setting reindex=1 in the settings in the Bitcoin App UI → Custom bitcoin.conf overrides. It will then connect to peers and everything seems to look ok beside that it’s showing not the complete latest block number in the UI but only the number, where I left of a couple of month ago. When the node is around ~6.x%, the Bitcoin Node App crashes unexpectedly. I tried this twice in the last 12 hours. When I restart the Bitcoin Node App, it starts all over again, which takes a couple of hours until it gets to the ~6.x%.

Any recommendations what I could do to solve it?

Cheers Paddy

[Soily]

Here are some logs from my last post before.

umbrel_bitcoin_2025-08-14_08-39.log (87.1 KB)

bitcoin-log-tail(1).txt (47.3 KB)

[Soily]

Interessting. After the crash I removed the “resync=1” from the settings and he automatically restarted the Bitcoin Node App and now it looks to rebuild the blockchain much faster. He is directly starting the sync at ~ 5% instead of 0% and no wait for some initializations. Let’s see how far it can come this time.

[Soily]

It got now completely stuck. Again at ~ 6%. I noticed that the RAM was at around 6.6GB from 8GB while it happened. Also when I touched the device, it was pretty hot. So I guess it’s a HW/RAM issue.

I’ve now restarted the device with the following settings in the Bitcoin Node App:
dbcache=1000
maxmempool=50

Since 20 minutes now, the device runs much much faster and is already at > 8% with syncing. Used ram is at around 5 GB. So at the moment it’s looking stable and fast. Also I stopped all other Apps on the device.

[Soily]

Just a short update. My node is still up and running fine. The syncing is becoming slower as it approaches the 100%. At the moment it is at 68%. I hope that this is normal behavior. The node is now up for 21 Hours so I think it’s in the normal range.

[Soily]

Another short update. The node is now running for more than 1 day stable. But the sync state is now still only at 69.58%. So for some reason it get’s really slow now. For me it looks like with that speed it will take ages again. Any advice how to speed it up, or is it normal behavior?

Kind Regards

Paddy