NEWS
Iobroker.admin update Probleme
-
Hänge mich mal hier dran.
Bekomme nach einem Update von dem Admin Adapter auch die Meldung:
This adapter cannot be installed directly from github. You must install it from npm. Write for that "npm install iobroker.admin" in according directory.JS-Controller läuft auf 1.2.7
Wie komme ich wieder zurück auf eine bestimmte Version? 3.1.12 lief bei mir.
-
Konnte das Problem schlussendlich mit diesem Beitrag Lösen!!
-
Möchte kein neues Thema eröffnen, habe beim Update immer folgende Fehlermeldung:
npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})
Bin Anfänger und parser sagt mir nichts:/
root@iobroker:/opt/iobroker# sudo npm install iobroker.admin --production npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.5","node":"12.18.1"}Systeminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
Möchte kein neues Thema eröffnen, habe beim Update immer folgende Fehlermeldung:
npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})
Bin Anfänger und parser sagt mir nichts:/
root@iobroker:/opt/iobroker# sudo npm install iobroker.admin --production npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.5","node":"12.18.1"} -
Was hattest du denn vor?
Den Admin IMMER über die GUI updaten!!
Nie manuell über die Konsole!@haselchen Da krieg ich auch immer die gleiche Fehlermeldung
host.iobroker 2020-06-24 23:59:20.606 info iobroker ERR! notsup Actual: {"npm":"6.14.5","node":"12.18.1"} host.iobroker 2020-06-24 23:59:20.606 info iobroker notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm host.iobroker 2020-06-24 23:59:20.605 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! host.iobroker 2020-06-24 23:59:20.605 info iobroker ERR! code ENOTSUPSysteminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
@haselchen Da krieg ich auch immer die gleiche Fehlermeldung
host.iobroker 2020-06-24 23:59:20.606 info iobroker ERR! notsup Actual: {"npm":"6.14.5","node":"12.18.1"} host.iobroker 2020-06-24 23:59:20.606 info iobroker notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm host.iobroker 2020-06-24 23:59:20.605 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! host.iobroker 2020-06-24 23:59:20.605 info iobroker ERR! code ENOTSUP -
ja auf einer Proxmox-VM, welche Node und NPM Version wäre richtig?
admin.0 2020-06-25 00:13:40.799 info (6884) Use link "http://localhost:8081" to configure. admin.0 2020-06-25 00:13:40.799 info (6884) http server listening on port 8081 admin.0 2020-06-25 00:13:40.741 info (6884) received all objects host.iobroker 2020-06-25 00:13:40.579 info iobroker exit 0 admin.0 2020-06-25 00:13:40.130 info (6884) requesting all objects admin.0 2020-06-25 00:13:40.129 info (6884) requesting all states admin.0 2020-06-25 00:13:40.117 info (6884) starting. Version 3.7.8 in /opt/iobroker/node_modules/iobroker.admin, node: v12.18.1, js-controller: 3.1.4 host.iobroker 2020-06-25 00:13:39.514 info instance system.adapter.admin.0 started with pid 6884 host.iobroker 2020-06-25 00:13:39.491 info "system.adapter.admin.0" enabled host.iobroker 2020-06-25 00:13:39.480 info iobroker host.iobroker Adapter "system.adapter.admin.0" is started host.iobroker 2020-06-25 00:13:39.480 info iobroker Adapter "admin" updated host.iobroker 2020-06-25 00:13:39.423 info iobroker upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png host.iobroker 2020-06-25 00:13:39.370 info iobroker upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html host.iobroker 2020-06-25 00:13:39.317 info iobroker upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html host.iobroker 2020-06-25 00:13:39.230 info iobroker upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript host.iobroker 2020-06-25 00:13:39.209 info iobroker npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2020-06-24T22_13_39_205Z-debug.log host.iobroker 2020-06-25 00:13:39.209 info iobroker host.iobroker 2020-06-25 00:13:39.203 info iobroker Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm ERR! nots host.iobroker 2020-06-25 00:13:39.203 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! notsup host.iobroker 2020-06-25 00:13:39.203 info iobroker ERR! code ENOTSUP host.iobroker 2020-06-25 00:13:39.202 info iobroker npm host.iobroker 2020-06-25 00:13:33.236 info instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) host.iobroker 2020-06-25 00:13:32.888 info iobroker npm install iobroker.admin@4.0.10 --loglevel error --prefix "/opt/iobroker" (System call) host.iobroker 2020-06-25 00:13:32.888 info iobroker NPM version: 6.14.5 admin.0 2020-06-25 00:13:32.712 info (5859) Terminated (NO_ERROR): Without reason admin.0 2020-06-25 00:13:32.712 info (5859) terminating admin.0 2020-06-25 00:13:32.707 info (5859) Got terminate signal TERMINATE_YOURSELF admin.0 2020-06-25 00:13:32.704 info (5859) terminating http server on port 8081 host.iobroker 2020-06-25 00:13:32.702 info stopInstance system.adapter.admin.0 send kill signal admin.0 2020-06-25 00:13:32.701 info (5859) Adapter is disabled => stop host.iobroker 2020-06-25 00:13:32.701 info stopInstance system.adapter.admin.0 (force=false, process=true) host.iobroker 2020-06-25 00:13:32.701 info "system.adapter.admin.0" disabled host.iobroker 2020-06-25 00:13:32.684 info iobroker host.iobroker Adapter "system.adapter.admin.0" is stopped. host.iobroker 2020-06-25 00:13:32.675 info iobroker Update admin from @3.7.8 to @4.0.10 host.iobroker 2020-06-25 00:13:31.704 info iobroker upgrade adminSysteminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
ja auf einer Proxmox-VM, welche Node und NPM Version wäre richtig?
admin.0 2020-06-25 00:13:40.799 info (6884) Use link "http://localhost:8081" to configure. admin.0 2020-06-25 00:13:40.799 info (6884) http server listening on port 8081 admin.0 2020-06-25 00:13:40.741 info (6884) received all objects host.iobroker 2020-06-25 00:13:40.579 info iobroker exit 0 admin.0 2020-06-25 00:13:40.130 info (6884) requesting all objects admin.0 2020-06-25 00:13:40.129 info (6884) requesting all states admin.0 2020-06-25 00:13:40.117 info (6884) starting. Version 3.7.8 in /opt/iobroker/node_modules/iobroker.admin, node: v12.18.1, js-controller: 3.1.4 host.iobroker 2020-06-25 00:13:39.514 info instance system.adapter.admin.0 started with pid 6884 host.iobroker 2020-06-25 00:13:39.491 info "system.adapter.admin.0" enabled host.iobroker 2020-06-25 00:13:39.480 info iobroker host.iobroker Adapter "system.adapter.admin.0" is started host.iobroker 2020-06-25 00:13:39.480 info iobroker Adapter "admin" updated host.iobroker 2020-06-25 00:13:39.423 info iobroker upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png host.iobroker 2020-06-25 00:13:39.370 info iobroker upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html host.iobroker 2020-06-25 00:13:39.317 info iobroker upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html host.iobroker 2020-06-25 00:13:39.230 info iobroker upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript host.iobroker 2020-06-25 00:13:39.209 info iobroker npm ERR! A complete log of this run can be found in:npm ERR! /home/iobroker/.npm/_logs/2020-06-24T22_13_39_205Z-debug.log host.iobroker 2020-06-25 00:13:39.209 info iobroker host.iobroker 2020-06-25 00:13:39.203 info iobroker Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm ERR! nots host.iobroker 2020-06-25 00:13:39.203 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! notsup host.iobroker 2020-06-25 00:13:39.203 info iobroker ERR! code ENOTSUP host.iobroker 2020-06-25 00:13:39.202 info iobroker npm host.iobroker 2020-06-25 00:13:33.236 info instance system.adapter.admin.0 terminated with code 0 (NO_ERROR) host.iobroker 2020-06-25 00:13:32.888 info iobroker npm install iobroker.admin@4.0.10 --loglevel error --prefix "/opt/iobroker" (System call) host.iobroker 2020-06-25 00:13:32.888 info iobroker NPM version: 6.14.5 admin.0 2020-06-25 00:13:32.712 info (5859) Terminated (NO_ERROR): Without reason admin.0 2020-06-25 00:13:32.712 info (5859) terminating admin.0 2020-06-25 00:13:32.707 info (5859) Got terminate signal TERMINATE_YOURSELF admin.0 2020-06-25 00:13:32.704 info (5859) terminating http server on port 8081 host.iobroker 2020-06-25 00:13:32.702 info stopInstance system.adapter.admin.0 send kill signal admin.0 2020-06-25 00:13:32.701 info (5859) Adapter is disabled => stop host.iobroker 2020-06-25 00:13:32.701 info stopInstance system.adapter.admin.0 (force=false, process=true) host.iobroker 2020-06-25 00:13:32.701 info "system.adapter.admin.0" disabled host.iobroker 2020-06-25 00:13:32.684 info iobroker host.iobroker Adapter "system.adapter.admin.0" is stopped. host.iobroker 2020-06-25 00:13:32.675 info iobroker Update admin from @3.7.8 to @4.0.10 host.iobroker 2020-06-25 00:13:31.704 info iobroker upgrade admin -
@haselchen welche Node und NPM Version wäre richtig?
Systeminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
@haselchen welche Node und NPM Version wäre richtig?
-
Richtig oder falsch gibt es nicht.
Bei mir auf ner Synology läuft 10.21.0
Ich kenne mich mit Proxmox nicht aus.
Wenn du weisst , wie Du auf ne 10er Nodejs Version kommst, würde ich damit erstmal anfangen.@haselchen Theoretisch sollte dies mit der 12er laufen?
host.iobroker 2020-06-25 00:13:39.203 info iobroker Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm ERR! nots host.iobroker 2020-06-25 00:13:39.203 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! notsup host.iobroker 2020-06-25 00:13:39.203 info iobroker ERR! code ENOTSUPWas ist hier genau nicht supportet?
Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"
Diesen Fehler bekomme ich auch bei gewissen anderen Adapter wenn ich diese Updaten möchte.
Systeminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
@haselchen Theoretisch sollte dies mit der 12er laufen?
host.iobroker 2020-06-25 00:13:39.203 info iobroker Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4npm ERR! notsup Required: {"node":"0.4-0.9"}npm ERR! nots host.iobroker 2020-06-25 00:13:39.203 info iobroker npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"12.18.1","npm":"6.14.5"})npm ERR! notsup host.iobroker 2020-06-25 00:13:39.203 info iobroker ERR! code ENOTSUPWas ist hier genau nicht supportet?
Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"
Diesen Fehler bekomme ich auch bei gewissen anderen Adapter wenn ich diese Updaten möchte.
Wie gesagt, ich kenne mich mit Proxmox und der Umgebung nicht aus.
Ich kann dir dabei wirklich nicht weiterhelfen.
Wenn du nen Terminal hast und das so funktioniert wie beim Raspi etc. , könntest du mal nen Update machen.
apt-get update
apt-get dist-upgradeMehr fällt mir dazu leider nicht ein.
-
Wie gesagt, ich kenne mich mit Proxmox und der Umgebung nicht aus.
Ich kann dir dabei wirklich nicht weiterhelfen.
Wenn du nen Terminal hast und das so funktioniert wie beim Raspi etc. , könntest du mal nen Update machen.
apt-get update
apt-get dist-upgradeMehr fällt mir dazu leider nicht ein.
Habe nun das ganze System neu aufgesetzt auf dem Proxmox / NUC...
jedoch kommt der Fehler wieder....
hat mir eventuell jemand einen Tipp?
Update admin from @4.0.10 to @4.1.7 host.iobroker2 Adapter "system.adapter.admin.0" is stopped. NPM version: 6.14.6 npm install iobroker.admin@4.1.7 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"10.22.0","npm":"6.14.6"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.6","node":"10.22.0"} npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-29T20_09_01_886Z-debug.log upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png Adapter "admin" updated host.iobroker2 Adapter "system.adapter.admin.0" is startedSysteminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
Habe nun das ganze System neu aufgesetzt auf dem Proxmox / NUC...
jedoch kommt der Fehler wieder....
hat mir eventuell jemand einen Tipp?
Update admin from @4.0.10 to @4.1.7 host.iobroker2 Adapter "system.adapter.admin.0" is stopped. NPM version: 6.14.6 npm install iobroker.admin@4.1.7 --loglevel error --prefix "/opt/iobroker" (System call) npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"10.22.0","npm":"6.14.6"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.6","node":"10.22.0"} npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-08-29T20_09_01_886Z-debug.log upload [3] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/words.js words.js application/javascript upload [2] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index_m.html index_m.html text/html upload [1] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/index.html index.html text/html upload [0] admin.admin /opt/iobroker/node_modules/iobroker.admin/admin/admin.png admin.png image/png Adapter "admin" updated host.iobroker2 Adapter "system.adapter.admin.0" is startedcd /opt/iobroker npm ls parserWobei ich mir jetzt bei einem frisch aufgesetzten System nicht erklären kann wo so eine alte Dependency herkommt. Was hast du denn da gemacht?
-
cd /opt/iobroker npm ls parserWobei ich mir jetzt bei einem frisch aufgesetzten System nicht erklären kann wo so eine alte Dependency herkommt. Was hast du denn da gemacht?
@Thomas-Braun
Habe eus neu aufgesetzt und das Backup eingespielt :(iobroker@iobroker2:/opt/iobroker$ sudo npm ls parser iobroker.inst@2.0.3 /opt/iobroker `-- iobroker.javascript@4.1.12 `-- UNMET DEPENDENCY parser@^0.1.4 npm ERR! missing: parser@^0.1.4, required by iobroker.javascript@4.1.12 iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ sudo npm ls parser -bash: iobroker@iobroker2:/opt/iobroker$: No such file or directory iobroker@iobroker2:/opt/iobroker$ iobroker.inst@2.0.3 /opt/iobroker -bash: iobroker.inst@2.0.3: command not found iobroker@iobroker2:/opt/iobroker$ `-- iobroker.javascript@4.1.12 > `-- UNMET DEPENDENCY parser@^0.1.4 -bash: --: command not found -bash: --: command not found iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ npm ERR! missing: parser@^0.1.4, required by iobroker.javascript@4.1.1Hier die Ausgabe :(
Systeminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
@Thomas-Braun
Habe eus neu aufgesetzt und das Backup eingespielt :(iobroker@iobroker2:/opt/iobroker$ sudo npm ls parser iobroker.inst@2.0.3 /opt/iobroker `-- iobroker.javascript@4.1.12 `-- UNMET DEPENDENCY parser@^0.1.4 npm ERR! missing: parser@^0.1.4, required by iobroker.javascript@4.1.12 iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ sudo npm ls parser -bash: iobroker@iobroker2:/opt/iobroker$: No such file or directory iobroker@iobroker2:/opt/iobroker$ iobroker.inst@2.0.3 /opt/iobroker -bash: iobroker.inst@2.0.3: command not found iobroker@iobroker2:/opt/iobroker$ `-- iobroker.javascript@4.1.12 > `-- UNMET DEPENDENCY parser@^0.1.4 -bash: --: command not found -bash: --: command not found iobroker@iobroker2:/opt/iobroker$ iobroker@iobroker2:/opt/iobroker$ npm ERR! missing: parser@^0.1.4, required by iobroker.javascript@4.1.1Hier die Ausgabe :(
@dali3
npm-Befehle nicht mit sudo ausführen!iobroker fixDanach
iobroker update iobroker upgrademal probieren. Wird aber vermutlich auf die gleiche Meldung laufen.
Bei mir ist parser jedenfalls keine dependency von iobroker.javascript:
├─┬ iobroker.javascript@4.6.26 │ ├── @iobroker/adapter-core@2.4.0 deduped │ ├── @types/node@14.6.1 │ ├─┬ @types/request@2.48.5 │ │ ├── @types/caseless@0.12.2 │ │ ├── @types/node@14.6.1 │ │ ├── @types/tough-cookie@4.0.0 │ │ └─┬ form-data@2.5.1 │ │ ├── asynckit@0.4.0 deduped │ │ ├── combined-stream@1.0.8 deduped │ │ └── mime-types@2.1.27 dedupedIst nodeJS bei dir sauber?
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs -
@dali3
npm-Befehle nicht mit sudo ausführen!iobroker fixDanach
iobroker update iobroker upgrademal probieren. Wird aber vermutlich auf die gleiche Meldung laufen.
Bei mir ist parser jedenfalls keine dependency von iobroker.javascript:
├─┬ iobroker.javascript@4.6.26 │ ├── @iobroker/adapter-core@2.4.0 deduped │ ├── @types/node@14.6.1 │ ├─┬ @types/request@2.48.5 │ │ ├── @types/caseless@0.12.2 │ │ ├── @types/node@14.6.1 │ │ ├── @types/tough-cookie@4.0.0 │ │ └─┬ form-data@2.5.1 │ │ ├── asynckit@0.4.0 deduped │ │ ├── combined-stream@1.0.8 deduped │ │ └── mime-types@2.1.27 dedupedIst nodeJS bei dir sauber?
which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejsIobroker fix hab ich schon probiert:
========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================genau beim update/upgrade erhalte ich die gleich fehlermeldung :(
npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"10.22.0","npm":"6.14.6"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.6","node":"10.22.0"}hier die Version:
iobroker@iobroker2:/opt/iobroker$ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs /usr/bin/nodejs v10.22.0 /usr/bin/node v10.22.0 /usr/bin/npm 6.14.6 nodejs: Installed: 10.22.0-1nodesource1 Candidate: 10.22.0-1nodesource1 Version table: *** 10.22.0-1nodesource1 500 500 https://deb.nodesource.com/node_10.x buster/main amd64 Packages 100 /var/lib/dpkg/status 10.21.0~dfsg-1~deb10u1 500 500 http://ftp.debian.org/debian buster/main amd64 Packages 500 http://security.debian.org buster/updates/main amd64 PackagesDanke dir für die Unterstützung! :)
Systeminfo:
Iobroker Pro, Surface 3 (Mobil), Acer T272 (Wand), Raspberry Pi 3, NUC, Synology DS212j (BackUp), Google Home, Xiaomi Aqara (Sensoren, Fühler, Kamera, LED), Revo Superconnect, Philips Hue, IKEA Tradfri... -
Iobroker fix hab ich schon probiert:
========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================genau beim update/upgrade erhalte ich die gleich fehlermeldung :(
npm ERR! code ENOTSUP npm ERR! notsup Unsupported engine for parser@0.1.4: wanted: {"node":"0.4-0.9"} (current: {"node":"10.22.0","npm":"6.14.6"}) npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Not compatible with your version of node/npm: parser@0.1.4 npm ERR! notsup Required: {"node":"0.4-0.9"} npm ERR! notsup Actual: {"npm":"6.14.6","node":"10.22.0"}hier die Version:
iobroker@iobroker2:/opt/iobroker$ which nodejs && nodejs -v && which node && node -v && which npm && npm -v && apt policy nodejs /usr/bin/nodejs v10.22.0 /usr/bin/node v10.22.0 /usr/bin/npm 6.14.6 nodejs: Installed: 10.22.0-1nodesource1 Candidate: 10.22.0-1nodesource1 Version table: *** 10.22.0-1nodesource1 500 500 https://deb.nodesource.com/node_10.x buster/main amd64 Packages 100 /var/lib/dpkg/status 10.21.0~dfsg-1~deb10u1 500 500 http://ftp.debian.org/debian buster/main amd64 Packages 500 http://security.debian.org buster/updates/main amd64 PackagesDanke dir für die Unterstützung! :)
@dali3
Zunächst würde ich node auf die Version 12 heben.
Danncd /opt/iobroker sudo -H -u iobroker npm install iobroker.js-controller
856
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge