Stuck at "starting umbrel"

Support and Troubleshooting
1

yesterday i got a notification that my node became unavailable. This happens ones in a while. Normally after a few minutes i get a second notification saying my node became available again. This time i didnt get that message. So i took off the power of my Rasberry pi. Stupid i know.

Now my node won’t start. It is stuck at “starting Umbrel”. I can’t get acces through ssh!

Can someone help me? Can it be restored? If not, do i need a clean install en how do i get my funds and lightning channels back?

2

Hi @Liel- sorry to hear that.
Just to clarify, you don’t have a screen that has a white-background and an error, with the option to restart, you only have the normal Umbrel background with ‘starting Umbrel’ in the center?

Also, when you say you can’t SSH into your Umbrel- what command are you using?
You should be able to SSH into your instance if the web dashboard is partly online. It could be worth scanning your network with angryip.org, or with using the tailscale IP if you have that set-up, to try SSHing into your Umbrel with ssh umbrel@<IP_address>

3

Hi @smolgrrr - thanks so much for your help.
Umbrel is stuck with only “starting Umbrel” in the center. A few days ago there was an option to push “reboot” or " restart". Ofcourse i pushed “reboot” but nothing hapened.

I use “ssh umbrel@umbrel.local”. I am then asked to give my password. After that nothing happens.
I also tried your "ssh umbrel@<ip_adress>. I think i found the right ip because it asks me my password. After a while i get the prompt “Connection closed by<ip_adress>”

Do you have any idea?

4

maybe it’s best to Re-flashing the microSD?

5

Ah unfortunate- yes that sounds like it may be a bad start-up, so as you say, reflashing the microSD and rebooting is the best approach here.
Please let me know how that goes.

6

Re-flashed my microSD and everyting works like a charm! After restart my node started synchronising the missing blocks. After that all my lightning channels started opening. Now everything is back to normal!

I would like to give a shout out to Umbrel! Job very well done!! I love it when my stupid mistakes are solved by great working software!

And thanks to @smolgrrr for helping me get on the right track

2 Likes
7

Great to hear, and thank you for the kind words :slight_smile:
Have a nice week!

8

Hi, sorry to bother you but I have a similar problem but when I reflash, nothing happens: Starting New Services, Running Migrations, or Stuck Starting/Failed Update Screen - #2 by Renanean

9

Maybe @smolgrrr can help you?

10

Can someone look at my logs and advise I have ttried everything, the problem umbrel starts and then stops.
I bought a new sd card but still the same sometimes the sd warnig comes up sometimes not???

= Umbrel debug info =

Umbrel version

0.5.4

Flashed OS version

v0.5.4-patch-1

Raspberry Pi Model

Revision : d03114
Serial : 10000000a42697ff
Model : Raspberry Pi 4 Model B Rev 1.4

Firmware

May 9 2023 12:16:34
Copyright (c) 2012 Broadcom
version 30aa0d70ab280427ba04ebc718c81d4350b9d394 (clean) (release) (start)

Temperature

temp=44.3’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 1.0G 5.8G 10M 991M 6.6G
Swap: 4.1G 0B 4.1G

total: 13.3%
bitcoin: 4.5%
lightning: 4.2%
mempool: 3.8%
electrs: 3.2%
system: 0%

Memory monitor logs

2024-03-03 10:20:50 Memory monitor running!
2024-03-03 19:49:26 Memory monitor running!
2024-03-04 08:54:13 Memory monitor running!
2024-03-04 15:10:40 Memory monitor running!
2024-03-04 16:41:49 Memory monitor running!
2024-03-04 18:20:24 Memory monitor running!
2024-03-04 19:24:26 Memory monitor running!
2024-03-04 19:39:20 Memory monitor running!
2024-03-04 19:50:05 Memory monitor running!
2024-03-04 20:02:08 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 60G 4.1G 53G 8% /
/dev/sda1 916G 371G 499G 43% /home/umbrel/umbrel

