Umbrel Bitcoin Node Sees Peers(Up to 10) but Stalls Syncing at 293 bytes

Support and Troubleshooting
1

I am trying to run a pruned node(yes I know they are slightly more limited, but it’s just not feasible to run that much storage space for me atm)

Things to note: I am on a Chromebook(yes it’s a bit odd, and I realize this may be the issue). I am using the Debian Debian, I believe it’s 11, but I could be wrong about this…I also have an Manjaro Device that is currently syncing to just a regular node via bitcoin core, but wouldn’t mind running this there too, as it has more functionality…

Anything you need me to get to figure out if there is even a solution to this let me know, I appreciate any help or advice!

Screenshot 2023-08-18 11.01.37 PM
Screenshot 2023-08-18 11.01.37 PM1363×606 47.8 KB

2

Hi @TheDeFiRaider, could you please run the following script from your command line and let us know the output

~/umbrel/scripts/app compose bitcoin logs --tail 100

General troubleshooting logs may also help if nothing stands out

sudo ~/umbrel/scripts/debug

3

~/umbrel/scripts/app compose electrs logs --tail 100 throws this

h4x0rman1@penguin:~$ ~/umbrel/scripts/app compose electrs logs --tail 100
cat: /home/h4x0rman1/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory
cat: /home/h4x0rman1/umbrel/app-data/electrs/umbrel-app.yml: No such file or directory

sudo ~/umbrel/scripts/debug

=====================
= Umbrel debug info =

Umbrel version

0.5.4

Memory usage

           total        used        free      shared  buff/cache   available

Mem: 2.8G 1.6G 176M 2.0M 1.0G 1.0G
Swap: 0B 0B 0B

total: 57.1%
system: 44.1%
bitcoin: 13%

Memory monitor logs

2023-08-18 22:54:43 Memory monitor running!
2356 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/vdb 20G 7.1G 13G 37% /
/dev/vdb 20G 7.1G 13G 37% /

Karen logs
Pulling server … extracting (27.6%)
Pulling server … extracting (36.5%)
sent 393 bytes received 28 bytes 842.00 bytes/sec
total size is 13,135 speedup is 31.20
Pulling server … extracting (99.0%)
Pulling bitcoind … done
Pulling server … done
Pulling i2pd_daemon … done
Pulling server … done
Pulling app_proxy … done
Starting app bitcoin…
Starting app bitcoin…
Executing hook: /home/h4x0rman1/umbrel/app-data/bitcoin/hooks/pre-start
Executing hook: /home/h4x0rman1/umbrel/app-data/bitcoin/hooks/pre-start
Creating bitcoin_bitcoind_1 …
Creating bitcoin_bitcoind_1 … error

ERROR: for bitcoin_bitcoind_1 Cannot create container for service bitcoind: Conflict. The container name “/bitcoin_bitcoind_1” is already in use by container “46cc79d653f0d85c9bf9cad7719327f760591ab9f46a992f456436f47918c96c”. You have to remove (or rename) that container to be able to reuse that name.

ERROR: for bitcoind Cannot create container for service bitcoind: Conflict. The container name “/bitcoin_bitcoind_1” is already in use by container “46cc79d653f0d85c9bf9cad7719327f760591ab9f46a992f456436f47918c96c”. You have to remove (or rename) that container to be able to reuse that name.
Creating bitcoin_bitcoind_1 … done
Creating bitcoin_tor_1 … done
bitcoin_tor_1 is up-to-date
App: bitcoin - Generating Tor Hidden Service…
App: bitcoin - Hidden service file created successfully!
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 …
bitcoin_bitcoind_1 is up-to-date
Creating bitcoin_i2pd_daemon_1 …
Creating bitcoin_i2pd_daemon_1 … error
Creating bitcoin_app_proxy_1 …
Creating bitcoin_server_1 …

ERROR: for bitcoin_i2pd_daemon_1 Cannot create container for service i2pd_daemon: Conflict. The container name “/bitcoin_i2pd_daemon_1” is already in use by container "18eb81cd592
Creating bitcoin_app_proxy_1 … errort container to be able to reuse that name.

