I have Umbrel OS 1.2.2 running on a Raspberry Pi 5 and bitcoin node is 100% synced.
However, Electrum appears to be dead - no CPU and it just says “Waiting for bitcoin node to finish syncing” - there’s no progress indicated. I’ve waited the 24 hours that people recommend - no dice.
Can someone help me out here? What is going on with Electrum in this context? I have tried restarting and reinstalling a few times.
Here’s the 4 electrum docker containers:
umbrel@umbrel:~/umbrel$ sudo docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
8a191e07a19b getumbrel/umbrel-electrs:v1.0.2 “docker-entrypoint.s…” 3 minutes ago Up 3 minutes 3006/tcp electrs_app_1
d4662d127e27 getumbrel/app-proxy:1.0.0 “docker-entrypoint.s…” 3 minutes ago Up 3 minutes 0.0.0.0:2102->2102/tcp, :::2102->2102/tcp electrs_app_proxy_1
2a9f90fd3169 getumbrel/electrs:v0.10.6 “electrs” 3 minutes ago Restarting (1) 28 seconds ago electrs_electrs_1
d24473439bed getumbrel/tor:0.4.7.8 “tor” 3 minutes ago Up 3 minutes electrs_tor_1
And here’s the error I’m getting for this one (2a9f90fd3169 getumbrel/electrs:v0.10.6):
umbrel@umbrel:~/umbrel$ sudo docker logs 2a9f90fd3169 | tail -50
Starting electrs 0.10.6 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, db_log_dir: None, daemon_dir: “/data/.bitcoin”, daemon_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon_rpc_addr: 10.21.21.8:8332, daemon_p2p_addr: 10.21.21.8:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: “Umbrel Electrs (0.10.6)”, signet_magic: f9beb4d9 }
[2024-11-16T11:34:01.039Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
[2024-11-16T11:34:01.039Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
[2024-11-16T11:34:01.103Z INFO electrs::db] “/data/db/bitcoin”: 99 SST files, 0.00010076 GB, 0.000000021 Grows
[2024-11-16T11:34:01.119Z WARN electrs::thread] p2p_recv thread failed: failed to recv a message from peer: IO error
[2024-11-16T11:34:01.120Z INFO electrs::db] closing DB at /data/db/bitcoin
[2024-11-16T11:34:01.120Z WARN electrs::p2p] failed to shutdown p2p connection: Transport endpoint is not connected (os error 107)
Error: electrs failed
Caused by:
receiving on an empty and disconnected channel
Starting electrs 0.10.6 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, db_log_dir: None, daemon_dir: “/data/.bitcoin”, daemon_auth: CookieFile(“/data/.bitcoin/.cookie”), daemon_rpc_addr: 10.21.21.8:8332, daemon_p2p_addr: 10.21.21.8:8333, electrum_rpc_addr: 0.0.0.0:50001, monitoring_addr: 127.0.0.1:4224, wait_duration: 10s, jsonrpc_timeout: 15s, index_batch_size: 10, index_lookup_limit: None, reindex_last_blocks: 0, auto_reindex: true, ignore_mempool: false, sync_once: false, skip_block_download_wait: false, disable_electrum_rpc: false, server_banner: “Umbrel Electrs (0.10.6)”, signet_magic: f9beb4d9 }
[2024-11-16T11:34:01.777Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
[2024-11-16T11:34:01.777Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
[2024-11-16T11:34:01.825Z INFO electrs::db] “/data/db/bitcoin”: 100 SST files, 0.000101778 GB, 0.000000021 Grows
[2024-11-16T11:34:01.840Z INFO electrs::db] closing DB at /data/db/bitcoin
[2024-11-16T11:34:01.840Z WARN electrs::p2p] failed to shutdown p2p connection: Transport endpoint is not connected (os error 107)
Error: electrs failed
This appears to be failing repeatedly.