Umbrel hängt fest

Hallo zusammen,
habe eine kurze Frage. Seit heute funktioniert bei Umbrel leider nichts mehr. habe auch schon neu gestartet aber nichts hilft. was kann ich sonst unternehmen?

LG

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

Umbrel version

0.3.10

Umbrel OS version

v0.3.8

Raspberry Pi Model

Revision : c03112
Serial : 100000005643313c
Model : Raspberry Pi 4 Model B Rev 1.2

Firmware

Feb 25 2021 12:10:40
Copyright (c) 2012 Broadcom
version 564e5f9b852b23a330b1764bcf0b2d022a20afd0 (clean) (release) (start)

Temperature

temp=41.3’C

Throttling

throttled=0x0

Memory usage

          total        used        free      shared  buff/cache   available

Mem: 3.8G 1.3G 1.4G 9.0M 1.1G 2.7G
Swap: 4.1G 0B 4.1G

total: 34.7%
mempool: 15.5%
lnd: 10.8%
thunderhub: 2.6%
ride-the-lightning: 1.9%
lightning-terminal: 1.6%
system: 1.3%
tor: 0.9%
electrs: 0.1%
bitcoin: 0%

Filesystem information

Filesystem Size Used Avail Use% Mounted on
/dev/root 59G 6.7G 50G 12% /
/dev/sda1 916G 484G 386G 56% /home/umbrel/umbrel

Startup service logs

May 08 19:10:26 umbrel umbrel startup[1021]: Creating bitcoin … done
May 08 19:10:26 umbrel umbrel startup[1021]: Creating middleware …
May 08 19:10:26 umbrel umbrel startup[1021]: Creating neutrino-switcher …
May 08 19:10:29 umbrel umbrel startup[1021]: Creating neutrino-switcher … done
May 08 19:10:29 umbrel umbrel startup[1021]: Creating middleware … done
May 08 19:10:29 umbrel umbrel startup[1021]: Starting installed apps…
May 08 19:10:29 umbrel umbrel startup[1021]: Starting app lightning-terminal…
May 08 19:10:32 umbrel umbrel startup[1021]: Creating lightning-terminal_web_1 …
May 08 19:10:48 umbrel umbrel startup[1021]: Creating lightning-terminal_web_1 … done
May 08 19:10:49 umbrel umbrel startup[1021]: Starting app mempool…
May 08 19:10:53 umbrel umbrel startup[1021]: Creating mempool_api_1 …
May 08 19:10:53 umbrel umbrel startup[1021]: Creating mempool_web_1 …
May 08 19:10:53 umbrel umbrel startup[1021]: Creating mempool_mariadb_1 …
May 08 19:10:56 umbrel umbrel startup[1021]: Creating mempool_mariadb_1 … done
May 08 19:10:56 umbrel umbrel startup[1021]: Creating mempool_api_1 … done
May 08 19:10:56 umbrel umbrel startup[1021]: Creating mempool_web_1 … done
May 08 19:10:56 umbrel umbrel startup[1021]: Starting app ride-the-lightning…
May 08 19:10:59 umbrel umbrel startup[1021]: Creating ride-the-lightning_loop_1 …
May 08 19:10:59 umbrel umbrel startup[1021]: Creating ride-the-lightning_web_1 …
May 08 19:11:01 umbrel umbrel startup[1021]: Creating ride-the-lightning_loop_1 … done
May 08 19:11:01 umbrel umbrel startup[1021]: Creating ride-the-lightning_web_1 … done
May 08 19:11:01 umbrel umbrel startup[1021]: Starting app thunderhub…
May 08 19:11:04 umbrel umbrel startup[1021]: Creating thunderhub_web_1 …
May 08 19:11:06 umbrel umbrel startup[1021]: Creating thunderhub_web_1 … done
May 08 19:11:07 umbrel umbrel startup[1021]: Umbrel is now accessible at
May 08 19:11:07 umbrel umbrel startup[1021]: http://umbrel.local
May 08 19:11:07 umbrel umbrel startup[1021]: http://192.168.0.110
May 08 19:11:07 umbrel systemd[1]: Started Umbrel Startup Service.
May 08 19:12:03 umbrel passwd[7181]: pam_unix(passwd:chauthtok): password changed for umbrel

External storage service logs

