[solved] Umbrel Bitcoin und Lightning Wallet Synchronizing Dauerschleife

Fragen Technik
1

Hi Leute ich brauche eure Hilfe!
Ich habe meine Umbrel Node neu gestartet und seitdem werden meine Wallet Bestände nicht mehr angezeigt und sowohl Bitcoin Wallet als auch Lightning zeigen schon seit Stunden „Synchronizing“ an. Die Blockchain selbst ist zu 100% synchronisiert.

Weiß jemand was in so einem Fall zu tun ist ? Ich habe meine Seeds und auch backups meiner Channels, jedoch finde ich in Umbrel nirgends die Möglichkeit die backups wiederherzustellen.
Ich habe jetzt die Angst, dass meine mühsam aufgebauten Channels dahin sind generell mein BTC-Guthaben weg ist … :grimacing:

Anbei ein Screenshot vom dzt. „Zustand“ meiner Node und die debug.log

wick3da node
wick3da node1888×2562 125 KB

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

Umbrel version

0.4.18

Flashed OS version

v0.4.17

Raspberry Pi Model

Revision : d03115
Serial : 1000000003337d91
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=59.9’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 1.0G 4.9G 9.0M 1.9G 6.6G
Swap: 4.1G 0B 4.1G

total: 13.4%
bitcoin: 6.8%
system: 2.5%
mempool: 2.1%
electrs: 1.7%
tor: 0.3%
lnd: 0%

Memory monitor logs

2022-05-07 12:45:54 Memory monitor running!
1248 ? S 0:12 bash ./scripts/memory-monitor
Memory monitor is already running
2022-05-19 12:42:58 Memory monitor running!
2022-05-21 09:31:08 Memory monitor running!
2022-05-21 09:47:34 Memory monitor running!
2022-05-21 09:56:32 Memory monitor running!
1017 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2022-05-21 11:07:57 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 117G 3.1G 109G 3% /
/dev/sda1 916G 519G 351G 60% /home/umbrel/umbrel

Startup service logs

May 21 11:08:04 umbrel umbrel startup[980]: Creating tor … done
May 21 11:08:04 umbrel umbrel startup[980]: Creating manager …
May 21 11:08:04 umbrel umbrel startup[980]: Creating dashboard … done
May 21 11:08:08 umbrel umbrel startup[980]: Creating manager … done
May 21 11:08:08 umbrel umbrel startup[980]: Creating nginx …
May 21 11:08:08 umbrel umbrel startup[980]: Creating lnd …
May 21 11:08:24 umbrel umbrel startup[980]: Creating lnd … done
May 21 11:08:24 umbrel umbrel startup[980]: Creating nginx … done
May 21 11:08:24 umbrel umbrel startup[980]: Creating bitcoin …
May 21 11:08:26 umbrel umbrel startup[980]: Creating bitcoin … done
May 21 11:08:26 umbrel umbrel startup[980]: Creating neutrino-switcher …
May 21 11:08:26 umbrel umbrel startup[980]: Creating middleware …
May 21 11:08:29 umbrel umbrel startup[980]: Creating middleware … done
May 21 11:08:30 umbrel umbrel startup[980]: Creating neutrino-switcher … done
May 21 11:08:30 umbrel umbrel startup[980]: Removing status server iptables entry…
May 21 11:08:30 umbrel umbrel startup[980]: Removed existing iptables entry.
May 21 11:08:30 umbrel umbrel startup[980]: Starting installed apps…
May 21 11:08:30 umbrel umbrel startup[980]: Starting app mempool…
May 21 11:08:34 umbrel umbrel startup[980]: Creating mempool_api_1 …
May 21 11:08:34 umbrel umbrel startup[980]: Creating mempool_web_1 …
May 21 11:08:34 umbrel umbrel startup[980]: Creating mempool_mariadb_1 …
May 21 11:08:36 umbrel passwd[3845]: pam_unix(passwd:chauthtok): password changed for umbrel
May 21 11:08:38 umbrel umbrel startup[980]: Creating mempool_api_1 … done
May 21 11:08:38 umbrel umbrel startup[980]: Creating mempool_web_1 … done
May 21 11:08:38 umbrel umbrel startup[980]: Creating mempool_mariadb_1 … done
May 21 11:08:38 umbrel umbrel startup[980]: Umbrel is now accessible at
May 21 11:08:38 umbrel umbrel startup[980]: http://umbrel.local
May 21 11:08:38 umbrel umbrel startup[980]: http://192.168.0.196
May 21 11:08:38 umbrel systemd[1]: Started Umbrel Startup Service.

External storage service logs

