NEWS
npm nach "apt upgrade" zerschossen?
-
Nach einem "apt upgrade" bekomme ich bei der Installation eines Adapters folgenden fehler.
$ iobroker add trashschedule --host miniserver /bin/sh: 1: npm: not found Error trying to check npm version: Command failed: npm -v/bin/sh: 1: npm: not found !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly. Use "npm install -g npm@8" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! ERROR: Process exited with code 30
Lässt sich das wieder beheben?
Edit:
Die genanneten Befehle funktionieren leider nicht...npm install -g npm@8 install: missing file operand Try 'install --help' for more information.
npm install -g npm@latest install: missing file operand Try 'install --help' for more information.
-
@meckii sagte in npm nach "apt upgrade" zerschossen?:
Lässt sich das wieder beheben?
iob nodejs-update
Und Finger weg von den 'npm'-Kommandos!
-
@meckii bitte iob diag in der Langfassung!
@meckii sagte in npm nach "apt upgrade" zerschossen?:
Use "npm install -g npm@8
wie alt ist die Installation? und mach das "empfohlene" bloß nicht!
-
@thomas-braun
Das hat leider nicht funktioniertFixing your nodejs setup *** Deleting *** rm: cannot remove '': No such file or directory *** Deleting *** rm: cannot remove '': No such file or directory Wrong paths have been fixed. Run 'iob diag' or 'iob node-fix' again to check if your installation is fine now Nothing to do - Your version is the recommended one. You can now keep your whole system up-to-date using the usual 'sudo apt update && sudo apt full-upgrade' commands. Please DO NOT USE node version managers like 'nvm', 'n' and others in parallel. They will break your current installation!
iob diag gibt folgendes aus:
2023-12-29 17:41:36.802 - error: host.raspberry iobroker !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly.Use "npm install -g npm@8" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2023-12-29 17:41:37.835 - info: host.raspberry iobroker exit 30 2023-12-29 17:45:00.019 - info: host.raspberry instance system.adapter.dwd.0 started with pid 84504 2023-12-29 17:45:01.054 - info: dwd.0 (84504) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 5.0.17 2023-12-29 17:45:01.970 - info: dwd.0 (84504) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-29 17:45:02.484 - info: host.raspberry instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-29 17:45:30.814 - info: host.raspberry iobroker add trashschedule --host raspberry 2023-12-29 17:45:32.015 - error: host.raspberry iobroker /bin/sh: 1: npm: not found 2023-12-29 17:45:32.017 - error: host.raspberry iobroker Error trying to check npm version: Command failed: npm -v/bin/sh: 1: npm: not found 2023-12-29 17:45:32.018 - error: host.raspberry iobroker !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!Aborting install because the npm version could not be checked!Please check that npm is installed correctly. 2023-12-29 17:45:32.018 - error: host.raspberry iobroker Use "npm install -g npm@8" or "npm install -g npm@latest" to install a supported version.You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2023-12-29 17:45:33.045 - info: host.raspberry iobroker exit 30 2023-12-29 17:48:43.084 - info: host.raspberry iobroker add trashschedule --host raspberry 2023-12-29 17:48:44.208 - error: host.raspberry iobroker /bin/sh: 1: npm: not found 2023-12-29 17:48:44.211 - error: host.raspberry iobroker Error trying to check npm version: Command failed: npm -v/bin/sh: 1: npm: not found 2023-12-29 17:48:44.213 - error: host.raspberry iobroker !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2023-12-29 17:48:44.214 - error: host.raspberry iobroker Aborting install because the npm version could not be checked! 2023-12-29 17:48:44.215 - error: host.raspberry iobroker Please check that npm is installed correctly. 2023-12-29 17:48:44.216 - error: host.raspberry iobroker Use "npm install -g npm@8" or "npm install -g npm@latest" to install a supported version. 2023-12-29 17:48:44.219 - error: host.raspberry iobroker You need to make sure to repeat this step after installing an update to NodeJS and/or npm!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! 2023-12-29 17:48:45.243 - info: host.raspberry iobroker exit 30 2023-12-29 17:50:00.021 - info: host.raspberry instance system.adapter.dwd.0 started with pid 84758 2023-12-29 17:50:01.084 - info: dwd.0 (84758) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 5.0.17 2023-12-29 17:50:02.354 - info: dwd.0 (84758) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-29 17:50:02.872 - info: host.raspberry instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
-
Recommended versions are nodejs 18.19.0 and npm 10.2.3 *** nodejs is NOT correctly installed *** Wrong installation path detected. This needs to be fixed.
-
@meckii sagte in npm nach "apt upgrade" zerschossen?:
iob diag gibt folgendes aus:
nee, das ist der log!
iob diag ist viel länger
-
@homoran sagte in npm nach "apt upgrade" zerschossen?:
iob diag
Sorry
======== Start marking the full check here =========
Skript v.2023-10-10 *** BASE SYSTEM *** Static hostname: raspberry Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-2712 Architecture: arm64 Model : Raspberry Pi 5 Model B Rev 1.0 Docker : false Virtualization : none Kernel : aarch64 Userland : arm64 Systemuptime and Load: 18:00:09 up 2 days, 10:14, 2 users, load average: 0.42, 0.36, 0.16 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Fri 2023-12-29 18:00:09 CET Universal time: Fri 2023-12-29 17:00:09 UTC RTC time: Fri 2023-12-29 17:00:09 Time zone: Europe/Berlin (CET, +0100) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** buehst /home/buehst buehst adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 8.4G 1.0G 6.5G 5.3M 1.0G 7.4G Swap: 104M 0B 104M Total: 8.5G 1.0G 6.6G 8053 M total memory 975 M used memory 860 M active memory 761 M inactive memory 6180 M free memory 118 M buffer memory 880 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: vc_gencmd_read_response returned -1 error=1 error_msg="Command not registered" *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on udev devtmpfs 3.8G 0 3.8G 0% /dev tmpfs tmpfs 806M 5.1M 801M 1% /run /dev/mmcblk0p2 ext4 59G 18G 38G 33% / tmpfs tmpfs 4.0G 0 4.0G 0% /dev/shm tmpfs tmpfs 5.0M 48K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 510M 61M 450M 12% /boot/firmware tmpfs tmpfs 806M 0 806M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Wed Dec 27 07:45:34 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 pci=pcie_bus_safe snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 smsc95xx.macaddr=D8:3A:DD:DA:0C:1A vc_mem.mem_base=0x3fc00000 vc_mem.mem_size=0x40000000 console=ttyAMA10,115200 console=tty1 root=PARTUUID=04071584-02 rootfstype=ext4 fsck.repair=yes rootwait [Wed Dec 27 07:45:37 2023] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Wed Dec 27 07:45:38 2023] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems \(real ones only\): TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime `-/boot/firmware /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 532M /var/ 218M /var/cache 212M /var/cache/apt 161M /var/lib 132M /var/lib/apt/lists Archived and active journals take up 53.1M in the file system. /opt/iobroker/backups: 4.0K /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 146M /opt/iobroker/iobroker-data/ 89M /opt/iobroker/iobroker-data/files 67M /opt/iobroker/iobroker-data/files/javascript.admin 48M /opt/iobroker/iobroker-data/files/javascript.admin/static 47M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 16M /opt/iobroker/iobroker-data/objects.jsonl 7.5M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/691.26ff76ce.chunk.js.map 7.1M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/610.d3cce782.chunk.js.map 7.0M /opt/iobroker/iobroker-data/states.jsonl 6.3M /opt/iobroker/iobroker-data/files/admin.admin/custom/static/js/vendors-node_modules_iobroker_adapter-react-v5_assets_devices_parseNames_js-node_modules_iobr-99c23e.847b8ad9.chunk.js.map USB-Devices by-id: USB-Sticks - Avoid direct links to /dev/* in your adapter setups, please always prefer the links 'by-id': /dev/serial/by-id/usb-ITEAD_SONOFF_Zigbee_3.0_USB_Dongle_Plus_V2_20231008111815-if00 *** NodeJS-Installation *** /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /home/iobroker/.diag.sh: line 279: npm: command not found /home/iobroker/.diag.sh: line 280: npx: command not found /home/iobroker/.diag.sh: line 281: corepack: command not found /home/iobroker/.diag.sh: line 290: npm: command not found /home/iobroker/.diag.sh: line 291: npx: command not found *** nodejs is NOT correctly installed *** nodejs: Installed: 18.19.0+dfsg-6~deb12u1 Candidate: 18.19.0+dfsg-6~deb12u1 Version table: *** 18.19.0+dfsg-6~deb12u1 500 500 http://deb.debian.org/debian-security bookworm-security/main arm64 Packages 100 /var/lib/dpkg/status 18.19.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.18.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.17.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.16.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.15.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.2-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.14.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.13.0+dfsg1-1 500 500 http://deb.debian.org/debian bookworm/main arm64 Packages 18.13.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.12.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.11.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.10.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.1-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.9.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.8.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.7.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.6.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.5.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.4.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.3.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.2.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.1.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages 18.0.0-1nodesource1 500 500 https://deb.nodesource.com/node_18.x nodistro/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: /home/iobroker/.diag.sh: line 360: npm: command not found *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 5.0.17 admin: 6.12.0 javascript: 7.1.6 /home/iobroker/.diag.sh: line 375: npm: command not found Adapters from github: 0 Adapter State + system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin system.adapter.backitup.0 : backitup : raspberry - disabled + system.adapter.discovery.0 : discovery : raspberry - enabled system.adapter.dwd.0 : dwd : raspberry - enabled + system.adapter.javascript.0 : javascript : raspberry - enabled + system.adapter.lametric.0 : lametric : raspberry - enabled + system.adapter.ping.0 : ping : raspberry - enabled + system.adapter.pushsafer.0 : pushsafer : raspberry - enabled + system.adapter.shelly.0 : shelly : raspberry - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.zigbee.0 : zigbee : raspberry - enabled, port: /dev/ttyACM0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : raspberry - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.zigbee.0 : zigbee : raspberry - enabled, port: /dev/ttyACM0 ioBroker-Repositories stable : http://download.iobroker.net/sources-dist.json beta : http://download.iobroker.net/sources-dist-latest.json Active repo(s): stable Installed ioBroker-Instances Used repository: stable Adapter "admin" : 6.12.0 , installed 6.12.0 Adapter "backitup" : 2.9.8 , installed 2.9.8 Adapter "discovery" : 4.2.0 , installed 4.2.0 Adapter "dwd" : 2.8.5 , installed 2.8.5 Adapter "javascript" : 7.1.6 , installed 7.1.6 Controller "js-controller": 5.0.17 , installed 5.0.17 Adapter "lametric" : 3.1.1 , installed 3.1.2 Adapter "ping" : 1.6.2 , installed 1.6.2 Adapter "pushsafer" : 1.0.3 , installed 1.0.3 Adapter "shelly" : 6.6.1 , installed 6.6.1 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 6.6.0 , installed 6.6.0 Adapter "web" : 6.1.10 , installed 6.1.10 Adapter "ws" : 2.5.8 , installed 2.5.8 Adapter "zigbee" : 1.8.25 , installed 1.9.3 Objects and States Please stand by - This may take a while Objects: 820 States: 565 *** OS-Repositories and Updates *** Hit:1 http://deb.debian.org/debian bookworm InRelease Hit:2 http://deb.debian.org/debian-security bookworm-security InRelease Hit:3 http://archive.raspberrypi.com/debian bookworm InRelease Hit:4 http://deb.debian.org/debian bookworm-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:9000 0.0.0.0:* LISTEN 1001 1158090 87024/iobroker.js-c tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 1158083 87024/iobroker.js-c tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 14940 791/sshd: /usr/sbin tcp6 0 0 :::8081 :::* LISTEN 1001 1159786 87042/io.admin.0 tcp6 0 0 :::22 :::* LISTEN 0 14942 791/sshd: /usr/sbin udp 0 0 0.0.0.0:49602 0.0.0.0:* 104 14860 676/avahi-daemon: r udp 0 0 0.0.0.0:5353 0.0.0.0:* 104 14858 676/avahi-daemon: r udp 0 0 0.0.0.0:5683 0.0.0.0:* 1001 1160569 87075/io.shelly.0 udp6 0 0 fe80::8025:66f6:35d:546 :::* 0 16215 756/NetworkManager udp6 0 0 :::41903 :::* 104 14861 676/avahi-daemon: r udp6 0 0 :::5353 :::* 104 14859 676/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-12-29 17:57:44.293 - info: zigbee.0 (87116) 0xbc026efffe5ecfc7 (addr 56408): LED2003G10 - IKEA TRADFRI LED bulb E26/27 1100/1055/1160 lumen, dimmable, white spectrum, opal white (Router) 2023-12-29 17:57:44.294 - info: zigbee.0 (87116) 0x0ceff6fffedc04d6 (addr 53326): SNZB-02D - SONOFF Temperature and humidity sensor with screen (EndDevice) 2023-12-29 17:57:44.295 - info: zigbee.0 (87116) 0x287681fffe1bf3ff (addr 26190): E2213 - IKEA SOMRIG shortcut button (EndDevice) 2023-12-29 17:57:44.295 - info: zigbee.0 (87116) 0x287681fffe4a0732 (addr 41650): E2213 - IKEA SOMRIG shortcut button (EndDevice) 2023-12-29 17:57:44.295 - info: zigbee.0 (87116) Zigbee started 2023-12-29 17:57:44.321 - info: zigbee.0 (87116) debug devices set to [] 2023-12-29 17:57:44.447 - info: host.raspberry instance scheduled system.adapter.dwd.0 */5 * * * * 2023-12-29 17:57:44.451 - info: host.raspberry instance system.adapter.dwd.0 started with pid 87154 2023-12-29 17:57:44.465 - info: shelly.0 (87075) [CoAP] Device 192.168.7.22 (shelly1pm / shelly1pm-8CAAB57780EB / SHSW-PM#8CAAB57780EB#1) connected! Polltime set to 15 sec. 2023-12-29 17:57:45.920 - info: dwd.0 (87154) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 5.0.17 2023-12-29 17:57:46.229 - info: dwd.0 (87154) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-29 17:57:46.753 - info: host.raspberry instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-12-29 17:57:48.423 - info: host.raspberry instance system.adapter.pushsafer.0 started with pid 87171 2023-12-29 17:57:49.258 - info: pushsafer.0 (87171) starting. Version 1.0.3 in /opt/iobroker/node_modules/iobroker.pushsafer, node: v18.19.0, js-controller: 5.0.17 2023-12-29 17:57:52.428 - info: host.raspberry instance system.adapter.lametric.0 started with pid 87188 2023-12-29 17:57:53.601 - info: lametric.0 (87188) starting. Version 3.1.2 in /opt/iobroker/node_modules/iobroker.lametric, node: v18.19.0, js-controller: 5.0.17 2023-12-29 17:57:53.622 - info: lametric.0 (87188) Starting - connecting to http://192.168.7.20:8080 2023-12-29 17:58:14.583 - warn: zigbee.0 (87116) DeviceAvailability:Failed to ping 0xa4c138a49d0cd3db TS011F 2023-12-29 17:58:14.771 - warn: zigbee.0 (87116) DeviceAvailability:Failed to ping 0xf082c0fffe008e6e TRADFRI bulb E14 WS globe 470lm 2023-12-29 17:58:14.967 - warn: zigbee.0 (87116) DeviceAvailability:Failed to ping 0xbc026efffe5ecfc7 TRADFRIbulbE27WSglobeopal1055lm 2023-12-29 17:59:47.161 - info: admin.0 (87042) ==> Connected system.user.admin from ::ffff:192.168.7.31 2023-12-29 18:00:00.030 - info: host.raspberry instance system.adapter.dwd.0 started with pid 88367 2023-12-29 18:00:01.146 - info: dwd.0 (88367) starting. Version 2.8.5 in /opt/iobroker/node_modules/iobroker.dwd, node: v18.19.0, js-controller: 5.0.17 2023-12-29 18:00:02.504 - info: dwd.0 (88367) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-12-29 18:00:03.020 - info: host.raspberry instance system.adapter.dwd.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
============ Mark until here for C&P =============
iob diag has finished.
Press any key for a summary
-
Copy text starting here:
======================= SUMMARY ======================= v.2023-10-10 Static hostname: raspberry Icon name: computer Operating System: Debian GNU/Linux 12 (bookworm) Kernel: Linux 6.1.0-rpi7-rpi-2712 Architecture: arm64 Installation: native Kernel: aarch64 Userland: arm64 Timezone: Europe/Berlin (CET, +0100) User-ID: 1000 X-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v18.19.0 /usr/bin/node v18.19.0 /home/iobroker/.diag.sh: line 488: npm: command not found /home/iobroker/.diag.sh: line 489: npx: command not found /home/iobroker/.diag.sh: line 490: corepack: command not found Recommended versions are nodejs 18.19.0 and npm 10.2.3 *** nodejs is NOT correctly installed *** Wrong installation path detected. This needs to be fixed. Please check https://forum.iobroker.net/topic/35090/howto-nodejs-installation-und-upgrades-unter-debian for more information on how to fix these errors. MEMORY: total used free shared buff/cache available Mem: 8.4G 1.1G 6.5G 5.4M 1.0G 7.4G Swap: 104M 0B 104M Total: 8.5G 1.1G 6.6G Active iob-Instances: 9 Active repo(s): stable ioBroker Core: js-controller 5.0.17 admin 6.12.0 ioBroker Status: iobroker is running on this host. Objects type: jsonl States type: jsonl Status admin and web instance: + system.adapter.admin.0 : admin : raspberry - enabled, port: 8081, bind: 0.0.0.0, run as: admin Objects: 820 States: 565 Size of iob-Database: 16M /opt/iobroker/iobroker-data/objects.jsonl 7.0M /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ====================
=== Mark text until here for copying ===
-
@meckii sagte in npm nach "apt upgrade" zerschossen?:
*** 18.19.0+dfsg-6~deb12u1 500
@Thomas-Braun hat dazu einen Thread eröffnet
https://forum.iobroker.net/topic/71461/dfsg-nodejs-eingehandelt-hier-die-korrektur/1 -
Das hat funktioniert! Vielen Dank!
Ich dachte schon ich müsste den rpi schon wieder neu aufsetzenDieses Forum ist echt spitze!
-
Das hatte ich vor 2 Tagen auch, und es war ein
sudo apt update && sudo apt full-upgrade
, das mir ein "neues" nodejs 18.19.0 angeboten hat.Ich habe es ausgeführt, und danach war npm nicht mehr vorhanden.
iob nodejs-update
hat mir anschließend den Arsch gerettet. -
@meckii sagte in npm nach "apt upgrade" zerschossen?:
Ich dachte schon ich müsste den rpi schon wieder neu aufsetzen
Das muss man eigentlich nie. Außer beim Upgrade auf 'Bookworm', da sollte man es schon frisch neu aufsetzen.