Umbrel fährt nach "Reboot" nicht mehr hoch (BTC und BTC LN Node)

Moin, ich habe meinen Umbrel über das Terminal mit dem Befehl
sudo ~/umbrel/scripts/stop && sudo reboot
heruntergefahren, weil ich nicht mehr auf meine Lightning Node App (Lila mit blitz) kam - lange Ladezeit bei ca 2/3 des Ladebalkens und dann freeze in. Im Terminal hat er nach Befehleingabe diese ganze Latte an Stopping dies und das gemeldet und dann das Prompt wieder angezeigt.

Nun kann ich über meinen Browser ganz normal umbrel.local wieder aufrufen. Meine installierten Apps (Bitcoin Node, Lightning Node, RTL) kann ich sehen. Bei der Wahl der BTC Node öffnet sich wie immer das extra Tab und oben links steht in grün „Running“ bei 100%.
Die Lightning Node App öffnet sich auch wie gehabt in einem neuen Tab und bleibt erneut bei ca 50-66% beim Ladebalken stehen. RTL meldet Error 500 „Waiting To Start, Rpc Services Not Available“

Ich befürchte, dass ich auf Terminalebene muss. Ich bin alles andere als damit vertraut. Kann mir hier jemand helfen, wie ich die beiden Nodes wieder zum Laufen bekomme?

Vielen Dank im voraus.

Scheint ein schwieriges Problem zu sein :frowning:

Nach Recherche online habe ich einen Befehl gefunden und auf Terminal eingegeben. Offenbar ist die LN Node erfolgreich gestoppt und wieder gestartet worden.

Allerdings weiß ich noch immer nicht, ob sie läuft. Geschweige denn kann ich über die GUI mit der LN Node App starten. Der Ladebalken friert immer noch bei 50-60% ein.

Kann mir wirklich niemand helfen?

Kannst du uns mal ein gesamtes log zur verfügung stellen.

Wenn Lightning nicht startet kann es auch ein Problem mit dem Bitcoin Core etc. sein

Hatte auch letztens Probleme.

Vielen lieben Dank für Deine Antwort!

Wie komme ich an die Logs? Über das GUI habe ich es versucht: Umbrel / Pref App / rechte Spalte Troubleshoot:
++Generating logs Error: Failed to fetch debug data++

Wie erwähnt kenne ich mich nicht (!) mit Terminal Befehlen aus. Ich weiß wie ich mich auf die umbrel einwählen/ anmelde und habe nun 3 Befehle gelernt :slight_smile: Vermutlich kann ich mir die Logs auch über Terminal holen, dann bräuchte ich den Befehl und auch die Hilfe, wie und wo ich die kopieren kann.

Danke für das Hilfeangebot.

You can try again, sometimes log fetching has this error,

Otherwise you can open the terminal and type in this command „~/umbrel/scripts/debug“

This will print out the whole log

Ok mit sudo davor habe ich jetzt eine ewig lange Liste bekommen. Soll ich Dir hier hinein kopieren?

Ganz am Ende steht das:

==== Result ====

================

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

Soweit ich das Log lesen kann, ist das hier vermutlich der Lightning Node App Teil. Da gibt es aber in der Tat „Fehler“.
lightning

Attaching to lightning_app_proxy_1, lightning_app_1, lightning_tor_1, lightning_tor_server_1, lightning_lnd_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 | 2023-06-01 07:59:10.423 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:11.476 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:12.528 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:13.130 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:13.735 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:14.868 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:15.958 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:17.225 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:18.285 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:19.352 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
tor_1 | Jun 01 05:57:51.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Jun 01 05:57:51.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 100% (done): Done
tor_1 | Jun 01 07:03:47.000 [warn] Received http status code 404 („Not found“) from server 23.146.184.21:9100 while fetching „/tor/keys/fp/EFCBE720AB3A82Bxxxxxxx“.
tor_1 | Jun 01 07:58:45.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:48.000 [notice] We now have enough directory information to build circuits.

Kannst du bitte die gesamte Ausgabe hier posten.

RPC deutet darauf hin das ein anderer Service ein Problem hat. Das LND nicht startet ist Scheinar nur die ein Symptom.

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

Umbrel version

0.5.3

Flashed OS version

v0.5.0

Raspberry Pi Model

Revision : c03115
Serial : 1000000029edf1b4
Model : Raspberry Pi 4 Model B Rev 1.5

Firmware

Dec 1 2021 15:01:54
Copyright (c) 2012 Broadcom
version 71bd3109023a0c8575585ba87cbb374d2eeb038f (clean) (release) (start)

Temperature

temp=66.2’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 1.1G 617M 1.0M 2.0G 2.6G
Swap: 4.1G 627M 3.5G

total: 30.0%
bitcoin: 14.8%
lightning: 10.8%
ride-the-lightning: 2.7%
system: 1.7%

Memory monitor logs

2022-08-02 16:05:46 Memory monitor running!
2022-10-11 18:46:45 Memory monitor running!
2023-04-15 13:48:14 Memory monitor running!
2023-05-31 16:52:49 Memory monitor running!
2023-05-31 17:42:51 Memory monitor running!
2023-05-31 18:28:40 Memory monitor running!
2023-05-31 21:50:49 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 15G 3.2G 11G 24% /
/dev/sda1 916G 576G 295G 67% /home/umbrel/umbrel

Startup service logs

Jun 01 03:59:14 umbrel umbrel startup[1174]: Creating lightning_app_proxy_1 …
Jun 01 03:59:14 umbrel umbrel startup[1174]: Creating lightning_tor_server_1 …
Jun 01 03:59:15 umbrel umbrel startup[1174]: Creating bitcoin_app_proxy_1 …
Jun 01 03:59:15 umbrel umbrel startup[1174]: Creating bitcoin_tor_1 …
Jun 01 03:59:15 umbrel umbrel startup[1174]: Creating bitcoin_tor_server_1 …
Jun 01 03:59:15 umbrel umbrel startup[1174]: Creating bitcoin_bitcoind_1 …
Jun 01 03:59:15 umbrel umbrel startup[1174]: Creating bitcoin_i2pd_daemon_1 …
Jun 01 03:59:34 umbrel umbrel startup[1174]: Creating lightning_tor_1 … done
Jun 01 03:59:35 umbrel umbrel startup[1174]: Creating lightning_app_proxy_1 … done
Jun 01 03:59:37 umbrel umbrel startup[1174]: Creating ride-the-lightning_boltz_1 … done
Jun 01 03:59:41 umbrel umbrel startup[1174]: Creating ride-the-lightning_tor_server_1 … done
Jun 01 03:59:47 umbrel umbrel startup[1174]: Creating bitcoin_i2pd_daemon_1 … done
Jun 01 03:59:48 umbrel umbrel startup[1174]: Creating lightning_app_1 … done
Jun 01 03:59:52 umbrel umbrel startup[1174]: Creating bitcoin_tor_server_1 … done
Jun 01 04:00:00 umbrel umbrel startup[1174]: Creating lightning_tor_server_1 … done
Jun 01 04:00:15 umbrel umbrel startup[1174]: Creating lightning_lnd_1 … done
Jun 01 04:00:19 umbrel umbrel startup[1174]: Creating bitcoin_bitcoind_1 … done
Jun 01 04:00:19 umbrel umbrel startup[1174]: Creating bitcoin_server_1 …
Jun 01 04:00:25 umbrel umbrel startup[1174]: Creating bitcoin_tor_1 … done
Jun 01 04:00:46 umbrel umbrel startup[1174]: Creating ride-the-lightning_app_proxy_1 … done
Jun 01 04:00:46 umbrel umbrel startup[1174]: Creating bitcoin_app_proxy_1 … done
Jun 01 04:00:49 umbrel umbrel startup[1174]: Creating ride-the-lightning_web_1 … done
Jun 01 04:01:29 umbrel umbrel startup[1174]: Creating bitcoin_server_1 … done
Jun 01 04:01:29 umbrel umbrel startup[1174]: Umbrel is now accessible at
Jun 01 04:01:29 umbrel umbrel startup[1174]: http://umbrel.local
Jun 01 04:01:29 umbrel umbrel startup[1174]: http://192.168.178.43
Jun 01 04:01:29 umbrel systemd[1]: Started Umbrel Startup Service.
Jun 01 04:10:25 umbrel passwd[18195]: pam_unix(passwd:): password changed for umbrel
Jun 01 05:24:18 umbrel passwd[5394]: pam_unix(passwd:): password changed for umbrel