– Logs begin at Sat 2022-05-21 11:07:36 UTC, end at Sat 2022-05-21 11:14:41 UTC. –
May 21 11:07:41 umbrel systemd[1]: Starting External Storage Mounter…
May 21 11:07:41 umbrel external storage mounter[477]: Running external storage mount script…
May 21 11:07:42 umbrel external storage mounter[477]: Found device „JMicron Generic“
May 21 11:07:42 umbrel external storage mounter[477]: Blacklisting USB device IDs against UAS driver…
May 21 11:07:42 umbrel external storage mounter[477]: Rebinding USB drivers…
May 21 11:07:42 umbrel external storage mounter[477]: Checking USB devices are back…
May 21 11:07:42 umbrel external storage mounter[477]: Waiting for USB devices…
May 21 11:07:43 umbrel external storage mounter[477]: Waiting for USB devices…
May 21 11:07:44 umbrel external storage mounter[477]: Waiting for USB devices…
May 21 11:07:45 umbrel external storage mounter[477]: Checking if the device is ext4…
May 21 11:07:45 umbrel external storage mounter[477]: Yes, it is ext4
May 21 11:07:45 umbrel external storage mounter[477]: Checking if device contains an Umbrel install…
May 21 11:07:45 umbrel external storage mounter[477]: Yes, it contains an Umbrel install
May 21 11:07:45 umbrel external storage mounter[477]: Bind mounting external storage over local Umbrel installation…
May 21 11:07:45 umbrel external storage mounter[477]: Bind mounting external storage over local Docker data dir…
May 21 11:07:45 umbrel external storage mounter[477]: Bind mounting external storage to /swap
May 21 11:07:45 umbrel external storage mounter[477]: Bind mounting SD card root at /sd-card…
May 21 11:07:45 umbrel external storage mounter[477]: Checking Umbrel root is now on external storage…
May 21 11:07:46 umbrel external storage mounter[477]: Checking /var/lib/docker is now on external storage…
May 21 11:07:46 umbrel external storage mounter[477]: Checking /swap is now on external storage…
May 21 11:07:46 umbrel external storage mounter[477]: Setting up swapfile
May 21 11:07:48 umbrel external storage mounter[477]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 21 11:07:48 umbrel external storage mounter[477]: no label, UUID=bd37ddfd-84dc-46ee-9aa9-4ea47a386ac8
May 21 11:07:48 umbrel external storage mounter[477]: Checking SD Card root is bind mounted at /sd-root…
May 21 11:07:48 umbrel external storage mounter[477]: Starting external drive mount monitor…
May 21 11:07:48 umbrel external storage mounter[477]: Mount script completed successfully!
May 21 11:07:48 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Sat 2022-05-21 11:07:36 UTC, end at Sat 2022-05-21 11:14:41 UTC. –
May 21 11:07:57 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 21 11:07:57 umbrel external storage updater[902]: Checking if SD card Umbrel is newer than external storage…
May 21 11:07:57 umbrel external storage updater[902]: No, SD version is not newer, exiting.
May 21 11:07:57 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Stopping bitcoin …
Stopping nginx …
Stopping lnd …
Stopping manager …
Stopping umbrel_tor_server_1 …
Stopping electrs …
Stopping dashboard …
Stopping tor …
Stopping middleware … done
Stopping electrs … done
Stopping lnd … done
Stopping bitcoin … done
Stopping nginx … done
Stopping dashboard … done
Stopping manager … done
Stopping umbrel_tor_server_1 … done
Stopping tor … done
Removing neutrino-switcher …
Removing middleware …
Removing bitcoin …
Removing nginx …
Removing lnd …
Removing manager …
Removing umbrel_tor_server_1 …
Removing electrs …
Removing dashboard …
Removing tor …
Removing neutrino-switcher … done
Removing dashboard … done
Removing middleware … done
Removing electrs … done
Removing tor … done
Removing nginx … done
Removing manager … done
Removing bitcoin … done
Removing lnd … done
Removing umbrel_tor_server_1 … done
Removing network umbrel_main_network
karen is running in /home/umbrel/umbrel/events
Got signal:
karen is getting triggered!
./karen: line 68: /home/umbrel/umbrel/events/triggers/: Is a directory
Got signal:
karen is getting triggered!
./karen: line 68: /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: debug
karen is getting triggered!

Docker containers

NAMES STATUS
mempool_mariadb_1 Up 6 minutes
mempool_web_1 Up 6 minutes
mempool_api_1 Up 6 minutes
middleware Up 6 minutes
bitcoin Up 6 minutes
lnd Restarting (1) 23 seconds ago
nginx Up 6 minutes
manager Up 6 minutes
dashboard Up 6 minutes
umbrel_tor_server_1 Up 7 minutes
electrs Up 7 minutes
tor Up 7 minutes

Umbrel logs

Attaching to middleware, manager
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:37 GMT] „GET /v1/lnd/lightning/invoices HTTP/1.0“ 500 61 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | Unable to list pending channels, failed to connect to all addresses
middleware | /v1/lnd/channel
middleware | LndError: Unable to list pending channels
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:37 GMT] „GET /v1/lnd/channel HTTP/1.0“ 500 69 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | Unable to get payments, failed to connect to all addresses
middleware | /v1/lnd/lightning/payments
middleware | LndError: Unable to get payments
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:40 GMT] „GET /v1/lnd/lightning/payments HTTP/1.0“ 500 60 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | LndUnlocker: Wallet failed to unlock!
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:58 GMT] „GET /v1/system/dashboard-hidden-service HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:58 GMT] „GET /v1/system/info HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:58 GMT] „GET /v1/system/uptime HTTP/1.0“ 200 3 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:58 GMT] „GET /v1/apps?installed=1 HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:58 GMT] „GET /v1/apps HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:15:01 GMT] „POST /v1/system/debug HTTP/1.0“ 200 17 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:15:02 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:15:03 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:15:04 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:14:56 GMT] „GET /v1/bitcoind/info/sync HTTP/1.0“ 200 88 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 11:15:05 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2022-05-21T11:09:07Z 2 block-relay-only anchors will be tried for connections.
bitcoin | 2022-05-21T11:09:07Z init message: Starting network threads…
bitcoin | 2022-05-21T11:09:07Z init message: Done loading
bitcoin | 2022-05-21T11:09:07Z msghand thread start
bitcoin | 2022-05-21T11:09:07Z opencon thread start
bitcoin | 2022-05-21T11:09:07Z addcon thread start
bitcoin | 2022-05-21T11:09:07Z net thread start
bitcoin | 2022-05-21T11:09:07Z dnsseed thread start
bitcoin | 2022-05-21T11:09:07Z Waiting 300 seconds before querying DNS seeds.
bitcoin | 2022-05-21T11:09:13Z Imported mempool transactions from disk: 472 succeeded, 0 failed, 0 expired, 0 already there, 0 waiting for initial broadcast
bitcoin | 2022-05-21T11:09:13Z loadblk thread exit
bitcoin | 2022-05-21T11:10:15Z Socks5() connect to 45.15.16.71:8333 failed: general failure
bitcoin | 2022-05-21T11:10:36Z Socks5() connect to 2600:70ff:b843::247:8333 failed: general failure
bitcoin | 2022-05-21T11:10:37Z New outbound peer connected: version: 70016, blocks=737286, peer=1 (outbound-full-relay)
bitcoin | 2022-05-21T11:10:58Z New outbound peer connected: version: 70016, blocks=737286, peer=2 (outbound-full-relay)
bitcoin | 2022-05-21T11:11:04Z New outbound peer connected: version: 70016, blocks=737286, peer=3 (outbound-full-relay)
bitcoin | 2022-05-21T11:11:05Z New outbound peer connected: version: 70015, blocks=737285, peer=4 (outbound-full-relay)
bitcoin | 2022-05-21T11:11:08Z P2P peers available. Skipped DNS seeding.
bitcoin | 2022-05-21T11:11:08Z dnsseed thread exit
bitcoin | 2022-05-21T11:11:08Z New outbound peer connected: version: 70016, blocks=737286, peer=5 (outbound-full-relay)
bitcoin | 2022-05-21T11:11:53Z New outbound peer connected: version: 70016, blocks=737286, peer=6 (outbound-full-relay)
bitcoin | 2022-05-21T11:12:24Z New outbound peer connected: version: 70016, blocks=737286, peer=7 (outbound-full-relay)
bitcoin | 2022-05-21T11:12:45Z New outbound peer connected: version: 70016, blocks=737286, peer=8 (outbound-full-relay)
bitcoin | 2022-05-21T11:13:48Z New outbound peer connected: version: 70016, blocks=737286, peer=9 (outbound-full-relay)
bitcoin | 2022-05-21T11:13:51Z New outbound peer connected: version: 70016, blocks=737286, peer=10 (outbound-full-relay)
bitcoin | 2022-05-21T11:13:57Z New outbound peer connected: version: 70015, blocks=737286, peer=11 (block-relay-only)
bitcoin | 2022-05-21T11:14:18Z New outbound peer connected: version: 70016, blocks=737286, peer=12 (block-relay-only)
bitcoin | 2022-05-21T11:14:22Z New outbound peer connected: version: 70016, blocks=737286, peer=13 (block-relay-only)
bitcoin | 2022-05-21T11:15:07Z New outbound peer connected: version: 70016, blocks=737286, peer=14 (block-relay-only)

LND logs

Attaching to lnd
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)

electrs logs

Attaching to electrs
electrs | [2022-05-21T11:08:29.752Z INFO electrs::chain] loading 737286 headers, tip=00000000000000000005957ed5f73c4b09ed54060679aded1dc521f99634fb4f
electrs | [2022-05-21T11:08:38.974Z INFO electrs::chain] chain updated: tip=00000000000000000005957ed5f73c4b09ed54060679aded1dc521f99634fb4f, height=737286
electrs | [2022-05-21T11:08:39.031Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:40.036Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:41.041Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:42.044Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:43.047Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:44.084Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:45.089Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:46.093Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:47.098Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:48.102Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:49.106Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:50.110Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:51.118Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:52.121Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:53.124Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:54.126Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:55.129Z INFO electrs::daemon] waiting for RPC warmup: Loading block index…
electrs | [2022-05-21T11:08:56.133Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:08:57.136Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:08:58.148Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:08:59.150Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:00.156Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:01.159Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:02.163Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:03.166Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:04.170Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:05.174Z INFO electrs::daemon] waiting for RPC warmup: Verifying blocks…
electrs | [2022-05-21T11:09:06.178Z INFO electrs::daemon] waiting for RPC warmup: Loading P2P addresses…

2

Tor logs

Attaching to umbrel_tor_server_1, tor
tor | May 21 11:10:11.000 [notice] Bootstrapped 64% (loading_descriptors): Loading relay descriptors
tor | May 21 11:10:12.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | May 21 11:10:12.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor | May 21 11:10:12.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor | May 21 11:10:12.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor | May 21 11:10:13.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | May 21 11:10:13.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | May 21 11:10:13.000 [notice] Bootstrapped 100% (done): Done
tor | May 21 11:10:15.000 [notice] Have tried resolving or connecting to address ‚[scrubbed]‘ at 3 different places. Giving up.
tor_server_1 | May 21 11:09:15.000 [warn] Guard MYLABSUKTOR01 ($DDD156E411CAA27E65EEAD73BBB207E8CAD4FD42) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 92/185. Use counts are 55/55. 92 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:15.000 [warn] Guard FreeAssange2022 ($2C46046CFD6358F7D4F78EC8993CE149D3B9A481) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 100/201. Use counts are 60/60. 100 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:15.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 130 buildtimes.
tor_server_1 | May 21 11:09:15.000 [notice] Guard torpidsDEnetcup2 ($8DCB526722FBE2B3F4C0CE9D020B0589170F8BDA) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 101/151. Use counts are 61/61. 101 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:16.000 [warn] Guard torpidsDEnetcup2 ($8DCB526722FBE2B3F4C0CE9D020B0589170F8BDA) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 101/203. Use counts are 61/61. 101 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:18.000 [notice] Guard 7d8d64935ed96451d1f ($B25E02013A30693556480274240B8B392AB04179) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 102/151. Use counts are 62/62. 102 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:18.000 [warn] Guard 7d8d64935ed96451d1f ($B25E02013A30693556480274240B8B392AB04179) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 102/205. Use counts are 62/62. 102 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:22.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60000ms after 18 timeouts and 100 buildtimes.
tor_server_1 | May 21 11:09:26.000 [notice] Guard gbt2USicebeer18b ($47EDA8E6E0025FD170205B94C97B17B983B0FAE5) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 99/151. Use counts are 61/61. 99 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor_server_1 | May 21 11:09:27.000 [warn] Guard gbt2USicebeer18b ($47EDA8E6E0025FD170205B94C97B17B983B0FAE5) is failing a very large amount of circuits. Most likely this means the Tor network is overloaded, but it could also mean an attack against you or potentially the guard itself. Success counts are 100/201. Use counts are 61/61. 100 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.

App logs

mempool

api_1 | May 21 11:15:14 [68] DEBUG: Fetched transaction 6 / 6
api_1 | May 21 11:15:14 [68] DEBUG: Mempool blocks calculated in 0.007 seconds
api_1 | May 21 11:15:14 [68] DEBUG: New mempool size: 1271 Change: 6
api_1 | May 21 11:15:14 [68] DEBUG: Mempool updated in 0.093 seconds
mariadb_1 | 2022-05-21 11:08:38+00:00 [Note] [Entrypoint]: Entrypoint script for MariaDB Server 1:10.5.12+maria~focal started.
mariadb_1 | 2022-05-21 11:08:40 0 [Note] mysqld (mysqld 10.5.12-MariaDB-1:10.5.12+maria~focal) starting as process 1 …
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Uses event mutexes
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Number of pools: 1
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Using ARMv8 crc32 instructions
mariadb_1 | 2022-05-21 11:08:40 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Using Linux native AIO
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Completed initialization of buffer pool
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: 128 rollback segments are active.
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Setting file ‚./ibtmp1‘ size to 12 MB. Physically writing the file full; Please wait …
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: File ‚./ibtmp1‘ size is now 12 MB.
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: 10.5.12 started; log sequence number 7978099; transaction id 40409
mariadb_1 | 2022-05-21 11:08:40 0 [Note] Plugin ‚FEEDBACK‘ is disabled.
mariadb_1 | 2022-05-21 11:08:40 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mariadb_1 | 2022-05-21 11:08:40 0 [Note] Server socket created on IP: ‚::‘.
mariadb_1 | 2022-05-21 11:08:40 0 [Warning] ‚proxies_priv‘ entry ‚@% root@42e9c73c9fe0‘ ignored in --skip-name-resolve mode.
mariadb_1 | 2022-05-21 11:08:40 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2022-05-21 11:08:40 0 [Note] Added new Master_info ‚‘ to hash table
mariadb_1 | 2022-05-21 11:08:40 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 | 2022-05-21 11:08:40 0 [Note] InnoDB: Buffer pool(s) load completed at 220521 11:08:40
mariadb_1 | 2022-05-21 11:08:40 3 [Warning] Aborted connection 3 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.27‘ (This connection closed normally without authentication)
mariadb_1 | 2022-05-21 11:08:40 4 [Warning] Aborted connection 4 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.26‘ (This connection closed normally without authentication)

==== Result ====

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

sorry musste die debug.log auf zwei posts aufteilen, weil zu lang.
Danke im Vorhinein für Eure Hilfe ! :pray:

LG wick3da

3

Habe nun nochmal die debug log geöffnet und nun folgendes gefunden:

Umbrel logs

= Umbrel debug info =

Umbrel version

0.4.18

Flashed OS version

v0.4.17

Raspberry Pi Model

Revision : d03115
Serial : 1000000003337d91
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=59.9’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 7.8G 1.5G 1.4G 9.0M 5.0G 6.3G
Swap: 4.1G 0B 4.1G

total: 18.6%
bitcoin: 8.3%
mempool: 2.7%
thunderhub: 2.3%
electrs: 2.1%
system: 1.7%
ride-the-lightning: 1.1%
tor: 0.4%
lnd: 0%
lightning-terminal: 0%

Memory monitor logs

1248 ? S 0:12 bash ./scripts/memory-monitor
Memory monitor is already running
2022-05-19 12:42:58 Memory monitor running!
2022-05-21 09:31:08 Memory monitor running!
2022-05-21 09:47:34 Memory monitor running!
2022-05-21 09:56:32 Memory monitor running!
1017 ? S 0:00 bash ./scripts/memory-monitor
Memory monitor is already running
2022-05-21 11:07:57 Memory monitor running!
2022-05-21 11:52:12 Memory monitor running!

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 117G 3.1G 109G 3% /
/dev/sda1 916G 521G 349G 60% /home/umbrel/umbrel

Startup service logs

May 21 11:53:40 umbrel umbrel startup[980]: Removing status server iptables entry…
May 21 11:53:40 umbrel umbrel startup[980]: Removed existing iptables entry.
May 21 11:53:40 umbrel umbrel startup[980]: Starting installed apps…
May 21 11:53:41 umbrel umbrel startup[980]: Starting app mempool…
May 21 11:53:41 umbrel umbrel startup[980]: Starting app ride-the-lightning…
May 21 11:53:41 umbrel umbrel startup[980]: Starting app thunderhub…
May 21 11:53:46 umbrel umbrel startup[980]: Creating mempool_web_1 …
May 21 11:53:46 umbrel umbrel startup[980]: Creating mempool_api_1 …
May 21 11:53:46 umbrel umbrel startup[980]: Creating mempool_mariadb_1 …
May 21 11:53:46 umbrel umbrel startup[980]: Creating thunderhub_web_1 …
May 21 11:53:47 umbrel umbrel startup[980]: Creating ride-the-lightning_boltz_1 …
May 21 11:53:47 umbrel umbrel startup[980]: Creating ride-the-lightning_loop_1 …
May 21 11:53:47 umbrel umbrel startup[980]: Creating ride-the-lightning_web_1 …
May 21 11:53:51 umbrel umbrel startup[980]: Creating thunderhub_web_1 … done
May 21 11:53:53 umbrel umbrel startup[980]: Creating ride-the-lightning_boltz_1 … done
May 21 11:53:54 umbrel umbrel startup[980]: Creating mempool_mariadb_1 … done
May 21 11:53:54 umbrel umbrel startup[980]: Creating mempool_web_1 … done
May 21 11:53:54 umbrel umbrel startup[980]: Creating ride-the-lightning_loop_1 … done
May 21 11:53:54 umbrel umbrel startup[980]: Creating mempool_api_1 … done
May 21 11:53:54 umbrel umbrel startup[980]: Creating ride-the-lightning_web_1 … done
May 21 11:53:55 umbrel umbrel startup[980]: Umbrel is now accessible at
May 21 11:53:55 umbrel umbrel startup[980]: http://umbrel.local
May 21 11:53:55 umbrel umbrel startup[980]: http://192.168.0.196
May 21 11:53:55 umbrel systemd[1]: Started Umbrel Startup Service.
May 21 11:57:00 umbrel passwd[10753]: pam_unix(passwd:chauthtok): password changed for umbrel
May 21 12:28:46 umbrel passwd[16838]: pam_unix(passwd:chauthtok): password changed for umbrel
May 21 12:30:19 umbrel passwd[18420]: pam_unix(passwd:chauthtok): password changed for umbrel
May 21 12:52:14 umbrel passwd[19814]: pam_unix(passwd:chauthtok): password changed for umbrel
May 21 12:56:50 umbrel passwd[26492]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Sat 2022-05-21 11:51:51 UTC, end at Sat 2022-05-21 13:01:49 UTC. –
May 21 11:51:56 umbrel systemd[1]: Starting External Storage Mounter…
May 21 11:51:56 umbrel external storage mounter[478]: Running external storage mount script…
May 21 11:51:56 umbrel external storage mounter[478]: Found device „JMicron Generic“
May 21 11:51:56 umbrel external storage mounter[478]: Blacklisting USB device IDs against UAS driver…
May 21 11:51:56 umbrel external storage mounter[478]: Rebinding USB drivers…
May 21 11:51:56 umbrel external storage mounter[478]: Checking USB devices are back…
May 21 11:51:56 umbrel external storage mounter[478]: Waiting for USB devices…
May 21 11:51:57 umbrel external storage mounter[478]: Waiting for USB devices…
May 21 11:51:58 umbrel external storage mounter[478]: Waiting for USB devices…
May 21 11:51:59 umbrel external storage mounter[478]: Checking if the device is ext4…
May 21 11:52:00 umbrel external storage mounter[478]: Yes, it is ext4
May 21 11:52:00 umbrel external storage mounter[478]: Checking if device contains an Umbrel install…
May 21 11:52:00 umbrel external storage mounter[478]: Yes, it contains an Umbrel install
May 21 11:52:00 umbrel external storage mounter[478]: Bind mounting external storage over local Umbrel installation…
May 21 11:52:00 umbrel external storage mounter[478]: Bind mounting external storage over local Docker data dir…
May 21 11:52:00 umbrel external storage mounter[478]: Bind mounting external storage to /swap
May 21 11:52:00 umbrel external storage mounter[478]: Bind mounting SD card root at /sd-card…
May 21 11:52:00 umbrel external storage mounter[478]: Checking Umbrel root is now on external storage…
May 21 11:52:01 umbrel external storage mounter[478]: Checking /var/lib/docker is now on external storage…
May 21 11:52:01 umbrel external storage mounter[478]: Checking /swap is now on external storage…
May 21 11:52:01 umbrel external storage mounter[478]: Setting up swapfile
May 21 11:52:03 umbrel external storage mounter[478]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 21 11:52:03 umbrel external storage mounter[478]: no label, UUID=004096bb-397a-4146-8036-faed1dece897
May 21 11:52:03 umbrel external storage mounter[478]: Checking SD Card root is bind mounted at /sd-root…
May 21 11:52:03 umbrel external storage mounter[478]: Starting external drive mount monitor…
May 21 11:52:03 umbrel external storage mounter[478]: Mount script completed successfully!
May 21 11:52:03 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Sat 2022-05-21 11:51:51 UTC, end at Sat 2022-05-21 13:01:49 UTC. –
May 21 11:52:11 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 21 11:52:11 umbrel external storage updater[902]: Checking if SD card Umbrel is newer than external storage…
May 21 11:52:12 umbrel external storage updater[902]: No, SD version is not newer, exiting.
May 21 11:52:12 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Pulling web … extracting (17.5%)
Pulling web … extracting (23.7%)
Pulling web … extracting (28.9%)
Pulling web … extracting (38.2%)
Pulling web … extracting (42.3%)
Pulling web … extracting (48.5%)
Pulling web … extracting (52.6%)
Pulling web … extracting (66.0%)
Pulling web … extracting (83.6%)
Pulling web … extracting (99.0%)
Pulling web … extracting (100.0%)
Pulling web … pull complete
Pulling web … extracting (1.0%)
Pulling web … extracting (2.0%)
Pulling web … extracting (10.2%)
Pulling web … extracting (17.3%)
Pulling web … extracting (24.5%)
Pulling web … extracting (29.6%)
Pulling web … extracting (38.8%)
Pulling web … extracting (42.9%)
Pulling web … extracting (50.0%)
Pulling web … extracting (55.1%)
Pulling web … extracting (72.4%)
Pulling web … extracting (91.8%)
Pulling web … extracting (100.0%)
Pulling web … pull complete
Pulling web … extracting (2.2%)
Pulling web … extracting (21.6%)
Pulling web … extracting (58.3%)
Pulling web … extracting (100.0%)
Pulling web … pull complete
Pulling web … digest: sha256:aba02fc2e41e9e2397…
Pulling web … status: downloaded newer image fo…
Pulling web … done
Starting app lightning-terminal…
Creating lightning-terminal_web_1 …
Creating lightning-terminal_web_1 … done
Saving app lightning-terminal in DB…
Successfully installed app lightning-terminal
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
Got signal: debug
karen is getting triggered!

Docker containers

NAMES STATUS
lightning-terminal_web_1 Restarting (1) 27 seconds ago
ride-the-lightning_web_1 Up About an hour
ride-the-lightning_loop_1 Restarting (1) 18 seconds ago
ride-the-lightning_boltz_1 Up About an hour
mempool_mariadb_1 Up About an hour
mempool_api_1 Up About an hour
thunderhub_web_1 Up About an hour
mempool_web_1 Up About an hour
middleware Up About an hour
bitcoin Up About an hour
lnd Restarting (1) 51 seconds ago
nginx Up About an hour
manager Up About an hour
umbrel_tor_server_1 Up About an hour
dashboard Up About an hour
tor Up About an hour
electrs Up About an hour

Umbrel logs

Attaching to middleware, manager
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:01:49 GMT] „GET /v1/lnd/transaction HTTP/1.0“ 500 74 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | Unable to get lnd information, failed to connect to all addresses
middleware | /v1/lnd/info/sync
middleware | LndError: Unable to get lnd information
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:01:49 GMT] „GET /v1/lnd/info/sync HTTP/1.0“ 500 67 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | LndUnlocker: Wallet failed to unlock!
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:09 GMT] „GET /v1/bitcoind/info/sync HTTP/1.0“ 200 87 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
middleware | Unable to get payments, failed to connect to all addresses
middleware | /v1/lnd/lightning/payments
middleware | LndError: Unable to get payments
middleware | at /app/services/lnd.js:69:18
middleware | at Object.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:1210:9)
middleware | at InterceptingListener._callNext (/app/node_modules/grpc/src/client_interceptors.js:568:42)
middleware | at InterceptingListener.onReceiveStatus (/app/node_modules/grpc/src/client_interceptors.js:618:8)
middleware | at callback (/app/node_modules/grpc/src/client_interceptors.js:847:24)
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:01:59 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:00 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:01 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:02 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:03 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:04 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:05 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:06 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:08 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:09 GMT] „GET /v1/lnd/lightning/payments HTTP/1.0“ 500 60 „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
middleware |
middleware | umbrel-middleware
manager |
manager | umbrel-manager
manager | ::ffff:10.21.21.2 - - [Sat, 21 May 2022 13:02:09 GMT] „GET /v1/system/debug-result HTTP/1.0“ 304 - „-“ „Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/101.0.4951.67 Safari/537.36“
manager |
manager | umbrel-manager

Bitcoin Core logs

Attaching to bitcoin
bitcoin | 2022-05-21T11:55:16Z dnsseed thread exit
bitcoin | 2022-05-21T11:55:39Z Socks5() connect to 217.146.29.67:8333 failed: general failure
bitcoin | 2022-05-21T11:55:45Z New outbound peer connected: version: 70016, blocks=737292, peer=6 (outbound-full-relay)
bitcoin | 2022-05-21T11:56:07Z New outbound peer connected: version: 70015, blocks=737292, peer=7 (outbound-full-relay)
bitcoin | 2022-05-21T11:56:28Z New outbound peer connected: version: 70016, blocks=737292, peer=8 (outbound-full-relay)
bitcoin | 2022-05-21T11:56:34Z New outbound peer connected: version: 70016, blocks=737292, peer=9 (outbound-full-relay)
bitcoin | 2022-05-21T11:56:55Z Socks5() connect to 136.169.59.165:8333 failed: connection refused
bitcoin | 2022-05-21T11:56:59Z New outbound peer connected: version: 70016, blocks=737292, peer=12 (outbound-full-relay)
bitcoin | 2022-05-21T11:57:00Z New outbound peer connected: version: 70016, blocks=737292, peer=13 (outbound-full-relay)
bitcoin | 2022-05-21T11:58:29Z New outbound peer connected: version: 70016, blocks=737292, peer=14 (outbound-full-relay)
bitcoin | 2022-05-21T12:04:17Z UpdateTip: new best=00000000000000000008b2252f8e9c57dd84e82fae05367f00d71905d7b55152 height=737293 version=0x3fffe004 log2_work=93.531379 tx=735330171 date=‚2022-05-21T12:03:01Z‘ progress=1.000000 cache=2.1MiB(15440txo)
bitcoin | 2022-05-21T12:11:44Z New outbound peer connected: version: 70016, blocks=737293, peer=15 (block-relay-only)
bitcoin | 2022-05-21T12:15:11Z New outbound peer connected: version: 70016, blocks=737293, peer=16 (block-relay-only)
bitcoin | 2022-05-21T12:16:32Z New outbound peer connected: version: 70016, blocks=737293, peer=17 (block-relay-only)
bitcoin | 2022-05-21T12:17:41Z New outbound peer connected: version: 70016, blocks=737293, peer=18 (block-relay-only)
bitcoin | 2022-05-21T12:18:24Z Socks5() connect to 15.164.203.130:8333 failed: general failure
bitcoin | 2022-05-21T12:18:31Z Socks5() connect to 15.164.203.130:8333 failed: general failure
bitcoin | 2022-05-21T12:19:06Z Socks5() connect to 15.164.203.130:8333 failed: general failure
bitcoin | 2022-05-21T12:26:12Z UpdateTip: new best=00000000000000000005d33f374003ecd3b535159eed292c489fab93b96d069d height=737294 version=0x2000e000 log2_work=93.531393 tx=735332886 date=‚2022-05-21T12:25:47Z‘ progress=1.000000 cache=4.3MiB(31366txo)
bitcoin | 2022-05-21T12:32:24Z Socks5() connect to 149.56.20.200:8333 failed: general failure
bitcoin | 2022-05-21T12:33:19Z Socks5() connect to 162.247.72.199:8333 failed: connection refused
bitcoin | 2022-05-21T12:34:32Z Socks5() connect to 104.197.37.54:8333 failed: general failure
bitcoin | 2022-05-21T12:35:32Z UpdateTip: new best=000000000000000000026cf8935f3e5ec7a53ed6a483f9dad1314367be60639a height=737295 version=0x20000004 log2_work=93.531406 tx=735335291 date=‚2022-05-21T12:34:15Z‘ progress=1.000000 cache=5.6MiB(41661txo)
bitcoin | 2022-05-21T12:43:19Z New outbound peer connected: version: 70016, blocks=737295, peer=24 (block-relay-only)
bitcoin | 2022-05-21T12:45:47Z New outbound peer connected: version: 70016, blocks=737295, peer=25 (block-relay-only)
bitcoin | 2022-05-21T12:50:44Z Socks5() connect to 2607:fa49:3442:cd00::1324:8333 failed: general failure
bitcoin | 2022-05-21T12:56:12Z New outbound peer connected: version: 70016, blocks=737295, peer=26 (block-relay-only)
bitcoin | 2022-05-21T12:58:37Z New outbound peer connected: version: 70015, blocks=737295, peer=27 (outbound-full-relay)
bitcoin | 2022-05-21T12:58:42Z New outbound peer connected: version: 70016, blocks=737295, peer=28 (outbound-full-relay)
bitcoin | 2022-05-21T13:00:03Z Socks5() connect to 136.49.226.4:8333 failed: general failure

LND logs

Attaching to lnd
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly. Any)
lnd | failed to load config: /data/.lnd/lnd.conf:1: malformed key=value (Warning: it’s not recommended to modify these files directly.

keine Ahnung was beim reboot passiert ist, aber ich glaube einfach abwarten wird mein Problem nicht lösen.
Habe mich auch schon durch diverse Foreneinträge durchgearbeitet, aber da ich mich nicht wirklich auskenne, möchte ich das ganze nicht noch schlimmer machen, als es schon ist.

Hat irgendjemand einen Tipp für mich, wie ich die Node wieder zum Laufen bringe ??

Danke und LG

4

Update:
konnte das Problem selbst lösen - anscheinend hat sich ein Fehler in meine lnd.conf eingeschlichen. Nun läuft wieder alles.

Bitte den Beitrag schließen :sweat_smile:

LG
wick3da