ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme
-
das Ergebnis vom (alten) Pi:
Copy text starting here: ======================= SUMMARY ======================= v.2023-10-10 /home/iobroker/.diag.sh: line 457: hostnamectl: command not found Installation: Kernel: armv7l Userland: armhf /home/iobroker/.diag.sh: line 466: timedatectl: command not found Timezone: User-ID: 1001 X-Server: false /home/iobroker/.diag.sh: line 473: systemctl: command not found Boot Target: Pending OS-Updates: 60 error: failed switching to "iobroker": operation not permitted Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.17.1 /usr/bin/node v18.17.1 /usr/bin/npm 9.6.7 /usr/bin/npx 9.6.7 /usr/bin/corepack 0.18.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 1.9G 4.9G 1.0M 1.1G 5.8G Swap: 99M 0B 99M Total: 8.0G 1.9G 5.0G error: failed switching to "iobroker": operation not permitted Active iob-Instances: 0 error: failed switching to "iobroker": operation not permitted error: failed switching to "iobroker": operation not permitted ioBroker Core: js-controller error: failed switching to "iobroker": operation not permitted admin error: failed switching to "iobroker": operation not permitted ioBroker Status: Status admin and web instance: error: failed switching to "iobroker": operation not permitted Objects: 0 States: 0 Size of iob-Database: 40M /opt/iobroker/iobroker-data/objects.jsonl 17M /opt/iobroker/iobroker-data/objects.json.migrated 17M /opt/iobroker/iobroker-data/objects.json.bak.migrated 16K /opt/iobroker/iobroker-data/objects.json.old 31M /opt/iobroker/iobroker-data/states.jsonl 2.3M /opt/iobroker/iobroker-data/states.json.migrated 2.3M /opt/iobroker/iobroker-data/states.json.bak.migrated 2.0M /opt/iobroker/iobroker-data/states.json.old =================== END OF SUMMARY ==================== === Mark text until here for copying === -
Der muss aber sehr alt sein, wenn die Kommandos da gar nicht funktionieren.
-
@thomas-braun
leider, ich gelobe Besserung.
Hatte wohl meist nur die iob updates gemacht -.-bei
sudo apt updatespuckt er mir direkt eine Fehlermeldung wegen eines key´s raus.
idash@raspberrypi:/opt/iobroker$ sudo apt update [sudo] password for idash: Hit:1 http://security.debian.org/debian-security buster/updates InRelease Hit:2 http://deb.debian.org/debian buster InRelease Hit:3 http://deb.debian.org/debian buster-updates InRelease Get:4 https://repos.influxdata.com/debian buster InRelease [7.047 B] Get:5 https://deb.nodesource.com/node_18.x buster InRelease [4.584 B] Err:4 https://repos.influxdata.com/debian buster InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E Fetched 11,6 kB in 2s (5.507 B/s) Reading package lists... Done Building dependency tree Reading state information... Done 60 packages can be upgraded. Run 'apt list --upgradable' to see them. W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://repos.influxdata.com/debian buster InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: Failed to fetch https://repos.influxdata.com/debian/dists/buster/InRelease The following signatures couldn't be verified because the public key is not available: NO_PUBKEY D8FF8E1F7DF8B07E W: Some index files failed to download. They have been ignored, or old ones used instead. idash@raspberrypi:/opt/iobroker$Daher ersteinmal nicht weiter gemacht.
-
@gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:
Fehlermeldung wegen eines key´s raus.
Findest du Anleitung auf Thomas Profil
Oder du kommentierst sie einfach aus in der repo list, brauchst ja eigentlich nimmer. Dann würden zumindest die updates für buster durchlaufenAllerdings sieht deine Ausgabe von diag nicht gerade prickelnd aus
-
@crunchip
die Anleitung auf Bullyseye hatte ich mir abgespeichert, hatte damit ja den Pi direkt gemacht xD
Aber wo finde ich diese Reprolist zum auskommentieren?
ah, evtl. mit der "apt list" -
@gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:
Aber wo finde ich diese Reprolist zum auskommentieren?
Lösch einfach die entsprechende Datei aus
/etc/apt/sources.list.d/ heraus. Heißt influx... -
@thomas-braun
konnte noch eben den key erneuern - war für mich einfacher. -
@thomas-braun
Frage: beim upgrade von buster auf bullseye, aus deiner Anleitung:
sudo nano /etc/systemd/system/dhcpcd.service.d/wait.conf
Die Datei gibt es bei mir anscheinen nicht.Mein "Ergebnis" sieht so aus:
idash@raspberrypi:/opt/iobroker$ sudo apt update [sudo] password for idash: Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 https://repos.influxdata.com/debian stable InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Hit:6 https://deb.nodesource.com/node_18.x bullseye InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. -
@gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:
Die Datei gibt es bei mir anscheinen nicht.
Muss es ja auch nicht. Der Part ist doch nur optional bei Problemen, wenn ich mich recht entsinne.
Influxdb ist allerdings doppelt angelegt.
Und nodesource ist nicht um aktuellen Format. -
@thomas-braun
okay, super & Merci.
Dann mache ich mal weiter
Edit: Muss ich bei der Influx noch was machen, irgendwie eine löschen?
Ist ja die Maschine, welche abgelöst werden soll.Nach nodesoure suche ich dann. (evtl. in deinem Footer)
-
@gismoh sagte in ioBroker auf neuer Maschine aufgesetzt und Adapter Probleme:
Nach nodesoure suche ich dann. (evtl. in deinem Footer)
iob nodejs-updaterichtet das.
-
@thomas-braun merci
-
@crunchip
die Ausgabe von iob diag vom Raspi:======== Start marking the full check here ========= Skript v.2023-10-10 *** BASE SYSTEM *** /home/iobroker/.diag.sh: line 63: hostnamectl: command not found Model : Raspberry Pi 4 Model B Rev 1.4 Docker : false Virtualization : Docker Kernel : armv7l Userland : armhf Systemuptime and Load: 20:12:13 up 20:35, 0 users, load average: 1.81, 1.87, 1.93 CPU threads: 4 *** Time and Time Zones *** /home/iobroker/.diag.sh: line 188: timedatectl: command not found *** User and Groups *** idash /home/idash idash adm dialout sudo plugdev input iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: /home/iobroker/.diag.sh: line 211: systemctl: command not found Boot Target: *** MEMORY *** total used free shared buff/cache available Mem: 7.9G 2.0G 3.6G 1.0M 2.3G 5.7G Swap: 99M 0B 99M Total: 8.0G 2.0G 3.7G 7898 M total memory 1955 M used memory 591 M active memory 3477 M inactive memory 3593 M free memory 227 M buffer memory 2121 M swap cache 99 M total swap 0 M used swap 99 M free swap *** FAILED SERVICES *** /home/iobroker/.diag.sh: line 232: systemctl: command not found *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on overlay overlay 59G 44G 13G 78% / tmpfs tmpfs 64M 0 64M 0% /dev shm tmpfs 64M 0 64M 0% /dev/shm /dev/root ext4 59G 44G 13G 78% /etc/influxdb tmpfs tmpfs 3.9G 0 3.9G 0% /proc/asound tmpfs tmpfs 3.9G 0 3.9G 0% /sys/firmware Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS /etc/influxdb /dev/root[/home/pi/influxdb/etc] ext4 rw,noatime /opt/iobroker /dev/root[/home/pi/iobroker] ext4 rw,noatime /etc/resolv.conf /dev/root[/var/lib/docker/containers/44cf01325e4af5b67c1ceefebfdd8ba53b8d1413acb411091f6e943bb11cf1cc/resolv.conf] ext4 rw,noatime /etc/hostname /dev/root[/var/lib/docker/containers/44cf01325e4af5b67c1ceefebfdd8ba53b8d1413acb411091f6e943bb11cf1cc/hostname] ext4 rw,noatime /etc/hosts /dev/root[/var/lib/docker/containers/44cf01325e4af5b67c1ceefebfdd8ba53b8d1413acb411091f6e943bb11cf1cc/hosts] ext4 rw,noatime /var/lib/influxdb /dev/root[/home/pi/influxdb/database] ext4 rw,noatime Files in neuralgic directories: /var: 27G /var/log/influxdb 27G /var/log 27G /var/ 563M /var/lib 532M /var/lib/influxdb /home/iobroker/.diag.sh: line 256: journalctl: command not found /opt/iobroker/backups: 4.6G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 460M /opt/iobroker/iobroker-data/ 216M /opt/iobroker/iobroker-data/files 117M /opt/iobroker/iobroker-data/backup-objects 52M /opt/iobroker/iobroker-data/files/javascript.admin 43M /opt/iobroker/iobroker-data/files/iot.admin The five largest files in iobroker-data are: 56M /opt/iobroker/iobroker-data/states.jsonl 33M /opt/iobroker/iobroker-data/objects.jsonl 33M /opt/iobroker/iobroker-data/files/iot.admin/static/js/main.1797d034.js.map 21M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.aaea95f8.js.map 17M /opt/iobroker/iobroker-data/objects.json.migrated USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': find: '/dev/serial/by-id/': No such file or directory *** NodeJS-Installation *** /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 nodejs: Installed: 18.18.2-1nodesource1 Candidate: 18.18.2-1nodesource1 Version table: *** 18.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 100 /var/lib/dpkg/status 18.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.2-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.1-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 18.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_18.x nodistro/main armhf Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main armhf Packages 500 http://security.debian.org/debian-security bullseye-security/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status error: failed switching to "iobroker": operation not permitted Core adapters versions error: failed switching to "iobroker": operation not permitted js-controller: error: failed switching to "iobroker": operation not permitted admin: error: failed switching to "iobroker": operation not permitted javascript: Adapters from github: 0 Adapter State error: failed switching to "iobroker": operation not permitted Enabled adapters with bindings error: failed switching to "iobroker": operation not permitted ioBroker-Repositories error: failed switching to "iobroker": operation not permitted Installed ioBroker-Instances error: failed switching to "iobroker": operation not permitted Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bullseye InRelease Hit:2 http://deb.debian.org/debian bullseye-updates InRelease Hit:3 http://security.debian.org/debian-security bullseye-security InRelease Hit:4 https://repos.influxdata.com/debian stable InRelease Hit:5 https://repos.influxdata.com/debian bullseye InRelease Hit:6 https://deb.nodesource.com/node_18.x nodistro InRelease Reading package lists... Pending Updates: 0 *** Listening Ports *** Active Internet connections (only servers) Proto Recv-Q Send-Q Local Address Foreign Address State User Inode PID/Program name tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 0 15514 - tcp 0 0 0.0.0.0:8080 0.0.0.0:* LISTEN 0 15008 - tcp 0 0 127.0.0.1:8085 0.0.0.0:* LISTEN 999 2436546 - tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 14375 - tcp 0 0 0.0.0.0:8088 0.0.0.0:* LISTEN 1000 18530 - tcp 0 0 0.0.0.0:1882 0.0.0.0:* LISTEN 1000 2441321 - tcp 0 0 0.0.0.0:8090 0.0.0.0:* LISTEN 1000 18488 - tcp 0 0 0.0.0.0:1883 0.0.0.0:* LISTEN 1000 2440287 - tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 0 11086 - tcp 0 0 0.0.0.0:8000 0.0.0.0:* LISTEN 0 14150 - tcp 0 0 0.0.0.0:9443 0.0.0.0:* LISTEN 0 11047 - tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 2438513 - tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 2436579 - tcp6 0 0 :::80 :::* LISTEN 0 15519 - tcp6 0 0 :::8080 :::* LISTEN 0 11055 - tcp6 0 0 :::8081 :::* LISTEN 1000 2436746 - tcp6 0 0 :::8082 :::* LISTEN 1000 2441021 - tcp6 0 0 :::8084 :::* LISTEN 1000 2441982 - tcp6 0 0 :::8086 :::* LISTEN 999 2438510 - tcp6 0 0 :::22 :::* LISTEN 0 11950 - tcp6 0 0 :::3000 :::* LISTEN 472 16567 - tcp6 0 0 :::443 :::* LISTEN 0 15028 - tcp6 0 0 :::8000 :::* LISTEN 0 11093 - tcp6 0 0 :::9443 :::* LISTEN 0 15468 - tcp6 0 0 :::61991 :::* LISTEN 1000 2443739 - udp 0 0 0.0.0.0:33747 0.0.0.0:* 108 10203 - udp 0 0 0.0.0.0:61991 0.0.0.0:* 1000 2443740 - udp 0 0 0.0.0.0:5683 0.0.0.0:* 1000 2438877 - udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12019 - udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 10201 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441396 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441394 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441391 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441389 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441387 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 2441383 - udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 17582 - udp6 0 0 :::546 :::* 0 14461 - udp6 0 0 :::45780 :::* 108 10204 - udp6 0 0 :::5353 :::* 108 10202 - udp6 0 0 :::1900 :::* 1000 2441397 - udp6 0 0 :::1900 :::* 1000 2441395 - udp6 0 0 :::1900 :::* 1000 2441393 - udp6 0 0 :::1900 :::* 1000 2441392 - udp6 0 0 :::1900 :::* 1000 2441390 - udp6 0 0 :::1900 :::* 1000 2441388 - udp6 0 0 :::1900 :::* 1000 2441386 - udp6 0 0 :::1900 :::* 1000 2441385 - *** Log File - Last 25 Lines *** 2023-11-10 20:12:13.836 - warn: sonoff.0 (265) Client [Tasmota1] has invalid password or username 2023-11-10 20:12:15.115 - warn: sonoff.0 (265) Client [TasmotaL2USB] has invalid password or username 2023-11-10 20:12:15.781 - warn: sonoff.0 (265) Client [Tasmota16] has invalid password or username 2023-11-10 20:12:15.847 - warn: sonoff.0 (265) Client [Tasmota9] has invalid password or username 2023-11-10 20:12:16.960 - warn: sonoff.0 (265) Client [Tasmota11] has invalid password or username 2023-11-10 20:12:21.471 - warn: sonoff.0 (265) Client [Tasmota8Twin_14133E] has invalid password or username 2023-11-10 20:12:21.747 - warn: sonoff.0 (265) Client [Tasmota3USB] has invalid password or username 2023-11-10 20:12:22.236 - warn: sonoff.0 (265) Client [Tasmota12] has invalid password or username 2023-11-10 20:12:25.300 - warn: sonoff.0 (265) Client [TasmotaL1USB] has invalid password or username 2023-11-10 20:12:26.508 - warn: sonoff.0 (265) Client [Tasmota2USB] has invalid password or username 2023-11-10 20:12:29.406 - warn: sonoff.0 (265) Client [Tasmota5USB] has invalid password or username 2023-11-10 20:12:34.992 - warn: sonoff.0 (265) Client [Tasmota7Twin_1449B7] has invalid password or username 2023-11-10 20:12:35.263 - warn: sonoff.0 (265) Client [Tasmota4USB] has invalid password or username 2023-11-10 20:12:36.027 - warn: sonoff.0 (265) Client [Tasmota6] has invalid password or username 2023-11-10 20:12:36.798 - warn: sonoff.0 (265) Client [Tasmota10] has invalid password or username 2023-11-10 20:12:39.605 - warn: sonoff.0 (265) Client [Tasmota1] has invalid password or username 2023-11-10 20:12:40.942 - warn: sonoff.0 (265) Client [TasmotaL2USB] has invalid password or username 2023-11-10 20:12:41.635 - warn: sonoff.0 (265) Client [Tasmota9] has invalid password or username 2023-11-10 20:12:42.734 - warn: sonoff.0 (265) Client [Tasmota11] has invalid password or username 2023-11-10 20:12:47.294 - warn: sonoff.0 (265) Client [Tasmota8Twin_14133E] has invalid password or username 2023-11-10 20:12:47.582 - warn: sonoff.0 (265) Client [Tasmota3USB] has invalid password or username 2023-11-10 20:12:48.060 - warn: sonoff.0 (265) Client [Tasmota12] has invalid password or username 2023-11-10 20:12:51.164 - warn: sonoff.0 (265) Client [TasmotaL1USB] has invalid password or username 2023-11-10 20:12:52.303 - warn: sonoff.0 (265) Client [Tasmota2USB] has invalid password or username 2023-11-10 20:12:55.186 - warn: sonoff.0 (265) Client [Tasmota5USB] has invalid password or username ============ Mark until here for C&P ============= iob diag has finished. Press any key for a summary======================= SUMMARY ======================= v.2023-10-10 /home/iobroker/.diag.sh: line 457: hostnamectl: command not found Installation: Kernel: armv7l Userland: armhf /home/iobroker/.diag.sh: line 466: timedatectl: command not found Timezone: User-ID: 1001 X-Server: false /home/iobroker/.diag.sh: line 473: systemctl: command not found Boot Target: Pending OS-Updates: 0 error: failed switching to "iobroker": operation not permitted Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.18.2 /usr/bin/node v18.18.2 /usr/bin/npm 9.8.1 /usr/bin/npx 9.8.1 /usr/bin/corepack 0.19.0 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.9G 2.0G 3.6G 1.0M 2.3G 5.7G Swap: 99M 0B 99M Total: 8.0G 2.0G 3.7G error: failed switching to "iobroker": operation not permitted Active iob-Instances: 0 error: failed switching to "iobroker": operation not permitted error: failed switching to "iobroker": operation not permitted ioBroker Core: js-controller error: failed switching to "iobroker": operation not permitted admin error: failed switching to "iobroker": operation not permitted ioBroker Status: Status admin and web instance: error: failed switching to "iobroker": operation not permitted Objects: 0 States: 0 Size of iob-Database: 34M /opt/iobroker/iobroker-data/objects.jsonl 17M /opt/iobroker/iobroker-data/objects.json.migrated 17M /opt/iobroker/iobroker-data/objects.json.bak.migrated 16K /opt/iobroker/iobroker-data/objects.json.old 7.0M /opt/iobroker/iobroker-data/states.jsonl 2.3M /opt/iobroker/iobroker-data/states.json.migrated 2.3M /opt/iobroker/iobroker-data/states.json.bak.migrated 2.0M /opt/iobroker/iobroker-data/states.json.old =================== END OF SUMMARY ==================== -
-
idash@raspberrypi:/opt/iobroker$ cat /etc/debian_version 11.8 -
-
@thomas-braun
Hatte den gestern auf Bullseye hochgezogen.idash@raspberrypi:~$ sudo systemctl daemon-reload sudo: systemctl: command not found -
Ja, denn 11.8 ist ein Bullseye.
Das ist dann aber wohl in die Hose gegangen. -
@thomas-braun
ja, vor gestern war es auch noch Buster -
Dann installier da ein Bookworm, von Null an.