ERROR: for bitcoin_app_proxy_1 Cannot create container for service app_proxy: Conflict. The container name “/bitcoin_app_proxy_1” is already in use by container “e2a0717a6e78f7176c78e00488a76e8c92024a6c9d7a3e3a61a45f8ac2f86ca0”. You have to remove (or rename) that cont
Creating bitcoin_server_1 … error

ERROR: for bitcoin_server_1 Cannot create container for service server: Conflict. The container name “/bitcoin_server_1” is already in use by container “0d85b25b3dd2d7b8a4978383336307ead7b22863807660f045fad6a07eb9d683”. You have to remove (or rename) that container to be able to reuse that name.

ERROR: for i2pd_daemon Cannot create container for service i2pd_daemon: Conflict. The container name “/bitcoin_i2pd_daemon_1” is already in use by container “18eb81cd59247aaae591695898aeb5bd2c38e1eefd2a80c1a42a5b5a38510667”. You have to remove (or rename) that container to be able to reuse that name.

ERROR: for app_proxy Cannot create container for service app_proxy: Conflict. The container name “/bitcoin_app_proxy_1” is already in use by container “e2a0717a6e78f7176c78e00488a76e8c92024a6c9d7a3e3a61a45f8ac2f86ca0”. You have to remove (or rename) that container to be able to reuse that name.

ERROR: for server Cannot create container for service server: Conflict. The container name “/bitcoin_server_1” is already in use by container "0d85b25b3dd2d7b8a4978383336307ead7b2
Creating bitcoin_i2pd_daemon_1 … done
Creating bitcoin_app_proxy_1 … done
Creating bitcoin_server_1 … done
Saving app bitcoin in DB…
Successfully installed app bitcoin

Docker containers

