npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie
-
-
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Dann weiß ich es auch nicht.
ioBroker läuft ja.
Vll. verschwindet der Fehler irgendwann von selbst.
Dernpm errorkommt nur beiiob diag.@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Zeig mal die komplette Ausgabe von
iob diagBitteschön:
========== 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: 19:17:09 up 1 day, 7:03, 1 user, load average: 0.43, 0.46, 0.47 CPU threads: 2 *** LIFE CYCLE STATUS *** Operating System is the current Debian stable version codenamed 'trixie'! *** TIME AND TIMEZONES *** Local time: Mon 2025-10-13 19:17:09 CEST Universal time: Mon 2025-10-13 17:17:09 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.5G 1.5G 6.3M 1.4G 2.8G Swap: 536M 278K 536M Total: 4.8G 1.5G 2.0G Active iob-Instances: 15 4096 M total memory 1427 M used memory 623 M active memory 1872 M inactive memory 1386 M free memory 0 M buffer memory 1288 M swap cache 512 M total swap 0 M used swap 511 M free swap *** top - Table Of Processes *** top - 19:17:09 up 1 day, 7:03, 1 user, load average: 0.43, 0.46, 0.47 Tasks: 52 total, 1 running, 51 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 4.5 sy, 0.0 ni, 90.9 id, 0.0 wa, 0.0 hi, 4.5 si, 0.0 st MiB Mem : 4096.0 total, 1384.7 free, 1428.7 used, 1288.4 buff/cache MiB Swap: 512.0 total, 511.7 free, 0.3 used. 2667.3 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.1G 4.2G 64% / //192.168.23.8/FRITZ.NAS/CT500MX5-00SSD1-01 cifs 467G 50G 417G 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 9.7G 2.8M 9.7G 1% /tmp tmpfs tmpfs 5.0M 0 5.0M 0% /run/lock 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.0G /var/ 1.3G /var/log/journal 1.3G /var/log 1.2G /var/log/journal/649cc30af99f46b985202f72e64de40c 496M /var/cache Archived and active journals take up 1.1G in the file system. /opt/iobroker/backups: 69M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 383M /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: 27M /opt/iobroker/iobroker-data/objects.jsonl 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 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: 71195) 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: 1053 *** 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 0.0.0.0:139 0.0.0.0:* LISTEN 0 30476144 255/smbd tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 0 30471050 1/init tcp 0 0 0.0.0.0:445 0.0.0.0:* LISTEN 0 30476143 255/smbd tcp 0 0 0.0.0.0:1885 0.0.0.0:* LISTEN 1001 31761702 1730/io.sonoff.0 tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 31759277 1579/iobroker.js-co tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 31758015 1579/iobroker.js-co tcp6 0 0 :::139 :::* LISTEN 0 30476142 255/smbd tcp6 0 0 :::22 :::* LISTEN 0 30476526 1/init tcp6 0 0 :::111 :::* LISTEN 0 30471052 1/init tcp6 0 0 :::445 :::* LISTEN 0 30476141 255/smbd tcp6 0 0 :::8086 :::* LISTEN 999 30476154 177/influxd tcp6 0 0 :::8081 :::* LISTEN 1001 31759357 1598/io.admin.0 tcp6 0 0 :::8082 :::* LISTEN 1001 31761907 1805/io.web.0 udp 0 0 0.0.0.0:111 0.0.0.0:* 0 30471051 1/init udp 0 0 192.168.23.255:137 0.0.0.0:* 0 30476030 208/nmbd udp 0 0 192.168.23.84:137 0.0.0.0:* 0 30476029 208/nmbd udp 0 0 0.0.0.0:137 0.0.0.0:* 0 30476017 208/nmbd udp 0 0 192.168.23.255:138 0.0.0.0:* 0 30476032 208/nmbd udp 0 0 192.168.23.84:138 0.0.0.0:* 0 30476031 208/nmbd udp 0 0 0.0.0.0:138 0.0.0.0:* 0 30476018 208/nmbd udp 0 0 192.168.23.84:5353 0.0.0.0:* 1001 31762800 1775/io.tr-064.0 udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 31762618 1715/io.shelly.0 udp6 0 0 :::111 :::* 0 30471053 1/init *** Log File - Last 25 Lines *** 2025-10-13 17:32:33.484 - info: web.0 (1805) ==> Connected system.user.admin from ::ffff:192.168.23.186 2025-10-13 17:34:19.147 - info: web.0 (1805) <== Disconnect system.user.admin from ::ffff:192.168.23.186 iqontrol.0 2025-10-13 17:34:19.705 - info: web.0 (1805) ==> Connected system.user.admin from ::ffff:192.168.23.186 2025-10-13 17:35:19.994 - info: web.0 (1805) <== Disconnect system.user.admin from ::ffff:192.168.23.186 iqontrol.0 2025-10-13 18:00:00.038 - info: host.iobroker84 instance system.adapter.ical.0 in version "1.17.0" started with pid 5332 2025-10-13 18:00:02.030 - info: ical.0 (5332) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.ical, node: v22.20.0, js-controller: 7.0.7 2025-10-13 18:00:02.414 - info: ical.0 (5332) processing URL: Abfuhrkalender https://calendar.google.com/calendar/ical/bd0a1fc1997514e89949bb190399d86de9d17b2640e28a28dbf8f1bf391e5f90%40group.calendar.google.com/private-7d7300d8d092a6268253c104d9f3fdf1/basic.ics 2025-10-13 18:00:07.500 - info: ical.0 (5332) Terminated (NO_ERROR): Without reason 2025-10-13 18:00:08.027 - info: host.iobroker84 instance system.adapter.ical.0 having pid 5332 terminated with code 0 (NO_ERROR) 2025-10-13 18:12:03.795 - info: web.0 (1805) ==> Connected system.user.admin from ::ffff:192.168.23.186 2025-10-13 18:12:11.020 - info: web.0 (1805) <== Disconnect system.user.admin from ::ffff:192.168.23.186 iqontrol.0 2025-10-13 18:30:00.031 - info: host.iobroker84 instance system.adapter.ical.0 in version "1.17.0" started with pid 5359 2025-10-13 18:30:01.837 - info: ical.0 (5359) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.ical, node: v22.20.0, js-controller: 7.0.7 2025-10-13 18:30:02.240 - info: ical.0 (5359) processing URL: Abfuhrkalender https://calendar.google.com/calendar/ical/bd0a1fc1997514e89949bb190399d86de9d17b2640e28a28dbf8f1bf391e5f90%40group.calendar.google.com/private-7d7300d8d092a6268253c104d9f3fdf1/basic.ics 2025-10-13 18:30:07.335 - info: ical.0 (5359) Terminated (NO_ERROR): Without reason 2025-10-13 18:30:07.859 - info: host.iobroker84 instance system.adapter.ical.0 having pid 5359 terminated with code 0 (NO_ERROR) 2025-10-13 18:46:50.115 - info: admin.0 (1598) ==> Connected system.user.admin from ::ffff:192.168.23.27 2025-10-13 18:47:13.830 - info: admin.0 (1598) <== Disconnect system.user.admin from ::ffff:192.168.23.27 admin 2025-10-13 19:00:00.040 - info: host.iobroker84 instance system.adapter.ical.0 in version "1.17.0" started with pid 6152 2025-10-13 19:00:01.904 - info: ical.0 (6152) starting. Version 1.17.0 in /opt/iobroker/node_modules/iobroker.ical, node: v22.20.0, js-controller: 7.0.7 2025-10-13 19:00:02.283 - info: ical.0 (6152) processing URL: Abfuhrkalender https://calendar.google.com/calendar/ical/bd0a1fc1997514e89949bb190399d86de9d17b2640e28a28dbf8f1bf391e5f90%40group.calendar.google.com/private-7d7300d8d092a6268253c104d9f3fdf1/basic.ics 2025-10-13 19:00:07.373 - info: ical.0 (6152) Terminated (NO_ERROR): Without reason 2025-10-13 19:00:07.903 - info: host.iobroker84 instance system.adapter.ical.0 having pid 6152 terminated with code 0 (NO_ERROR) 2025-10-13 19:09:32.661 - info: admin.0 (1598) ==> Connected system.user.admin from ::ffff:192.168.23.27 2025-10-13 19:09:43.940 - info: admin.0 (1598) <== Disconnect system.user.admin from ::ffff:192.168.23.27 admin============ Mark until here for C&P =============
iob diag has finished.
-
@meute Nutzt dir zwar nix, aber unter nodejs@22 ist das bei mir alles sauber:
echad@chet:/opt/iobroker $ node -v v22.20.0 echad@chet:/opt/iobroker $ npm ls canvas iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.echarts@2.0.10 │ ├── canvas@3.2.0 │ └─┬ jsdom@26.1.0 │ └── canvas@3.2.0 deduped ├─┬ iobroker.mihome-vacuum@5.3.0 │ └── canvas@3.2.0 deduped └─┬ iobroker.parcel@0.2.10 └─┬ jsdom@25.0.1 └── canvas@2.11.2 echad@chet:/opt/iobroker $ npm ls iobroker.inst@3.0.0 /opt/iobroker ├── iobroker.admin@7.7.3 ├── iobroker.alexa2@3.27.3 ├── iobroker.alias-manager@2.0.0 ├── iobroker.ankersolix2@2.4.1 ├── iobroker.awtrix-light@2.0.0 ├── iobroker.backitup@3.3.9 ├── iobroker.ble@0.14.1 ├── iobroker.cloud@5.0.1 ├── iobroker.devices@1.2.9 ├── iobroker.echarts@2.0.10 ├── iobroker.firetv@2.1.0 ├── iobroker.followthesun@0.5.2 ├── iobroker.govee-app@0.0.6 (git+ssh://git@github.com/TA2k/ioBroker.govee-app.git#6a0f84cfb34eb3a0ca647c7a519b9d5a48ccfb85) ├── iobroker.govee-local@0.2.9 ├── iobroker.history@3.0.1 ├── iobroker.ical@1.17.0 ├── iobroker.iceroad@1.2.1 ├── iobroker.iot@4.1.0 ├── iobroker.javascript@9.0.11 ├── iobroker.js-controller@7.0.7 ├── iobroker.mihome-cloud@0.1.1 ├── iobroker.mihome-vacuum@5.3.0 ├── iobroker.mihome@1.4.0 ├── iobroker.mqtt@6.1.4 ├── iobroker.nina@0.0.26 ├── iobroker.notification-manager@1.3.0 ├── iobroker.nuki-extended@2.7.0 ├── iobroker.nut@1.7.0 ├── iobroker.opendtu@3.1.0 ├── iobroker.openweathermap@1.4.0 ├── iobroker.parcel@0.2.10 ├── iobroker.playstation@0.0.3 ├── iobroker.rpi2@2.4.0 (git+ssh://git@github.com/Grothesk242/ioBroker.rpi2.git#c87e9539d89bac8f4d19b266679bcb78ed554f1d) ├── iobroker.sainlogic@0.12.1 ├── iobroker.samsung_tizen@1.1.0 ├── iobroker.samsung@0.6.1 ├── iobroker.switchbot-hub@0.1.2 (git+ssh://git@github.com/DrozmotiX/ioBroker.switchbot-hub.git#7a05fa59dfc5e3ce8d73018badc4e420996452f8) ├── iobroker.tado@0.8.0 ├── iobroker.tankerkoenig@3.4.0 ├── iobroker.tr-064@4.3.0 ├── iobroker.tradfri@3.1.3 ├── iobroker.trashschedule@4.0.1 ├── iobroker.tuya@3.17.0 ├── iobroker.weather-warnings@0.8.0 ├── iobroker.web@7.0.9 ├── iobroker.whatsapp-cmb@0.3.0 └── iobroker.zigbee@3.1.5 echad@chet:/opt/iobroker $ lsb_release -cs trixie echad@chet:/opt/iobroker $ -
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
@meute Nutzt dir zwar nix, aber unter nodejs@22 ist das bei mir alles sauber:
So sieht es bei mir aus:
mf@iobroker84:/opt/iobroker $ node -v v22.20.0 mf@iobroker84:/opt/iobroker $ npm ls canvas iobroker.inst@3.0.0 /opt/iobroker └── (empty) mf@iobroker84:/opt/iobroker $ npm ls iobroker.inst@3.0.0 /opt/iobroker ├── @mapbox/node-pre-gyp@1.0.11 extraneous ├── abbrev@1.1.1 extraneous ├── aproba@2.1.0 extraneous ├── are-we-there-yet@2.0.0 extraneous ├── color-support@1.1.3 extraneous ├── concat-map@0.0.1 extraneous ├── console-control-strings@1.1.0 extraneous ├── delegates@1.0.0 extraneous ├── detect-libc@2.1.2 extraneous ├── gauge@3.0.2 extraneous ├── has-unicode@2.0.1 extraneous ├── iobroker.admin@7.7.2 ├── iobroker.alias-manager@2.0.0 ├── iobroker.backitup@3.3.5 ├── iobroker.discovery@5.0.0 ├── iobroker.echarts@1.9.2 ├── iobroker.ical@1.17.0 ├── iobroker.influxdb@4.0.2 ├── iobroker.iqontrol@3.0.0 ├── iobroker.javascript@8.9.2 ├── iobroker.js-controller@7.0.7 ├── iobroker.modbus@6.3.2 ├── iobroker.ping@1.6.2 ├── iobroker.shelly@10.2.0 ├── iobroker.simple-api@2.8.0 ├── iobroker.socketio@6.7.1 ├── iobroker.sonoff@3.2.1 ├── iobroker.tr-064@4.3.0 ├── iobroker.trashschedule@3.3.0 ├── iobroker.web@7.0.8 ├── iobroker.whatsapp-cmb@0.3.0 ├── iobroker.ws@2.6.2 ├── make-dir@3.1.0 extraneous ├── mimic-response@2.1.0 extraneous ├── nopt@5.0.0 extraneous ├── npmlog@5.0.1 extraneous ├── path-is-absolute@1.0.1 extraneous ├── rimraf@3.0.2 extraneous ├── set-blocking@2.0.0 extraneous ├── simple-concat@1.0.1 extraneous ├── simple-get@3.1.1 extraneous └── wide-align@1.1.5 extraneous -
Mir sagt canvas jetzt nicht wirklich was.
Benötigt der Adapter echarts canvas?
Wenn ja, warum ist es bei mir (empty)? -
@meute sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Benötigt der Adapter echarts canvas?
Ja, einmal als direkte Abhängigkeit und dann braucht jsdom auch canvas. Sieht man hier:
├─┬ iobroker.echarts@2.0.10 │ ├── canvas@3.2.0 │ └─┬ jsdom@26.1.0 │ └── canvas@3.2.0 dedupedDeduped bedeutet, das es keine doppelte Installation ist sondern das auf das Modul (in gleicher Versionsnummer) auf einer höheren Ebene zurückgegriffen werden kann.
Wenn ja, warum ist es bei mir (empty)?
Weil es aus irgendwelchen Gründen bei dir nicht gebaut/kompiliert werden kann.
-
Was spuckt denn ein
apt policy build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-devaus?
-
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
apt policy build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev
$ apt policy build-essential libcairo2-dev libpango1.0-dev libjpeg-dev libgif-dev librsvg2-dev build-essential: Installiert: 12.12 Installationskandidat: 12.12 Versionstabelle: *** 12.12 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status libcairo2-dev: Installiert: 1.18.4-1+b1 Installationskandidat: 1.18.4-1+b1 Versionstabelle: *** 1.18.4-1+b1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status libpango1.0-dev: Installiert: 1.56.3-1 Installationskandidat: 1.56.3-1 Versionstabelle: *** 1.56.3-1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status libjpeg-dev: Installiert: 1:2.1.5-4 Installationskandidat: 1:2.1.5-4 Versionstabelle: *** 1:2.1.5-4 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status libgif-dev: Installiert: 5.2.2-1+b1 Installationskandidat: 5.2.2-1+b1 Versionstabelle: *** 5.2.2-1+b1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status librsvg2-dev: Installiert: 2.60.0+dfsg-1 Installationskandidat: 2.60.0+dfsg-1 Versionstabelle: *** 2.60.0+dfsg-1 500 500 http://deb.debian.org/debian trixie/main amd64 Packages 100 /var/lib/dpkg/status -
Schau mal ob canvas alleine baut.
cd npm install canvasDamit wird das Modul unabhängig vom iobroker in deinem Heimverzeichnis gebaut.
Zeig mal die Meldungen dazu.[Edit:]
Mitnpm uninstall canvasim gleichen Verzeichnis wirste das auch wieder los.
-
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Schau mal ob canvas alleine baut.
cd npm install canvasDamit wird das Modul unabhängig vom iobroker in deinem Heimverzeichnis gebaut.
Zeig mal die Meldungen dazu.mf@iobroker84:~ $ npm install canvas added 37 packages in 5s 9 packages are looking for funding run `npm fund` for detailsHabs im Home wieder deinstalliert.
-
@meute sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Habs im Home wieder deinstalliert.
War es denn davor im Baum zu finden?
npm lshätte da ein Modul canvas@3.2.0 zeigen müssen.
-
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
@meute sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
War es denn davor im Baum zu finden?npm lshätte da ein Modul canvas@3.2.0 zeigen müssen.
mf@iobroker84:~ $ npm install canvas added 37 packages in 4s 9 packages are looking for funding run `npm fund` for details mf@iobroker84:~ $ npm ls mf@ /home/mf └── canvas@3.2.0 mf@iobroker84:~ $ npm uninstall canvas removed 37 packages, and audited 1 package in 721ms found 0 vulnerabilities -
Dann ist da 'irgendwas' anderes in der Installation.
Ich kann dir da aber leider nicht wirklich weiterhelfen. -
@thomas-braun sagte in npm error bei "iob diag" nach Upgrade auf Debian 13 Trixie:
Dann ist da 'irgendwas' anderes in der Installation.
Ich kann dir da aber leider nicht wirklich weiterhelfen.Danke trotzdem für alles.
Komisch ist aber, dass trotz dem Problem der Adapter
echartsfunktioniert.
