Mempool broken after update

Support and Troubleshooting
1

Hi all,

image
image1365×333 16.5 KB

My mempool app shows backend is syncing. I did successful reindex on the electrs. Here is what my mempool log shows:

api_1 | Dec 27 16:34:01 [205] WARN: runMainLoop error: Cannot fetch coinbase tx 078c7a26fbbc2975f17f82ba20a72d22151be2d071b6923335a28c7f2b819084. Reason: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions… Retrying in 60 sec.
api_1 | Dec 27 16:35:02 [205] ERR: Cannot fetch coinbase tx ee539325982ee0419e7fbd8338b64889e3548bec639d65805d742427d1f999b8. Reason: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions.
api_1 | Dec 27 16:35:02 [205] WARN: runMainLoop error: Cannot fetch coinbase tx ee539325982ee0419e7fbd8338b64889e3548bec639d65805d742427d1f999b8. Reason: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions… Retrying in 60 sec.
api_1 | Dec 27 16:36:09 [205] ERR: Cannot fetch coinbase tx ee539325982ee0419e7fbd8338b64889e3548bec639d65805d742427d1f999b8. Reason: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions.
api_1 | Dec 27 16:36:09 [205] WARN: runMainLoop error: Cannot fetch coinbase tx ee539325982ee0419e7fbd8338b64889e3548bec639d65805d742427d1f999b8. Reason: No such mempool transaction. Use -txindex or provide a block hash to enable blockchain transaction queries. Use gettransaction for wallet transactions… Retrying in 60 sec.

Transaction keep changing after I refresh the app and looks like are 1 block higher.

3 Likes
3

I had the same problem since I updated my Bitcoin Core to 24.0.1

I tried a manual restart of the mempool docker but this didn’t changed anything.

The mempool error log looked like this:
Attaching to mempool_web_1, mempool_mariadb_1, mempool_app_proxy_1, mempool_tor_server_1, mempool_api_1
api_1 | Dec 28 21:09:54 [117] WARN: runMainLoop error: Verifying blocks…. Retrying in 60 sec.
api_1 | Dec 28 21:11:03 [117] INFO: Connected to Electrum Server at 10.21.21.10:50001 ([“electrs/0.9.9”,“1.4”])
api_1 | Dec 28 21:11:08 [117] ERR: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
api_1 | Dec 28 21:11:08 [117] WARN: runMainLoop error: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions… Retrying in 60 sec.
api_1 | Dec 28 21:12:10 [117] ERR: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
api_1 | Dec 28 21:12:10 [117] WARN: runMainLoop error: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions… Retrying in 60 sec.
api_1 | Dec 28 21:13:13 [117] ERR: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
api_1 | Dec 28 21:13:13 [117] WARN: runMainLoop error: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions… Retrying in 60 sec.
api_1 | Dec 28 21:14:21 [117] ERR: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions.
api_1 | Dec 28 21:14:21 [117] WARN: runMainLoop error: Cannot fetch coinbase tx ed349eb94dfe7e90cff5c4144b1cb5c410343896bc4ae3d675e145e0b55ca39e. Reason: No such mempool transaction. Blockchain transactions are still in the process of being indexed. Use gettransaction for wallet transactions… Retrying in 60 sec.
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / -> http://10.21.21.26:3006
app_proxy_1 | Waiting for 10.21.21.26:3006 to open…
app_proxy_1 | mempool is now ready…
app_proxy_1 | Listening on port: 3006
app_proxy_1 | [HPM] Upgrading to WebSocket
app_proxy_1 | [HPM] Client disconnected

To me this looks like a cache problem so I restarted the whole Umbel instance. After a short sync period (like 10 minutes or so) everything is up and running again.

4

I have fixed my mempool problems by stopping the service and removing the mempool.dat file

6

I had this issue as well - It started working again after i set mempoolfullrbf off in advanced settings in Bitcoin Core.

7

hm for me the RBF setting was off by default.
i can recommend delete mempool and electrs!
reinstall electrs wait to sync than mempool should also work again.
because it’s necessary to be fully synced and working.

cheers

9

try to delete mempool again
than start Bitcoin Core, also electrs that’s its fully synced and running.
shutdown the node (restart)
try mempool again.

last option is to try reinstalling Bitcoin core
first you can also try to save the blocks that you don’t need to download again.

~/umbrel/app-data/bitcoin/data/bitcoin/blocks**

there is also a mempool.dat maybe you can replace because it’s broken

~/umbrel/app-data/bitcoin/data/bitcoin/mempool.dat

cheers

13

If anyone is having an issue with mempool after the recent Bitcoin Node 24.0.1 update, please go to advanced settings (accessed via the the three dots … in upper right corner of the app) and click ‘save and restart bitcoin node’. There is no need to change any of the settings for this to work. There was a bug in the 24.0.1 update that impacted some users by removing the txindex config option from their Bitcoin Node. Mempool (and some other apps) require txindex to operate properly. Clicking ‘save and restart bitcoin node’ will result in txindex being applied.

Please let me know if you still have issues!

3 Likes
14

I still have a strange issue. when ever I want to have a look at the details of a mined block. there is a issue with the mempool UI

Bildschirm­foto 2023-02-13 um 14.29.15
Bildschirm­foto 2023-02-13 um 14.29.152338×1560 188 KB

A complete restart, a reinstall of mempool and even a reinstall of electrs has noting changed :confused:

15

This fixed my issue.

16

One thing about this solution though. I’ve recently dealt with an issue where electrs would never finish syncing. I came across this thread Electrs stuck - reading app logs (and identifying docker processes) - #29 by LAN1 and in my case, deleting bitcoin.conf and restarting umbrel solved my problem.

Now, clicking ‘save and restart bitcoin node’ does fix the mempool issue, but then, electrs starts to fail again. If I do the fix for electrs once more, it solves electrs, but breaks mempool… problem loop :confused: