Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie'
-
pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/deconz* deb http://phoscon.de/apt/deconz generic main Types: deb URIs: http://phoscon.de/apt/deconz/ Suites: generic Components: main Signed-By:pi@raspberrypi:~ $ cat /etc/apt/sources.list.d/raspi* deb http://archive.raspberrypi.com/debian/ trixie main # Uncomment line below then 'apt-get update' to enable 'apt-get source' #deb-src http://archive.raspberrypi.com/debian/ trixie main Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By:EDIT: war wohl ein "cat" zuviel
-
Das sind Doubletten und Dateien im neuen Format.
Lösch die deconz.list und deconz.sources und leg die neu an:wget -qO- http://phoscon.de/apt/deconz.pub.key | sudo gpg --dearmor -o /etc/apt/keyrings/deconz.gpg > /dev/null sudo sh -c "echo 'deb [signed-by=/etc/apt/keyrings/deconz.gpg] http://phoscon.de/apt/deconz $(lsb_release -cs) main' > /etc/apt/sources.list.d/deconz.list"Bei der raspi.sources fehlt der Eintrag zur Signatur. Und es ist wohl auch eine Doublette, es wird da auch noch eine raspi.list geben.
raspi.sources schaut bei mir so aus:
Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgp -
muß dann die raspi.list auch weg ? und wie ändere ich die raspi.sources?
-
@michael-schmitt sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
muß dann die raspi.list auch weg ?
Ja, entweder .list oder .sources. Beides gleichzeitig führt zu Chaos.
und wie ändere ich die raspi.sources?
Mit einem Editor? nano?
-
pi@raspberrypi:~ $ sudo apt update Ign:1 http://phoscon.de/apt/deconz trixie InRelease Hit:2 http://archive.raspberrypi.com/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie InRelease Hit:4 http://deb.debian.org/debian-security trixie-security InRelease Hit:5 http://deb.debian.org/debian trixie-updates InRelease Err:6 http://phoscon.de/apt/deconz trixie Release 404 Not Found [IP: 144.76.96.194 80] Hit:7 https://deb.nodesource.com/node_22.x nodistro InRelease Error: The repository 'http://phoscon.de/apt/deconz trixie Release' does not have a Release file. Notice: Updating from such a repository can't be done securely, and is therefore disabled by default. Notice: See apt-secure(8) manpage for repository creation and user configuration details. Warning: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details pi@raspberrypi:~ $ -
@michael-schmitt sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Error: The repository 'http://phoscon.de/apt/deconz trixie Release' does not have a Release file.
Es gibt noch keine Veröffentlichung für
trixie. Stell da einstweilenbookwormein. -
so aber jetzt
pi@raspberrypi:~ $ sudo apt update Hit:1 http://phoscon.de/apt/deconz bookworm InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian-security trixie-security InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 http://deb.debian.org/debian trixie-updates InRelease Hit:6 https://deb.nodesource.com/node_22.x nodistro 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 pi@raspberrypi:~ $ -
Jetzt passt es.
-
@thomas-braun viiieeeelllleeen Dank
da ist noch eine nodesource.list.bak drin, kann die auch weg ?
-
@michael-schmitt
Das ist da Buckup der vorherigen nodesource.list, kann weg, muss aber nicht. -
@thomas-braun sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
@michael-schmitt sagte in Upgrade von Debian 12 'Bookworm' auf Debian 13 'Trixie':
Error: The repository 'http://phoscon.de/apt/deconz trixie Release' does not have a Release file.
Es gibt noch keine Veröffentlichung für
trixie. Stell da einstweilenbookwormein.Hab gerade nochmal geschaut, das Repo verwendet nun keine release names mehr sondern nur noch generische Pakete.
Ersetze also den Eintragbookwormdurchgeneric. -
@thomas-braun erledigt
pi@raspberrypi:~ $ sudo apt update Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian-security trixie-security InRelease Hit:3 http://phoscon.de/apt/deconz generic InRelease Hit:4 http://archive.raspberrypi.com/debian trixie InRelease Hit:5 http://deb.debian.org/debian trixie-updates InRelease Hit:6 https://deb.nodesource.com/node_22.x nodistro 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 pi@raspberrypi:~ $ -
@thomas-braun
Hi!Danke für die erstklassige Anleitung zum Upgrade auf Debian 13 "Trixie"! Für mich als 2025-Linux-Newbie war das sehr schlüssig nachvollziehbar und das Upgrade hat wunderbar geklappt. Natürlich - ein paar alte MS DOS Kenntnisse aus den 80ern waren hilfreich
Gruß, hf
Edit: Das Upgrade bezog sich auf einen produktiven Raspi 5 per SSH via Putty. Auf dem darauf installiertem IOB mit einer mySQL-Datenbank läuft seit einigen Wochen das gesamte Strommanagement meines Hauses (PV, WR, Akku, 2 Wallboxen, Not- und Fremdstrombezug) sowie die Klimatisierungssteuerung (Solarluft, Pelletsofen, WW-Boiler, Kühlung). Und natürlich die Auswertung der relevanten Infos.
-
Hallo,
ich habe nun auch nach der Top-Anleitung das Debian-Upgrade von 12 bookworm zu 13 trixie gemacht.
Debian läuft in einem LXC-Container auf Proxmox.Es hat soweit geklappt.
Aber ich erhalte bei
iob diageinennpm error.
Wie kann ich den Fehler beheben?$ iob diag [sudo] Passwort für mf: *** iob diag is starting up, please wait *** npm error code ELSPROBLEMS npm error invalid: buffer@5.7.1 /opt/iobroker/node_modules/buffer npm error missing: @csstools/css-parser-algorithms@^3.0.4, required by @asamuzakjp/css-color@3.2.0 npm error missing: @csstools/css-tokenizer@^3.0.3, required by @asamuzakjp/css-color@3.2.0 npm error missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-calc@2.1.4 npm error missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-calc@2.1.4 npm error missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-color-parser@3.1.0 npm error missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-color-parser@3.1.0 npm error A complete log of this run can be found in: /home/mf/.npm/_logs/2025-10-12T09_42_27_454Z-debug-0.log *** ioBroker Diagnosis *** Please stretch the window of your terminal programm (puTTY) as wide as possible or switch to full screen The following checks may give hints to potential malconfigurations or errors, please post them in our forum: https://forum.iobroker.net Just copy and paste the Summary Page, including the ``` characters at start and end. It helps us to help you! ************************************************************************** * Some output is masked. For full results please use 'iob diag --unmask' * ************************************************************************** Press any key to continue ========== Start marking the full check here ===========Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: iobroker84 Icon name: computer-container Chassis: container ☐ Virtualization: lxc Kernel: Linux 6.14.11-3-pve Architecture: x86-64 OS is similar to: model name : Intel(R) Celeron(R) J4105 CPU @ 1.50GHz Docker : false Virtualization : lxc Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 11:42:36 up 3 min, 1 user, load average: 0.80, 1.12, 1.01 CPU threads: 2 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Sun 2025-10-12 11:42:36 CEST Universal time: Sun 2025-10-12 09:42:36 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: inactive RTC in local TZ: no *** Users and Groups *** User that called 'iob diag': mf HOME=/home/mf GROUPS=mf adm sudo users iobroker lxc_shares User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/mf GROUPS=iobroker tty dialout audio video plugdev lxc_shares *** 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: 4.3G 1.3G 2.6G 3.9M 470M 3.0G Swap: 536M 0B 536M Total: 4.8G 1.3G 3.1G Active iob-Instances: 15 4096 M total memory 1203 M used memory 1449 M active memory 127 M inactive memory 2446 M free memory 0 M buffer memory 449 M swap cache 512 M total swap 0 M used swap 512 M free swap *** top - Table Of Processes *** top - 11:42:37 up 3 min, 1 user, load average: 0.80, 1.12, 1.01 Tasks: 52 total, 1 running, 51 sleeping, 0 stopped, 0 zombie %Cpu(s): 4.0 us, 4.0 sy, 0.0 ni, 88.0 id, 4.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 4096.0 total, 2445.0 free, 1205.2 used, 449.4 buff/cache MiB Swap: 512.0 total, 512.0 free, 0.0 used. 2890.8 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION * run-rpc_pipefs.mount loaded failed failed RPC Pipe File System * sys-kernel-config.mount loaded failed failed Kernel Configuration File System Legend: LOAD -> Reflects whether the unit definition was properly loaded. ACTIVE -> The high-level unit activation state, i.e. generalization of SUB. SUB -> The low-level unit activation state, values depend on unit type. 2 loaded units listed. *** DMESG CRITICAL ERRORS *** dmesg: read kernel buffer failed: Operation not permitted No critical errors detected *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/mapper/pve-vm--100--disk--0 ext4 12G 7.7G 3.5G 70% / //192.168.23.8/FRITZ.NAS/CT500MX5-00SSD1-01 cifs 467G 51G 416G 11% /mnt/nas8 none tmpfs 492K 4.0K 488K 1% /dev udev devtmpfs 9.7G 0 9.7G 0% /dev/tty tmpfs tmpfs 9.7G 0 9.7G 0% /dev/shm tmpfs tmpfs 3.9G 3.3M 3.9G 1% /run tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock tmpfs tmpfs 9.7G 460K 9.7G 1% /tmp tmpfs tmpfs 2.0G 8.0K 2.0G 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: dmesg: read kernel buffer failed: Operation not permitted Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mapper/pve-vm--100--disk--0 ext4 rw,relatime,stripe=16 `-/mnt/nas8 //192.168.23.8/FRITZ.NAS/CT500MX5-00SSD1-01 cifs rw,relatime,vers=3.0,cache=strict,upcall_target=app,username=fritznas,uid=100000,forceuid,gid=110000,forcegid,addr=192.168.23.8,file_mode=0770,dir_mode=0770,soft,nounix,mapposix,reparse=nfs,nativesocket,symlink=native,rsize=1048576,wsize=1048576,bsize=1048576,retrans=1,echo_interval=60,actimeo=1,closetimeo=1 Files in neuralgic directories: /var: 2.7G /var/ 1.3G /var/log/journal 1.3G /var/log 1.2G /var/cache/apt 1.2G /var/cache Archived and active journals take up 1G in the file system. /opt/iobroker/backups: 69M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 369M /opt/iobroker/iobroker-data/ 300M /opt/iobroker/iobroker-data/files 67M /opt/iobroker/iobroker-data/files/echarts.admin 61M /opt/iobroker/iobroker-data/files/echarts 53M /opt/iobroker/iobroker-data/backup-objects The five largest files in iobroker-data are: 26M /opt/iobroker/iobroker-data/files/echarts/static/js/main.41cee985.js.map 26M /opt/iobroker/iobroker-data/files/echarts.admin/chart/static/js/main.41cee985.js.map 24M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.6a71b34c.js.map 24M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.70a15e1f.js.map 18M /opt/iobroker/iobroker-data/files/echarts/preview/static/js/main.5fe9c7da.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/tty* in your adapter setups, please always prefer the links 'by-id': No Devices found 'by-id' 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 11.6.2 /usr/bin/npx 11.6.2 /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: █████ ██ ██ ██████ ██████ ██████ ██████ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ██ ██ ██ ███ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ██ ███████ ███████ ██████ ██████ ██████ ██████ ██ *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Hosts: iobroker84 iobroker84 (version: 7.0.7, hostname: iobroker84 , alive, uptime: 183) Core adapters versions js-controller: 7.0.7 admin: 7.7.2 javascript: 8.9.2 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : iobroker84 - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alias-manager.0 : alias-manager : iobroker84 - disabled + system.adapter.backitup.0 : backitup : iobroker84 - enabled + system.adapter.discovery.0 : discovery : iobroker84 - enabled + system.adapter.echarts.0 : echarts : iobroker84 - enabled system.adapter.ical.0 : ical : iobroker84 - enabled + system.adapter.influxdb.0 : influxdb : iobroker84 - enabled, port: 8086 + system.adapter.iqontrol.0 : iqontrol : iobroker84 - enabled + system.adapter.javascript.0 : javascript : iobroker84 - enabled + system.adapter.modbus.0 : modbus : iobroker84 - enabled system.adapter.ping.0 : ping : iobroker84 - disabled + system.adapter.shelly.0 : shelly : iobroker84 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker84 - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.tr-064.0 : tr-064 : iobroker84 - enabled + system.adapter.trashschedule.0 : trashschedule : iobroker84 - enabled + system.adapter.web.0 : web : iobroker84 - enabled, port: 8082, bind: 0.0.0.0, run as: admin + system.adapter.whatsapp-cmb.0 : whatsapp-cmb : iobroker84 - enabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : iobroker84 - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.influxdb.0 : influxdb : iobroker84 - enabled, port: 8086 + system.adapter.shelly.0 : shelly : iobroker84 - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.sonoff.0 : sonoff : iobroker84 - enabled, port: 1885, bind: 0.0.0.0 + system.adapter.web.0 : web : iobroker84 - enabled, port: 8082, bind: 0.0.0.0, run as: admin 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 "alias-manager": 2.0.0 , installed 2.0.0 Adapter "backitup" : 3.3.5 , installed 3.3.5 Adapter "discovery" : 5.0.0 , installed 5.0.0 Adapter "echarts" : 1.9.2 , installed 1.9.2 Adapter "ical" : 1.17.0 , installed 1.17.0 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 "modbus" : 6.3.2 , installed 6.3.2 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "shelly" : 10.2.0 , installed 10.2.0 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 "tr-064" : 4.3.0 , installed 4.3.0 Adapter "trashschedule": 3.3.0 , installed 3.3.0 Adapter "web" : 7.0.8 , installed 7.0.8 Adapter "whatsapp-cmb" : 0.3.0 , installed 0.3.0 Adapter "ws" : 2.6.2 , installed 2.6.2 Objects and States Please stand by - This may take a while Objects: 1346 States: 1056 *** OS-Repositories and Updates *** W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details Hit:1 http://deb.debian.org/debian trixie InRelease Hit:2 http://deb.debian.org/debian trixie-updates InRelease Hit:3 http://security.debian.org trixie-security InRelease Hit:4 https://repos.influxdata.com/debian stable InRelease Hit:5 https://deb.nodesource.com/node_22.x nodistro InRelease Reading package lists... W: https://deb.nodesource.com/node_22.x/dists/nodistro/InRelease: Policy will reject signature within a year, see --audit for details 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 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 30392745 277/iobroker.js-con tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 30392287 277/iobroker.js-con tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 30392581 264/smbd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 30390652 1/init tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 30392580 264/smbd tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 30393200 450/io.sonoff.0 tcp6 0 0 :::8081 :::* LISTEN 1001 30392832 313/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 30396478 525/io.web.0 tcp6 0 0 :::8086 :::* LISTEN 999 30392118 192/influxd tcp6 0 0 :::139 :::* LISTEN 0 30392579 264/smbd tcp6 0 0 :::111 :::* LISTEN 0 30390654 1/init tcp6 0 0 :::22 :::* LISTEN 0 30391102 1/init tcp6 0 0 :::445 :::* LISTEN 0 30392578 264/smbd udp 0 0 0.0.0.0:111 0.0.0.0:* 0 30390653 1/init udp 0 0 192.168.23.255:137 0.0.0.0:* 0 30392381 222/nmbd udp 0 0 192.168.23.84:137 0.0.0.0:* 0 30392380 222/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 30392368 222/nmbd udp 0 0 192.168.23.255:138 0.0.0.0:* 0 30392383 222/nmbd udp 0 0 192.168.23.84:138 0.0.0.0:* 0 30392382 222/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 30392369 222/nmbd udp 0 0 192.168.23.84:5353 0.0.0.0:* 1001 30396440 495/io.tr-064.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 30393134 430/io.shelly.0 udp6 0 0 :::111 :::* 0 30390655 1/init *** Log File - Last 25 Lines *** 2025-10-12 11:40:23.767 - info: host.iobroker84 instance system.adapter.web.0 in version "7.0.8" started with pid 525 2025-10-12 11:40:25.537 - info: web.0 (525) starting. Version 7.0.8 in /opt/iobroker/node_modules/iobroker.web, node: v22.20.0, js-controller: 7.0.7 2025-10-12 11:40:25.795 - info: web.0 (525) socket.io server listening on port 8082 2025-10-12 11:40:25.799 - info: web.0 (525) http server listening on port 8082 2025-10-12 11:40:27.762 - info: host.iobroker84 instance system.adapter.iqontrol.0 in version "3.0.0" started with pid 540 2025-10-12 11:40:29.125 - info: iqontrol.0 (540) starting. Version 3.0.0 in /opt/iobroker/node_modules/iobroker.iqontrol, node: v22.20.0, js-controller: 7.0.7 2025-10-12 11:40:29.169 - info: iqontrol.0 (540) systemLanguage = de 2025-10-12 11:40:29.170 - info: iqontrol.0 (540) Creating Passphrase... 2025-10-12 11:40:29.217 - info: iqontrol.0 (540) Creating Popup States... 2025-10-12 11:40:29.290 - info: iqontrol.0 (540) Creating Widget States... 2025-10-12 11:40:29.291 - info: iqontrol.0 (540) Lists deactivated. 2025-10-12 11:40:29.292 - info: iqontrol.0 (540) Deleting unused Objects... 2025-10-12 11:40:29.292 - info: iqontrol.0 (540) Subscribing to states... 2025-10-12 11:40:29.294 - info: iqontrol.0 (540) iQontrol ready. 2025-10-12 11:40:31.715 - info: host.iobroker84 instance system.adapter.trashschedule.0 in version "3.3.0" started with pid 555 2025-10-12 11:40:33.165 - info: trashschedule.0 (555) starting. Version 3.3.0 in /opt/iobroker/node_modules/iobroker.trashschedule, node: v22.20.0, js-controller: 7.0.7 2025-10-12 11:40:33.243 - info: trashschedule.0 (555) [onReady] starting with source "ical" -> ical 2025-10-12 11:40:33.249 - info: trashschedule.0 (555) [ical] configured ical preview is 45 days (until 26.11.2025) - increase this value to find more events in the future 2025-10-12 11:40:35.666 - info: host.iobroker84 instance system.adapter.echarts.0 in version "1.9.2" started with pid 570 2025-10-12 11:40:36.881 - info: echarts.0 (570) starting. Version 1.9.2 in /opt/iobroker/node_modules/iobroker.echarts, node: v22.20.0, js-controller: 7.0.7 2025-10-12 11:40:52.818 - info: sonoff.0 (450) Client [Steckdose01] connected with secret 1760262052812_6539 2025-10-12 11:40:52.978 - info: sonoff.0 (450) Client [Steckdose02] connected with secret 1760262052977_7832 2025-10-12 11:40:53.209 - info: sonoff.0 (450) Client [Stromzaehler] connected with secret 1760262053207_304 2025-10-12 11:41:20.278 - info: admin.0 (313) ==> Connected system.user.admin from ::ffff:192.168.23.27 2025-10-12 11:41:35.334 - info: admin.0 (313) <== Disconnect system.user.admin from ::ffff:192.168.23.27 admin============ Mark until here for C&P =============
iob diag has finished.
EDIT:
Hier der Inhalt vom npm-Log/home/mf/.npm/_logs/2025-10-12T09_42_27_454Z-debug-0.log$ cat /home/mf/.npm/_logs/2025-10-12T09_42_27_454Z-debug-0.log 0 verbose cli /usr/bin/node /usr/bin/npm 1 info using npm@11.6.2 2 info using node@v22.20.0 3 silly config load:file:/usr/lib/node_modules/npm/npmrc 4 silly config load:file:/opt/iobroker/.npmrc 5 silly config load:file:/home/mf/.npmrc 6 silly config load:file:/usr/etc/npmrc 7 verbose title npm ls 8 verbose argv "ls" "--all" 9 verbose logfile logs-max:10 dir:/home/mf/.npm/_logs/2025-10-12T09_42_27_454Z- 10 verbose logfile /home/mf/.npm/_logs/2025-10-12T09_42_27_454Z-debug-0.log 11 silly logfile start cleaning logs, removing 1 files 12 silly packumentCache heap:2197815296 maxSize:549453824 maxEntrySize:274726912 13 silly logfile done cleaning log files 14 verbose shrinkwrap failed to load node_modules/.package-lock.json out of date, updated: node_modules/iobroker.js-controller 15 verbose stack Error: invalid: buffer@5.7.1 /opt/iobroker/node_modules/buffer 15 verbose stack missing: @csstools/css-parser-algorithms@^3.0.4, required by @asamuzakjp/css-color@3.2.0 15 verbose stack missing: @csstools/css-tokenizer@^3.0.3, required by @asamuzakjp/css-color@3.2.0 15 verbose stack missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-calc@2.1.4 15 verbose stack missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-calc@2.1.4 15 verbose stack missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-color-parser@3.1.0 15 verbose stack missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-color-parser@3.1.0 15 verbose stack at LS.exec (/usr/lib/node_modules/npm/lib/commands/ls.js:206:9) 15 verbose stack at async Npm.exec (/usr/lib/node_modules/npm/lib/npm.js:208:9) 15 verbose stack at async module.exports (/usr/lib/node_modules/npm/lib/cli/entry.js:67:5) 16 error code ELSPROBLEMS 17 error invalid: buffer@5.7.1 /opt/iobroker/node_modules/buffer 17 error missing: @csstools/css-parser-algorithms@^3.0.4, required by @asamuzakjp/css-color@3.2.0 17 error missing: @csstools/css-tokenizer@^3.0.3, required by @asamuzakjp/css-color@3.2.0 17 error missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-calc@2.1.4 17 error missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-calc@2.1.4 17 error missing: @csstools/css-parser-algorithms@^3.0.5, required by @csstools/css-color-parser@3.1.0 17 error missing: @csstools/css-tokenizer@^3.0.4, required by @csstools/css-color-parser@3.1.0 18 verbose cwd /opt/iobroker 19 verbose os Linux 6.14.11-3-pve 20 verbose node v22.20.0 21 verbose npm v11.6.2 22 verbose exit 1 23 verbose code 1 24 error A complete log of this run can be found in: /home/mf/.npm/_logs/2025-10-12T09_42_27_454Z-debug-0.log -
Hallo,
Danke für die Super-Anleitung
!Ich habe aktuell 2 Probleme, vielleicht kann mir da jemand helfen:
(1) vor dem Upgrade auf Trixie ist unter /etc/apt/sources.list.d nur eine Datei mit Namen raspi.list, nach dem Upgrade und dem Modernisieren habe ich eine "raspi.sources" (http://archive.raspberrypi.org/debian/) und eine "raspbian.sources" (http://raspbian.raspberrypi.org/raspbian/). Die raspi.sources ist NICHT "Signed-By". Braucht man beide rasp*.sources oder nur die raspbian.sources? Wenn man beide braucht, wo/wie bekomme ich die Signierung für raspi.sources (http://archive.raspberrypi.org/debian/)?
(2) Nach dem Upgrade auf Trixie habe ich Probleme mit Botprogrammen (Bookworm war ja python 3.11.2 und Trixie ist 3.13.5).
Fehlermeldung z.B.
"traceback (most recent call last):
File "/usr/local/searxng/searxng-src/searx/webapp.py", line 21, in <module>
import httpx
ModuleNotFoundError: No module named 'httpx'"
In der webapp.py ist die line 21:
#!/usr/bin/env python3- - coding: utf-8 - -
....
import httpx
Muss man Pfade o.ä. ändern/anpassen? -
Was steht denn drin?
Eine raspbian.sources gibt es auf meinem System nicht. Die/etc/apt/sources.list.d/raspi.sourcesschaut so aus:Types: deb URIs: http://archive.raspberrypi.com/debian/ Suites: trixie Components: main Signed-By: /usr/share/keyrings/raspberrypi-archive-keyring.pgpIst der keyring installiert?
apt policy raspberrypi-archive-keyringZu 2) fragst du wohl besser bei
https://docs.searxng.org/admin/installation-searxng.html#installation-basic
nach. -
@thomas-braun
ja, komisch, auf dem 64bit PI ist es so wie Du es beschrieben hast.
Auf dem 32bit PI ist nach dem Upgrade eine raspberian und eine raspi sources da, mit dem beschriebenen Inhalt.
Die /usr/share/keyrings/raspberrypi-archive-keyring.pgp habe ich jetzt vom 64bit zum 32bit rüberkopiert. Beim nächsten Upgrade-Versuch mal testen.Hat jemand ein Upgrade auf einem 32bit PI gemacht und auch den Effekt?
Thomas, wenn Du nur die eine hast heißt das im Extremfall ich brauche bei dem 32bit auch nur die eine sources (raspi.sources)?
-
Auf 32Bit kann das wieder anders aussehen.
Ich würde aber im Jahre 2025 kein 32Bit mehr fahren. Installier da 64Bit, wenn es die Hardware hergibt. -
Damit es hier nicht untergeht, wollte ich nochmal auf meinen
npm errornach dem Upgrade auf Trixie hinweisen.
https://forum.iobroker.net/post/1299664
Vll. kann @Thomas-Braun was dazu sagen. -
npm Fehler haben Null mit einem Dist-Upgrade deines Betriebssystems zu tun.
Mach nen eigenen Thread dazu auf.