Startup service logs

Mar 04 20:02:22 umbrel umbrel startup[1742]: Creating bitcoin_bitcoind_1 …
Mar 04 20:02:23 umbrel umbrel startup[1742]: Creating electrs_app_proxy_1 …
Mar 04 20:02:23 umbrel umbrel startup[1742]: Creating bitcoin_i2pd_daemon_1 …
Mar 04 20:02:23 umbrel umbrel startup[1742]: Creating mempool_mariadb_1 …
Mar 04 20:02:24 umbrel umbrel startup[1742]: Creating mempool_web_1 …
Mar 04 20:02:24 umbrel umbrel startup[1742]: Creating mempool_app_proxy_1 …
Mar 04 20:02:24 umbrel umbrel startup[1742]: Creating mempool_api_1 …
Mar 04 20:02:25 umbrel umbrel startup[1742]: Creating lightning_tor_1 … done
Mar 04 20:02:28 umbrel umbrel startup[1742]: Creating bitcoin_tor_1 … done
Mar 04 20:02:28 umbrel umbrel startup[1742]: Creating electrs_tor_1 … done
Mar 04 20:02:28 umbrel umbrel startup[1742]: Creating lightning_app_1 … done
Mar 04 20:02:28 umbrel umbrel startup[1742]: Creating mempool_mariadb_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating bitcoin_i2pd_daemon_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating mempool_web_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating electrs_app_proxy_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating lightning_app_proxy_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating electrs_electrs_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating electrs_app_1 …
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating mempool_api_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating bitcoin_bitcoind_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating bitcoin_server_1 …
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating bitcoin_app_proxy_1 … done
Mar 04 20:02:29 umbrel umbrel startup[1742]: Creating mempool_app_proxy_1 … done
Mar 04 20:02:30 umbrel umbrel startup[1742]: Creating lightning_lnd_1 … done
Mar 04 20:02:34 umbrel umbrel startup[1742]: Creating bitcoin_server_1 … done
Mar 04 20:02:34 umbrel umbrel startup[1742]: Creating electrs_app_1 … done
Mar 04 20:02:35 umbrel umbrel startup[1742]: Umbrel is now accessible at
Mar 04 20:02:35 umbrel umbrel startup[1742]: http://umbrel.local
Mar 04 20:02:35 umbrel umbrel startup[1742]: http://192.168.0.243
Mar 04 20:02:35 umbrel systemd[1]: Started Umbrel Startup Service.

External storage service logs

