Probleme mit Update von 7.0.6 auf 7.0.7 - solved
-
Hallo zusammen,
nachdem ich seit Stunden versuche, von 7.0.6 auf 7.0.7 upzudaten, brauche ich Eure Hilfe.
Das System ist Debian Trixie (alles aktuell) auf einem Proxmox.
Das Update auf 7.0.7 läuft normal durch. Aber danach ist Iobroker tot (lässt sich nicht mehr aufrufen).
Fixer habe ich schon mehrfach durchlaufen lassen.
Nachfolgend die Ausgaben von iob diag.
Würde mich freuen, wenn mir jemand weiterhelfen kann.========== Start marking the full check here ===========
Script v.2025-08-09 *** BASE SYSTEM *** Operating System: Debian GNU/Linux 13 (trixie) Static hostname: IOBrokerhost 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: Standard PC _i440FX + PIIX, 1996_ Firmware Version: rel-1.16.3-0-ga6ed6b701f0a-prebuilt.qemu.org Firmware Date: Tue 2014-04-01 Firmware Age: 11y 6month 1w 1d OS is similar to: model name : Common KVM processor Docker : false Virtualization : kvm Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 10:42:30 up 17 min, 2 users, load average: 2.33, 1.71, 0.97 CPU threads: 16 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Thu 2025-10-09 10:42:30 CEST Universal time: Thu 2025-10-09 08:42:30 UTC RTC time: Thu 2025-10-09 08:42:30 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': deifel HOME=/home/deifel GROUPS=deifel adm cdrom floppy sudo audio dip video plugdev netdev iobroker User that is running 'js-controller': iobroker HOME=/home/iobroker SUDO_HOME=/home/deifel GROUPS=iobroker tty dialout audio video plugdev bluetooth *** 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: 12G 3.6G 6.1G 11M 2.9G 8.6G Swap: 8.4G 0B 8.4G Total: 20G 3.6G 14G Active iob-Instances: 8 11682 M total memory 3454 M used memory 3006 M active memory 2273 M inactive memory 5822 M free memory 210 M buffer memory 2518 M swap cache 7997 M total swap 0 M used swap 7997 M free swap *** top - Table Of Processes *** top - 10:42:30 up 17 min, 2 users, load average: 2.33, 1.71, 0.97 Tasks: 197 total, 2 running, 195 sleeping, 0 stopped, 0 zombie %Cpu(s): 16.7 us, 0.0 sy, 0.0 ni, 83.3 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 11682.2 total, 5826.7 free, 3450.3 used, 2728.8 buff/cache MiB Swap: 7998.0 total, 7998.0 free, 0.0 used. 8231.9 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 5.7G 0 5.7G 0% /dev tmpfs tmpfs 1.2G 8.6M 1.2G 1% /run /dev/sda1 ext4 24G 9.4G 14G 42% / tmpfs tmpfs 5.8G 0 5.8G 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 5.8G 2.2M 5.8G 1% /tmp tmpfs tmpfs 1.0M 0 1.0M 0% /run/credentials/getty@tty1.service tmpfs tmpfs 1.2G 8.0K 1.2G 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Thu Oct 9 10:25:12 2025] EXT4-fs (sda1): mounted filesystem 093412ee-6337-497e-81e2-34ee5e4b22ac ro with ordered data mode. Quota mode: none. [Thu Oct 9 10:25:12 2025] EXT4-fs (sda1): re-mounted 093412ee-6337-497e-81e2-34ee5e4b22ac r/w. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/sda1 ext4 rw,relatime,errors=remount-ro Files in neuralgic directories: /var: 314M /var/ 205M /var/lib 154M /var/lib/apt/lists 154M /var/lib/apt 104M /var/cache Archived and active journals take up 8M in the file system. /opt/iobroker/backups: 24K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.8G /opt/iobroker/iobroker-data/ 420M /opt/iobroker/iobroker-data/backup-objects 409M /opt/iobroker/iobroker-data/files 307M /opt/iobroker/iobroker-data/history 76M /opt/iobroker/iobroker-data/files/iqontrol.meta/userimages The five largest files in iobroker-data are: 228M /opt/iobroker/iobroker-data/BSZExtLog_1_Oelverbrauch_Liter.csv 141M /opt/iobroker/iobroker-data/objects.jsonl 58M /opt/iobroker/iobroker-data/objects.json.migrated 58M /opt/iobroker/iobroker-data/objects.json.bak.migrated 43M /opt/iobroker/iobroker-data/states.jsonl 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 v20.19.5 /usr/bin/node v20.19.5 /usr/bin/npm 10.8.2 /usr/bin/npx 10.8.2 /usr/bin/corepack 0.33.0 nodejs: Installed: 20.19.5-1nodesource1 Candidate: 20.19.5-1nodesource1 Version table: *** 20.19.5-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 20.19.4-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.2+dfsg-1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 20.19.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.19.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.3-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.18.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.17.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/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: Uncaught Rejection: Error [ERR_MODULE_NOT_FOUND]: Cannot find module '/opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupList.js' imported from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup.js at finalizeResolution (node:internal/modules/esm/resolve:283:11) at moduleResolve (node:internal/modules/esm/resolve:952:10) at defaultResolve (node:internal/modules/esm/resolve:1188:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:708:12) at #cachedDefaultResolve (node:internal/modules/esm/loader:657:25) at ModuleLoader.resolve (node:internal/modules/esm/loader:640:38) at ModuleLoader.getModuleJobForImport (node:internal/modules/esm/loader:264:38) at ModuleLoader.import (node:internal/modules/esm/loader:605:34) at defaultImportModuleDynamicallyForModule (node:internal/modules/esm/utils:221:31) at importModuleDynamicallyCallback (node:internal/modules/esm/utils:260:12) Core adapters versions node:internal/modules/cjs/loader:1210 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1207:15) at Module._load (node:internal/modules/cjs/loader:1038:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.5 js-controller: node:internal/modules/cjs/loader:1210 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1207:15) at Module._load (node:internal/modules/cjs/loader:1038:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.5 admin: node:internal/modules/cjs/loader:1210 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1207:15) at Module._load (node:internal/modules/cjs/loader:1038:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.5 javascript: nodejs modules from github: 3 | `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc | +-- samsungtv@0.0.0 invalid: "https://git@github.com/luca-saggese/samsungtv" from node_modules/iobroker.samsung | +-- syno@3.0.0 invalid: "git+https://git@github.com/MeisterTR/syno.git" from node_modules/iobroker.synology Adapter State system.adapter.admin.0 : admin : IOBrokerhost - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.alexa2.0 : alexa2 : IOBrokerhost - enabled system.adapter.backitup.1 : backitup : IOBrokerhost - enabled system.adapter.ble.0 : ble : IOBrokerhost - disabled system.adapter.bring.0 : bring : IOBrokerhost - enabled system.adapter.cloud.0 : cloud : IOBrokerhost - disabled system.adapter.daswetter.0 : daswetter : IOBrokerhost - disabled system.adapter.discovery.0 : discovery : IOBrokerhost - disabled system.adapter.dwd.0 : dwd : IOBrokerhost - disabled system.adapter.email.0 : email : IOBrokerhost - disabled system.adapter.feiertage.0 : feiertage : IOBrokerhost - disabled system.adapter.govee-app.0 : govee-app : IOBrokerhost - enabled system.adapter.hass.0 : hass : IOBrokerhost - disabled, port: 8123 system.adapter.history.0 : history : IOBrokerhost - disabled + system.adapter.hm-rega.0 : hm-rega : IOBrokerhost - enabled + system.adapter.hm-rpc.0 : hm-rpc : IOBrokerhost - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : IOBrokerhost - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : IOBrokerhost - enabled, port: 0 system.adapter.homeconnect.1 : homeconnect : IOBrokerhost - disabled system.adapter.hue.0 : hue : IOBrokerhost - disabled, port: 443 + system.adapter.ical.0 : ical : IOBrokerhost - enabled system.adapter.info.0 : info : IOBrokerhost - enabled system.adapter.iot.0 : iot : IOBrokerhost - enabled system.adapter.iqontrol.0 : iqontrol : IOBrokerhost - disabled + system.adapter.javascript.0 : javascript : IOBrokerhost - enabled system.adapter.mbus.0 : mbus : IOBrokerhost - disabled, port: 3493 system.adapter.mbus.1 : mbus : IOBrokerhost - disabled, port: 3493 system.adapter.melcloud.0 : melcloud : IOBrokerhost - disabled system.adapter.mihome-vacuum.1 : mihome-vacuum : IOBrokerhost - disabled, port: 54321 system.adapter.mihome-vacuum.2 : mihome-vacuum : IOBrokerhost - disabled, port: 54321 system.adapter.mihome.0 : mihome : IOBrokerhost - disabled, port: 9898, bind: 0.0.0.0 system.adapter.mqtt-client.0 : mqtt-client : IOBrokerhost - enabled, port: 1883 system.adapter.mqtt.0 : mqtt : IOBrokerhost - disabled, port: 1883, bind: 0.0.0.0 system.adapter.openweathermap.0 : openweathermap : IOBrokerhost - disabled system.adapter.pollenflug.0 : pollenflug : IOBrokerhost - disabled system.adapter.scenes.0 : scenes : IOBrokerhost - disabled system.adapter.shelly.0 : shelly : IOBrokerhost - disabled, port: 1882, bind: 0.0.0.0 system.adapter.simple-api.0 : simple-api : IOBrokerhost - enabled, port: 8087, bind: 0.0.0.0, run as: admin system.adapter.sma-em.0 : sma-em : IOBrokerhost - disabled system.adapter.smartgarden.0 : smartgarden : IOBrokerhost - disabled system.adapter.smartthings.0 : smartthings : IOBrokerhost - enabled system.adapter.sourceanalytix.0 : sourceanalytix : IOBrokerhost - enabled system.adapter.synology.0 : synology : IOBrokerhost - disabled, port: 5001 + system.adapter.telegram.0 : telegram : IOBrokerhost - enabled, port: 8443, bind: 0.0.0.0 system.adapter.trashschedule.0 : trashschedule : IOBrokerhost - disabled system.adapter.unifi.0 : unifi : IOBrokerhost - disabled system.adapter.velux.0 : velux : IOBrokerhost - enabled system.adapter.viessmannapi.0 : viessmannapi : IOBrokerhost - disabled system.adapter.web.0 : web : IOBrokerhost - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.wifilight.0 : wifilight : IOBrokerhost - enabled + instance is alive Enabled adapters with bindings system.adapter.admin.0 : admin : IOBrokerhost - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.hm-rpc.0 : hm-rpc : IOBrokerhost - enabled, port: 0 + system.adapter.hm-rpc.1 : hm-rpc : IOBrokerhost - enabled, port: 0 + system.adapter.hm-rpc.2 : hm-rpc : IOBrokerhost - enabled, port: 0 system.adapter.mqtt-client.0 : mqtt-client : IOBrokerhost - enabled, port: 1883 system.adapter.simple-api.0 : simple-api : IOBrokerhost - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.telegram.0 : telegram : IOBrokerhost - enabled, port: 8443, bind: 0.0.0.0 system.adapter.web.0 : web : IOBrokerhost - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories node:internal/modules/cjs/loader:1210 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1207:15) at Module._load (node:internal/modules/cjs/loader:1038:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.5 Installed ioBroker-Adapters node:internal/modules/cjs/loader:1210 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1207:15) at Module._load (node:internal/modules/cjs/loader:1038:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:164:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.19.5 Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** W: https://deb.nodesource.com/node_20.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-security trixie-security InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Hit:4 http://deb.debian.org/debian trixie-backports InRelease Hit:5 https://deb.nodesource.com/node_20.x nodistro InRelease Reading package lists... W: https://deb.nodesource.com/node_20.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 0.0.0.0:111 0.0.0.0:* LISTEN 0 5170 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 8952 747/sshd: /usr/sbin tcp 0 0 192.168.1.172:2001 0.0.0.0:* LISTEN 1001 48216 14770/io.hm-rpc.0 tcp 0 0 0.0.0.0:9001 0.0.0.0:* LISTEN 1001 38744 13384/iobroker.js-c tcp 0 0 0.0.0.0:9000 0.0.0.0:* LISTEN 1001 38749 13384/iobroker.js-c tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 0 5773 993/exim4 tcp6 0 0 ::1:25 :::* LISTEN 0 5774 993/exim4 tcp6 0 0 :::111 :::* LISTEN 0 4561 1/init tcp6 0 0 :::22 :::* LISTEN 0 8954 747/sshd: /usr/sbin udp 0 0 0.0.0.0:5353 0.0.0.0:* 107 9251 653/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 5745 673/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 5171 1/init udp 0 0 0.0.0.0:59950 0.0.0.0:* 107 9253 653/avahi-daemon: r udp6 0 0 :::5353 :::* 107 9252 653/avahi-daemon: r udp6 0 0 :::111 :::* 0 2521 1/init udp6 0 0 :::58570 :::* 107 9254 653/avahi-daemon: r *** Log File - Last 25 Lines *** 2025-10-09 10:42:41.609 - info: velux.0 (15606) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-10-09 10:42:41.786 - info: mqtt-client.0 (15040) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-10-09 10:42:41.608 - info: host.IOBrokerhost stopInstance system.adapter.javascript.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.hm-rega.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.hm-rpc.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.hm-rpc.1 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.hm-rpc.2 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.backitup.1 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.alexa2.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.wifilight.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.info.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.iot.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.velux.0 send kill signal 2025-10-09 10:42:41.899 - info: host.IOBrokerhost stopInstance system.adapter.sourceanalytix.0 send kill signal 2025-10-09 10:42:41.902 - info: hm-rega.0 (14759) terminating 2025-10-09 10:42:41.902 - info: hm-rega.0 (14759) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-10-09 10:42:42.079 - info: hm-rega.0 (14759) terminating 2025-10-09 10:42:42.079 - info: javascript.0 (14733) terminating 2025-10-09 10:42:42.079 - info: alexa2.0 (14960) terminating 2025-10-09 10:42:42.082 - info: backitup.1 (14932) terminating 2025-10-09 10:42:42.083 - info: wifilight.0 (15010) terminating 2025-10-09 10:42:42.083 - info: telegram.0 (14672) terminating 2025-10-09 10:42:42.083 - info: telegram.0 (14672) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2025-10-09 10:42:42.083 - info: info.0 (15070) terminating 2025-10-09 10:42:42.110 - info: velux.0 (15606) terminating============ Mark until here for C&P =============
-
@deifel den Controller nochmal drüber installieren
iob stop cd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller@7.0.7 iob start -
@crunchip
Das habe ich bereits mehrfach versucht. Die Installation läuft auch durch:npm warn skipping integrity check for git dependency ssh://git@github.com/TA2k/ioBroker.govee-app.git npm warn deprecated dgram@1.0.1: npm is holding this package for security reasons. As it's a core Node module, we will not transfer it over to other users. You may safely remove the package from your dependencies. npm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful. npm warn deprecated npmlog@2.0.4: This package is no longer supported. npm warn deprecated npmlog@5.0.1: This package is no longer supported. npm warn deprecated request-promise-native@1.0.9: request-promise-native has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated npmlog@4.1.2: This package is no longer supported. npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated request-promise@4.2.6: request-promise has been deprecated because it extends the now deprecated request package, see https://github.com/request/request/issues/3142 npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported. npm warn deprecated are-we-there-yet@1.1.7: This package is no longer supported. npm warn deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@8.1.0: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated querystring@0.2.1: The querystring API is considered Legacy. new code should use the URLSearchParams API instead. npm warn deprecated gauge@1.2.7: This package is no longer supported. npm warn deprecated yaeti@0.0.6: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm warn deprecated q@1.5.1: You or someone you depend on is using Q, the JavaScript Promise library that gave JavaScript developers strong feelings about promises. They can almost certainly migrate to the native JavaScript promise now. Thank you literally everyone for joining me in this bet against the odds. Be excellent to each other. npm warn deprecated npm warn deprecated (For a CapTP with native promises, see @endo/eventual-send and @endo/captp) npm warn deprecated node-inspect@2.0.0: This module is part of Node.js core and does not need to be installed separately. It is now unmaintained. npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated debug@4.1.1: Debug versions >=3.2.0 <3.2.7 || >=4 <4.3.1 have a low-severity ReDos regression when used in a Node.js environment. It is recommended you upgrade to 3.2.7 or 4.3.1. (https://github.com/visionmedia/debug/issues/797) npm warn deprecated gauge@3.0.2: This package is no longer supported. npm warn deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm warn deprecated gauge@2.7.4: This package is no longer supported. npm warn deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm warn deprecated node-domexception@1.0.0: Use your platform's native DOMException instead npm warn deprecated appium-logger@2.1.0: Moved into appium-support npm warn deprecated xmldom@0.1.16: Deprecated due to CVE-2021-21366 resolved in 0.5.0 npm warn deprecated sinon@15.2.0: 16.1.1 npm warn deprecated core-js@1.2.7: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. npm warn deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js. changed 1710 packages in 1m 199 packages are looking for funding run `npm fund` for detailsNach der Anmeldung verhaut es allerdings wieder alles. Dann ist er plötzlich wieder nicht erreichbar...
Habe das bereits paar mal versucht. Immer nach der Anmeldung verhaut es dann wieder alles.
Woran kann das liegen?open Request’s Past, Present and Future #3142
open Request’s Past, Present and Future #3142
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
closed ReDos Vulnerability Regression Visibility Notice #797
open Request’s Past, Present and Future #3142
-
Bring das zunächst mal auf nodejs@22.
iob nodejs-updateUnd dann probierst du es nochmal per
iob update iob stop iob upgrade all iob upgrade self iob start -
@deifel sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
nachdem ich seit Stunden versuche, von 7.0.6 auf 7.0.7 upzudaten,
was denn bitte?
Auch Threadtitel sinnvoll anpassen -
@deifel sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
@crunchip
Das habe ich bereits mehrfach versucht. Die Installation läuft auch durch:[...SNIP]
Nach der Anmeldung verhaut es allerdings wieder alles. Dann ist er plötzlich wieder nicht erreichbar...
Habe das bereits paar mal versucht. Immer nach der Anmeldung verhaut es dann wieder alles.
Woran kann das liegen?Wie wärs mal mit dem vollständigen Log der Installation, nicht nur mit den Warnungen / Fehlern ? Da muss es mehr geben als das was Du da gepostet hast.
@thomas-braun sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
Bring das zunächst mal auf nodejs@22.
Mag sinnvoll sein, wird aber die Fehler bei der Installation des JS-Controllers (der Node22 nicht fordert) nicht beheben.
A.
-
@asgothian sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
Mag sinnvoll sein, wird aber die Fehler bei der Installation des JS-Controllers (der Node22 nicht fordert) nicht beheben.
Ist aber die sinnvollste Ausgangsbasis für den weiteren Betrieb.
-
@thomas-braun sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
@asgothian sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
Mag sinnvoll sein, wird aber die Fehler bei der Installation des JS-Controllers (der Node22 nicht fordert) nicht beheben.
Ist aber die sinnvollste Ausgangsbasis für den weiteren Betrieb.
Das ist unbestritten, aber aus Erfahrung bei der Reparatur von komplexen Systemen hat sich gezeigt das es besser ist erst den Fehler zu elimineren und dann grössere Updates zu fahren als erst Updates zu fahren und damit dann ggf. weitere Fehler zu riskieren. Wer weiss ob alle Adapter des OP unter Node22 wirklich laufen, z.Bsp.
Und in diesem Fall ist ganz eindeutig das Node 20 kompatibel ist - ich setz das auf meinem Entwicklungssystem so ein.
A.
-
Vielen Dank für Eure Hilfe! Tatsächlich hat es nach einem Update auf Node 22 funktioniert bzw. es zerhaut jetzt das ganze nicht mehr. Sehr eigenartig - hatte hier überhaupt keinen Zusammenhang gesehen...
Hoffentlich bleibt das so. Kommt mir sehr instabil vor das ganze. Bekam am Anfang immer wieder einen GUI-Fehler (leider nicht gespeichert). Nachdem ich dann den Browser-Cache geleert hatte, bin ich drauf gekommen und seitdem scheint es zu laufen. -
@deifel sagte in Probleme mit Update von 7.0.6 auf 7.0.7:
Tatsächlich hat es nach einem Update auf Node 22 funktioniert bzw. es zerhaut jetzt das ganze nicht mehr. Sehr eigenartig - hatte hier überhaupt keinen Zusammenhang gesehen...
Das hatte ich genauso erwartet...
