Node-Red lädt Nodes beim Starten nicht mehr
-
@mickym said in Node-Red lädt Nodes beim Starten nicht mehr:
Danke für die schnelle Antwort!
iob diag
Skript v.2023-04-16 *** BASE SYSTEM *** Model : Raspberry Pi 4 Model B Rev 1.4 Architecture : aarch64 Docker : false Virtualization : none Distributor ID: Raspbian Description: Raspbian GNU/Linux 11 (bullseye) Release: 11 Codename: bullseye PRETTY_NAME="Raspbian GNU/Linux 11 (bullseye)" NAME="Raspbian GNU/Linux" VERSION_ID="11" VERSION="11 (bullseye)" VERSION_CODENAME=bullseye ID=raspbian ID_LIKE=debian HOME_URL="http://www.raspbian.org/" SUPPORT_URL="http://www.raspbian.org/RaspbianForums" BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs" Systemuptime and Load: 23:06:18 up 9:37, 1 user, load average: 0.28, 0.32, 0.29 CPU threads: 4 Raspberry only: throttled=0x0 Other values than 0x0 hint to temperature/voltage problems temp=64.2'C volt=0.9260V *** Time and Time Zones *** Local time: Tue 2023-07-18 23:06:18 CEST Universal time: Tue 2023-07-18 21:06:18 UTC RTC time: n/a Time zone: Europe/Berlin (CEST, +0200) System clock synchronized: yes NTP service: active RTC in local TZ: no *** User and Groups *** pi /home/pi pi adm tty uucp dialout cdrom sudo audio video plugdev games users input netdev lpadmin gpio i2c spi iobroker *** X-Server-Setup *** X-Server: false Desktop: Terminal: tty Boot Target: multi-user.target *** MEMORY *** total used free shared buff/cache available Mem: 7.8G 958M 5.0G 1.0M 1.8G 6.7G Swap: 99M 0B 99M Total: 7.9G 958M 5.1G 7823 M total memory 958 M used memory 1235 M active memory 1338 M inactive memory 5017 M free memory 200 M buffer memory 1646 M swap cache 99 M total swap 0 M used swap 99 M free swap Raspberry only: oom events: 0 lifetime oom required: 0 Mbytes total time in oom handler: 0 ms max time spent in oom handler: 0 ms *** FILESYSTEM *** Filesystem Type Size Used Avail Use% Mounted on /dev/root ext4 29G 14G 15G 48% / devtmpfs devtmpfs 3.6G 0 3.6G 0% /dev tmpfs tmpfs 3.9G 0 3.9G 0% /dev/shm tmpfs tmpfs 1.6G 920K 1.6G 1% /run tmpfs tmpfs 5.0M 4.0K 5.0M 1% /run/lock /dev/sda1 vfat 253M 51M 202M 20% /boot //192.168.2.111/homes cifs 11T 2.3T 8.3T 22% /media/NAS tmpfs tmpfs 783M 24K 783M 1% /run/user/1000 Messages concerning ext4 filesystem in dmesg: [Tue Jul 18 13:29:16 2023] Kernel command line: coherent_pool=1M 8250.nr_uarts=1 snd_bcm2835.enable_headphones=0 snd_bcm2835.enable_headphones=1 snd_bcm2835.enable_hdmi=1 snd_bcm2835.enable_hdmi=0 smsc95xx.macaddr=DC:A6:32:EA:D1:8C vc_mem.mem_base=0x3eb00000 vc_mem.mem_size=0x3ff00000 console=tty1 root=PARTUUID=c85e32c5-02 rootfstype=ext4 fsck.repair=yes rootwait [Tue Jul 18 13:29:18 2023] EXT4-fs (sda2): mounted filesystem with ordered data mode. Quota mode: none. [Tue Jul 18 13:29:18 2023] VFS: Mounted root (ext4 filesystem) readonly on device 8:2. [Tue Jul 18 13:29:20 2023] EXT4-fs (sda2): re-mounted. Quota mode: none. Show mounted filesystems (real ones only): TARGET SOURCE FSTYPE OPTIONS / /dev/sda2 ext4 rw,noatime |-/boot /dev/sda1 vfat rw,relatime,fmask=0022,dmask=0022,codepage=437,iocharset=ascii,shortname=mixed,flush,errors=remount-ro `-/media/NAS //192.168.2.111/homes cifs rw,nosuid,nodev,noexec,relatime,vers=3.1.1,cache=strict,username=backup,domain=192.168.2.111,uid=1000,noforceuid,gid=1000,noforcegid,addr=192.168.2.111,file_mode=0755,dir_mode=0755,soft,nounix,serverino,mapposix,rsize=4194304,wsize=4194304,bsize=1048576,echo_interval=60,actimeo=1,closetimeo=5 Files in neuralgic directories: /var: 4.0G /var/ 3.0G /var/log/journal/45677fd33dca4b97838c0214e7692911 3.0G /var/log/journal 3.0G /var/log 822M /var/cache Archived and active journals take up 2.9G in the file system. /opt/iobroker/backups: 105M /opt/iobroker/backups/ /opt/iobroker/iobroker-data: 1.4G /opt/iobroker/iobroker-data/ 621M /opt/iobroker/iobroker-data/files 558M /opt/iobroker/iobroker-data/node-red 543M /opt/iobroker/iobroker-data/node-red/node_modules 403M /opt/iobroker/iobroker-data/files/vis-2-beta The five largest files in iobroker-data are: 35M /opt/iobroker/iobroker-data/files/devices.admin/static/js/main.24f2bb56.js.map 31M /opt/iobroker/iobroker-data/objects.jsonl 11M /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/typescript/lib/tsserverlibrary.js 11M /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman/node_modules/typescript/lib/tsserver.js 11M /opt/iobroker/iobroker-data/node-red/node_modules/zigbee-herdsman-converters/node_modules/zigbee-herdsman/node_modules/typescript/lib/tsserverlibrary.js *** NodeJS-Installation *** /usr/bin/nodejs v18.16.1 /usr/bin/node v18.16.1 /usr/bin/npm 9.5.1 /usr/bin/npx 9.5.1 nodejs: Installed: 18.16.1-deb-1nodesource1 Candidate: 18.16.1-deb-1nodesource1 Version table: *** 18.16.1-deb-1nodesource1 500 500 https://deb.nodesource.com/node_18.x bullseye/main armhf Packages 100 /var/lib/dpkg/status 12.22.12~dfsg-1~deb11u4 500 500 http://raspbian.raspberrypi.org/raspbian bullseye/main armhf Packages Temp directories causing npm8 problem: 0 No problems detected *** ioBroker-Installation *** ioBroker Status iobroker is running on this host. Objects type: jsonl States type: jsonl MULTIHOSTSERVICE/enabled: false Core adapters versions js-controller: 4.0.24 admin: 6.3.5 javascript: 7.0.3 Adapters from github: 1 Adapter State + system.adapter.admin.0 : admin : IOBroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin system.adapter.alias-manager.0 : alias-manager : IOBroker - disabled + system.adapter.backitup.0 : backitup : IOBroker - enabled + system.adapter.bmw.0 : bmw : IOBroker - enabled + system.adapter.cul.0 : cul : IOBroker - enabled, port: 23 + system.adapter.denon.0 : denon : IOBroker - enabled system.adapter.devices.0 : devices : IOBroker - disabled + system.adapter.discovery.0 : discovery : IOBroker - enabled + system.adapter.enocean.0 : enocean : IOBroker - enabled system.adapter.ical.0 : ical : IOBroker - enabled system.adapter.info.0 : info : IOBroker - disabled + system.adapter.javascript.0 : javascript : IOBroker - enabled + system.adapter.klf200.0 : klf200 : IOBroker - enabled + system.adapter.knx.0 : knx : IOBroker - enabled, bind: 192.168.3.195 + system.adapter.kodi.0 : kodi : IOBroker - enabled, port: 9090 system.adapter.mihome-vacuum.0 : mihome-vacuum : IOBroker - disabled, port: 54321 + system.adapter.node-red.0 : node-red : IOBroker - enabled, port: 1880, bind: 192.168.3.195 + system.adapter.rpi2.0 : rpi2 : IOBroker - enabled + system.adapter.sonos.0 : sonos : IOBroker - enabled + system.adapter.trashschedule.0 : trashschedule : IOBroker - enabled system.adapter.vis-2-beta.0 : vis-2-beta : IOBroker - disabled system.adapter.vis-2-widgets-energy.0 : vis-2-widgets-energy : IOBroker - enabled system.adapter.vis-2-widgets-gauges.0 : vis-2-widgets-gauges : IOBroker - enabled system.adapter.vis-2-widgets-material.0 : vis-2-widgets-material: IOBroker - enabled system.adapter.vis-icontwo.0 : vis-icontwo : IOBroker - disabled system.adapter.vis-inventwo.0 : vis-inventwo : IOBroker - disabled system.adapter.vis.0 : vis : IOBroker - disabled system.adapter.web.0 : web : IOBroker - disabled, port: 8082, bind: 192.168.3.195, run as: admin + system.adapter.zigbee.1 : zigbee : IOBroker - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fa8660cd8e93eb11a22f214f3d98b6d1-if00-port0 + instance is alive Enabled adapters with bindings + system.adapter.admin.0 : admin : IOBroker - enabled, port: 8081, bind: 0.0.0.0 (SSL), run as: admin + system.adapter.cul.0 : cul : IOBroker - enabled, port: 23 + system.adapter.kodi.0 : kodi : IOBroker - enabled, port: 9090 + system.adapter.node-red.0 : node-red : IOBroker - enabled, port: 1880, bind: 192.168.3.195 + system.adapter.zigbee.1 : zigbee : IOBroker - enabled, port: /dev/serial/by-id/usb-ITead_Sonoff_Zigbee_3.0_USB_Dongle_Plus_fa8660cd8e93eb11a22f214f3d98b6d1-if00-port0 ioBroker-Repositories Latest (possibly unstable): http://download.iobroker.net/sources-dist-latest.json Stable : http://download.iobroker.net/sources-dist.json Active repo(s): Stable Installed ioBroker-Instances Used repository: Stable Adapter "admin" : 6.3.5 , installed 6.3.5 Adapter "alias-manager": 1.2.4 , installed 1.2.4 Adapter "backitup" : 2.6.23 , installed 2.6.23 Adapter "bmw" : 2.5.7 , installed 2.5.7 Adapter "cul" : 2.2.0 , installed 2.2.0 Adapter "denon" : 1.15.2 , installed 1.15.2 Adapter "devices" : 1.1.5 , installed 1.1.5 Adapter "discovery" : 3.1.0 , installed 3.1.0 Adapter "ical" : 1.13.3 , installed 1.13.3 Adapter "info" : 1.9.26 , installed 1.9.26 Adapter "javascript" : 7.0.3 , installed 7.0.3 Controller "js-controller": 4.0.24 , installed 4.0.24 Adapter "klf200" : 1.0.1 , installed 1.0.1 Adapter "knx" : 2.0.17 , installed 2.0.17 Adapter "kodi" : 2.0.9 , installed 2.0.9 Adapter "mihome-vacuum": 3.11.0 , installed 3.11.0 Adapter "node-red" : 4.0.3 , installed 4.0.3 Adapter "octoprint" : 4.0.0 , installed 4.0.0 Adapter "openweathermap": 0.3.9 , installed 0.3.9 Adapter "rpi2" : 1.3.2 , installed 1.3.2 Adapter "simple-api" : 2.7.2 , installed 2.7.2 Adapter "socketio" : 4.2.0 , installed 4.2.0 Adapter "sonos" : 2.3.1 , installed 2.3.1 Adapter "trashschedule": 2.2.0 , installed 2.2.0 Adapter "viessmannapi" : 2.0.9 , installed 2.0.9 Adapter "vis" : 1.4.16 , installed 1.4.16 Adapter "vis-icontwo" : 0.96.0 , installed 0.96.0 Adapter "vis-inventwo" : 3.3.3 , installed 3.3.3 Adapter "web" : 4.3.0 , installed 4.3.0 Adapter "ws" : 1.3.0 , installed 1.3.0 Adapter "zigbee" : 1.8.16 , installed 1.8.16 Objects and States Please stand by - This may take a while Objects: 5840 States: 4086 *** OS-Repositories and Updates *** Hit:1 http://phoscon.de/apt/deconz bullseye InRelease Hit:2 http://raspbian.raspberrypi.org/raspbian bullseye InRelease Hit:3 http://ftp.debian.org/debian bullseye-backports InRelease Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease Hit:5 https://deb.nodesource.com/node_18.x bullseye InRelease Reading package lists... Pending Updates: 3 *** 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:5900 0.0.0.0:* LISTEN 0 16464 634/vncserver-x11-c tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 0 1705 643/sshd: /usr/sbin tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN 1000 1693 481/deCONZ tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN 1000 1750 481/deCONZ tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 0 15625 621/cupsd tcp 0 0 127.0.0.1:9001 0.0.0.0:* LISTEN 1001 1068677 4205/iobroker.js-co tcp 0 0 127.0.0.1:9000 0.0.0.0:* LISTEN 1001 1069394 4205/iobroker.js-co tcp 0 0 192.168.3.195:1880 0.0.0.0:* LISTEN 1001 1287019 314/node-red tcp6 0 0 :::5900 :::* LISTEN 0 16463 634/vncserver-x11-c tcp6 0 0 :::22 :::* LISTEN 0 1707 643/sshd: /usr/sbin tcp6 0 0 :::3500 :::* LISTEN 1001 1072229 4753/io.sonos.0 tcp6 0 0 :::8081 :::* LISTEN 1001 1070137 4284/io.admin.0 tcp6 0 0 ::1:631 :::* LISTEN 0 15624 621/cupsd udp 0 0 0.0.0.0:68 0.0.0.0:* 0 1763 835/dhcpcd udp 0 0 0.0.0.0:33215 0.0.0.0:* 108 15017 475/avahi-daemon: r udp 0 0 0.0.0.0:631 0.0.0.0:* 0 15713 646/cups-browsed udp 0 0 0.0.0.0:5353 0.0.0.0:* 108 15015 475/avahi-daemon: r udp 0 0 0.0.0.0:1900 0.0.0.0:* 1000 1753 481/deCONZ udp 0 0 192.168.3.195:35494 0.0.0.0:* 1001 1072521 5045/io.knx.0 udp6 0 0 :::5353 :::* 108 15016 475/avahi-daemon: r udp6 0 0 :::47211 :::* 108 15018 475/avahi-daemon: r *** Log File - Last 25 Lines *** 2023-07-18 22:56:08.764 - info: bmw.0 (4914) Got terminate signal TERMINATE_YOURSELF 2023-07-18 22:56:08.766 - info: bmw.0 (4914) terminating 2023-07-18 22:56:08.768 - info: bmw.0 (4914) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason 2023-07-18 22:56:08.851 - info: host.IOBroker stopInstance system.adapter.bmw.0 send kill signal 2023-07-18 22:56:09.359 - info: host.IOBroker instance system.adapter.bmw.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION) 2023-07-18 22:56:09.594 - info: admin.0 (4284) <== Disconnect system.user.admin from ::ffff:192.168.2.202 2023-07-18 22:56:11.944 - info: host.IOBroker instance system.adapter.bmw.0 started with pid 4609 2023-07-18 22:56:14.286 - info: bmw.0 (4609) starting. Version 2.5.7 in /opt/iobroker/node_modules/iobroker.bmw, node: v18.16.1, js-controller: 4.0.24 2023-07-18 22:56:15.080 - info: bmw.0 (4609) Start getting mini vehicles 2023-07-18 22:56:15.440 - error: bmw.0 (4609) getvehicles v2 failed 2023-07-18 22:56:15.442 - error: bmw.0 (4609) AxiosError: Request failed with status code 404 2023-07-18 22:56:15.442 - error: bmw.0 (4609) {"statusCode":404,"message":"Resource not found"} 2023-07-18 22:56:52.797 - info: admin.0 (4284) ==> Connected system.user.admin from ::ffff:192.168.2.202 2023-07-18 22:57:00.765 - warn: zigbee.1 (4642) DeviceAvailability:Stopping to ping 0x00158d00079a90b9 500.46 after 109 ping attempts 2023-07-18 23:00:00.004 - info: javascript.0 (4331) script.js.Zentrale_Funktionen.HCL_Helligkeit_nach_Zeit: Variable Helligkeit: 40 2023-07-18 23:00:00.006 - info: javascript.0 (4331) script.js.Zentrale_Funktionen.HCL_Farbtemperatur_nach_Zeit: Variable Helligkeit: 2000 2023-07-18 23:00:05.093 - warn: trashschedule.0 (5136) no events matches type "Restmüll" with match "Restmuell" 2023-07-18 23:00:05.143 - warn: trashschedule.0 (5136) no events matches type "Papier" with match "Papier" 2023-07-18 23:00:05.193 - warn: trashschedule.0 (5136) no events matches type "Gelber Sack" with match "gelber Sack" 2023-07-18 23:01:20.520 - error: bmw.0 (4609) getvehicles v2 failed 2023-07-18 23:01:20.522 - error: bmw.0 (4609) AxiosError: Request failed with status code 404 2023-07-18 23:01:20.523 - error: bmw.0 (4609) {"statusCode":404,"message":"Resource not found"} 2023-07-18 23:06:20.518 - error: bmw.0 (4609) getvehicles v2 failed 2023-07-18 23:06:20.519 - error: bmw.0 (4609) AxiosError: Request failed with status code 404 2023-07-18 23:06:20.520 - error: bmw.0 (4609) {"statusCode":404,"message":"Resource not found"} -
@mickym said in Node-Red lädt Nodes beim Starten nicht mehr:
Nutzt den paletten-Manager.
Den nehm ich normalerweise auch, nur komm ich da z.Zt. eben nicht mehr ran.
-
@cfau Nun das einfachste ist erst mal den Node-Red Adapter im Sicherheitsmodus zu starten. Versuch das mal. Wenn das nicht geht - dann ist die Frage, ob Du NodeRed mit dem Backup Adapter gesichert hast?
-
@mickym said in Node-Red lädt Nodes beim Starten nicht mehr:
Node-Red Adapter im Sicherheitsmodus
Keine Änderunghab auch schon den letzten Export von flows.json nach /opt/iobroker/iobroker-data/node-red zurückgeschrieben, auch das bringt nichts.
-
@cfau Nochmal hast Du eine Sicherung von NodeRed im Backitup-Adapter?
-
@mickym Sieht nicht so aus (als ich backitup eingerichtet hab, gabs das m.W. noch nicht als Option)
-
@mickym
Würde es Sinn machen, auf eine nodejs-version 16.4.x zurückzugehen? -
@cfau Ja das ist relativ neu - aber gut dann hast Du es nicht. Nein - das macht keinen Sinn - du musst eh updaten und ich habe keine Probleme.
Dann solltest Du zukünftig in jedem Fall das Backup mit aufnehmen.Poste mal deine package.json im Verzeichnis /opt/iobroker/iobroker-data/node-red
-
@mickym said in Node-Red lädt Nodes beim Starten nicht mehr:
Dann solltest Du zukünftig in jedem Fall das Backup mit aufnehmen.
Hatte ich nach dem Update heute schon erledigt.Poste mal deine package.json im Verzeichnis /opt/iobroker/iobroker-data/node-red
pi@IOBroker:/opt/iobroker/iobroker-data/node-red $ cat package.json { "dependencies": { "node-red-contrib-boolean-logic-ultimate": "~1.0.59", "node-red-contrib-buffer-parser": "~3.2.2", "node-red-contrib-ccu": "~3.4.2", "node-red-contrib-chroma": "~0.0.3", "node-red-contrib-color-convert": "^0.0.8", "node-red-contrib-cul": "0.0.16", "node-red-contrib-deconz": "~2.3.9", "node-red-contrib-enocean": "~0.8.5", "node-red-contrib-influxdb": "~0.6.1", "node-red-contrib-knx-ultimate": "~1.4.13", "node-red-contrib-merge": "~0.1.1", "node-red-contrib-merge-topic": "~0.1.2", "node-red-contrib-schedex": "~1.10.6", "node-red-contrib-sonos-events": "~1.2.1", "node-red-contrib-sonos-plus": "~6.6.1", "node-red-contrib-state": "~1.6.1", "node-red-contrib-string": "~1.0.0", "node-red-contrib-toggle": "~0.1.1", "node-red-contrib-ui-contextmenu": "~2.0.1", "node-red-contrib-zigbee": "~0.21.0", "node-red-dashboard": "~3.3.1", "node-red-node-email": "~1.18.4", "node-red-node-feedparser": "~0.3.0", "node-red-node-tail": "~0.4.0", "node-red-node-ui-table": "~0.4.3" } } -
@cfau ok - dann stoppe mal den Node-Red Adapter. - Irgendwo fehlt zwar in meinen Augen oben was in der Datei. Aber versuchs mal.
Benenne Dein node_modules Verzeichnis in dem Node Red Verzeichnis um - und dann lass alles nochmal installieren
Bitte kein Sudo und nichts und nur in diesem Verzeichnis
/opt/iobroker/iobroker-data/node-red ausführen.Am Besten vorher noch unter der iobroker-Kennung,
Also
sudo -su iobroker npm install -
@mickym
Das ist das Ergebnis:npm install npm WARN old lockfile npm WARN old lockfile The package-lock.json file was created with an old version of npm, npm WARN old lockfile so supplemental metadata must be fetched from the registry. npm WARN old lockfile npm WARN old lockfile This is a one-time fix-up, please be patient... npm WARN old lockfile npm WARN deprecated string-similarity@4.0.4: Package no longer supported. Contact Support at https://www.npmjs.com/support for more info. npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See https://v8.dev/blog/math-random for details. npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated vis@4.21.0: Please consider using https://github.com/visjs added 641 packages, and audited 687 packages in 2m 94 packages are looking for funding run `npm fund` for details 27 vulnerabilities (4 low, 14 moderate, 8 high, 1 critical) To address issues that do not require attention, run: npm audit fix To address all issues possible (including breaking changes), run: npm audit fix --force Some issues need review, and may require choosing a different dependency. Run `npm audit` for details.open Request’s Past, Present and Future #3142
-
@cfau Ok die package-lock.json - kannst du löschen oder weg sichern. Aber es wurde ja nun neu aufgebaut. Startet nun Dein NodeRed Adapter wieder ?
Das andere kannst ignorieren.
-
@mickym
Das wars, der Editor wird wieder gestartet: MERCI!!!!!Soll ich noch die vorgeschlagenen Fixes durchlaufen lassen?
-
@cfau Nein mach das nicht - schau in den Paletten-Manager und schau, welche Nodes aktualisiert werden müssen. Wie gesagt lösch noch die package-lock.json - die wird dann wieder neu angelegt, wenn was neu installiert wird.
-
@mickym
Erledigt, auch nach dem Update der Module läuft alles wieder!Vielen Dank!!!!
