romanz / romanz/electrs

Bug: mempool sync failed: batch request failed

Open
#985 7 comments 2 reactions 1 assignee View on GitHub

@romanz is already working on this.

Since Jan 6, 2024.

bug
Dominant language
Rust
Stars
1.4k
Forks
561
Avg merge
2d 14h
Merged PRs (30d)
6

Description

Describe the bug
after updating to the newest version today electrs spits out a bunch of mempool sync failed: batch request failed warnings
one time after about 20 of them electrs exited, this could be unrelated, it said something like receiving on an unconnected channel (i lost that part of the log)

Electrs version
84c9a79cacc3cfb0131a75bd1d85f9bad27e6b45 (v0.10.2)

To Reproduce
Steps to reproduce the behavior:

  1. Configure and start electrs
  2. Connect with electrum client mempool (mempool.space local instance) server
  3. Wait
  4. See warnings (log level must be at least warn), maybe it exits

Expected behavior
not getting warnings that say something failed (mempool server does not use that part of electrs, mempool functions fine, including address lookup)

Configuration
no config file or env
Arguments: --log-filters DEBUG --db-dir /home/node/.bitcoin/electrs --electrum-rpc-addr=0.0.0.0:50002 --index-lookup-limit=500

System running electrs

  • Deployment method: manual
  • OS name and version: archlinux (uname -r: 6.1.69-1-lts)

Electrum client
Client name (if not upstream desktop Electrum) and version: mempool/mempool bf4a1fcd7ad04a9ec626e82b36668916a600bee9

Additional context
it happened just after updating 0.9.14

if it is not directly clear where this comes from i can set up a way to test the mempool sync part of electrs (i think using electrum wallet should be fine)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.