Update von Debian 12 auf 13 möglich?
-
@duffy sagte in Update von Debian 12 auf 13 möglich?:
Jetzt kann ich über das blöde Tool die Dateien nicht ändern aufgrund fehlender Berechtigungen.
An diese Dateien darf schreibend nur der 'root' bzw. ein user, der in diese Rolle temporär mittels 'sudo' schlüpfen kann.
Also persudo nano /pfad/zur/dateiginge das direkt in der Konsole mit dem nano. Ganz ohne 'Tool'.
Wobei wir dann wieder bei dem Thema 'Grundlagen' wären. Das nimmt dir aber kein Tool der Welt ab, bzw. erschweren die den Erwerb der erforderlichen Grundkenntnisse. Nutzt dir ja nix, da irgendwie mit irgendwas planlos durch die Gegend zu klicken.
-
Ich weiß ja nicht ob es wichtig ist, aber was mir auffällt in den obigen dateien (Codetags)
Da werden 2 verschiedene Dateiendungen geschrieben.?
Signed-By: /usr/share/keyrings/debian-archive-keyring.gpg (gpg) ?
und so
Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgp (pgp) ? -
@teletapi sagte in Update von Debian 12 auf 13 möglich?:
Da werden 2 verschiedene Dateiendungen geschrieben.?
Ja. Aber es sind ja auch verschiedene Schlüssel mit verschiedenen Crypto-Verfahren.
-
Ich habe es über Nano gewagt und es scheint geklappt zu haben es kommt keine Meldung mehr ausser der einen die man derzeit ignorieren soll.
pi@raspberrypi:~ $ sudo apt update && sudo apt full-upgrade Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 https://apt.grafana.com stable InRelease Hit:6 https://deb.nodesource.com/node_22.x nodistro InRelease Hit:7 https://repos.influxdata.com/debian stable InRelease All packages are up to date. Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Summary: Upgrading: 0, Installing: 0, Removing: 0, Not Upgrading: 0 pi@raspberrypi:~ $Jett sollte ich für die nächsten Wochen bereit für die ZUkunft sein, oder?
VG Duffy
-
@duffy sagte in Update von Debian 12 auf 13 möglich?:
Jett sollte ich für die nächsten Wochen bereit für die ZUkunft sein, oder?
Ja, schaut jetzt richtig aus.
-
-
... da der Beitrag noch aktuell ist hänge ich mich mal dran ...
@thomas-braun
Funktioniert deine Anleitung auch bei meiner Ausgangssituation (QNAP VM) ?========== Start marking the full check here =========== ```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 12 (bookworm) Static hostname: VM-ioBroker Icon name: computer-vm Chassis: vm 🖴 Virtualization: kvm Kernel: Linux 6.1.0-40-amd64 Architecture: x86-64 Hardware Vendor: qemu Hardware Model: qemu Firmware Version: e0d6339-dirty-20220919_024111-d528eb931742 OS is similar to: model name : Westmere E56xx/L56xx/X56xx (Nehalem-C) Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 20:48:56 up 15 days, 5:38, 2 users, load average: 0.30, 0.15, 0.10 CPU threads: 4 *** LIFE CYCLE STATUS *** Debian 'bookworm' is the current oldstable version. Please upgrade to the latest stable release 'trixie' in due time! *** TIME AND TIMEZONES *** Local time: Sun 2025-10-19 20:48:56 CEST Universal time: Sun 2025-10-19 18:48:56 UTC RTC time: Sun 2025-10-19 18:48:56 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout cdrom floppy sudo audio dip video plugdev users netdev User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout cdrom floppy sudo audio dip video plugdev users netdev A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'! A root login is not required in most Linux Distributions. Run 'iobroker fix' or use the system tools to create a user. *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.3G 3.2G 4.1G 593K 1.3G 5.1G Swap: 1.0G 0B 1.0G Total: 9.3G 3.2G 5.2G Active iob-Instances: 30 7940 M total memory 3033 M used memory 659 M active memory 3062 M inactive memory 3936 M free memory 319 M buffer memory 916 M swap cache 974 M total swap 0 M used swap 974 M free swap *** top - Table Of Processes *** top - 20:48:57 up 15 days, 5:38, 2 users, load average: 0.30, 0.15, 0.10 Tasks: 140 total, 4 running, 136 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 25.0 sy, 0.0 ni, 75.0 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7940.7 total, 3936.2 free, 3033.9 used, 1236.1 buff/cache MiB Swap: 975.0 total, 975.0 free, 0.0 used. 4906.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** [sudo] password for iobroker: No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 795M 588K 794M 1% /run /dev/sda1 ext4 48G 7.8G 38G 18% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 795M 0 795M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Oct 4 15:10:29 2025] EXT4-fs (sda1): mounted filesystem with ordered data mode. Quota mode: none. [Sat Oct 4 15:10:30 2025] EXT4-fs (sda1): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro Files in neuralgic directories: /var: 1.3G /var/ 580M /var/cache 573M /var/cache/apt 572M /var/log 558M /var/log/journal/27bb2095ba2b41ccb088ec3ad41fc1f5 Hint: You are currently not seeing messages from other users and the system. Users in groups 'adm', 'systemd-journal' can see all messages. Pass -q to turn off this notice. Archived and active journals take up 253.5M in the file system. /opt/iobroker/backups: 20M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 308M /opt/iobroker/iobroker-data/ 163M /opt/iobroker/iobroker-data/files 103M /opt/iobroker/iobroker-data/backup-objects 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets The five largest files in iobroker-data are: 39M /opt/iobroker/iobroker-data/objects.jsonl 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js 4.6M /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js 4.2M /opt/iobroker/iobroker-data/backup-objects/2025-10-19_19-49_objects.jsonl.gz 4.2M /opt/iobroker/iobroker-data/backup-objects/2025-10-19_17-49_objects.jsonl.gz USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c421aa81b69ded118718d3a5a7669f5d-if00-port0 *** ZigBee Settings *** Your zigbee.0 COM-Port is matching 'by-id'. Very good! Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.20.0 /usr/bin/node v22.20.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.20.0-1nodesource1 Candidate: 22.20.0-1nodesource1 Version table: *** 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 18.20.4+dfsg-1~deb12u1 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 500 http://security.debian.org/debian-security bookworm-security/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: VM-ioBroker VM-ioBroker (version: 7.0.7, hostname: VM-ioBroker , alive, uptime: 896367) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 2 +-- iobroker.frontier_silicon@0.5.0 (git+ssh://git@github.com/iobroker-community-adapters/ioBroker.frontier_silicon.git#6fa3c2fb582cb38932bf443b38867e572874e66a) +-- iobroker.go-e@1.0.42 (git+ssh://git@github.com/MK-2001/ioBroker.go-e.git#d7874e9d5200daf7d104b6d805b97c1f6f14793a) Adapter State + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.alpha-ess.0 : alpha-ess : VM-ioBroker - enabled + system.adapter.awtrix-light.0 : awtrix-light : VM-ioBroker - enabled system.adapter.awtrix-light.1 : awtrix-light : VM-ioBroker - disabled + system.adapter.awtrix-light.2 : awtrix-light : VM-ioBroker - enabled + system.adapter.backitup.0 : backitup : VM-ioBroker - enabled + system.adapter.canbus.0 : canbus : VM-ioBroker - enabled + system.adapter.cloud.0 : cloud : VM-ioBroker - enabled + system.adapter.discovery.0 : discovery : VM-ioBroker - enabled system.adapter.energiefluss-erweitert.0 : energiefluss-erweitert: VM-ioBroker - disabled system.adapter.feiertage.0 : feiertage : VM-ioBroker - enabled + system.adapter.frontier_silicon.0 : frontier_silicon : VM-ioBroker - enabled system.adapter.go-e.0 : go-e : VM-ioBroker - disabled system.adapter.history.0 : history : VM-ioBroker - disabled + system.adapter.hm-rega.0 : hm-rega : VM-ioBroker - enabled + system.adapter.hm-rpc.0 : hm-rpc : VM-ioBroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : VM-ioBroker - enabled, port: 0 + system.adapter.hue.0 : hue : VM-ioBroker - enabled, port: 443 system.adapter.influxdb.0 : influxdb : VM-ioBroker - disabled, port: 8086 + system.adapter.iqontrol.0 : iqontrol : VM-ioBroker - enabled + system.adapter.javascript.0 : javascript : VM-ioBroker - enabled + system.adapter.klf200.0 : klf200 : VM-ioBroker - enabled + system.adapter.lgtv.0 : lgtv : VM-ioBroker - enabled system.adapter.luftdaten.0 : luftdaten : VM-ioBroker - enabled + system.adapter.mqtt.0 : mqtt : VM-ioBroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.onkyo.0 : onkyo : VM-ioBroker - enabled system.adapter.openweathermap.0 : openweathermap : VM-ioBroker - disabled + system.adapter.sainlogic.0 : sainlogic : VM-ioBroker - enabled, port: 1030, bind: 0.0.0.0 + system.adapter.shuttercontrol.0 : shuttercontrol : VM-ioBroker - enabled + system.adapter.simple-api.0 : simple-api : VM-ioBroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : VM-ioBroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : VM-ioBroker - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : VM-ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : VM-ioBroker - enabled + system.adapter.vw-connect.0 : vw-connect : VM-ioBroker - enabled + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : VM-ioBroker - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c421aa81b69ded118718d3a5a7669f5d-if00-port0 system.adapter.zigbee2mqtt.0 : zigbee2mqtt : VM-ioBroker - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : VM-ioBroker - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : VM-ioBroker - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : VM-ioBroker - enabled, port: 0 + system.adapter.hue.0 : hue : VM-ioBroker - enabled, port: 443 + system.adapter.mqtt.0 : mqtt : VM-ioBroker - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.sainlogic.0 : sainlogic : VM-ioBroker - enabled, port: 1030, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : VM-ioBroker - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.socketio.0 : socketio : VM-ioBroker - enabled, port: 8084, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : VM-ioBroker - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.telegram.0 : telegram : VM-ioBroker - enabled, port: 8443, bind: 0.0.0.0 + system.adapter.web.0 : web : VM-ioBroker - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.zigbee.0 : zigbee : VM-ioBroker - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c421aa81b69ded118718d3a5a7669f5d-if00-port0 ioBroker-Repositories ┌─────────┬──────────┬─────────────────────────────────────────────────────────┬──────────────┐ │ (index) │ name │ url │ auto upgrade │ ├─────────┼──────────┼─────────────────────────────────────────────────────────┼──────────────┤ │ 0 │ 'stable' │ 'http://download.iobroker.net/sources-dist.json' │ false │ │ 1 │ 'beta' │ 'http://download.iobroker.net/sources-dist-latest.json' │ false │ └─────────┴──────────┴─────────────────────────────────────────────────────────┴──────────────┘ Active repo(s): stable Upgrade policy: none Installed ioBroker-Adapters Used repository: stable Adapter "admin" : 7.7.2 , installed 7.7.2 Adapter "alpha-ess" : 3.0.1 , installed 3.0.1 Adapter "awtrix-light" : 2.0.0 , installed 2.0.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "canbus" : 2.2.0 , installed 2.2.0 Adapter "cloud" : 5.0.1 , installed 5.0.1 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "energiefluss-erweitert": 0.7.7, installed 0.7.7 Adapter "feiertage" : 1.2.1 , installed 1.2.1 Adapter "frontier_silicon": 0.5.0 , installed 0.5.0 Adapter "go-e" : 1.0.41 , installed 1.0.42 Adapter "history" : 3.0.1 , installed 3.0.1 Adapter "hm-rega" : 5.1.0 , installed 5.1.0 Adapter "hm-rpc" : 2.0.2 , installed 2.0.2 Adapter "hue" : 3.16.2 , installed 3.16.2 Adapter "influxdb" : 4.0.2 , installed 4.0.2 Adapter "iqontrol" : 3.0.0 , installed 3.0.0 Adapter "javascript" : 8.9.2 , installed 8.9.2 Controller "js-controller": 7.0.7 , installed 7.0.7 Adapter "klf200" : 1.3.5 , installed 1.3.5 Adapter "lgtv" : 2.5.0 , installed 2.5.0 Adapter "luftdaten" : 4.0.0 , installed 4.0.0 Adapter "mqtt" : 6.1.4 , installed 6.1.4 Adapter "onkyo" : 2.1.2 , installed 2.1.2 Adapter "openweathermap": 1.1.2 , installed 1.1.2 Adapter "sainlogic" : 0.11.6 , installed 0.11.6 Adapter "shuttercontrol": 2.0.5 , installed 2.0.5 Adapter "simple-api" : 2.8.0 , installed 2.8.0 Adapter "socketio" : 6.7.1 , installed 6.7.1 Adapter "sonoff" : 3.2.1 , installed 3.2.1 Adapter "telegram" : 4.1.0 , installed 4.1.0 Adapter "tr-064" : 4.3.0 , installed 4.3.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "ws" : 2.6.2 , installed 2.6.2 Adapter "zigbee" : 3.0.5 , installed 3.0.5 Adapter "zigbee2mqtt" : 3.0.9 , installed 3.0.9 Objects and States Please stand by - This may take a while Objects: 7355 States: 5654 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian bookworm-updates InRelease Hit:3 http://security.debian.org/debian-security bookworm-security InRelease Hit:4 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... Pending Updates: 3 *** 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:1885 0.0.0.0:* LISTEN 1000 423702 10636/io.sonoff.0 tcp 0 0 192.168.178.120:42001 0.0.0.0:* LISTEN 1000 456890 11400/io.hm-rpc.0 tcp 0 0 192.168.178.120:42010 0.0.0.0:* LISTEN 1000 456279 11385/io.hm-rpc.1 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1000 425294 10351/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1000 424273 10351/iobroker.js-c tcp 0 0 0.0.0.0:1030 0.0.0.0:* LISTEN 1000 424827 10757/io.sainlogic. tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 2124 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 16623 534/sshd: /usr/sbin tcp6 0 0 :::8082 :::* LISTEN 1000 426154 10787/io.web.0 tcp6 0 0 :::8081 :::* LISTEN 1000 425353 10372/io.admin.0 tcp6 0 0 :::8087 :::* LISTEN 1000 426185 10802/io.simple-api tcp6 0 0 :::8084 :::* LISTEN 1000 424929 10862/io.socketio.0 tcp6 0 0 :::111 :::* LISTEN 0 4007 1/init tcp6 0 0 :::22 :::* LISTEN 0 16634 534/sshd: /usr/sbin udp 0 0 0.0.0.0:20000 0.0.0.0:* 65534 16676 586/cannelloni udp 0 0 0.0.0.0:68 0.0.0.0:* 0 15562 426/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 14356 1/init udp6 0 0 :::111 :::* 0 2127 1/init *** Log File - Last 25 Lines *** 2025-10-19 19:51:57.928 - info: admin.0 (10372) ==> Connected system.user.admin from ::ffff:192.168.178.20 2025-10-19 19:52:12.714 - info: admin.0 (10372) ==> Connected system.user.admin from ::ffff:192.168.178.20 2025-10-19 19:53:50.705 - info: javascript.0 (10401) Stopping script script.js.5_Skripte_AWTRIX.Terrasse_Strom_sparen_2 2025-10-19 19:53:50.768 - info: javascript.0 (10401) Start JavaScript script.js.5_Skripte_AWTRIX.Terrasse_Strom_sparen_2 (Blockly) 2025-10-19 19:53:50.790 - info: javascript.0 (10401) script.js.5_Skripte_AWTRIX.Terrasse_Strom_sparen_2: registered 0 subscriptions, 1 schedule, 0 messages, 0 logs and 0 file subscriptions 2025-10-19 19:53:54.980 - info: admin.0 (10372) <== Disconnect system.user.admin from ::ffff:192.168.178.20 javascript 2025-10-19 19:54:27.553 - info: admin.0 (10372) <== Disconnect system.user.admin from ::ffff:192.168.178.20 admin 2025-10-19 20:00:00.110 - info: host.VM-ioBroker "system.adapter.go-e.0" disabled 2025-10-19 20:00:00.111 - info: host.VM-ioBroker stopInstance system.adapter.go-e.0 (force=false, process=true) 2025-10-19 20:00:00.119 - info: go-e.0 (27963) Got terminate signal TERMINATE_YOURSELF 2025-10-19 20:00:00.129 - info: go-e.0 (27963) terminating 2025-10-19 20:00:00.131 - info: go-e.0 (27963) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-10-19 20:00:00.163 - info: host.VM-ioBroker stopInstance system.adapter.go-e.0 send kill signal 2025-10-19 20:00:00.635 - info: go-e.0 (27963) terminating 2025-10-19 20:00:01.186 - info: host.VM-ioBroker instance system.adapter.go-e.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2025-10-19 20:00:26.035 - info: host.VM-ioBroker instance system.adapter.luftdaten.0 in version "4.0.0" started with pid 28968 2025-10-19 20:00:28.218 - info: luftdaten.0 (28968) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.luftdaten, node: v22.20.0, js-controller: 7.0.7 2025-10-19 20:00:31.662 - info: luftdaten.0 (28968) [fillSensorData] error: connect EHOSTUNREACH 192.168.178.72:80 2025-10-19 20:00:31.735 - info: luftdaten.0 (28968) Terminated (NO_ERROR): Without reason 2025-10-19 20:00:32.343 - info: host.VM-ioBroker instance system.adapter.luftdaten.0 having pid 28968 terminated with code 0 (NO_ERROR) 2025-10-19 20:30:26.035 - info: host.VM-ioBroker instance system.adapter.luftdaten.0 in version "4.0.0" started with pid 29856 2025-10-19 20:30:28.107 - info: luftdaten.0 (29856) starting. Version 4.0.0 in /opt/iobroker/node_modules/iobroker.luftdaten, node: v22.20.0, js-controller: 7.0.7 2025-10-19 20:30:31.389 - info: luftdaten.0 (29856) [fillSensorData] error: connect EHOSTUNREACH 192.168.178.72:80 2025-10-19 20:30:31.408 - info: luftdaten.0 (29856) Terminated (NO_ERROR): Without reason 2025-10-19 20:30:32.006 - info: host.VM-ioBroker instance system.adapter.luftdaten.0 having pid 29856 terminated with code 0 (NO_ERROR)Danke für die Stellungnahme.
-
@raspiuser sagte in Update von Debian 12 auf 13 möglich?:
A default user should be created! This user will be enabled to temporarily switch to root via 'sudo'!
Mach das! Und den neuen User kannste dann direkt in die Gruppe
admsetzen.Ansonsten sollte da ein 'in-line-upgrade' auf Trixie möglich sein.
-
@thomas-braun
Danke für die Hinweise ...
"Augen zu und durch" ... das Update hat geklappt, Danke auch für die Anleitung.
Ich habe den User angelegt und "iob diag" ausgeführt. Jetzt bleibt das Programm hier hängen ...```bash Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: VM-ioBroker Icon name: computer-vm Chassis: vm 🖴 AF_VSOCK CID: 1 Virtualization: kvm Kernel: Linux 6.12.48+deb13-amd64 Architecture: x86-64 Hardware Vendor: qemu Hardware Model: qemu Firmware Version: e0d6339-dirty-20220919_024111-d528eb931742 Firmware Date: Tue 2014-04-01 Firmware Age: 11y 6month 2w 6d OS is similar to: model name : Westmere E56xx/L56xx/X56xx (Nehalem-C) Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 11:23:20 up 2 min, 1 user, load average: 4.48, 1.54, 0.56 CPU threads: 4 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Mon 2025-10-20 11:23:20 CEST Universal time: Mon 2025-10-20 09:23:20 UTC RTC time: Mon 2025-10-20 09:23:20 Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': raspiuser HOME=/home/raspiuser GROUPS=raspiuser adm dialout sudo audio video plugdev users iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/raspiuser GROUPS=iobroker tty dialout cdrom floppy sudo audio dip video plugdev users netdev *** DISPLAY-SERVER SETUP *** Display-Server: false Unit display-manager.service could not be found. Display-Manager: Desktop: Session: tty *** MEMORY *** total used free shared buff/cache available Mem: 8.3G 2.6G 5.5G 1.0M 394M 5.7G Swap: 1.0G 0B 1.0G Total: 9.4G 2.6G 6.6G Active iob-Instances: 19 7947 M total memory 2525 M used memory 2293 M active memory 151 M inactive memory 5277 M free memory 42 M buffer memory 334 M swap cache 974 M total swap 0 M used swap 974 M free swap *** top - Table Of Processes *** top - 11:23:21 up 2 min, 1 user, load average: 4.48, 1.54, 0.56 Tasks: 164 total, 5 running, 159 sleeping, 0 stopped, 0 zombie %Cpu(s): 54.7 us, 18.8 sy, 0.0 ni, 7.8 id, 0.0 wa, 0.0 hi, 0.0 si, 18.8 st MiB Mem : 7947.3 total, 5276.3 free, 2526.1 used, 376.6 buff/cache MiB Swap: 975.0 total, 975.0 free, 0.0 used. 5421.2 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** DMESG CRITICAL ERRORS *** No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.9G 0 3.9G 0% /dev tmpfs tmpfs 795M 588K 795M 1% /run /dev/sda1 ext4 48G 8.1G 38G 18% / tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/systemd-journald.service tmpfs tmpfs 3.9G 412K 3.9G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 795M 8.0K 795M 1% /run/user/1001 Messages concerning ext4 filesystem in dmesg: [Mon Oct 20 11:21:14 2025] EXT4-fs (sda1): mounted filesystem b4ce8297-3803-48c4-b2a4-b0f408a6baba ro with ordered data mode. Quota mode: none. [Mon Oct 20 11:21:16 2025] EXT4-fs (sda1): re-mounted b4ce8297-3803-48c4-b2a4-b0f408a6baba r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro Files in neuralgic directories: /var: 1.5G /var/ 688M /var/cache 677M /var/cache/apt 586M /var/cache/apt/archives 573M /var/log Archived and active journals take up 557.1M in the file system. /opt/iobroker/backups: 20M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 293M /opt/iobroker/iobroker-data/ 163M /opt/iobroker/iobroker-data/files 103M /opt/iobroker/iobroker-data/backup-objects 47M /opt/iobroker/iobroker-data/files/admin.admin 46M /opt/iobroker/iobroker-data/files/admin.admin/custom/assets The five largest files in iobroker-data are: 22M /opt/iobroker/iobroker-data/objects.jsonl 8.6M /opt/iobroker/iobroker-data/files/backitup.admin/assets/index-BBu8-Y_o.js 4.6M /opt/iobroker/iobroker-data/files/javascript.admin/vs/language/typescript/tsWorker.js 4.3M /opt/iobroker/iobroker-data/states.jsonl 4.2M /opt/iobroker/iobroker-data/backup-objects/2025-10-20_09-49_objects.jsonl.gz USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_c421aa81b69ded118718d3a5a7669f5d-if00-port0 *** ZigBee Settings *** Your zigbee.0 COM-Port is matching 'by-id'. Very good! Zigbee Network Settings on your coordinator/in nvbackup are: zigbee.X Extended Pan ID: *** MASKED *** Pan ID: *** MASKED *** Channel: *** MASKED *** Network Key: *** MASKED *** To unmask the settings run 'iob diag --unmask' *** NodeJS-Installation *** /usr/bin/nodejs v22.20.0 /usr/bin/node v22.20.0 /usr/bin/npm 10.9.3 /usr/bin/npx 10.9.3 /usr/bin/corepack 0.34.0 nodejs: Installed: 22.20.0-1nodesource1 Candidate: 22.20.0-1nodesource1 Version table: *** 22.20.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 22.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.1-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 22.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_22.x nodistro/main amd64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages Temp directories causing deletion problem: 0 No problems detected Errors in npm tree: 0 No problems detected Checking for nodejs vulnerability:Was habe ich falsch gemacht ?
EDIT: Sorry, ich hatte den Beitrag überarbeitet ...
-
@raspiuser sagte in Update von Debian 12 auf 13 möglich?:
Ich habe den User angelegt
Und danach die Kiste einmal sauber neugestartet? Erst dann werden die (Gruppen)Rechte, die an der Stelle benötigt werden, sauber gesetzt.
Edit: Ich sehe gerade:
10:33:38 up 15 days, 19:23, 2 users, load average: 0.54, 0.47, 0.49Also neustarten, dann funktioniert das auch.
-
@raspiuser sagte in Update von Debian 12 auf 13 möglich?:
Was habe ich falsch gemacht ?
EDIT: Sorry, ich hatte den Beitrag überarbeitet ...Hast du mal den
iob fixausgeführt?
-
@thomas-braun ```
Your installation was fixed successfully Run iobroker start to start ioBroker again!'iob diag' läuft leider noch immer nicht durch ...
EDIT: Nach ca. 10 Minuten ist iob diag fertig ... das hat zuvor vielleicht 2 Minuten benötigt ...
-
@raspiuser
Führ das mal als raspiuser aus:cd /home/iobroker/ sudo -H -u iobroker npm i is-my-node-vulnerable sudo -H -u iobroker npx is-my-node-vulnerable cd -
@raspiuser sagte in Update von Debian 12 auf 13 möglich?:
EDIT: Nach ca. 10 Minuten ist iob diag fertig ... das hat zuvor vielleicht 2 Minuten benötigt ...
Ja, das Skript prüft ja nun auch mehr...
Klar dauert das länger. -
@thomas-braun
... läuft und läuft ... und läuft noch
-
@thomas-braun sagte in Update von Debian 12 auf 13 möglich?:
Klar dauert das länger.
Ok ... dann ist das ja gar kein Fehler, Danke.
-
So lange sich die Punkte da bewegen läuft npm noch.
-
-
Dann dürfte da bei dir noch was anderes in der Pipeline hängen.
Hier dauert die Installation von dem Modul natürlich keine 7 Minuten.Edit: Gerade nochmal selber getestet, in der Tat dauert die Installation gerade sehr lange. Da kann ich aber erstmal nix dran machen.
Und bitte keine Screenshots von Text. Schon gar nicht unvollständige.
-
@thomas-braun
sorry ... soll ich dann nochmal die komplette Ausgabe von 'diag' reinstellen oder hat Du noch einen anderen Hinweis ?