Mar 04 20:01:54 umbrel external storage mounter[508]: Waiting for USB devices…
Mar 04 20:01:55 umbrel external storage mounter[508]: Checking if the device is ext4…
Mar 04 20:01:55 umbrel external storage mounter[508]: Yes, it is ext4
Mar 04 20:01:55 umbrel external storage mounter[508]: Checking filesystem for corruption…
Mar 04 20:01:55 umbrel external storage mounter[508]: e2fsck 1.44.5 (15-Dec-2018)
Mar 04 20:01:55 umbrel external storage mounter[508]: umbrel: recovering journal
Mar 04 20:01:58 umbrel external storage mounter[508]: Clearing orphaned inode 27918795 (uid=1000, gid=1000, mode=0100600, size=0)
Mar 04 20:01:58 umbrel external storage mounter[508]: Clearing orphaned inode 27918794 (uid=1000, gid=1000, mode=0100600, size=0)
Mar 04 20:01:58 umbrel external storage mounter[508]: Clearing orphaned inode 27918793 (uid=1000, gid=1000, mode=0100600, size=0)
Mar 04 20:01:58 umbrel external storage mounter[508]: Clearing orphaned inode 27918742 (uid=1000, gid=1000, mode=0100600, size=0)
Mar 04 20:01:58 umbrel external storage mounter[508]: Setting free inodes count to 60783181 (was 60783322)
Mar 04 20:01:58 umbrel external storage mounter[508]: Setting free blocks count to 142862140 (was 142861779)
Mar 04 20:01:58 umbrel external storage mounter[508]: umbrel: clean, 271795/61054976 files, 101328068/244190208 blocks
Mar 04 20:01:58 umbrel external storage mounter[508]: Mounting partition…
Mar 04 20:01:58 umbrel external storage mounter[508]: Checking if device contains an Umbrel install…
Mar 04 20:01:58 umbrel external storage mounter[508]: Yes, it contains an Umbrel install
Mar 04 20:01:58 umbrel external storage mounter[508]: Bind mounting external storage over local Umbrel installation…
Mar 04 20:01:58 umbrel external storage mounter[508]: Bind mounting external storage over local Docker data dir…
Mar 04 20:01:58 umbrel external storage mounter[508]: Bind mounting external storage to /swap
Mar 04 20:01:58 umbrel external storage mounter[508]: Bind mounting SD card root at /sd-card…
Mar 04 20:01:58 umbrel external storage mounter[508]: Checking Umbrel root is now on external storage…
Mar 04 20:01:59 umbrel external storage mounter[508]: Checking /var/lib/docker is now on external storage…
Mar 04 20:01:59 umbrel external storage mounter[508]: Checking /swap is now on external storage…
Mar 04 20:01:59 umbrel external storage mounter[508]: Setting up swapfile
Mar 04 20:01:59 umbrel external storage mounter[508]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
Mar 04 20:01:59 umbrel external storage mounter[508]: no label, UUID=f69eef55-f2b2-47e8-afa8-2ecfdc53ef7c
Mar 04 20:01:59 umbrel external storage mounter[508]: Checking SD Card root is bind mounted at /sd-root…
Mar 04 20:01:59 umbrel external storage mounter[508]: Starting external drive mount monitor…
Mar 04 20:01:59 umbrel external storage mounter[508]: Mount script completed successfully!
Mar 04 20:01:59 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Mon 2024-03-04 20:01:46 UTC, end at Mon 2024-03-04 20:02:50 UTC. –
Mar 04 20:02:07 umbrel systemd[1]: Starting External Storage SDcard Updater…
Mar 04 20:02:07 umbrel external storage updater[1665]: Checking if SD card Umbrel is newer than external storage…
Mar 04 20:02:07 umbrel external storage updater[1665]: No, SD version is not newer, exiting.
Mar 04 20:02:07 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: debug
karen is getting triggered!
Debug result file generated
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
Got signal:
karen is getting triggered!
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
./karen: line 75: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
bitcoin_server_1 Up 20 seconds
electrs_app_1 Up 20 seconds
mempool_api_1 Up 25 seconds
mempool_app_proxy_1 Up 25 seconds
mempool_web_1 Up 25 seconds
mempool_mariadb_1 Up 26 seconds
bitcoin_i2pd_daemon_1 Up 25 seconds
bitcoin_bitcoind_1 Up 25 seconds
bitcoin_app_proxy_1 Up 25 seconds
bitcoin_tor_1 Up 26 seconds
electrs_electrs_1 Up 20 seconds
electrs_app_proxy_1 Up 25 seconds
electrs_tor_1 Up 26 seconds
lightning_lnd_1 Up 24 seconds
lightning_app_proxy_1 Up 25 seconds
lightning_tor_1 Up 28 seconds
lightning_app_1 Up 26 seconds
nginx Up 39 seconds
auth Up 41 seconds
dashboard Up 41 seconds
manager Up 40 seconds
tor_proxy Up 41 seconds

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:54 GMT] “GET /v1/system/info HTTP/1.0” 200 671 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:54 GMT] “GET /v1/system/uptime HTTP/1.0” 200 2 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:54 GMT] “GET /v1/system/remote-tor-access-status HTTP/1.0” 200 35 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:55 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:55 GMT] “GET /v1/apps?installed=1 HTTP/1.0” 200 8218 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:55 GMT] “GET /v1/apps HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:55 GMT] “POST /v1/system/debug HTTP/1.0” 200 17 “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:56 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.0.6 - - [Mon, 04 Mar 2024 20:02:56 GMT] “GET /v1/account/token?token=7215c7d246f42f5c18dd55eb2876da3b421d3778af39052c250f6140a2251f4f HTTP/1.1” 200 16 “-” “app-proxy/0.0.1”
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Mon, 04 Mar 2024 20:02:56 GMT] “GET /v1/system/debug-result HTTP/1.0” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Mar 04 20:02:22.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_proxy | Mar 04 20:02:23.000 [notice] Bootstrapped 62% (loading_descriptors): Loading relay descriptors
tor_proxy | Mar 04 20:02:24.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | Mar 04 20:02:25.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | Mar 04 20:02:26.000 [notice] Bootstrapped 100% (done): Done

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_tor_1
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
app_proxy_1 | Validating token: 7215c7d246f4 …
bitcoind_1 | 2024-03-04T20:02:35Z * Using 53.4 MiB for transaction index database
bitcoind_1 | 2024-03-04T20:02:35Z * Using 46.7 MiB for basic block filter index database
bitcoind_1 | 2024-03-04T20:02:35Z * Using 8.0 MiB for chain state database
bitcoind_1 | 2024-03-04T20:02:35Z * Using 318.9 MiB for in-memory UTXO set (plus up to 286.1 MiB of unused mempool space)
bitcoind_1 | 2024-03-04T20:02:35Z init message: Loading block index…
bitcoind_1 | 2024-03-04T20:02:35Z Assuming ancestors of block 00000000000000000001a0a448d6cf2546b06801389cc030b2b18c6491266815 have valid signatures.
bitcoind_1 | 2024-03-04T20:02:35Z Setting nMinimumChainWork=000000000000000000000000000000000000000052b2559353df4117b7348b64
bitcoind_1 | 2024-03-04T20:02:35Z Opening LevelDB in /data/.bitcoin/blocks/index
bitcoind_1 | 2024-03-04T20:02:36Z Opened LevelDB successfully
bitcoind_1 | 2024-03-04T20:02:36Z Using obfuscation key for /data/.bitcoin/blocks/index: 0000000000000000
i2pd_daemon_1 | 20:02:37@637/error - Tunnels: Can’t select next hop for v2EO4OTULNiHewekrkaj2S-ILfv6A7~LH9V5jDULnqk=
i2pd_daemon_1 | 20:02:37@637/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 20:02:46@637/error - Tunnels: Can’t select next hop for v2EO4OTULNiHewekrkaj2S-ILfv6A7~LH9V5jDULnqk=
i2pd_daemon_1 | 20:02:46@637/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 20:02:51@637/error - Tunnels: Can’t select next hop for 7IiQsIYaSij9o-DQnqe5cs-ntsIbJnnFdeyI1jkshII=
i2pd_daemon_1 | 20:02:51@637/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 20:03:14@637/error - Tunnels: Can’t select next hop for 150DYw09w5sC301-QT3E5Hcfwa-23~d9poRwtXjd~N4=
i2pd_daemon_1 | 20:03:14@637/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 20:03:14@637/error - Tunnels: Can’t select next hop for baTsVpUfED3JnEQptoH4U-uza4NpMa6i8EHKoWo2rFQ=
i2pd_daemon_1 | 20:03:14@637/error - Tunnels: Can’t create inbound tunnel, no peers available
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Mon, 04 Mar 2024 20:03:00 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Mon, 04 Mar 2024 20:03:14 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Mon, 04 Mar 2024 20:03:15 GMT] “GET /v1/bitcoind/info/status HTTP/1.1” 304 - “-” “Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:123.0) Gecko/20100101 Firefox/123.0”
server_1 |
server_1 | umbrel-middleware
tor_1 | Mar 04 20:02:52.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:52.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:53.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:53.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Mar 04 20:02:53.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Mar 04 20:02:54.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Mar 04 20:02:54.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Mar 04 20:02:54.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Mar 04 20:02:54.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Mar 04 20:02:54.000 [notice] Bootstrapped 100% (done): Done