External storage service logs

May 31 21:50:23 umbrel external storage mounter[490]: Running external storage mount script…
May 31 21:50:23 umbrel external storage mounter[490]: Found device „Seagate Portable“
May 31 21:50:23 umbrel external storage mounter[490]: Blacklisting USB device IDs against UAS driver…
May 31 21:50:24 umbrel external storage mounter[490]: Rebinding USB drivers…
May 31 21:50:24 umbrel external storage mounter[490]: Checking USB devices are back…
May 31 21:50:24 umbrel external storage mounter[490]: Waiting for USB devices…
May 31 21:50:25 umbrel external storage mounter[490]: Waiting for USB devices…
May 31 21:50:26 umbrel external storage mounter[490]: Waiting for USB devices…
May 31 21:50:27 umbrel external storage mounter[490]: Checking if the device is ext4…
May 31 21:50:27 umbrel external storage mounter[490]: Yes, it is ext4
May 31 21:50:27 umbrel external storage mounter[490]: Checking filesystem for corruption…
May 31 21:50:27 umbrel external storage mounter[490]: e2fsck 1.44.5 (15-Dec-2018)
May 31 21:50:28 umbrel external storage mounter[490]: umbrel: clean, 210392/61054976 files, 154722905/244190208 blocks
May 31 21:50:28 umbrel external storage mounter[490]: Mounting partition…
May 31 21:50:28 umbrel external storage mounter[490]: Checking if device contains an Umbrel install…
May 31 21:50:28 umbrel external storage mounter[490]: Yes, it contains an Umbrel install
May 31 21:50:28 umbrel external storage mounter[490]: Bind mounting external storage over local Umbrel installation…
May 31 21:50:28 umbrel external storage mounter[490]: Bind mounting external storage over local Docker data dir…
May 31 21:50:28 umbrel external storage mounter[490]: Bind mounting external storage to /swap
May 31 21:50:28 umbrel external storage mounter[490]: Bind mounting SD card root at /sd-card…
May 31 21:50:28 umbrel external storage mounter[490]: Checking Umbrel root is now on external storage…
May 31 21:50:29 umbrel external storage mounter[490]: Checking /var/lib/docker is now on external storage…
May 31 21:50:29 umbrel external storage mounter[490]: Checking /swap is now on external storage…
May 31 21:50:29 umbrel external storage mounter[490]: Setting up swapfile
May 31 21:50:35 umbrel external storage mounter[490]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 31 21:50:35 umbrel external storage mounter[490]: no label, UUID=1f037xxxxxx
May 31 21:50:35 umbrel external storage mounter[490]: Checking SD Card root is bind mounted at /sd-root…
May 31 21:50:35 umbrel external storage mounter[490]: Starting external drive mount monitor…
May 31 21:50:35 umbrel external storage mounter[490]: Mount script completed successfully!
May 31 21:50:35 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Wed 2023-05-31 21:50:19 UTC, end at Thu 2023-06-01 07:58:58 UTC. –
May 31 21:50:43 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 31 21:50:43 umbrel external storage updater[1096]: Checking if SD card Umbrel is newer than external storage…
May 31 21:50:43 umbrel external storage updater[1096]: No, SD version is not newer, exiting.
May 31 21:50:43 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Removing bitcoin_i2pd_daemon_1 … done
Removing bitcoin_tor_1 … done
Removing bitcoin_tor_server_1 … done
Removing bitcoin_server_1 … done
Removing bitcoin_app_proxy_1 … done
Going to remove bitcoin_server_1, bitcoin_bitcoind_1, bitcoin_app_proxy_1, bitcoin_tor_1, bitcoin_i2pd_daemon_1, bitcoin_tor_server_1

Stopping Docker services…

Stopping nginx …
Stopping auth …
Stopping tor_proxy …
Stopping tor_server …
Stopping manager …
Stopping dashboard …
Stopping tor_server … done
Stopping tor_proxy … done
Stopping nginx … done
Stopping auth … done
Stopping manager … done
Stopping dashboard … done
Removing nginx …
Removing auth …
Removing tor_proxy …
Removing tor_server …
Removing manager …
Removing dashboard …
Removing tor_server … done
Removing tor_proxy … done
Removing dashboard … done
Removing nginx … done
Removing auth … done
Removing manager … done
Removing network umbrel_main_network
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
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: change-password
karen is getting triggered!
New password: Retype new password: passwd: password updated successfully
Got signal: debug
karen is getting triggered!
Debug result file generated

Docker containers

NAMES STATUS
lightning_app_proxy_1 Up 2 hours
lightning_app_1 Up 2 hours
lightning_tor_1 Up 2 hours
lightning_tor_server_1 Up 2 hours
lightning_lnd_1 Up 2 hours
bitcoin_server_1 Up 4 hours
bitcoin_i2pd_daemon_1 Up 4 hours
bitcoin_bitcoind_1 Up 4 hours
bitcoin_tor_1 Up 4 hours
bitcoin_tor_server_1 Up 4 hours
bitcoin_app_proxy_1 Up 4 hours
ride-the-lightning_app_proxy_1 Up 4 hours
ride-the-lightning_web_1 Up 4 hours
ride-the-lightning_boltz_1 Up 4 hours
ride-the-lightning_tor_server_1 Up 4 hours
nginx Up 4 hours
tor_proxy Up 4 hours
tor_server Up 4 hours
dashboard Up 4 hours
manager Up 4 hours
auth Up 4 hours

Umbrel logs

Attaching to manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/memory HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/temperature HTTP/1.0“ 200 2 „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/apps?installed=1 HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/info HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/update-status HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/apps HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/storage HTTP/1.0“ 200 514 „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:39 GMT] „GET /v1/system/get-update HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:46 GMT] „POST /v1/account/logout HTTP/1.0“ 200 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Thu, 01 Jun 2023 06:11:47 GMT] „GET /v1/account/registered HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
manager |
manager | umbrel-manager

Tor Proxy logs

Attaching to tor_proxy
tor_proxy | Jun 01 03:58:56.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor_proxy | Jun 01 03:58:56.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_proxy | Jun 01 03:58:57.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_proxy | Jun 01 03:58:58.000 [notice] Bootstrapped 100% (done): Done
tor_proxy | Jun 01 04:45:59.000 [warn] Received http status code 404 („Not found“) from server 193.30.123.23:9000 while fetching „/tor/keys/fp/EFCBxxxxxx“.

App logs

bitcoin