NAMES STATUS
bitcoin_server_1 Up 43 minutes
bitcoin_app_proxy_1 Up 43 minutes
bitcoin_i2pd_daemon_1 Up 43 minutes
bitcoin_tor_1 Up 43 minutes
bitcoin_bitcoind_1 Up 41 minutes
nginx Up 46 minutes
auth Up 46 minutes
manager Up 46 minutes
dashboard Up 51 minutes
tor_proxy Up 51 minutes

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:36 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:36 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:37 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:38 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:39 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:40 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:41 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:41 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:41 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:42 GMT] “GET /v1/account/token?token=383da92fadba7e6070d5a1e0859fcebd092316cbbb870e9c33b30e5248a391d5 HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Aug 19 03:51:09.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_proxy | Aug 19 03:51:10.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | Aug 19 03:51:10.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | Aug 19 03:51:10.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | Aug 19 03:51:10.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | Aug 19 03:51:10.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | Aug 19 03:51:13.000 [notice] Bootstrapped 100% (done): Done
tor_proxy | Aug 19 04:19:50.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_proxy | Aug 19 04:19:50.000 [notice] Our circuit 0 (id: 147) died due to an invalid selected path, purpose General-purpose client. This may be a torrc configuration issue, or a bug.
tor_proxy | Aug 19 04:35:06.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_app_proxy_1, bitcoin_i2pd_daemon_1, bitcoin_tor_1, bitcoin_bitcoind_1
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
app_proxy_1 | Validating token: 383da92fadba …
bitcoind_1 | 2023-08-19T04:00:44Z New outbound peer connected: version: 70016, blocks=803844, peer=13 (block-relay-only)
bitcoind_1 | 2023-08-19T04:00:45Z Pre-synchronizing blockheaders, height: 34000 (~4.54%)
bitcoind_1 | 2023-08-19T04:00:46Z Pre-synchronizing blockheaders, height: 36000 (~4.80%)
bitcoind_1 | 2023-08-19T04:00:48Z Pre-synchronizing blockheaders, height: 38000 (~5.07%)
bitcoind_1 | 2023-08-19T04:00:49Z New outbound peer connected: version: 70016, blocks=803844, peer=10 (outbound-full-relay)
bitcoind_1 | 2023-08-19T04:00:52Z Pre-synchronizing blockheaders, height: 40000 (~5.33%)
bitcoind_1 | 2023-08-19T04:00:54Z Pre-synchronizing blockheaders, height: 42000 (~5.59%)
bitcoind_1 | 2023-08-19T04:00:56Z Pre-synchronizing blockheaders, height: 44000 (~5.85%)
bitcoind_1 | 2023-08-19T04:01:55Z New outbound peer connected: version: 70016, blocks=803844, peer=14 (block-relay-only)
bitcoind_1 | 2023-08-19T04:32:16Z Potential stale tip detected, will try using extra outbound peer (last tip update: 1890 seconds ago)
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t select next hop for 2-R6lAJfBXJGmqGEUt04-sjGmDUzuzTc9EsxsDdHAQw=
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t select next hop for 2-R6lAJfBXJGmqGEUt04-sjGmDUzuzTc9EsxsDdHAQw=
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t select next hop for IM0WrPAJi0-hXWSmQhMI6BykDYsKcxExTDoYHsDDbdQ=
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t select next hop for 1PvGe0hyh5KYeGf8FMviYbkXvcUFn0cbtMuIuvXD5uE=
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t select next hop for 1PvGe0hyh5KYeGf8FMviYbkXvcUFn0cbtMuIuvXD5uE=
i2pd_daemon_1 | 04:41:54@86/error - Tunnels: Can’t create inbound tunnel, no peers available
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:41 GMT] “GET /v1/bitcoind/info/stats HTTP/1.1” 304 - “-” “Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:41 GMT] “GET /v1/bitcoind/info/connections HTTP/1.1” 304 - “-” “Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.2 - - [Sat, 19 Aug 2023 04:03:42 GMT] “GET /v1/bitcoind/info/sync HTTP/1.1” 200 123 “-” “Mozilla/5.0 (X11; CrOS x86_64 14541.0.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/115.0.0.0 Safari/537.36”
server_1 |
server_1 | umbrel-middleware
tor_1 | Aug 19 03:58:39.000 [notice] Bootstrapped 100% (done): Done
tor_1 | Aug 19 04:00:01.000 [notice] New control connection opened from 10.21.21.8.
tor_1 | Aug 19 04:07:59.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:07:59.000 [notice] Our circuit 0 (id: 172) died due to an invalid selected path, purpose Hidden service: Establishing introduction point. This may be a torrc configuration issue, or a bug.
tor_1 | Aug 19 04:14:32.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:20:49.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:23:46.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:29:17.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:33:47.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.
tor_1 | Aug 19 04:40:20.000 [notice] Failed to find node for hop #1 of our path. Discarding this circuit.

==== Result ====

==== END =====

4

Apologies I gave you the wrong script it should’ve been

~/umbrel/scripts/app compose bitcoin logs --tail 100

Anyway I can see a couple potential issues here.
Firstly, is this running on a VM or directly on the Chromebook? Either is fine, but I’m noticing that only 20GB is allocated to this instance, so I just wanted to confirm you intend to prune the chain enough to fit within that?
It looks like the bitcoin app might have had a bad install, I would uninstall it from the web GUI or cli, and then reinstall using the following command, then set-up the pruning settings again

sudo ~/umbrel/scripts/app install bitcoin

5

Yes its a VM, its a feature that comes with the device to enable a containerized Linux installation. Also yes I planned to keep it as small as needed to function effectively which to my knowledge pruning doesn’t lower security, just limitations on your nodes abilities to draw back history paste pruned blocks no?

6

h4x0rman1@penguin:~$ ~/umbrel/scripts/app compose bitcoin logs --tail 100
ERROR: Couldn’t connect to Docker daemon at http+docker://localhost - is it running?

If it’s at a non-standard location, specify the URL with the DOCKER_HOST environment variable.

Now this is what I get with that O.o

Also the reinstall bit doesn’t seem to have fixed it…I do appreciate the assistance thus far though. Thank you. :slight_smile:

7

Interesting, I’m not sure why there would be a conflicting container.
We could try removing it, but first, did you run ‘sudo apt update’ & ‘sudo apt upgrade’ before installing Umbrel on the VM?

8

Well…it seems like leaving it running overnight fixed it…maybe it was just taking extra long to sync block headers? Idk either way, your help was definitely good sorry for wasting any of your time, it just didn’t seem to say what it was doing/I wasn’t sure how to see.

1 Like
9

Good to hear!