electrs

Attaching to electrs_app_1, electrs_electrs_1, electrs_app_proxy_1, electrs_tor_1
app_1 | > umbrel-electrs@1.0.1 dev:backend
app_1 | > npm run start -w umbrel-electrs-backend
app_1 |
app_1 |
app_1 | > umbrel-electrs-backend@0.1.12 start
app_1 | > node ./bin/www
app_1 |
app_1 | Mon, 04 Mar 2024 20:02:52 GMT morgan deprecated morgan(options): use morgan(“default”, options) instead at app.js:28:9
app_1 | Mon, 04 Mar 2024 20:02:52 GMT morgan deprecated default format: use combined format at app.js:28:9
app_1 | Listening on port 3006
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.4:3006
app_proxy_1 | Waiting for 10.21.22.4:3006 to open…
app_proxy_1 | Electrs is now ready…
app_proxy_1 | Listening on port: 2102
tor_1 | Mar 04 20:02:47.000 [notice] Bootstrapped 56% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:48.000 [notice] Bootstrapped 61% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:48.000 [notice] Bootstrapped 70% (loading_descriptors): Loading relay descriptors
tor_1 | Mar 04 20:02:49.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_1 | Mar 04 20:02:49.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_1 | Mar 04 20:02:49.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Mar 04 20:02:50.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Mar 04 20:02:50.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Mar 04 20:02:50.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Mar 04 20:02:50.000 [notice] Bootstrapped 100% (done): Done
electrs_1 | Error: electrs failed
electrs_1 |
electrs_1 | Caused by:
electrs_1 | 0: bitcoind RPC polling failed
electrs_1 | 1: daemon not available
electrs_1 | 2: JSON-RPC error: transport error: Couldn’t connect to host: Connection refused (os error 111)
electrs_1 | Starting electrs 0.10.2 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.2)”, signet_magic: f9beb4d9, args: }
electrs_1 | [2024-03-04T20:02:34.757Z INFO electrs::metrics::metrics_impl] serving Prometheus metrics on 127.0.0.1:4224
electrs_1 | [2024-03-04T20:02:34.769Z INFO electrs::server] serving Electrum RPC on 0.0.0.0:50001
electrs_1 | [2024-03-04T20:02:35.252Z INFO electrs::db] “/data/db/bitcoin”: 363 SST files, 0.000369512 GB, 0.000000021 Grows

