Rpc work Queue Exceeded
Rpc work Queue Exceeded
Loading saved threads...
Abbeville · External communityPost link
External question — Bitcoin Stack Exchange
Author: Abbeville
Original post: https://bitcoin.stackexchange.com/questions/117044
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
I am trying to make rpc calls to an Rpc Interface "listunspent". So i get this Error: ESOCKETTIMEDOUT. I checked the bitcoin node debug file and saw the error message "Depth queue work exceeded". I have added this option rpcworkqueue= settings to the bitcoin.conf file.
Here is my bitcoin.conf file
prune=550 port=8333 rpcworkqueue=1000 rpcuser=user rpcpassword=userpass zmqpubrawblock=tcp://127.0.0.1:29000 zmqpubrawtx=tcp://127.0.0.1:29000 zmqpubhashtx=tcp://127.0.0.1:29000 zmqpubhashblock=tcp://127.0.0.1:29000
The following is the error response i get while trying to make rpc calls from my node app
{
"status": 500,
"error": {
"name": "RequestError",
"message": "Error: ESOCKETTIMEDOUT",
"cause": {
"code": "ESOCKETTIMEDOUT",
"connect": false
},
"error": {
"code": "ESOCKETTIMEDOUT",
"connect": false
},
"options": {
"auth": {
"user": "user",
"pass": "userpass"
},
"uri": "/",
"baseUrl": "http://127.0.0.1:8332",
"timeout": 30,
"json": true,
"body": {
"method": "listunspent",
"params": {},
"jsonrpc": 1,
"id": "rpc-bitcoin"
},
"method": "POST",
"simple": true,
"resolveWithFullResponse": false,
"transform2xxOnly": false
}
}
}
Any help to solve this?
Quote
Report
Geremia · External communityPost link
External answer — Bitcoin Stack Exchange
Author: Geremia
Original post: https://bitcoin.stackexchange.com/a/122800
License: CC BY-SA 4.0 — https://creativecommons.org/licenses/by-sa/4.0/
Adaptation: HTML converted to plain text; contact email addresses removed.
Something is trying to make too many simultaneous RPC requests.
Running parallel jobs making RPC requests, I've noticed that only 2 requests can be made simultaneously for certain things, and even then it occasionally threw
error: Server response: Work queue depth exceeded
.
Quote
Report
Post Reply
Checking account access…