electrs: Bug: getmempoolentry RPC error
Ive been using Electrum + electrs as a PoS for a online business of mine so I get a lot of txs though it. For some reason when I load electrum it no longer syncs to my electrs server.
When I open the electrs logs it shows a long list of the following error DEBUG - no mempool entry 8322da89e0fe37ee108d74c0f6a0d650b92540793f4ca380065cafda12fd4202: getmempoolentry RPC error: {"code":-5,"message":"Transaction not in mempool"}
It shows a bunch of errors like this with different TXIDs but none of the IDs seem to be valid when entered into a block explorer.
Im running electrs through the latest Umbrel 0.3.2 release.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 21 (10 by maintainers)
I have tons of this messages in my log during each startup of electrs on my raspberry pi. The startup takes a very long time, usually 30 minutes or more. Electrum client won’t sync during the startup time either and I think it is related to the “Transaction not in mempool” messages. I checked the transactions and they are in fact no longer in mempool but already mined in recent blocks. Even if the time between shutdown and restart of electrs is only 1-2 minutes, I get this behavior, so I think it somehow has an old version of the mempool, Is there any configuration possibility to avoid this scenario?
It has only happened once so far, it has cleared up now and I am able to sync my wallet again.
I have since increased
-mempoolexpiryand-maxmempoollimits in bitcoin.conf in hopes to mitigate the problem.@ascisco try bumping mempool size
@lukechilds thanks for info! My progress is still slow sadly, too much other stuff to do. 😦