lightning

Attaching to lightning_lnd_1, lightning_app_proxy_1, lightning_tor_1, lightning_app_1
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_1 | Checking LND status…
app_1 | Waiting for LND…
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.22.3:3006
app_proxy_1 | Waiting for 10.21.22.3:3006 to open…
app_proxy_1 | Lightning Node is now ready…
app_proxy_1 | Listening on port: 2101
lnd_1 | 2024-03-04 20:02:32.768 [INF] LTND: Opening the main database, this might take a few minutes…
lnd_1 | 2024-03-04 20:02:32.768 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd_1 | 2024-03-04 20:02:32.938 [INF] LTND: Creating local graph and channel state DB instances
lnd_1 | 2024-03-04 20:02:33.177 [INF] CHDB: Checking for schema update: latest_version=31, db_version=31
lnd_1 | 2024-03-04 20:02:33.177 [INF] CHDB: Checking for optional update: prune_revocation_log=false, db_version=empty
lnd_1 | 2024-03-04 20:02:33.177 [INF] LTND: Database(s) now open (time_to_open=408.918315ms)!
lnd_1 | 2024-03-04 20:02:33.177 [INF] LTND: We’re not running within systemd or the service type is not ‘notify’
lnd_1 | 2024-03-04 20:02:33.178 [INF] LTND: Waiting for wallet encryption password. Use lncli create to create a wallet, lncli unlock to unlock an existing wallet, or lncli changepassword to change the password of an existing wallet and unlock it.
lnd_1 | 2024-03-04 20:02:49.967 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access
lnd_1 | 2024-03-04 20:02:50.004 [ERR] RPCS: [/lnrpc.Lightning/DescribeGraph]: wallet locked, unlock it to enable full RPC access
tor_1 | Mar 04 20:02:25.946 [notice] Opened Socks listener connection (ready) on 127.0.0.1:9050
tor_1 | Mar 04 20:02:26.000 [notice] Bootstrapped 0% (starting): Starting
tor_1 | Mar 04 20:02:26.000 [notice] Starting with guard context “default”
tor_1 | Mar 04 20:02:27.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor_1 | Mar 04 20:02:29.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor_1 | Mar 04 20:02:29.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor_1 | Mar 04 20:02:43.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor_1 | Mar 04 20:02:43.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor_1 | Mar 04 20:02:43.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor_1 | Mar 04 20:02:43.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus

mempool

Attaching to mempool_api_1, mempool_app_proxy_1, mempool_web_1, mempool_mariadb_1
mariadb_1 | 2024-03-04 20:02:32 0 [Note] Plugin ‘FEEDBACK’ is disabled.
mariadb_1 | 2024-03-04 20:02:33 0 [Note] Server socket created on IP: ‘::’.
mariadb_1 | 2024-03-04 20:02:33 0 [Warning] ‘proxies_priv’ entry ‘@% root@406a3a869823’ ignored in --skip-name-resolve mode.
mariadb_1 | 2024-03-04 20:02:33 0 [Note] InnoDB: Buffer pool(s) load completed at 240304 20:02:33
mariadb_1 | 2024-03-04 20:02:33 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2024-03-04 20:02:33 0 [Note] Added new Master_info ‘’ to hash table
mariadb_1 | 2024-03-04 20:02:33 0 [Note] mysqld: ready for connections.
mariadb_1 | Version: ‘10.5.12-MariaDB-1:10.5.12+maria~focal’ socket: ‘/run/mysqld/mysqld.sock’ port: 3306 mariadb.org binary distribution
mariadb_1 | 2024-03-04 20:02:33 3 [Warning] Aborted connection 3 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.26’ (This connection closed normally without authentication)
mariadb_1 | 2024-03-04 20:02:33 4 [Warning] Aborted connection 4 to db: ‘unconnected’ user: ‘unauthenticated’ host: ‘10.21.21.27’ (This connection closed normally without authentication)
api_1 | at processTicksAndRejections (node:internal/process/task_queues:83:21)
api_1 | Mar 4 20:02:56 [116] INFO: [Mining] Fetching daily price history from exchanges and saving missing ones into the database
api_1 | Mar 4 20:02:59 [116] INFO: [Mining] Fetching hourly price history from exchanges and saving missing ones into the database
api_1 | Mar 4 20:03:18 [116] WARN: Exception in runMainUpdateLoop(). Retrying in 20 sec. Reason: Loading block index…. Stack trace: Error: Loading block index…
api_1 | at /backend/package/rpc-api/jsonrpc.js:128:35
api_1 | at Array.forEach ()
api_1 | at IncomingMessage. (/backend/package/rpc-api/jsonrpc.js:125:25)
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://10.21.21.26:3006
app_proxy_1 | Waiting for 10.21.21.26:3006 to open…
app_proxy_1 | mempool is now ready…
app_proxy_1 | Listening on port: 3006
web_1 | /var/www/mempool/browser/resources
api_1 | at IncomingMessage.emit (node:events:539:35)
api_1 | at endReadableNT (node:internal/streams/readable:1345:12)
api_1 | at processTicksAndRejections (node:internal/process/task_queues:83:21)

==== Result ====

The debug script did not automatically detect any issues with your Umbrel.