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

1

Hi,
I am in the process of syncing bitcoin core blocks but its been more than 8 days and i amuable to sync fully. It is going at snails pace.
I tried every thing to rempove this error"WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting"

Tried all rpcworkqueue options from 16 to 100 to 500.

I also have a windows bitcoin node in the same lan, i tried to to link it to my umbrel but it rarely sends data.

These are my settings
raspberry pi 5 8gb
1tb nvme pcie 3 x1 argon40 neo case
umbrel os
bitcoin core installed.

config settings:
rpcworkqueue=16
rpcthreads=50
rpcclienttimeout=600
dbcache=7000
maxconnections=60
server=1
rpcbind=192.168.200.189 : (umbrel os)
rpcallowip=192.168.200.233 :(windows with fully synced bitcoin core)
addnode=192.168.200.233
maxorphantx=10
maxmempool=300
maxorphantx=1
maxuploadtarget=250
externalip=192.168.200.189
listen=1

these are my windows bitcoin core config
txindex=1
prune=0
peerbloomfilters=1

server=1
listen=1
rpcallowip=127.0.0.1
rpcallowip=192.168.200.0/24
rpcuser=****
rpcpassword=****
bind=192.168.200.233
port=8333
externalip=192.168.200.233
discover=1
natpmp=1
rpcbind=192.168.200.233
addnode=192.168.200.189
whitelist=192.168.200.189
maxconnections=50
maxmempool=500
dbcache=8192
logips=1
rpcport=8332
maxuploadtarget=5000
rpcworkqueue=2000
rpcthreads=20

Any help would be appreciated.

2

Hmm, I wonder if the Pi just has too many resource limits to handle a high number of rpcthreads. Might be a pain but I’d maybe try to restart the sync and then try reducing the number of rpcthreads (to maybe something single digit). Also, try connecting directly to your node (connect: 192.168.200.233) instead of using addnode (see this: json rpc - What is the difference between the bitcoind command line options "addnode" and "connect"? - Bitcoin Stack Exchange).