Fresh install of Umbrel using Ubuntu 20.04 LTS.
Installation of Bitcoin Node, and completed full sync in 3 days.
Installed Electrs after bitcoin node fully synced.
It has been another 3 days since Electrs has been installed, showing the same thing…
I have tried restarting app in console. Still shows the same thing.
I’m sure more the one person is having the same issue, so how are we supposed to connect to a wallet?
Same issue here with electrs…Bitcoin node 100% synced, Electrum server ran through the inital sync in roughly 30-60min and since then in ““Waiting for Bitcoin Node to finish syncing” status. Used disc space of electrs is 66GB which should indicate a successful sync though
restart of the app or full system didn’t help so far.
Never mind, I’m running a pruned node.
first of all
report error …
secondly
and
check if the bitcoin.conf file exists in the following directory
/home/umbrel/umbrel/app-data/bitcoin/data/bitcoin
if the bitcoin.conf file exists, edit it, if not, create it with a default entry, e.g.
# Load additional configuration file, relative to the data directory.
the following entries must be commented out
# maxconnections=
# rpcuser=
# rpcpassword=
after creating the bitcoin.conf file a reboot must be done otherwise the .cookie file will not be created
thirdly
then wait for about 1-3h
it will work if you find the following entry
electrs_1 [date INFO electrs::db] finished full compaction
I get this in my error log on my Raspi4 (4GB), repeated again and again:
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | receiving on an empty and disconnected channel
electrs_1 | Starting electrs 0.10.1 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, 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.1)”, signet_magic: f9beb4d9, args: }
electrs_1 | [2023-11-17T14:21:37.794Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1 | [2023-11-17T14:21:37.794Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1 | [2023-11-17T14:21:38.302Z INFO electrs::db] “/data/db/bitcoin”: 2699 SST files, 0.002753771 GB, 0.000000202 Grows
electrs_1 | [2023-11-17T14:21:38.361Z INFO electrs::chain] loading 60 headers, tip=00000000c47a58b89434bd7c7af8334b366f713330dfb89119d67d79424d2cdf
electrs_1 | [2023-11-17T14:21:38.361Z INFO electrs::chain] chain updated: tip=00000000c47a58b89434bd7c7af8334b366f713330dfb89119d67d79424d2cdf, height=60
electrs_1 | [2023-11-17T14:21:38.513Z WARN electrs::p2p] failed to shutdown p2p connection: Transport endpoint is not connected (os error 107)
electrs_1 | [2023-11-17T14:21:38.514Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | receiving on an empty and disconnected channel
electrs_1 | Starting electrs 0.10.1 on aarch64 linux with Config { network: Bitcoin, db_path: “/data/db/bitcoin”, 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.1)”, signet_magic: f9beb4d9, args: }
electrs_1 | [2023-11-17T14:22:40.515Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1 | [2023-11-17T14:22:40.515Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1 | [2023-11-17T14:22:41.030Z INFO electrs::db] “/data/db/bitcoin”: 2700 SST files, 0.002754789 GB, 0.000000202 Grows
electrs_1 | [2023-11-17T14:22:41.078Z INFO electrs::chain] loading 60 headers, tip=00000000c47a58b89434bd7c7af8334b366f713330dfb89119d67d79424d2cdf
electrs_1 | [2023-11-17T14:22:41.079Z INFO electrs::chain] chain updated: tip=00000000c47a58b89434bd7c7af8334b366f713330dfb89119d67d79424d2cdf, height=60
electrs_1 | [2023-11-17T14:22:41.583Z WARN electrs::thread] p2p_recv thread failed: failed to recv a message from peer: IO error
electrs_1 | [2023-11-17T14:22:41.583Z WARN electrs::p2p] failed to shutdown p2p connection: Transport endpoint is not connected (os error 107)
electrs_1 | [2023-11-17T14:22:41.583Z INFO electrs::db] closing DB at /data/db/bitcoin
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | receiving on an empty and disconnected channel
intermittently, the following block appears:
app_1 | ::ffff:10.21.0.11 - - [Fri, 17 Nov 2023 14:20:55 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 500 2 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36”
app_1 |
app_1 | umbrel-middleware
app_1 | Electrum attempting reconnect…
app_1 | syncPercent error: Error: connect EHOSTUNREACH 10.21.21.10:50001
app_1 | at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1187:16) {
app_1 | errno: -113,
app_1 | code: ‘EHOSTUNREACH’,
app_1 | syscall: ‘connect’,
app_1 | address: ‘10.21.21.10’,
app_1 | port: 50001
app_1 | }
app_1 | ::ffff:10.21.0.11 - - [Fri, 17 Nov 2023 14:21:08 GMT] “GET /v1/electrs/syncPercent HTTP/1.1” 500 93 “-” “Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/118.0.0.0 Safari/537.36”
app_1 |
app_1 | umbrel-middleware
app_1 | Electrum attempting reconnect…
app_1 | Electrum attempting reconnect…
app_1 | syncPercent error: Error: connect EHOSTUNREACH 10.21.21.10:50001
did you find a solution to this problem? it appears i have the same issue
Same here… My node is pruned, I don’t know if it’s why but not so much information out there…
I have the same probleme, and the solution is on the log… Electrs not support pruned node…