Probleme beim Update Host node.js
-
@thomas-braun said in Probleme beim Update Host node.js:
Eine Neustart machst du per
sudo rebootNicht per Strom weg wegsensen.
da bin ich deiner meinung, leider kann ich nicht via konsole auf den raspery zugreifen
gibt es noch weiter alternativen?
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
leider kann ich nicht via konsole auf den raspery zugreifen
Warum nicht? Auch nicht mit den anderen Zugangsparametern?
-
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
leider kann ich nicht via konsole auf den raspery zugreifen
Warum nicht? Auch nicht mit den anderen Zugangsparametern?
habe es mit ping probiert, keine Antwort obwohl netzwerk und Kontrollleuchten leuchten bzw blinken
habe es stromlosgemacht und kann für kurze zeit darauf zugreifensudo iob diaglief kurz an und hat dann wieder verbindung verloren (lief also nicht durch)
output bis dahinThe state system.host.SmartHomeRohlik.versions.nodeNewestNext was not found! The state system.host.SmartHomeRohlik.versions.npmNewestNext was not found! The state system.host.SmartHomeRohlik.versions.nodeCurrent was not found!über die weboberfläche kam ich auch kurz auf die admin flache.
dort wurde eine langsame netztwerkverbindung erkannt (da hat sich aber von der Hardware nichts verändert) -
@keineahnungvonprogrmieren said in Probleme beim Update Host node.js:
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
leider kann ich nicht via konsole auf den raspery zugreifen
Warum nicht? Auch nicht mit den anderen Zugangsparametern?
habe es mit ping probiert, keine Antwort obwohl netzwerk und Kontrollleuchten leuchten bzw blinken
habe es stromlosgemacht und kann für kurze zeit darauf zugreifensudo iob diaglief kurz an und hat dann wieder verbindung verloren (lief also nicht durch)
output bis dahinThe state system.host.SmartHomeRohlik.versions.nodeNewestNext was not found! The state system.host.SmartHomeRohlik.versions.npmNewestNext was not found! The state system.host.SmartHomeRohlik.versions.nodeCurrent was not found!über die weboberfläche kam ich auch kurz auf die admin flache.
dort wurde eine langsame netztwerkverbindung erkannt (da hat sich aber von der Hardware nichts verändert)jetzt ist die diagnose weitergekommen:
======== 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: 16:37:57 up 2 min, 1 user, load average: 1.73, 0.89, 0.35 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** Time and Time Zones *** Local time: Thu 2024-08-08 16:37:57 CEST Universal time: Thu 2024-08-08 14:37:57 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': root HOME=/root GROUPS=root User that is running 'js-controller': iobroker HOME=/home/iobroker GROUPS=iobroker tty dialout audio video plugdev bluetooth gpio i2c *** Display-Server-Setup *** Display-Server: false Desktop: Terminal: Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 961M 6.6G 1.0M 287M 6.7G Swap: 99M 0B 99M Total: 7.9G 961M 6.7G Active iob-Instances: 13 7812 M total memory 962 M used memory 1016 M active memory 127 M inactive memory 6563 M free memory 40 M buffer memory 246 M swap cache 99 M total swap 0 M used swap 99 M free swap *** top - Table Of Processes *** top - 16:37:58 up 2 min, 1 user, load average: 1.73, 0.89, 0.35 Tasks: 174 total, 1 running, 173 sleeping, 0 stopped, 0 zombie %Cpu(s): 5.9 us, 2.9 sy, 0.0 ni, 91.2 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7812.3 total, 6563.3 free, 961.7 used, 287.3 buff/cache MiB Swap: 100.0 total, 100.0 free, 0.0 used. 6735.2 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 5.8G 51G 11% / 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: [Thu Aug 8 16:35:35 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 [Thu Aug 8 16:35:36 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [Thu Aug 8 16:35:36 2024] EXT4-fs (mmcblk0p2): write access will be enabled during recovery [Thu Aug 8 16:35:37 2024] EXT4-fs (mmcblk0p2): recovery complete [Thu Aug 8 16:35:37 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Thu Aug 8 16:35:37 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Aug 8 16:35:39 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/kernel/config configfs configfs rw,nosuid,nodev,noexec,relatime | `-/sys/fs/fuse/connections fusectl fusectl 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: 1.5G /var/ 989M /var/log 817M /var/log/journal/9ab67524321c46fcbcc935773dd5bf51 817M /var/log/journal 379M /var/cache Archived and active journals take up 816.2M in the file system. /opt/iobroker/backups: 67M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 654M /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 14M /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 iobroker is running on this host. Objects type: jsonl States type: jsonl Core adapters versions js-controller: 6.0.9 admin: 7.0.22 javascript: 8.7.6 nodejs modules from github: 0 Adapter State + system.adapter.admin.0 : admin : SmartHomeRohlik - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.backitup.0 : backitup : SmartHomeRohlik - enabled system.adapter.bshb.0 : bshb : SmartHomeRohlik - disabled + system.adapter.discovery.0 : discovery : SmartHomeRohlik - enabled + system.adapter.javascript.0 : javascript : SmartHomeRohlik - enabled system.adapter.mihome-vacuum.0 : mihome-vacuum : SmartHomeRohlik - disabled, port: 54321 + system.adapter.modbus.0 : modbus : SmartHomeRohlik - enabled system.adapter.rainbird.0 : rainbird : SmartHomeRohlik - enabled + system.adapter.rpi2.0 : rpi2 : SmartHomeRohlik - enabled + system.adapter.shelly.0 : shelly : SmartHomeRohlik - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : SmartHomeRohlik - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : SmartHomeRohlik - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : SmartHomeRohlik - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.vis-inventwo.0 : vis-inventwo : SmartHomeRohlik - enabled system.adapter.vis-timeandweather.0 : vis-timeandweather : SmartHomeRohlik - enabled system.adapter.vis.0 : vis : SmartHomeRohlik - enabled + system.adapter.web.0 : web : SmartHomeRohlik - enabled, port: 8082, bind: 0.0.0.0, run as: admin system.adapter.whatsapp-cmb.0 : whatsapp-cmb : SmartHomeRohlik - disabled + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : SmartHomeRohlik - enabled, port: 8081, bind: 0.0.0.0, run as: admin + system.adapter.shelly.0 : shelly : SmartHomeRohlik - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.shelly.1 : shelly : SmartHomeRohlik - enabled, port: 1882, bind: 0.0.0.0 + system.adapter.simple-api.0 : simple-api : SmartHomeRohlik - enabled, port: 8087, bind: 0.0.0.0, run as: admin + system.adapter.sonoff.0 : sonoff : SmartHomeRohlik - enabled, port: 1883, bind: 0.0.0.0 + system.adapter.web.0 : web : SmartHomeRohlik - enabled, port: 8082, bind: 0.0.0.0, run as: admin ioBroker-Repositories -
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
sudo iob diag
NEIN.
iob-Kommandos werden NIE, GAR NICHT, KEINEN FALLS per sudo eingeleitet.
Wie kommt man immer auf den Quark? Steht das irgendwo? -
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
sudo iob diag
NEIN.
iob-Kommandos werden NIE, GAR NICHT, KEINEN FALLS per sudo eingeleitet.
Wie kommt man immer auf den Quark? Steht das irgendwo?bin davon ausgegangen das sudo immer davor steht
sorryliegt es daran?
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
liegt es daran?
Es liegt immer an verfummelten Rechten. Also ja.
-
@thomas-braun said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
liegt es daran?
Es liegt immer an verfummelten Rechten. Also ja.
neue diag und admin auf 7.0.23 upgedatet (wegen dem Fehler auf der weboberfläche)
https://github.com/ioBroker/ioBroker.admin/issues/2599Copy text starting here:
======================= 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 86M 7.5G 1.0M 264M 7.6G Swap: 99M 0B 99M Total: 7.9G 86M 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: 24M /opt/iobroker/iobroker-data/objects.jsonl 4.4M /opt/iobroker/iobroker-data/states.jsonl ********************************************************************* Some problems detected, please run iob fix and try to have them fixed ********************************************************************* =================== END OF SUMMARY ======================= Mark text until here for copying ===
closed [bug]: Error in GUI #2599
-
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
please run iob fix and try to have them fixed
hattest du das gemacht?
-
Jetzt hast es ganz kauttgefrickelt...
iob stop cd /opt/iobroker npm install iobroker.js-controller@6.0.9 iob startDann die Langfassung von
iob diag -
@homoran said in Probleme beim Update Host node.js:
@keineahnungvonprogrmieren sagte in Probleme beim Update Host node.js:
please run iob fix and try to have them fixed
hattest du das gemacht?
ja habe ich
-
@thomas-braun said in Probleme beim Update Host node.js:
Jetzt hast es ganz kauttgefrickelt...
iob stop cd /opt/iobroker npm install iobroker.js-controller@6.0.9 iob startDann die Langfassung von
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: 18:14:07 up 1 min, 1 user, load average: 0.43, 0.15, 0.05 CPU threads: 4 *** RASPBERRY THROTTLING *** Current issues: No throttling issues detected. Previously detected issues: ~ Under-voltage has occurred ~ Arm frequency capping has occurred *** Time and Time Zones *** Local time: Thu 2024-08-08 18:14:07 CEST Universal time: Thu 2024-08-08 16:14:07 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 87M 7.5G 1.0M 194M 7.6G Swap: 99M 0B 99M Total: 7.9G 87M 7.6G Active iob-Instances: 0 7812 M total memory 87 M used memory 139 M active memory 57 M inactive memory 7530 M free memory 36 M buffer memory 158 M swap cache 99 M total swap 0 M used swap 99 M free swap *** top - Table Of Processes *** top - 18:14:08 up 1 min, 1 user, load average: 0.43, 0.15, 0.05 Tasks: 160 total, 1 running, 159 sleeping, 0 stopped, 0 zombie %Cpu(s): 2.9 us, 1.5 sy, 0.0 ni, 95.6 id, 0.0 wa, 0.0 hi, 0.0 si, 0.0 st MiB Mem : 7812.3 total, 7530.5 free, 87.1 used, 194.7 buff/cache MiB Swap: 100.0 total, 100.0 free, 0.0 used. 7614.3 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 5.7G 51G 11% / 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: [Thu Aug 8 18:12:51 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 [Thu Aug 8 18:12:52 2024] EXT4-fs (mmcblk0p2): INFO: recovery required on readonly filesystem [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 complete [Thu Aug 8 18:12:53 2024] EXT4-fs (mmcblk0p2): mounted filesystem with ordered data mode. Quota mode: none. [Thu Aug 8 18:12:53 2024] VFS: Mounted root (ext4 filesystem) readonly on device 179:2. [Thu Aug 8 18:12:55 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/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 |-/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: 1.5G /var/ 1011M /var/log 833M /var/log/journal/9ab67524321c46fcbcc935773dd5bf51 833M /var/log/journal 379M /var/cache Archived and active journals take up 832.2M 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://deb.debian.org/debian bullseye InRelease Hit:3 http://deb.debian.org/debian bullseye-updates InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye 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 14089 532/sshd: /usr/sbin tcp6 0 0 :::22 :::* LISTEN 0 14091 532/sshd: /usr/sbin udp 0 0 0.0.0.0:68 0.0.0.0:* 0 14100 723/dhcpcd udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 11931 364/avahi-daemon: r udp 0 0 0.0.0.0:58854 0.0.0.0:* 108 11933 364/avahi-daemon: r udp6 0 0 :::32981 :::* 108 11934 364/avahi-daemon: r udp6 0 0 :::546 :::* 0 12006 723/dhcpcd udp6 0 0 :::5353 :::* 108 11932 364/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 =============
======================= 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 256M 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 ====================so richtig?
-
@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.
