Probleme beim Update Host node.js
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
[Thu Aug 8 18:12:52 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[Thu Aug 8 18:12:53 2024] EXT4-fs (mmcblk0p2): recovery completeDein Dateisystem hängt in den Angeln. Kommt besonders gerne und häufig bei Kisten vor, die nicht ordentlich behandelt werden. Auch bekannt als 'Tod durch plötzlichen Stromentzug'
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
~ Under-voltage has occurred
~ Arm frequency capping has occurredwas hängt alkes am USB dran?
was für ein Netzteil hast du?
-
@homoran said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
~ Under-voltage has occurred
~ Arm frequency capping has occurredwas hängt alkes am USB dran?
was für ein Netzteil hast du?
ist alles an der Fritzbox, anschluss via Netzwerk und Stromversorgung via USB von der Fritzbox
-
??? Du befeuerst den Raspberry Pi 4 Model B Rev 1.5 über den USB-Anschluss der FritzBox????
-
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
[Thu Aug 8 18:12:52 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery
[Thu Aug 8 18:12:53 2024] EXT4-fs (mmcblk0p2): recovery completeDein Dateisystem hängt in den Angeln. Kommt besonders gerne und häufig bei Kisten vor, die nicht ordentlich behandelt werden. Auch bekannt als 'Tod durch plötzlichen Stromentzug'
d.h. ein Netzteil und nicht versorgen via Fritzbox und dann läuft es wieder?
oder was ist die abhilfe? -
Manche Ideen gibt es...
Ja, besorg dir ein stabiles, richtiges Netzteil für den Raspberry. Kein Handyladegerät oder sowas, ein richtiges, ausgewiesenes Netzteil. Am besten gleich das originale. -
@thomas-braun said in Probleme beim Update Host node.js:
Manche Ideen gibt es...
Ja, besorg dir ein stabiles, richtiges Netzteil für den Raspberry. Kein Handyladegerät oder sowas, ein richtiges, ausgewiesenes Netzteil. Am besten gleich das originale.ok Netzteil ist bestellt bei Berrybase als offizielles Netzteil mit 3A Leistung.
und die Fehler zb.Node.js v20.16.0 admin: node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG'kommen also von zuwenig bereitgestelltem Strom?
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
kommen also von zuwenig bereitgestelltem Strom?
durchaus möglich, wenn die Spannung beim Schreiben von Daten wegbricht und dasurch korrupte Dateien entstehen.
-
@thomas-braun said in Probleme beim Update Host node.js:
Manche Ideen gibt es...
Ja, besorg dir ein stabiles, richtiges Netzteil für den Raspberry. Kein Handyladegerät oder sowas, ein richtiges, ausgewiesenes Netzteil. Am besten gleich das originale.@thomas-braun said in Probleme beim Update Host node.js:
Manche Ideen gibt es...
Ja, besorg dir ein stabiles, richtiges Netzteil für den Raspberry. Kein Handyladegerät oder sowas, ein richtiges, ausgewiesenes Netzteil. Am besten gleich das originale.Originales Netzteil ist angeschlossen, scheinbar ohne erfolg.
iob diag======== Start marking the full check here =========
Skript v.2024-05-22 *** BASE SYSTEM *** Static hostname: SmartHomeRohlik Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Model : Raspberry Pi 4 Model B Rev 1.5 Docker : false Virtualization : none Kernel : aarch64 Userland : 64 bit Systemuptime and Load: 14:01:53 up 7 min, 1 user, load average: 0.51, 0.24, 0.10 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: No throttling issues detected. *** Time and Time Zones *** Local time: Sat 2024-08-10 14:01:53 CEST Universal time: Sat 2024-08-10 12:01:53 UTC RTC time: n/a 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': SmartHomeRohlik HOME=/home/SmartHomeRohlik GROUPS=SmartHomeRohlik adm dialout cdrom sudo audio video plugdev games users input render netdev gpio i2c spi 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: 7.8G 86M 7.5G 1.0M 193M 7.6G Swap: 99M 0B 99M Total: 7.9G 86M 7.6G Active iob-Instances: 0 7812 M total memory 86 M used memory 141 M active memory 54 M inactive memory 7532 M free memory 33 M buffer memory 160 M swap cache 99 M total swap 0 M used swap 99 M free swap *** top - Table Of Processes *** top - 14:01:53 up 7 min, 1 user, load average: 0.55, 0.25, 0.11 Tasks: 153 total, 1 running, 152 sleeping, 0 stopped, 0 zombie %Cpu(s): 0.0 us, 2.9 sy, 0.0 ni, 97.1 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7812.3 total, 7531.9 free, 86.6 used, 193.8 buff/cache MiB Swap: 100.0 total, 100.0 free, 0.0 used. 7614.7 avail Mem *** FAILED SERVICES *** UNIT LOAD ACTIVE SUB DESCRIPTION 0 loaded units listed. *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 59G 6.6G 50G 12% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 1.1M 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/mmcblk0p1 vfat 255M 31M 225M 13% /boot tmpfs tmpfs 782M 0 782M 0% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Sat Aug 10 13:54:13 2024] Kernel command line: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=D8:3A:DD:26:C6:E7 vc_mem.mem_base=0x3ec00000 vc_mem.mem_size=0x40000000 console=ttyS0,115200 console=tty1 root=PARTUUID=f99eefee-02 rootfstype=ext4 fsck.repair=yes rootwait [Sat Aug 10 13:54:14 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Sat Aug 10 13:54:14 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Sat Aug 10 13:54:14 2024] EXT4-fs (mmcblk0p2): recovery complete [Sat Aug 10 13:54:14 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Sat Aug 10 13:54:14 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Sat Aug 10 13:54:17 2024] EXT4-fs (mmcblk0p2): re-mounted. Quota mode: none. Show mounted filesystems: TARGET SOURCE FSTYPE OPTIONS / /dev/mmcblk0p2 ext4 rw,noatime |-/dev devtmpfs devtmpfs rw,relatime,size=3735680k,nr_inodes=933920,mode=755 | |-/dev/shm tmpfs tmpfs rw,nosuid,nodev | |-/dev/pts devpts devpts rw,nosuid,noexec,relatime,gid=5,mode=620,ptmxmode=000 | `-/dev/mqueue mqueue mqueue rw,nosuid,nodev,noexec,relatime |-/proc proc proc rw,relatime | `-/proc/sys/fs/binfmt_misc systemd-1 autofs rw,relatime,fd=30,pgrp=1,timeout=0,minproto=5,maxproto=5,direct |-/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/fs/bpf bpf bpf rw,nosuid,nodev,noexec,relatime,mode=700 | |-/sys/kernel/debug debugfs debugfs rw,nosuid,nodev,noexec,relatime | |-/sys/kernel/tracing tracefs tracefs rw,nosuid,nodev,noexec,relatime | |-/sys/fs/fuse/connections fusectl fusectl rw,nosuid,nodev,noexec,relatime | `-/sys/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime |-/run tmpfs tmpfs rw,nosuid,nodev,size=1599964k,nr_inodes=819200,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=799980k,nr_inodes=199995,mode=700,uid=1000,gid=1000 `-/boot /dev/mmcblk0p1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,errors=remount-ro Files in neuralgic directories: /var: 2.4G /var/ 1.9G /var/log 1.6G /var/log/journal/9ab67524321c46fcbcc935773dd5bf51 1.6G /var/log/journal 379M /var/cache Archived and active journals take up 1.5G in the file system. /opt/iobroker/backups: 67M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 646M /opt/iobroker/iobroker-data/ 561M /opt/iobroker/iobroker-data/files 441M /opt/iobroker/iobroker-data/files/javascript.admin 409M /opt/iobroker/iobroker-data/files/javascript.admin/static 408M /opt/iobroker/iobroker-data/files/javascript.admin/static/js The five largest files in iobroker-data are: 24M /opt/iobroker/iobroker-data/files/web.admin/static/js/main.135279a0.js.map 22M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.18496c94.js.map 11M /opt/iobroker/iobroker-data/objects.jsonl 9.0M /opt/iobroker/iobroker-data/files/modbus.admin/static/js/main.18496c94.js 8.7M /opt/iobroker/iobroker-data/files/javascript.admin/static/js/838.0aa41cb0.chunk.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' *** NodeJS-Installation *** /usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 nodejs: Installed: 20.16.0-1nodesource1 Candidate: 20.16.0-1nodesource1 Version table: *** 20.16.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 100 /var/lib/dpkg/status 20.15.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.15.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.14.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.13.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.2-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.12.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.11.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.10.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.9.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.8.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.7.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.6.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.5.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.4.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.1-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.3.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.2.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.1.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 20.0.0-1nodesource1 1001 500 https://deb.nodesource.com/node_20.x nodistro/main arm64 Packages 12.22.12~dfsg-1~deb11u4 500 500 http://security.debian.org/debian-security bullseye-security/main arm64 Packages Temp directories causing npm8 problem: 0 No problems detected Errors in npm tree: *** ioBroker-Installation *** ioBroker Status node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 Core adapters versions node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 js-controller: node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 admin: node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 javascript: nodejs modules from github: 0 Adapter State Enabled adapters with bindings ioBroker-Repositories node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 Installed ioBroker-Instances node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 Objects and States Please stand by - This may take a while Objects: 0 States: 0 *** OS-Repositories and Updates *** Hit:1 http://security.debian.org/debian-security bullseye-security InRelease Hit:2 http://archive.raspberrypi.org/debian bullseye 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_20.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 0.0.0.0:22 0.0.0.0:* LISTEN 0 15389 540/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 15391 540/sshd: /usr/sbin udp 0 0 0.0.0.0:52459 0.0.0.0:* 108 11249 393/avahi-daemon: r udp 0 0 0.0.0.0:68 0.0.0.0:* 0 12667 739/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 11247 393/avahi-daemon: r udp6 0 0 :::546 :::* 0 12694 739/dhcpcd udp6 0 0 :::5353 :::* 108 11248 393/avahi-daemon: r udp6 0 0 :::42978 :::* 108 11250 393/avahi-daemon: r *** Log File - Last 25 Lines *** 2024-08-08 17:05:54.683 - info: shelly.0 (1028) [firmwareUpdate] Auto-Update enabled - devices will be updated automatically 2024-08-08 17:05:54.693 - info: shelly.0 (1028) Starting in CoAP mode. Listening on 0.0.0.0:5683 2024-08-08 17:05:54.752 - info: shelly.1 (1045) starting. Version 7.0.0 in /opt/iobroker/node_modules/iobroker.shelly, node: v20.16.0, js-controller: 6.0.9 2024-08-08 17:05:54.940 - info: shelly.0 (1028) [CoAP Server] Listening for packets in the network 2024-08-08 17:05:55.072 - error: host.SmartHomeRohlik Caught by controller[0]: /opt/iobroker/node_modules/iobroker.rainbird/main.js:33 2024-08-08 17:05:55.073 - error: host.SmartHomeRohlik Caught by controller[0]: adapter = new utils.Adapter(options); 2024-08-08 17:05:55.073 - error: host.SmartHomeRohlik Caught by controller[0]: ^ 2024-08-08 17:05:55.074 - error: host.SmartHomeRohlik Caught by controller[0]: TypeError: utils.Adapter is not a constructor 2024-08-08 17:05:55.074 - error: host.SmartHomeRohlik Caught by controller[0]: at startAdapter (/opt/iobroker/node_modules/iobroker.rainbird/main.js:33:12) 2024-08-08 17:05:55.075 - error: host.SmartHomeRohlik Caught by controller[0]: at Object.<anonymous> (/opt/iobroker/node_modules/iobroker.rainbird/main.js:319:2) 2024-08-08 17:05:55.075 - error: host.SmartHomeRohlik Caught by controller[0]: at Module._compile (node:internal/modules/cjs/loader:1358:14) 2024-08-08 17:05:55.076 - error: host.SmartHomeRohlik Caught by controller[0]: at Module._extensions..js (node:internal/modules/cjs/loader:1416:10) 2024-08-08 17:05:55.076 - error: host.SmartHomeRohlik Caught by controller[0]: at Module.load (node:internal/modules/cjs/loader:1208:32) 2024-08-08 17:05:55.077 - error: host.SmartHomeRohlik Caught by controller[0]: at Module._load (node:internal/modules/cjs/loader:1024:12) 2024-08-08 17:05:55.077 - error: host.SmartHomeRohlik Caught by controller[0]: at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:174:12) 2024-08-08 17:05:55.078 - error: host.SmartHomeRohlik Caught by controller[0]: at node:internal/main/run_main_module:28:49 2024-08-08 17:05:55.090 - error: host.SmartHomeRohlik Caught by controller[0]: Node.js v20.16.0 2024-08-08 17:05:55.091 - error: host.SmartHomeRohlik instance system.adapter.rainbird.0 terminated with code 1 (JS_CONTROLLER_STOPPED) 2024-08-08 17:05:55.092 - info: host.SmartHomeRohlik Restart adapter system.adapter.rainbird.0 because enabled 2024-08-08 17:05:56.105 - info: host.SmartHomeRohlik instance system.adapter.modbus.0 in version "6.2.3" started with pid 1112 2024-08-08 17:05:56.334 - info: shelly.1 (1045) [firmwareUpdate] Auto-Update enabled - devices will be updated automatically 2024-08-08 17:05:56.337 - info: shelly.1 (1045) Starting in MQTT mode. Listening on 0.0.0.0:1882 (QoS 0) 2024-08-08 17:05:56.795 - info: rpi2.0 (1089) starting. Version 1.3.2 in /opt/iobroker/node_modules/iobroker.rpi2, node: v20.16.0, js-controller: 6.0.9 2024-08-08 17:05:57.071 - info: rpi2.0 (1089) GPIO ports are not configured============ Mark until here for C&P =============
iob diag has finished.
======================= SUMMARY ======================= v.2024-05-22 Static hostname: SmartHomeRohlik Icon name: computer Operating System: Debian GNU/Linux 11 (bullseye) Kernel: Linux 6.1.21-v8+ Architecture: arm64 Installation: native Kernel: aarch64 Userland: 64 bit Timezone: Europe/Berlin (CEST, +0200) User-ID: 1000 Display-Server: false Boot Target: multi-user.target Pending OS-Updates: 0 node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 Pending iob updates: 0 Nodejs-Installation: /usr/bin/nodejs v20.16.0 /usr/bin/node v20.16.0 /usr/bin/npm 10.8.1 /usr/bin/npx 10.8.1 /usr/bin/corepack 0.28.2 Recommended versions are nodejs and npm Your nodejs installation is correct MEMORY: total used free shared buff/cache available Mem: 7.8G 87M 7.5G 1.0M 257M 7.6G Swap: 99M 0B 99M Total: 7.9G 87M 7.6G Active iob-Instances: 0 node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 ioBroker Core: js-controller node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 admin node:internal/modules/package_json_reader:83 throw new ERR_INVALID_PACKAGE_CONFIG( ^ Error [ERR_INVALID_PACKAGE_CONFIG]: Invalid package config /opt/iobroker/node_modules/axios/package.json while importing "axios" from /opt/iobroker/node_modules/@iobroker/js-controller-cli/build/esm/lib/setup/setupUpload.js. Unexpected end of JSON input at Object.read (node:internal/modules/package_json_reader:83:15) at packageResolve (node:internal/modules/esm/resolve:835:45) at moduleResolve (node:internal/modules/esm/resolve:927:18) at defaultResolve (node:internal/modules/esm/resolve:1169:11) at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:383:12) at ModuleLoader.resolve (node:internal/modules/esm/loader:352:25) at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:227:38) at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:87:39) at link (node:internal/modules/esm/module_job:86:36) { code: 'ERR_INVALID_PACKAGE_CONFIG' } Node.js v20.16.0 ioBroker Status: Status admin and web instance: Objects: 0 States: 0 Size of iob-Database: 11M /opt/iobroker/iobroker-data/objects.jsonl 236K /opt/iobroker/iobroker-data/states.jsonl =================== END OF SUMMARY ======================= Mark text until here for copying ===
SmartHomeRohlik@SmartHomeRohlik:/opt/iobroker $ -
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.Previously detected issues:
No throttling issues detected.Das ist der 'Erfolg'. Die Meldungen zur wackeligen Stromversorgung sind weg.
Einmal zerbröselte Dateien bekommst du natürlich nicht zurück, die sind kaputt. -
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
*** RASPBERRY THROTTLING ***
Current issues:
No throttling issues detected.Previously detected issues:
No throttling issues detected.Das ist der 'Erfolg'. Die Meldungen zur wackeligen Stromversorgung sind weg.
Einmal zerbröselte Dateien bekommst du natürlich nicht zurück, die sind kaputt.ok das heiß ich muss alles neu ausetzten? oder gibts da nen trick?
-
@keineahnungvonprogrmieren Da Dir niemand sagen kann, ob und welche Dateien da bereits zerstört wurden und Du die einfach so auch eh nicht mehr „retten“ kannst und damit auch niemand voraussehen kann, ob und wann sich das in welcher Form auswirkt, bleibt Dir da nur ein komplettes Neu-Installieren mit anschließendem Einspielen des Backups. Zumindest wäre das für mich die einzige Lösung, da ich für solche Dinge wie Smarthome und dergleichen ein 100% lauffähiges und verlässliches System ohne tickende Zeitbomben haben wollte.
Deshalb laufen für etwaige Stromausfälle auch USVs bei den kritischen Rechnern/Geräten, um da im Bedarfsfall sauber runterzufahren anhand Strom hart weg zu nehmen. Das war noch nie eine gute Idee oder gar Lösung für Probleme.Gruss, Jürgen
-
Chat GPT sagt dazu folgendes:
Zusammenfassung der möglichen Ursachen:
Beschädigte package.json-Datei: Die Datei könnte fehlerhaft sein, was bedeutet, dass sie möglicherweise nicht korrekt geladen wurde oder während der Installation beschädigt wurde.
Kompatibilitätsprobleme: Es könnte auch ein Problem mit der Node.js-Version oder mit der Art und Weise, wie ioBroker und seine Abhängigkeiten installiert wurden, geben.Schritte zur Problemlösung:
-
Überprüfen der package.json von axios:
Öffne die Datei /opt/iobroker/node_modules/axios/package.json und stelle sicher, dass sie vollständig und korrekt formatiert ist.
Eine typische package.json-Datei sollte korrekt geschlossen sein und keine Syntaxfehler enthalten. -
Neuinstallation von axios:
Führe in deinem ioBroker-Verzeichnis den Befehl zur Neuinstallation von axios aus:
bash cd /opt/iobroker/ npm install axios --forceDies sollte die fehlerhafte package.json-Datei ersetzen.
- Neuinstallation der Abhängigkeiten:
Wenn das Problem weiterhin besteht, führe den folgenden Befehl aus, um alle Abhängigkeiten von ioBroker neu zu installieren:
bash npm install --production --force- Node.js-Version prüfen:
Stelle sicher, dass die Node.js-Version, die du verwendest (v20.16.0), mit ioBroker kompatibel ist. Es kann sein, dass ioBroker oder bestimmte Adapter Probleme mit dieser Node.js-Version haben. Eventuell ist eine frühere Version stabiler.
- Backup und Neuinstallation von ioBroker:
Falls alle oben genannten Schritte nicht helfen, könnte eine vollständige Neuinstallation von ioBroker erforderlich sein. Stelle sicher, dass du vorher ein Backup aller wichtigen Konfigurationen und Daten machst.
Ist das eine möglich Abhilfe für das Problem?
wenn ja wie kann ich auf den ordner zugreifen? und wo bekomme ich die Datei her? oder doch besser gleich Abhilfe 2? sind die befehle korrekt?wäre echt froh wenn ich um eine Neuinstallation rum komme da wir kommende Woche in den Familien Urlaub fahren wollen und die Automationen da wieder laufen sollten zwecks wasserversorgung unserer Pflanzen.
Danke fürs Helfen
-
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
, könnte eine vollständige Neuinstallation von ioBroker erforderlich sein.
und für dies "Neuigkeit" dafür quälst du chatGPT?
oder hattest du gehofft, dass chatGPT dir was anderes erzählt als wir?
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
wäre echt froh wenn ich um eine Neuinstallation rum komme da wir kommende Woche in den Familien Urlaub fahren wollen und die Automationen da wieder laufen sollten zwecks wasserversorgung unserer Pflanzen.
du wärst schon längst damit fertig, wenn du dich direkt daran gemacht hättest.
dauert erwa 1h.
