search

dashpay / dash

Dash - Reinventing Cryptocurrency
https://www.dash.org
MIT License
1.49k stars 1.2k forks source link

Dash V.16.1 Http workqueue errors with MPOS #3891

Open ManageableIT opened 3 years ago

ManageableIT commented 3 years ago

Since update 16 the Linux daemon is terribly slow, i use MPOS with NOMP to accept mining. MPOS is not MNAuth compatible yet and uses rpc username and password. After updating to V16 when i start the node.js (stratum) everything turns really slow. every command i request with cli takes 6 minutes or longer and the debuglog is getting full of errors saying work queue depth exceeded. It takes 45 minutes to start the stratum (instead of 1 second) and everything is slow as hell.

2020-12-20 23:35:11.874010 Timeout downloading block * from peer=0, disconnecting 2020-12-20 23:35:11.874210 ThreadRPCServer method=getmininginfo 2020-12-20 23:35:11.874254 ThreadRPCServer method=getmininginfo 2020-12-20 23:35:11.874277 ThreadRPCServer method=getmininginfo 2020-12-20 23:35:11.874317 ThreadRPCServer method=getmininginfo 2020-12-20 23:35:11.874338 ThreadRPCServer method=validateaddress 2020-12-20 23:35:11.874356 ThreadRPCServer method=getdifficulty 2020-12-20 23:35:11.874508 ThreadRPCServer method=getdifficulty 2020-12-20 23:35:11.874534 ThreadRPCServer method=getmininginfo 2020-12-20 23:35:11.874563 ThreadRPCServer method=submitblock 2020-12-20 23:35:11.874658 ThreadRPCServer method=getblockchaininfo

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

2020-12-20 23:43:56.938144 Received a POST request for / from 127.0.0.1:47216 2020-12-20 23:43:56.938184 WARNING: request rejected because http work queue depth exceeded, it can be increased with the -rpcworkqueue= setting 2020-12-20 23:43:58.818049 ThreadRPCServer method=getnetworkinfo 2020-12-20 23:43:58.818156 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818182 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818194 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818214 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818219 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818236 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818241 ThreadRPCServer method=getdifficulty 2020-12-20 23:43:58.818256 ThreadRPCServer method=getmininginfo 2020-12-20 23:43:58.818262 ThreadRPCServer method=getmininginfo 2020-12-20 23:43:58.818307 ThreadRPCServer method=getmininginfo 2020-12-20 23:43:58.818343 ThreadRPCServer method=getmininginfo 2020-12-20 23:43:58.818410 ThreadRPCServer method=getmininginfo

is there any way to fix this issue, did i miss something?

ManageableIT commented 3 years ago

did some test, even with my workload higher (128) the rpc calls are terribly slow (7 minutes voor getblockchaininfo 49 minutes for starting stratum) somehow rpc user en password blow up HTTP server

ManageableIT commented 3 years ago

@UdjinM6 @codablock @PastaPastaPasta Do you guy's have any idea, i went through half the code still cannot find why http request hang on rpc calls

PastaPastaPasta commented 3 years ago

@ManageableIT does this issue still occur for you? I doesn't sound like anything I've experienced

ManageableIT commented 3 years ago

hey @PastaPastaPasta Yes it does, weirdly enough, we have tried so much things but still did not figure out why we get this sudden behavior

PastaPastaPasta commented 3 years ago

What version are you running? Have you upgraded to v17? What if you downgrade to v15 does that fix it?

ManageableIT commented 3 years ago

i tried it on V14, V15 en V16

PastaPastaPasta commented 3 years ago

Please try v17. Also, does downgrading fix the performance issue?