– Logs begin at Sat 2021-05-08 19:09:59 UTC, end at Sat 2021-05-08 19:12:03 UTC. –
May 08 19:10:02 umbrel systemd[1]: Starting External Storage Mounter…
May 08 19:10:02 umbrel external storage mounter[349]: Running external storage mount script…
May 08 19:10:02 umbrel external storage mounter[349]: Found device „ASMT 2115“
May 08 19:10:02 umbrel external storage mounter[349]: Blacklisting USB device IDs against UAS driver…
May 08 19:10:02 umbrel external storage mounter[349]: Rebinding USB drivers…
May 08 19:10:03 umbrel external storage mounter[349]: Checking USB devices are back…
May 08 19:10:03 umbrel external storage mounter[349]: Waiting for USB devices…
May 08 19:10:04 umbrel external storage mounter[349]: Waiting for USB devices…
May 08 19:10:05 umbrel external storage mounter[349]: Checking if the device is ext4…
May 08 19:10:05 umbrel external storage mounter[349]: Yes, it is ext4
May 08 19:10:05 umbrel external storage mounter[349]: Checking if device contains an Umbrel install…
May 08 19:10:05 umbrel external storage mounter[349]: Yes, it contains an Umbrel install
May 08 19:10:05 umbrel external storage mounter[349]: Bind mounting external storage over local Umbrel installation…
May 08 19:10:05 umbrel external storage mounter[349]: Bind mounting external storage over local Docker data dir…
May 08 19:10:05 umbrel external storage mounter[349]: Bind mounting external storage to /swap
May 08 19:10:05 umbrel external storage mounter[349]: Bind mounting SD card root at /sd-card…
May 08 19:10:05 umbrel external storage mounter[349]: Checking Umbrel root is now on external storage…
May 08 19:10:06 umbrel external storage mounter[349]: Checking /var/lib/docker is now on external storage…
May 08 19:10:06 umbrel external storage mounter[349]: Checking /swap is now on external storage…
May 08 19:10:06 umbrel external storage mounter[349]: Setting up swapfile
May 08 19:10:06 umbrel external storage mounter[349]: Setting up swapspace version 1, size = 4 GiB (4294963200 bytes)
May 08 19:10:06 umbrel external storage mounter[349]: no label, UUID=c8c86524-a44d-4895-936c-ab969ea50dec
May 08 19:10:06 umbrel external storage mounter[349]: Checking SD Card root is bind mounted at /sd-root…
May 08 19:10:06 umbrel external storage mounter[349]: Starting external drive mount monitor…
May 08 19:10:06 umbrel external storage mounter[349]: Mount script completed successfully!
May 08 19:10:06 umbrel systemd[1]: Started External Storage Mounter.

External storage SD card update service logs

– Logs begin at Sat 2021-05-08 19:09:59 UTC, end at Sat 2021-05-08 19:12:03 UTC. –
May 08 19:10:15 umbrel systemd[1]: Starting External Storage SDcard Updater…
May 08 19:10:15 umbrel external storage updater[944]: Checking if SD card Umbrel is newer than external storage…
May 08 19:10:16 umbrel external storage updater[944]: No, SD version is not newer, exiting.
May 08 19:10:16 umbrel systemd[1]: Started External Storage SDcard Updater.

Karen logs

Stopping app thunderhub…
Stopping thunderhub_web_1 …

Stopping thunderhub_web_1 … done

Removing thunderhub_web_1 …

Removing thunderhub_web_1 … done

Going to remove thunderhub_web_1

Stopping Docker services…

Stopping middleware …

Stopping bitcoin …

Stopping nginx …

Stopping lnd …

Stopping manager …

Stopping tor …

Stopping dashboard …

Stopping electrs …

Stopping electrs … done

Stopping middleware … done

Stopping bitcoin … done

Stopping nginx … done

Stopping lnd … done

Stopping dashboard … done

Stopping manager … done

Stopping tor … done

Removing middleware …

Removing neutrino-switcher …

Removing bitcoin …

Removing nginx …

Removing lnd …

Removing manager …

Removing tor …

Removing dashboard …

Removing electrs …

Removing lnd … done

Removing electrs … done

Removing nginx … done

Removing manager … done

Removing bitcoin … done

Removing middleware … done

Removing neutrino-switcher … done

Removing dashboard … done

Removing tor … done

