Hello! I am having trouble syncing my Bitcoin node on my Umbrel. Currently, my Bitcoin node status shows the following information:
Synchronization Progress: 0%
Number of Connections: 0 peers
Mempool Size: 0 Bytes
Hashrate: 0 H/s
Blockchain Size: 293 Bytes
I am new to using Umbrel and I have included my log file in this post, although I am not sure what it means. Unfortunately, since this is my first post on the Umbrel community, I cannot share any documents at the moment.
Also, I have noticed that most of the answers to similar problems are related to Raspberry Pi, and there is limited information available regarding this issue on Ubuntu.
=====================
= Umbrel debug info =
Umbrel version
0.5.3
Memory usage
total used free shared buff/cache available
Mem: 3,4G 1,8G 208M 372M 1,4G 1,0G
Swap: 4,5G 255M 4,2G
bitcoin: 11083194%
total: 52,2%
system: %
Memory monitor logs
2023-04-05 20:18:57 Memory monitor running!
2023-04-05 20:35:25 Memory monitor running!
2023-04-05 20:42:47 Memory monitor running!
2355 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2023-04-05 21:09:36 Memory monitor running!
Filesystem information
Filesystem Size Used Avail Use% Mounted on
/dev/sda3 219G 18G 191G 9% /
/dev/sdb1 932G 15G 917G 2% /media/moises/PortableSSD
Karen logs
Creating bitcoin_bitcoind_1 … done
Creating bitcoin_tor_1 …
Creating bitcoin_tor_1 … done
App: bitcoin - Generating Tor Hidden Service…
App: bitcoin - Hidden service file created successfully!
bitcoin_tor_1 is up-to-date
bitcoin_bitcoind_1 is up-to-date
Creating bitcoin_i2pd_daemon_1 …
Creating bitcoin_app_proxy_1 …
Creating bitcoin_server_1 …
Creating bitcoin_i2pd_daemon_1 … done
Creating bitcoin_server_1 … done
Creating bitcoin_app_proxy_1 … done
Saving app bitcoin in DB…
Successfully installed app bitcoin
karen is running in /media/moises/PortableSSD/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
karen is running in /media/moises/PortableSSD/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
2342 ? S 0:00 bash ./karen
2379 ? S 0:00 bash ./karen
karen is already running
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: debug
karen is getting triggered!
Debug result file generated
karen is running in /media/moises/PortableSSD/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./karen: line 75: /media/moises/PortableSSD/umbrel/events/triggers/: Is a directory
Got signal: change-password
karen is getting triggered!
This script must only be run on Umbrel OS
Got signal: debug
karen is getting triggered!
Docker containers
NAMES STATUS
bitcoin_server_1 Up 7 minutes
bitcoin_i2pd_daemon_1 Up 7 minutes
bitcoin_bitcoind_1 Up 7 minutes
bitcoin_app_proxy_1 Up 7 minutes
bitcoin_tor_1 Restarting (1) 43 seconds ago
nginx Up 7 minutes
dashboard Up 7 minutes
manager Up 7 minutes
auth Up 7 minutes
tor_proxy Up 7 minutes
Umbrel logs
Attaching to manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:27 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 06 Apr 2023 00:17:27 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:28 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:28 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:28 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 06 Apr 2023 00:17:28 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:29 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:29 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:29 GMT] “GET /v1/account/token?token=c6a68dd84058e6c26bb8b6e5a7a64d2f4ae7172194b44d343fa82c223363a0ff HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 06 Apr 2023 00:17:29 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
manager |
manager | umbrel-manager
Tor Proxy logs
Attaching to tor_proxy
tor_proxy | Apr 06 00:13:42.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor_proxy | Apr 06 00:13:42.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor_proxy | Apr 06 00:13:42.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor_proxy | Apr 06 00:13:42.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor_proxy | Apr 06 00:13:43.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
tor_proxy | Apr 06 00:13:44.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
tor_proxy | Apr 06 00:13:44.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
tor_proxy | Apr 06 00:13:45.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
tor_proxy | Apr 06 00:13:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6665, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
App logs
bitcoin
Attaching to bitcoin_server_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_tor_1
bitcoind_1 | 2023-04-06T00:17:05Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:08Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:11Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:15Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:18Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:21Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:24Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:27Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:30Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
bitcoind_1 | 2023-04-06T00:17:33Z connect() to 10.21.22.10:9050 failed after wait: Host is unreachable (113)
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
app_proxy_1 | Validating token: c6a68dd84058 …
i2pd_daemon_1 | 00:09:49@386/error - Tunnels: Can’t select next hop for W-DE6NZ~OUyRYvxMBobK2m5xatbYgx-BVay953zHg5k=
i2pd_daemon_1 | 00:09:49@386/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 00:09:49@386/error - Tunnels: Can’t select next hop for W-DE6NZ~OUyRYvxMBobK2m5xatbYgx-BVay953zHg5k=
i2pd_daemon_1 | 00:09:49@386/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 00:09:54@386/error - Tunnels: Can’t select next hop for W-DE6NZ~OUyRYvxMBobK2m5xatbYgx-BVay953zHg5k=
i2pd_daemon_1 | 00:09:54@386/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 00:09:54@386/error - Tunnels: Can’t select next hop for W-DE6NZ~OUyRYvxMBobK2m5xatbYgx-BVay953zHg5k=
i2pd_daemon_1 | 00:09:54@386/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 00:11:56@226/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 00:12:51@537/error - Garlic: Can’t handle ECIES-X25519-AEAD-Ratchet message
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:33 GMT] “GET /v1/bitcoind/info/connections HTTP/1.1” 304 - “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:33 GMT] “GET /v1/bitcoind/info/sync HTTP/1.1” 200 95 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Thu, 06 Apr 2023 00:17:33 GMT] “GET /v1/bitcoind/info/sync HTTP/1.1” 200 95 “-” “Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:109.0) Gecko/20100101 Firefox/110.0”
server_1 |
server_1 | umbrel-middleware
tor_1 | Apr 06 00:15:44.084 [warn] Failed to parse/validate config: Failed to configure rendezvous options. See logs for details.
tor_1 | Apr 06 00:15:44.084 [err] Reading config failed–see warnings above.
tor_1 | Apr 06 00:16:45.046 [notice] Tor 0.4.7.8 running on Linux with Libevent 2.1.12-stable, OpenSSL 1.1.1n, Zlib 1.2.11, Liblzma N/A, Libzstd N/A and Glibc 2.31 as libc.
tor_1 | Apr 06 00:16:45.046 [notice] Tor can’t help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
tor_1 | Apr 06 00:16:45.046 [notice] Read configuration file “/etc/tor/torrc”.
tor_1 | Apr 06 00:16:45.048 [warn] You have a ControlPort set to accept connections from a non-local address. This means that programs not running on your computer can reconfigure your Tor. That’s pretty bad, since the controller protocol isn’t encrypted! Maybe you should just listen on 127.0.0.1 and use a tool like stunnel or ssh to encrypt remote connections to your control port.
tor_1 | Apr 06 00:16:45.048 [warn] CookieAuthFileGroupReadable is set, but will have no effect: you must specify an explicit CookieAuthFile to have it group-readable.
tor_1 | Apr 06 00:16:45.048 [warn] Permissions on directory /data/app-bitcoin-p2p are too permissive.
tor_1 | Apr 06 00:16:45.048 [warn] Failed to parse/validate config: Failed to configure rendezvous options. See logs for details.
tor_1 | Apr 06 00:16:45.048 [err] Reading config failed–see warnings above.
==== Result ====
The debug script did not automatically detect any issues with your Umbrel.