Attaching to bitcoin_server_1, bitcoin_i2pd_daemon_1, bitcoin_bitcoind_1, bitcoin_tor_1, bitcoin_tor_server_1, bitcoin_app_proxy_1
bitcoind_1 | 2023-06-01T07:52:29Z Syncing txindex with block chain from height 790210
bitcoind_1 | 2023-06-01T07:53:01Z Syncing txindex with block chain from height 790213
bitcoind_1 | 2023-06-01T07:53:43Z Syncing txindex with block chain from height 790218
bitcoind_1 | 2023-06-01T07:54:16Z Syncing txindex with block chain from height 790221
bitcoind_1 | 2023-06-01T07:54:59Z Syncing txindex with block chain from height 790222
bitcoind_1 | 2023-06-01T07:55:36Z Syncing txindex with block chain from height 790226
bitcoind_1 | 2023-06-01T07:56:10Z Syncing txindex with block chain from height 790229
bitcoind_1 | 2023-06-01T07:56:46Z Syncing txindex with block chain from height 790232
bitcoind_1 | 2023-06-01T07:59:15Z UpdateTip: new best=00000000000000000002c2c32eb8b214bed6947775147785ab4bceb866e78820 height=792349 version=0x20200000 log2_work=94.214628 tx=846524409 date=‚2023-06-01T07:54:08Z‘ progress=0.999999 cache=76.4MiB(527316txo)
bitcoind_1 | 2023-06-01T07:59:15Z Syncing txindex with block chain from height 790233
tor_1 | Jun 01 07:18:46.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:23:55.000 [notice] Application asked to connect to port 0. Refusing.
tor_1 | Jun 01 07:24:42.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:26:27.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:27:17.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:28:10.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:30:25.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:34:04.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_1 | Jun 01 07:34:19.000 [notice] Closed 1 streams for service [scrubbed].onion for reason resolve failed. Fetch status: No more HSDir available to query.
tor_1 | Jun 01 07:38:12.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
i2pd_daemon_1 | 06:35:26@206/error - NetDb: 0w8U5Ftc~OMKU3UxmnGoSRzXqZPI2HicksYc3lOX6iI= destination requested, but no tunnels found
i2pd_daemon_1 | 06:41:48@565/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 06:45:05@565/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 06:54:48@565/error - SSU2: RelayIntro unknown router to introduce
i2pd_daemon_1 | 06:58:10@453/error - Tunnels: Can’t select next hop for Jb3WOdRrD3xdXVwfNH1uK2Hs4hxN3yca2i4px4ytQ-Q=
i2pd_daemon_1 | 06:58:10@453/error - Tunnels: Can’t create inbound tunnel, no peers available
i2pd_daemon_1 | 07:06:42@453/error - Tunnel: Tunnel with id 2011375621 already exists
i2pd_daemon_1 | 07:20:58@453/error - Tunnel: Tunnel with id 3315334484 already exists
i2pd_daemon_1 | 07:21:30@453/error - Tunnels: Can’t select next hop for 8N8daMtnDi-iYqAH4iXruwZ8W2XWlObGSc7MvOjJkbs=
i2pd_daemon_1 | 07:21:30@453/error - Tunnels: Can’t create inbound tunnel, no peers available
app_proxy_1 | code: ‚ECONNRESET‘
app_proxy_1 | }
app_proxy_1 | [HPM] ECONNRESET: Error: socket hang up
app_proxy_1 | at connResetException (node:internal/errors:705:14)
app_proxy_1 | at Socket.socketOnEnd (node:_http_client:518:23)
app_proxy_1 | at Socket.emit (node:events:525:35)
app_proxy_1 | at endReadableNT (node:internal/streams/readable:1358:12)
app_proxy_1 | at processTicksAndRejections (node:internal/process/task_queues:83:21) {
app_proxy_1 | code: ‚ECONNRESET‘
app_proxy_1 | }
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Thu, 01 Jun 2023 06:12:14 GMT] „GET /v1/bitcoind/info/connections HTTP/1.1“ - - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Thu, 01 Jun 2023 06:12:14 GMT] „GET /v1/bitcoind/info/stats HTTP/1.1“ - - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
server_1 |
server_1 | umbrel-middleware
server_1 | ::ffff:10.21.0.6 - - [Thu, 01 Jun 2023 06:12:14 GMT] „GET /v1/bitcoind/info/sync HTTP/1.1“ - - „-“ „Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/16.3 Safari/605.1.15“
server_1 |
server_1 | umbrel-middleware

lightning

