Beim Update von Adaptern stürzt der ioBroker ab
-
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
Habt Ihr eine Idee, wie ich mein System wieder lauffähig bekomme?
iob diaganschauen.
-
@flommaster Windows??
-
@homoran
Nein. Das System läuft auf einem NUC mit Linux. -
@flommaster dann bitte die Langfassung von
iob diag -
Hier ist das komplette Ergebnis.
Ich habe nach dem letzten Versuch das Problem, dass ich den Controller gar nicht mehr zum laufen bekomme...Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: ioBrokerdebian Icon name: computer-desktop Chassis: desktop Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 5.10.0-32-amd64 Architecture: x86-64 model name : Intel(R) Celeron(R) CPU J3355 @ 2.00GHz Docker : false Virtualization : none Kernel : x86_64 Userland : 64 bit Systemuptime and Load: 14:18:18 up 54 min, 1 user, load average: 2.75, 4.55, 3.06 CPU threads: 2 *** Time and Time Zones *** Local time: Sun 2024-08-18 14:18:19 CEST Universal time: Sun 2024-08-18 12:18:19 UTC RTC time: Sun 2024-08-18 12:18:19 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': flo HOME=/home/flo GROUPS=flo cdrom floppy sudo audio dip video plugdev netdev iobroker User that is running 'js-controller': js-controller is not running *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 3.7G 158M 3.0G 2.0M 606M 3.3G Swap: 3.9G 27M 3.9G Total: 7.7G 185M 6.9G Active iob-Instances: 0 3749 M total memory 158 M used memory 401 M active memory 198 M inactive memory 2983 M free memory 299 M buffer memory 307 M swap cache 3923 M total swap 27 M used swap 3896 M free swap *** top - Table Of Processes *** top - 14:18:19 up 54 min, 1 user, load average: 2.75, 4.55, 3.06 Tasks: 106 total, 2 running, 104 sleeping, 0 stopped, 0 zombie %Cpu(s): 3.1 us, 0.0 sy, 0.0 ni, 96.9 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 3749.5 total, 2983.8 free, 158.6 used, 607.1 buff/cache MiB Swap: 3924.0 total, 3897.0 free, 27.0 used. 3348.1 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 1.9G 0 1.9G 0% /dev tmpfs tmpfs 375M 2.2M 373M 1% /run /dev/mmcblk0p2 ext4 53G 21G 30G 42% / tmpfs tmpfs 1.9G 0 1.9G 0% /dev/shm tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock /dev/mmcblk0p1 vfat 511M 5.8M 506M 2% /boot/efi tmpfs tmpfs 375M 0 375M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sun Aug 18 13:23:25 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Opts: (null) [Sun Aug 18 13:23:26 2024] EXT4-fs (mmcblk0p2): re-mounted. Opts: errors=remount-ro Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,relatime,errors=remount-ro |-/sys sysfs sysfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/security securityfs securityfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/cgroup cgroup2 cgroup2 rw,nosuid,nodev,noexec,relatime,nsdelegate,memory_recursiveprot | |-/sys/fs/pstore pstore pstore rw,nosuid,nodev,noexec,relatime | |-/sys/firmware/efi/efivars efivarfs efivarfs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/bpf none bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime | `-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,nosuid,nodev,noexec,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct,pipe_ino=11397 |-/dev udev devtmpfs rw,nosuid,relatime,size=1901928k,nr_inodes=475482,mode=755 | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime | `-/dev/hugepages hugetlbfs hugetlbfs rw,relatime,pagesize=2M |-/run tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=383948k,mode=755 | |-/run/lock tmpfs tmpfs rw,nosuid,nodev,noexec,relatime,size=5120k | |-/run/rpc_pipefs sunrpc rpc_pipefs rw,relatime | `-/run/user/1000 tmpfs tmpfs rw,nosuid,nodev,relatime,size=383944k,nr_inodes=95986,mode=700,uid=1000,gid=1000 `-/boot/efi /dev/mmcblk0p1 vfat rw,relatime,fmask=0077,dmask=0077,codepage=437,iocharset=ascii,shortname=mixed,utf8,errors=remount-ro Files in neuralgic directories: /var: 4.7G /var/ 4.0G /var/log/journal/37ccd33008fc48b08294fcfc7d596e40 4.0G /var/log/journal 4.0G /var/log 521M /var/cache 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 72.0M in the file system. /opt/iobroker/backups: 2.1G /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 2.5G /opt/iobroker/iobroker-data/ 1.7G /opt/iobroker/iobroker-data/history 512M /opt/iobroker/iobroker-data/files 139M /opt/iobroker/iobroker-data/backup-objects 88M /opt/iobroker/iobroker-data/files/echarts.admin The five largest files in iobroker-data are: 41M /opt/iobroker/iobroker-data/files/material/static/js/main.c5478f66.js.map 23M /opt/iobroker/iobroker-data/objects.json.migrated 23M /opt/iobroker/iobroker-data/objects.json.bak.migrated 23M /opt/iobroker/iobroker-data/files/echarts/static/js/main.eb0afecd.js.map 23M /opt/iobroker/iobroker-data/files/echarts.admin/static/js/main.7952f0f7.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': /dev/serial/by-id/usb-FTDI_FT230X_Basic_UART_D307ZMZV-if00-port0 *** NodeJS-Installation *** /usr/bin/nodejs v18.20.4 /usr/bin/node v18.20.4 /usr/bin/npm 10.7.0 /usr/bin/npx 10.7.0 /usr/bin/corepack 0.28.0 nodejs: Installed: 18.20.4-1nodesource1 Candidate: 18.20.4-1nodesource1 Version table: *** 18.20.4-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 18.20.3-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.20.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://deb.debian.org/debian bullseye/main amd64 Packages 500 http://security.debian.org/debian-security bullseye-security/main amd64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 Core adapters versions node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 js-controller: node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 admin: node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 javascript: nodejs modules from github: 1 | `-- xmlbuilder@0.4.2 invalid: "https://github.com/hobbyquaker/xmlbuilder-js/tarball/29fe5030dc6852007dc8d1bfd5109d75f8da58d5" from node_modules/homematic-xmlrpc Adapter State Enabled adapters with bindings ioBroker-Repositories node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 Installed ioBroker-Instances node:internal/modules/cjs/loader:1143 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1140:15) at Module._load (node:internal/modules/cjs/loader:981:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:128:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v18.20.4 Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** Hit:1 http://ftp.debian.org/debian bullseye-backports InRelease Hit:2 http://security.debian.org/debian-security bullseye-security InRelease Hit:3 http://deb.debian.org/debian bullseye InRelease Hit:4 http://deb.debian.org/debian bullseye-updates InRelease Hit:5 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 127.0.0.1:25 0.0.0.0:* LISTEN 0 16130 703/exim4 tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 16363 786/smbd tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 0 16364 786/smbd tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN 109 16070 425/redis-server 12 tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 10125 1/init tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 14876 461/sshd: /usr/sbin tcp6 0 0 ::1:25 :::* LISTEN 0 16131 703/exim4 tcp6 0 0 :::445 :::* LISTEN 0 16361 786/smbd tcp6 0 0 ::1:6379 :::* LISTEN 109 16071 425/redis-server 12 tcp6 0 0 :::139 :::* LISTEN 0 16362 786/smbd tcp6 0 0 :::111 :::* LISTEN 0 10129 1/init tcp6 0 0 :::22 :::* LISTEN 0 14887 461/sshd: /usr/sbin udp 0 0 0.0.0.0:39663 0.0.0.0:* 108 16019 418/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 16017 418/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 16032 407/dhclient udp 0 0 0.0.0.0:111 0.0.0.0:* 0 10126 1/init udp 0 0 192.168.178.255:137 0.0.0.0:* 0 16280 424/nmbd udp 0 0 192.168.178.66:137 0.0.0.0:* 0 16279 424/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 16117 424/nmbd udp 0 0 192.168.178.255:138 0.0.0.0:* 0 16282 424/nmbd udp 0 0 192.168.178.66:138 0.0.0.0:* 0 16281 424/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 16118 424/nmbd udp6 0 0 :::5353 :::* 108 16018 418/avahi-daemon: r udp6 0 0 :::36880 :::* 108 16020 418/avahi-daemon: r udp6 0 0 :::111 :::* 0 10132 1/init *** Log File - Last 25 Lines *** 2024-08-18 13:35:45.339 - info: sql.0 (879) Terminated (NO_ERROR): Without reason 2024-08-18 13:35:45.802 - error: sql.0 (879) Objects database error: read ECONNRESET 2024-08-18 13:35:46.445 - info: modbus.1 (1048) terminating with timeout 2024-08-18 13:35:45.384 - info: admin.0 (755) terminating http server on port 8081 2024-08-18 13:35:46.272 - info: admin.0 (755) terminating 2024-08-18 13:35:46.366 - info: admin.0 (755) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-08-18 13:35:43.410 - info: eusec.0 (1746) Disconnect from station T8410P202112109E 2024-08-18 13:35:43.423 - info: eusec.0 (1746) Disconnect from station T84A1P102312214F 2024-08-18 13:35:43.424 - info: eusec.0 (1746) Disconnect from station T84A1P1023122467 2024-08-18 13:35:43.464 - info: eusec.0 (1746) terminating 2024-08-18 13:35:43.466 - info: eusec.0 (1746) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-08-18 13:35:43.492 - info: eusec.0 (1746) Disconnected from station T8410P202112109E 2024-08-18 13:35:44.969 - info: eusec.0 (1746) Disconnected from station T84A1P102312214F 2024-08-18 13:35:46.206 - info: eusec.0 (1746) Disconnected from station T84A1P1023122467 2024-08-18 13:35:46.776 - info: eusec.0 (1746) terminating 2024-08-18 13:35:46.997 - info: admin.0 (755) terminating 2024-08-18 13:35:47.926 - info: meross.0 (978) terminating 2024-08-18 13:35:47.980 - info: meross.0 (978) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2024-08-18 13:35:48.000 - info: admin.0 (755) terminating with timeout 2024-08-18 13:35:50.865 - info: meross.0 (978) terminating 2024-08-18 13:35:50.896 - error: eusec.0 (1746) go2rtc error: exit with signal: terminated 2024-08-18 13:35:50.905 - info: eusec.0 (1746) go2rtc terminated with exitcode 0 2024-08-18 13:35:50.907 - info: eusec.0 (1746) terminating with timeout 2024-08-18 13:35:51.525 - error: history.0 (795) Cannot find view "system" for search "instance" : Connection is closed. -
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
load average: 2.75, 4.55, 3.06
oh ja, der rödelt gewaltig!
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
js-controller is not running
ok, läuft ja im Moment nicht.
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
usr/bin/nodejs v18.20.4
sollte beizeiten mal auf v20 hochgezogen werden.
mal sehn was @Thomas-Braun meint.
ich würde versuchen den Controller drüberzuinstallieren -
Läuft das System von einer SD-Karte? Hat der NUC keine SSD/Festplatte?
sudo usermod -aG adm flo exitiob nodejs-update cd /opt/iobroker npm install iobroker.js-controller@6.0.9Dann mal einen kompletten Neustart von der Kiste.
Und wenn das läuft installierst du da Debian 12 'Bookworm', dein Debian 11 hat das Lebensende erreicht. -
Hallo Thomas, hallo Homoran,
vielen Dank für die schnelle Unterstützung!
Doch der NUC hat ne SSD. Eine SD-Karte nutze ich bei dem Gerät nicht.
Ok, ich habe die Kiste neu gestartet und die Befehle ausgeführt.
Am Schluss erhalte ich folgende Fehlermeldung:
npm warn cleanup Failed to remove some directories [ npm warn cleanup [ npm warn cleanup '/opt/iobroker/node_modules/iobroker.javascript/node_modules', npm warn cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.javascript/node_modules/.bin'] { npm warn cleanup errno: -39, npm warn cleanup code: 'ENOTEMPTY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: '/opt/iobroker/node_modules/iobroker.javascript/node_modules/.bin' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup '/opt/iobroker/node_modules/iobroker.javascript', npm warn cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.javascript/node_modules/readable-stream'] { npm warn cleanup errno: -39, npm warn cleanup code: 'ENOTEMPTY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: '/opt/iobroker/node_modules/iobroker.javascript/node_modules/readable-stream' npm warn cleanup } npm warn cleanup ], npm warn cleanup [ npm warn cleanup '/opt/iobroker/node_modules/iobroker.javascript', npm warn cleanup [Error: ENOTEMPTY: directory not empty, rmdir '/opt/iobroker/node_modules/iobroker.javascript/node_modules/readable-stream'] { npm warn cleanup errno: -39, npm warn cleanup code: 'ENOTEMPTY', npm warn cleanup syscall: 'rmdir', npm warn cleanup path: '/opt/iobroker/node_modules/iobroker.javascript/node_modules/readable-stream' npm warn cleanup } npm warn cleanup ] npm warn cleanup ] npm error code 127 npm error path /opt/iobroker/node_modules/zlib npm error command failed npm error command sh -c node-waf clean || true; node-waf configure build npm error sh: 1: node-waf: not found npm error sh: 1: node-waf: not found npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-08-18T12_33_37_590Z-debug-0.logHabt Ihr eine Idee, wie ich das System noch retten kann?
Vielen Dank und viele Grüße
Florian
-
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
wie ich das System noch retten kann?
iob stop iob fix iob start -
@flommaster
Ich wunder mich nur, weil typischerweise das Gerät
/dev/mmcblk0p2
eine SD-Karte beschreibt.node-waf liefert:
https://forum.iobroker.net/topic/74670/adapter-lassen-sich-nicht-mehr-aktualisieren -
@thomas-braun laut den Daten ist keine SSD gemountet. Das Teil läuft von einer SD-Karte. Meine Vermutung. Das Teil hat einen SD-Karten-Slot. Karte rein und dann vielleicht Klonen wollen auf SSD und vergessen rauszunehmen. Oder Geklont und ohne SD-KArte läuft das Teil nicht. Oder Oder Oder...
Ro75.
-
@ro75 sagte in Beim Update von Adaptern stürzt der ioBroker ab:
Das Teil läuft von einer SD-Karte.
Ja, würde ich auch so sehen.
-
Ich weiß beim besten Willen nicht, wie das Teil auf einer SD-Karten laufen soll.
Ich habe gerade noch mal alle Anschlüsse geprüft. In meinem NUC steckt keine SD-Karte...
Es könnte ggf. dran liegen, dass ich den NUC vor ein paar Jahren von einem Raspberry PI mit SD-Karte umgezogen habe...Mit den Updates bin ich jetzt durch.
Das System läuft jetzt auf Debian Bookworm
/usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 nodejs: Installiert: 20.16.0-1nodesource1 Installationskandidat: 20.16.0-1nodesource1 Versionstabelle: *** 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main amd64 Packages 100 /var/lib/dpkg/status 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 18.19.0+dfsg-6~deb12u2 500 500 http://deb.debian.org/debian bookworm/main amd64 Packages 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main amd64 PackagesDen ioBroker bekomme ich aber leider nicht zum laufen.
Ich habe mehrfach den Fixer (iob fix) als auch die Installation ausgeführt.
Mir ist gerade aufgefallen, dass im Verzeichnis die Datei "/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js" fehlt.
/opt/iobroker/node_modules/iobroker.js-controller$ dir build LICENSE node_modules -
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
Es könnte ggf. dran liegen, dass ich den NUC vor ein paar Jahren von einem Raspberry PI mit SD-Karte umgezogen habe...
Vermutlich geclont. Da clonst du aber auch die falschen Devices mit.
-
iob stop cd /opt/iobroker npm install iobroker.js-controller@6.0.9 iob start -
Hallo Thomas,
nach zahlreichen Warnmeldungen, kommt dann eine Error Meldung (npm error code 127) die den Vorgang abbricht.
npm warn skipping integrity check for git dependency ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.git npm warn skipping integrity check for git dependency ssh://git@github.com/peterbaumert/ioBroker.vofo-speedtest.git npm warn skipping integrity check for git dependency ssh://git@github.com/Scrounger/ioBroker.vis-materialdesign.git npm warn skipping integrity check for git dependency ssh://git@github.com/ioBroker/ioBroker.vis-2-widgets-material.git npm warn skipping integrity check for git dependency ssh://git@github.com/ioBroker/ioBroker.vis-2.git npm warn skipping integrity check for git dependency ssh://git@github.com/DrozmotiX/ioBroker.sourceanalytix.git npm warn skipping integrity check for git dependency ssh://git@github.com/aendue/ioBroker.reolink.git npm warn skipping integrity check for git dependency ssh://git@github.com/iobroker-community-adapters/ioBroker.ical.git npm warn skipping integrity check for git dependency ssh://git@github.com/TA2k/ioBroker.gartenbewaesserung.git npm warn skipping integrity check for git dependency ssh://git@github.com/SKB-CGN/ioBroker.energiefluss.git npm warn skipping integrity check for git dependency ssh://git@github.com/WLAN-Kabel/ioBroker.calendar.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 @types/bl@5.1.0: This is a stub types definition. bl provides its own type definitions, so you do not need this installed. 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 @npmcli/move-file@1.1.2: This functionality has been moved to @npmcli/fs npm warn deprecated @npmcli/move-file@2.0.1: This functionality has been moved to @npmcli/fs npm warn deprecated uid-number@0.0.6: This package is no longer supported. npm warn deprecated npmlog@5.0.1: 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 npmlog@6.0.2: This package is no longer supported. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated npmlog@6.0.2: This package is no longer supported. npm warn deprecated har-validator@5.1.5: this library is no longer supported npm warn deprecated rimraf@3.0.2: Rimraf versions prior to v4 are no longer supported npm warn deprecated abab@2.0.6: Use your platform's native atob() and btoa() methods instead npm warn deprecated are-we-there-yet@2.0.0: This package is no longer supported. npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated are-we-there-yet@3.0.1: This package is no longer supported. npm warn deprecated q@1.1.2: 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 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 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@7.2.3: Glob versions prior to v9 are no longer supported npm warn deprecated domexception@4.0.0: Use your platform's native DOMException instead 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 google-p12-pem@4.0.1: Package is no longer maintained 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 google-p12-pem@3.1.4: Package is no longer maintained 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@4.0.4: This package is no longer supported. npm warn deprecated gauge@4.0.4: This package is no longer supported. npm warn deprecated gauge@4.0.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 later@1.2.0: Please upgrade to the maintained and new drop-in replacement @breejs/later at https://github.com/breejs/later 🚀 Thanks and happy hacking! 🚀 @niftylettuce npm error code 127 npm error path /opt/iobroker/node_modules/zlib npm error command failed npm error command sh -c node-waf clean || true; node-waf configure build npm error sh: 1: node-waf: not found npm error sh: 1: node-waf: not found npm error A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-08-18T19_24_28_844Z-debug-0.logKann ich da noch was retten?
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
-
@flommaster sagte in Beim Update von Adaptern stürzt der ioBroker ab:
npm error path /opt/iobroker/node_modules/zlib
npm error command failed
npm error command sh -c node-waf clean || true; node-waf configure build
npm error sh: 1: node-waf: not found
npm error sh: 1: node-waf: not found
Das ist genau das Ding aus dem anderen Thread. Welcher Adapter war das da? mihome-vaccuum?
Versuch den mal zu aktualisieren.iob update iob upgrade BÖSER_ADAPTER -
Das geht gar nicht mehr.
iob upgrade mihome-vaccuum node:internal/modules/cjs/loader:1148 throw err; ^ Error: Cannot find module '/opt/iobroker/node_modules/iobroker.js-controller/iobroker.js' at Module._resolveFilename (node:internal/modules/cjs/loader:1145:15) at Module._load (node:internal/modules/cjs/loader:986:27) at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) at node:internal/main/run_main_module:28:49 { code: 'MODULE_NOT_FOUND', requireStack: [] } Node.js v20.16.0Kann ich den Adapter auch komplett löschen. Den Staubsauger nutze ich nur noch manuell...
-
-
Wo stammen eigentlich die ganzen GITHUB dependencies her, z.B.
npm warn skipping integrity check for git dependency ssh://git@github.com/iobroker-community-adapters/ioBroker.web-speedy.gitDen Adapter gibts (dort) gar nicht ...
