node-red 4.0 fehler beim Adapterstart
-
System: ioBroker 4.0.23
node: 16.16nach dem Update des Node-red Adapter auf 4.0 startet dieser immer mit folgendem Fehler:
TypeError: files.forEach is not a function at /opt/iobroker/node_modules/fs.notify/notify.js:45:11 at /opt/iobroker/node_modules/async/dist/async.js:2955:29 at wrapper (/opt/iobroker/node_modules/async/dist/async.js:271:20) at iteratorCallback (/opt/iobroker/node_modules/async/dist/async.js:499:17) at /opt/iobroker/node_modules/async/dist/async.js:327:20 at /opt/iobroker/node_modules/async/dist/async.js:2952:17 at suppressedCallback (node:fs:263:5) at FSReqCallback.oncomplete (node:fs:188:23)im node-log steh
verbose stack Error: ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/argparse' -> '/opt/iobroker/node_modules/.argparse-S5zfMSQi'iobroker fixundiobroker rebuildbereits durchlaufen lassen.
Was kann ich noch versuchen? Das Modul argparse manuell installieren, den Ordern argparse löschen, ein Github-Issue eröffnen, ....?
Danke schon mal.nuc i5: RaspberryMatic, ioBroker, pi-hole, SQL-Server, OMV-NAS, Influx-DB & Grafana, OpenHab, tasmoadmin
-
System: ioBroker 4.0.23
node: 16.16nach dem Update des Node-red Adapter auf 4.0 startet dieser immer mit folgendem Fehler:
TypeError: files.forEach is not a function at /opt/iobroker/node_modules/fs.notify/notify.js:45:11 at /opt/iobroker/node_modules/async/dist/async.js:2955:29 at wrapper (/opt/iobroker/node_modules/async/dist/async.js:271:20) at iteratorCallback (/opt/iobroker/node_modules/async/dist/async.js:499:17) at /opt/iobroker/node_modules/async/dist/async.js:327:20 at /opt/iobroker/node_modules/async/dist/async.js:2952:17 at suppressedCallback (node:fs:263:5) at FSReqCallback.oncomplete (node:fs:188:23)im node-log steh
verbose stack Error: ENOTEMPTY: directory not empty, rename '/opt/iobroker/node_modules/argparse' -> '/opt/iobroker/node_modules/.argparse-S5zfMSQi'iobroker fixundiobroker rebuildbereits durchlaufen lassen.
Was kann ich noch versuchen? Das Modul argparse manuell installieren, den Ordern argparse löschen, ein Github-Issue eröffnen, ....?
Danke schon mal.@johgre sagte in node-red 4.0 fehler beim Adapterstart:
cd /opt/iobroker/node_modules for i in $(ls -d .[^.]*-*/); do rm -rf ${i%%/}; done npm ls -
@johgre sagte in node-red 4.0 fehler beim Adapterstart:
cd /opt/iobroker/node_modules for i in $(ls -d .[^.]*-*/); do rm -rf ${i%%/}; done npm ls@thomas-braun sagte in node-red 4.0 fehler beim Adapterstart:
for i in $(ls -d .[^.]-/); do rm -rf ${i%%/}; done npm ls
bitte schön
pi@ioBroker-VM-Slave:~$ cd /opt/iobroker/node_modules/ pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$ for i in $(ls -d .[^.]*-*/); do rm -rf ${i%%/}; done pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$ npm ls [sudo] password for pi: iobroker.inst@3.0.0 /opt/iobroker +-- @types/caseless@0.12.2 extraneous +-- @types/request@2.48.8 extraneous +-- @types/tough-cookie@4.0.2 extraneous +-- coffeescript@1.12.7 extraneous +-- iobroker.awattar@1.0.6 +-- iobroker.botvac@1.0.0 +-- iobroker.daswetter@3.1.3 +-- iobroker.email@1.1.3 +-- iobroker.fahrplan@1.2.2 +-- iobroker.fakeroku@0.2.1 +-- iobroker.feiertage@1.1.0 +-- iobroker.govee@0.0.5 (git+ssh://git@github.com/nbuenger/ioBroker.govee.git#0d983c49135b87ac2f88f9d832a6d632c4889606) +-- iobroker.heizoel@1.0.3 +-- iobroker.javascript@6.0.0 +-- iobroker.js-controller@4.0.23 +-- iobroker.netatmo@1.7.1 +-- iobroker.node-red@4.0.0 invalid: "3.3.1" from the root project +-- iobroker.octoprint@4.0.0 +-- iobroker.openuv@0.0.5 (git+ssh://git@github.com/x3l4c0d3/ioBroker.openuv.git#810f8d7ec1fb30af3cc77f8ee0aee709ae68dbc3) +-- iobroker.ping@1.5.3 +-- iobroker.pvforecast@2.3.0 +-- iobroker.traccar@0.0.12 +-- iobroker.trashschedule@2.0.3 +-- iobroker.uv-protect@0.3.6 +-- iobroker.wifilight@1.1.4 +-- node-inspect@2.0.0 extraneous +-- picocolors@1.0.0 extraneous +-- setimmediate@1.0.5 extraneous +-- suncalc2@1.8.1 extraneous +-- typescript@4.7.4 extraneous +-- virtual-tsc@0.6.2 extraneous `-- wake_on_lan@1.0.0 extraneous npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.2 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.8 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.2 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: coffeescript@1.12.7 /opt/iobroker/node_modules/coffeescript npm ERR! invalid: iobroker.node-red@4.0.0 /opt/iobroker/node_modules/iobroker.node-red npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect npm ERR! extraneous: picocolors@1.0.0 /opt/iobroker/node_modules/picocolors npm ERR! extraneous: setimmediate@1.0.5 /opt/iobroker/node_modules/setimmediate npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2 npm ERR! extraneous: typescript@4.7.4 /opt/iobroker/node_modules/typescript npm ERR! extraneous: virtual-tsc@0.6.2 /opt/iobroker/node_modules/virtual-tsc npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-08-16T10_37_58_740Z-debug-0.log pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$nuc i5: RaspberryMatic, ioBroker, pi-hole, SQL-Server, OMV-NAS, Influx-DB & Grafana, OpenHab, tasmoadmin
-
@thomas-braun sagte in node-red 4.0 fehler beim Adapterstart:
for i in $(ls -d .[^.]-/); do rm -rf ${i%%/}; done npm ls
bitte schön
pi@ioBroker-VM-Slave:~$ cd /opt/iobroker/node_modules/ pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$ for i in $(ls -d .[^.]*-*/); do rm -rf ${i%%/}; done pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$ npm ls [sudo] password for pi: iobroker.inst@3.0.0 /opt/iobroker +-- @types/caseless@0.12.2 extraneous +-- @types/request@2.48.8 extraneous +-- @types/tough-cookie@4.0.2 extraneous +-- coffeescript@1.12.7 extraneous +-- iobroker.awattar@1.0.6 +-- iobroker.botvac@1.0.0 +-- iobroker.daswetter@3.1.3 +-- iobroker.email@1.1.3 +-- iobroker.fahrplan@1.2.2 +-- iobroker.fakeroku@0.2.1 +-- iobroker.feiertage@1.1.0 +-- iobroker.govee@0.0.5 (git+ssh://git@github.com/nbuenger/ioBroker.govee.git#0d983c49135b87ac2f88f9d832a6d632c4889606) +-- iobroker.heizoel@1.0.3 +-- iobroker.javascript@6.0.0 +-- iobroker.js-controller@4.0.23 +-- iobroker.netatmo@1.7.1 +-- iobroker.node-red@4.0.0 invalid: "3.3.1" from the root project +-- iobroker.octoprint@4.0.0 +-- iobroker.openuv@0.0.5 (git+ssh://git@github.com/x3l4c0d3/ioBroker.openuv.git#810f8d7ec1fb30af3cc77f8ee0aee709ae68dbc3) +-- iobroker.ping@1.5.3 +-- iobroker.pvforecast@2.3.0 +-- iobroker.traccar@0.0.12 +-- iobroker.trashschedule@2.0.3 +-- iobroker.uv-protect@0.3.6 +-- iobroker.wifilight@1.1.4 +-- node-inspect@2.0.0 extraneous +-- picocolors@1.0.0 extraneous +-- setimmediate@1.0.5 extraneous +-- suncalc2@1.8.1 extraneous +-- typescript@4.7.4 extraneous +-- virtual-tsc@0.6.2 extraneous `-- wake_on_lan@1.0.0 extraneous npm ERR! code ELSPROBLEMS npm ERR! extraneous: @types/caseless@0.12.2 /opt/iobroker/node_modules/@types/caseless npm ERR! extraneous: @types/request@2.48.8 /opt/iobroker/node_modules/@types/request npm ERR! extraneous: @types/tough-cookie@4.0.2 /opt/iobroker/node_modules/@types/tough-cookie npm ERR! extraneous: coffeescript@1.12.7 /opt/iobroker/node_modules/coffeescript npm ERR! invalid: iobroker.node-red@4.0.0 /opt/iobroker/node_modules/iobroker.node-red npm ERR! extraneous: node-inspect@2.0.0 /opt/iobroker/node_modules/node-inspect npm ERR! extraneous: picocolors@1.0.0 /opt/iobroker/node_modules/picocolors npm ERR! extraneous: setimmediate@1.0.5 /opt/iobroker/node_modules/setimmediate npm ERR! extraneous: suncalc2@1.8.1 /opt/iobroker/node_modules/suncalc2 npm ERR! extraneous: typescript@4.7.4 /opt/iobroker/node_modules/typescript npm ERR! extraneous: virtual-tsc@0.6.2 /opt/iobroker/node_modules/virtual-tsc npm ERR! extraneous: wake_on_lan@1.0.0 /opt/iobroker/node_modules/wake_on_lan npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2022-08-16T10_37_58_740Z-debug-0.log pi@ioBroker-VM-Slave:/opt/iobroker/node_modules$@johgre sagte in node-red 4.0 fehler beim Adapterstart:
iobroker.node-red@4.0.0 invalid: "3.3.1" from the root project
Multihost? Und im anderen Host ist das Beta-Repo nicht aktiv?
iobroker upgrade node-red@3.3.1 --debug -
@johgre sagte in node-red 4.0 fehler beim Adapterstart:
iobroker.node-red@4.0.0 invalid: "3.3.1" from the root project
Multihost? Und im anderen Host ist das Beta-Repo nicht aktiv?
iobroker upgrade node-red@3.3.1 --debug@thomas-braun sagte in node-red 4.0 fehler beim Adapterstart:
@johgre sagte in node-red 4.0 fehler beim Adapterstart:
iobroker.node-red@4.0.0 invalid: "3.3.1" from the root project
Multihost? Und im anderen Host ist das Beta-Repo nicht aktiv?
ja, Multihost und beide am Beta-Repro
Hey! Du scheinst an dieser Unterhaltung interessiert zu sein, hast aber noch kein Konto.
Hast du es satt, bei jedem Besuch durch die gleichen Beiträge zu scrollen? Wenn du dich für ein Konto anmeldest, kommst du immer genau dorthin zurück, wo du zuvor warst, und kannst dich über neue Antworten benachrichtigen lassen (entweder per E-Mail oder Push-Benachrichtigung). Du kannst auch Lesezeichen speichern und Beiträge positiv bewerten, um anderen Community-Mitgliedern deine Wertschätzung zu zeigen.
Mit deinem Input könnte dieser Beitrag noch besser werden 💗
Registrieren AnmeldenSupport us
528
Online32.8k
Benutzer82.6k
Themen1.3m
Beiträge