Removing network umbrel_main_network
karen is running in /home/umbrel/umbrel/events
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
thunderhub_web_1 Up About a minute
ride-the-lightning_web_1 Up About a minute
ride-the-lightning_loop_1 Up About a minute
mempool_web_1 Up About a minute
mempool_mariadb_1 Up About a minute
mempool_api_1 Up About a minute
lightning-terminal_web_1 Up About a minute
middleware Up 2 minutes
bitcoin Restarting (1) 50 seconds ago
nginx Up 2 minutes
lnd Up 2 minutes
manager Up 2 minutes
dashboard Up 2 minutes
tor Up 2 minutes
electrs Up 2 minutes

Bitcoin Core logs

Attaching to bitcoin
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |
bitcoin | Error: Failed loading settings file:
bitcoin | - Unable to parse settings file /data/.bitcoin/settings.json
bitcoin |

LND logs

Attaching to lnd
lnd | 2021-05-08 19:10:25.600 [INF] LTND: Version: 0.12.1-beta commit=v0.12.1-beta, build=production, logging=default, debuglevel=info
lnd | 2021-05-08 19:10:25.601 [INF] LTND: Active chain: Bitcoin (network=mainnet)
lnd | 2021-05-08 19:10:25.601 [INF] LTND: Opening the main database, this might take a few minutes…
lnd | 2021-05-08 19:10:25.601 [INF] LTND: Opening bbolt database, sync_freelist=false, auto_compact=false
lnd | 2021-05-08 19:10:53.330 [INF] CHDB: Checking for schema update: latest_version=20, db_version=20
lnd | 2021-05-08 19:10:53.331 [INF] LTND: Database now open (time_to_open=14.20589375s)!
lnd | 2021-05-08 19:10:53.381 [INF] RPCS: Password gRPC proxy started at 0.0.0.0:8080
lnd | 2021-05-08 19:10:53.384 [INF] RPCS: Password RPC server listening on 0.0.0.0:10009
lnd | 2021-05-08 19:10:53.386 [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.

Tor logs

Attaching to tor
tor | May 08 19:10:21.000 [notice] Bootstrapped 0% (starting): Starting
tor | May 08 19:10:21.000 [notice] Starting with guard context „default“
tor | May 08 19:10:22.000 [notice] Bootstrapped 5% (conn): Connecting to a relay
tor | May 08 19:10:22.000 [notice] Bootstrapped 10% (conn_done): Connected to a relay
tor | May 08 19:10:22.000 [notice] Bootstrapped 14% (handshake): Handshaking with a relay
tor | May 08 19:10:22.000 [notice] Bootstrapped 15% (handshake_done): Handshake with a relay done
tor | May 08 19:10:22.000 [notice] Bootstrapped 20% (onehop_create): Establishing an encrypted directory connection
tor | May 08 19:10:22.000 [notice] Bootstrapped 25% (requesting_status): Asking for networkstatus consensus
tor | May 08 19:10:22.000 [notice] Bootstrapped 30% (loading_status): Loading networkstatus consensus
tor | May 08 19:10:23.000 [notice] I learned some more directory information, but not enough to build a circuit: We have no usable consensus.
tor | May 08 19:10:23.000 [notice] Bootstrapped 40% (loading_keys): Loading authority key certs
tor | May 08 19:10:24.000 [notice] Bootstrapped 45% (requesting_descriptors): Asking for relay descriptors
tor | May 08 19:10:24.000 [notice] I learned some more directory information, but not enough to build a circuit: We need more microdescriptors: we have 0/6578, and can only build 0% of likely paths. (We have 0% of guards bw, 0% of midpoint bw, and 0% of end bw (no exits in consensus, using mid) = 0% of path bw.)
tor | May 08 19:10:24.000 [notice] Bootstrapped 50% (loading_descriptors): Loading relay descriptors
tor | May 08 19:10:24.000 [notice] The current consensus contains exit nodes. Tor can build exit and internal paths.
tor | May 08 19:10:25.000 [notice] Bootstrapped 55% (loading_descriptors): Loading relay descriptors
tor | May 08 19:10:26.000 [notice] Bootstrapped 63% (loading_descriptors): Loading relay descriptors
tor | May 08 19:10:26.000 [notice] Bootstrapped 68% (loading_descriptors): Loading relay descriptors
tor | May 08 19:10:27.000 [notice] Bootstrapped 75% (enough_dirinfo): Loaded enough directory info to build circuits
tor | May 08 19:10:28.000 [notice] Bootstrapped 80% (ap_conn): Connecting to a relay to build circuits
tor | May 08 19:10:28.000 [notice] Bootstrapped 85% (ap_conn_done): Connected to a relay to build circuits
tor | May 08 19:10:28.000 [notice] Bootstrapped 89% (ap_handshake): Finishing handshake with a relay to build circuits
tor | May 08 19:10:28.000 [notice] Bootstrapped 90% (ap_handshake_done): Handshake finished with a relay to build circuits
tor | May 08 19:10:28.000 [notice] Bootstrapped 95% (circuit_create): Establishing a Tor circuit
tor | May 08 19:10:28.000 [notice] Bootstrapped 100% (done): Done
tor | May 08 19:10:51.000 [warn] Guard x23tor89 ($68953B4A234966515C2F296A402448A0FE5D39E8) is failing an extremely large amount of circuits. This could indicate a route manipulation attack, extreme network overload, or a bug. Success counts are 1/151. Use counts are 0/0. 1 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | May 08 19:10:51.000 [warn] Guard x23tor89 ($68953B4A234966515C2F296A402448A0FE5D39E8) 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 62/171. Use counts are 53/53. 62 circuits completed, 0 were unusable, 0 collapsed, and 0 timed out. For reference, your timeout cutoff is 60 seconds.
tor | May 08 19:11:12.000 [notice] Your network connection speed appears to have changed. Resetting timeout to 60s after 18 timeouts and 177 buildtimes.
tor | May 08 19:11:13.000 [notice] Guard x23tor89 ($68953B4A234966515C2F296A402448A0FE5D39E8) is failing more circuits than usual. Most likely this means the Tor network is overloaded. Success counts are 172/246. Use counts are 107/107. 172 circuits completed, 0 were unusable, 0 collapsed, and 4 timed out. For reference, your timeout cutoff is 60 seconds.

App logs

lightning-terminal

Attaching to lightning-terminal_web_1
web_1 | 2021-05-08 19:10:49.667 [INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
web_1 | 2021-05-08 19:10:49.680 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = „transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused“. Reconnecting…
web_1 | 2021-05-08 19:10:50.571 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
web_1 | 2021-05-08 19:10:50.572 [INF] LITD: Listening for http on: [::]:3004
web_1 | 2021-05-08 19:10:50.577 [WRN] GRPC: grpc: addrConn.createTransport failed to connect to {10.21.21.9:10009 0 }. Err: connection error: desc = „transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused“. Reconnecting…
web_1 | 2021-05-08 19:10:50.578 [INF] SGNL: Received shutdown request.
web_1 | error displaying startup info: error querying remote node : rpc error: code = Unavailable desc = connection error: desc = „transport: Error while dialing dial tcp 10.21.21.9:10009: connect: connection refused“
web_1 | 2021-05-08 19:10:54.595 [INF] LITD: Dialing lnd gRPC server at 10.21.21.9:10009
web_1 | 2021-05-08 19:10:55.287 [INF] LITD: Listening for http_tls on: 127.0.0.1:8443
web_1 | 2021-05-08 19:10:55.288 [INF] LITD: Listening for http on: [::]:3004
web_1 | ----------------------------------------------------------
web_1 | Lightning Terminal (LiT) by Lightning Labs
web_1 |
web_1 | Operating mode remote
web_1 | Node status locked
web_1 | Alias ??? (node is locked)
web_1 | Version 0.12.1-beta
web_1 | Web interface https://127.0.0.1:8443, http://localhost:3004
web_1 | ----------------------------------------------------------
web_1 | 2021-05-08 19:10:55.508 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
web_1 | 2021-05-08 19:10:55.509 [INF] LNDC: Connected to lnd
web_1 | 2021-05-08 19:10:55.509 [INF] LNDC: Waiting for lnd to unlock

mempool

api_1 | May 8 19:12:42 [38] INFO: Disconnected from Electrum Server at 10.21.21.10:50001
api_1 | May 8 19:12:43 [38] WARN: runMainLoop error: connect EHOSTUNREACH 10.21.21.8:8332. Retrying in 60 sec.
api_1 | May 8 19:12:43 [38] DEBUG: {„errno“:„EHOSTUNREACH“,„code“:„EHOSTUNREACH“,„syscall“:„connect“,„address“:„10.21.21.8“,„port“:8332}
mariadb_1 | 2021-05-08 19:10:56+00:00 [Note] [Entrypoint]: Entrypoint script for MySQL Server 1:10.5.8+maria~focal started.
mariadb_1 | 2021-05-08 19:10:57 0 [Note] mysqld (mysqld 10.5.8-MariaDB-1:10.5.8+maria~focal) starting as process 1 …
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Using Linux native AIO
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Uses event mutexes
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Compressed tables use zlib 1.2.11
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Number of pools: 1
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Using ARMv8 crc32 instructions
mariadb_1 | 2021-05-08 19:10:57 0 [Note] mysqld: O_TMPFILE is not supported on /tmp (disabling future attempts)
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Initializing buffer pool, total size = 134217728, chunk size = 134217728
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Completed initialization of buffer pool
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: If the mysqld execution user is authorized, page cleaner thread priority can be changed. See the man page of setpriority().
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: 128 rollback segments are active.
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Creating shared tablespace for temporary tables
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Setting file ‚./ibtmp1‘ size to 12 MB. Physically writing the file full; Please wait …
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: File ‚./ibtmp1‘ size is now 12 MB.
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: 10.5.8 started; log sequence number 10150041; transaction id 54663
mariadb_1 | 2021-05-08 19:10:57 0 [Note] Plugin ‚FEEDBACK‘ is disabled.
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Loading buffer pool(s) from /var/lib/mysql/ib_buffer_pool
mariadb_1 | 2021-05-08 19:10:57 0 [Note] Server socket created on IP: ‚::‘.
mariadb_1 | 2021-05-08 19:10:57 0 [Warning] ‚proxies_priv‘ entry ‚@% root@930e4f3984dd‘ ignored in --skip-name-resolve mode.
mariadb_1 | 2021-05-08 19:10:57 0 [Note] InnoDB: Buffer pool(s) load completed at 210508 19:10:57
mariadb_1 | 2021-05-08 19:10:57 0 [Note] Reading of all Master_info entries succeeded
mariadb_1 | 2021-05-08 19:10:57 0 [Note] Added new Master_info ‚‘ to hash table
mariadb_1 | 2021-05-08 19:10:57 0 [Note] mysqld: ready for connections.
mariadb_1 | Version: ‚10.5.8-MariaDB-1:10.5.8+maria~focal‘ socket: ‚/run/mysqld/mysqld.sock‘ port: 3306 mariadb.org binary distribution
mariadb_1 | 2021-05-08 19:10:57 3 [Warning] Aborted connection 3 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.26‘ (This connection closed normally without authentication)
mariadb_1 | 2021-05-08 19:10:58 4 [Warning] Aborted connection 4 to db: ‚unconnected‘ user: ‚unauthenticated‘ host: ‚10.21.21.27‘ (This connection closed normally without authentication)

ride-the-lightning

Attaching to ride-the-lightning_web_1, ride-the-lightning_loop_1
loop_1 | 2021-05-08 19:11:01.616 [INF] LOOPD: Version: 0.12.1-beta commit=
loop_1 | 2021-05-08 19:11:01.627 [INF] LNDC: Creating lnd connection to 10.21.21.9:10009
loop_1 | 2021-05-08 19:11:01.639 [INF] LNDC: Connected to lnd
loop_1 | 2021-05-08 19:11:01.639 [INF] LNDC: Waiting for lnd to unlock
web_1 | Server is up and running, please open the UI at http://localhost:3001

thunderhub

Attaching to thunderhub_web_1
web_1 |
web_1 | > thunderhub@0.12.14 start /app
web_1 | > next start
web_1 |
web_1 | ready - started server on 0.0.0.0:3000, url: http://localhost:3000

==== Result ====

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

Grüße,

auch ich habe so Problem, die Node will sich nicht synchronisieren.
Kann jemand hier zu Hilfe geben? Bitte und besten Dank in voraus.


![grafik|453x500]
(upload://riSYT0MVB7sSlMv6G4AzcJFgluv.png)


Frag am besten mal @Aaron. Der dürfte die helfen können.

Meine hing auch neulich. Ich hab die SD Karte neu geflasht und jetzt geht sie wieder. Und ich hab den Raspi nun nicht mehr über WLAN sondern nur über LAN angeschlossen. Vllt hilft dir das weiter.

Danke für den Tipp. Meine umbrel hängt jetzt auch mit LAN dran. Sie ging zb. Gestern wieder. Jetzt grade kann ich sie nicht mehr über Browser erreichen. Außer dem will sie nicht fertig Synchronisieren. Das ist alles so zermürbend auf die Dauer. :woozy_face: Ich spiele schon mit den Gedanken jetzt echt auf Raspibliz zu wechseln. In der Hoffnung das es besser läuft.