Attaching to lightning_app_proxy_1, lightning_app_1, lightning_tor_1, lightning_tor_server_1, lightning_lnd_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 | 2023-06-01 07:59:10.423 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:11.476 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:12.528 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:13.130 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:13.735 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:14.868 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:15.958 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:17.225 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:18.285 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
lnd_1 | 2023-06-01 07:59:19.352 [ERR] RPCS: [/lnrpc.Lightning/GetInfo]: waiting to start, RPC services not available
tor_1 | Jun 01 05:57:51.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor_1 | Jun 01 05:57:51.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor_1 | Jun 01 05:57:52.000 [notice] Bootstrapped 100% (done): Done
tor_1 | Jun 01 07:03:47.000 [warn] Received http status code 404 („Not found“) from server 23.146.184.21:9100 while fetching „/tor/keys/fp/EFCBE7xxxxxx“.
tor_1 | Jun 01 07:58:45.000 [notice] Our directory information is no longer up-to-date enough to build circuits: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:45.000 [notice] I learned some more directory information, but not enough to build a circuit: We’re missing descriptors for 1/3 of our primary entry guards (total microdescriptors: 6778/6880). That’s ok. We will try to fetch missing descriptors soon.
tor_1 | Jun 01 07:58:48.000 [notice] We now have enough directory information to build circuits.

ride-the-lightning

Attaching to ride-the-lightning_app_proxy_1, ride-the-lightning_web_1, ride-the-lightning_boltz_1, ride-the-lightning_tor_server_1
boltz_1 | WARN : 2023/06/01 07:58:13 Could not connect to LND: rpc error: code = Unknown desc = waiting to start, RPC services not available
boltz_1 | INFO : 2023/06/01 07:58:13 Retrying in 15 seconds
boltz_1 | WARN : 2023/06/01 07:58:28 Could not connect to LND: rpc error: code = Unknown desc = waiting to start, RPC services not available
boltz_1 | INFO : 2023/06/01 07:58:28 Retrying in 15 seconds
boltz_1 | WARN : 2023/06/01 07:58:43 Could not connect to LND: rpc error: code = Unknown desc = waiting to start, RPC services not available
boltz_1 | INFO : 2023/06/01 07:58:43 Retrying in 15 seconds
boltz_1 | WARN : 2023/06/01 07:58:58 Could not connect to LND: rpc error: code = Unknown desc = waiting to start, RPC services not available
boltz_1 | INFO : 2023/06/01 07:58:58 Retrying in 15 seconds
boltz_1 | WARN : 2023/06/01 07:59:13 Could not connect to LND: rpc error: code = Unknown desc = waiting to start, RPC services not available
boltz_1 | INFO : 2023/06/01 07:59:13 Retrying in 15 seconds
app_proxy_1 | yarn run v1.22.19
app_proxy_1 | $ node ./bin/www
app_proxy_1 | [HPM] Proxy created: / → http://ride-the-lightning_web_1:3001
app_proxy_1 | Waiting for ride-the-lightning_web_1:3001 to open…
app_proxy_1 | Ride The Lightning is now ready…
app_proxy_1 | Listening on port: 3001
web_1 | [6/1/2023, 4:02:26 AM] INFO: App => Setting up Application Routes…
web_1 |
web_1 | [6/1/2023, 4:02:26 AM] INFO: App => Application Routes Set.
web_1 |
web_1 | [6/1/2023, 4:02:26 AM] INFO: WebSocketServer => Connecting Websocket Server…
web_1 |
web_1 | [6/1/2023, 4:02:26 AM] INFO: WebSocketServer => Websocket Server Connected.
web_1 |
web_1 | [6/1/2023, 4:02:26 AM] INFO: RTL => Server is up and running, please open the UI at http://localhost:3001 or your proxy configured url.
web_1 |

==== Result ====

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

Was bei einigen schon geholfen hat, war das Löschen von peers.dat der Bitcoin-Node.
Wie genau es zu tun ist, sollte über die Forensuche zu finden sein.
Viel Glück.

Das habe ich auch gelesen, aber mir wäre tatsächlich wichtig, was anhand des Logs denn jetzt schief läuft. Erst danach beginnt man doch mit Massnahmen, oder?

Die Lösung war - dank umbrel support - das erneute Flashen der SD Karte

1 „Gefällt mir“

Das Problem mit der peers.dat hatte ich auch schon zwei mal. Das war nämlich meine Vermutung.
Aber das steht ganz Eindeutig im Log, wenn das der Fall gewesen wäre.

@nikolaj2172 na wunderbar das sich eine Lösung hat finden lassen.