NEWS
Lösung für Fehler: TypeError [ERR_INVALID_ARG_VALUE]
-
@thomas-braun hab unter /opt/iobroker "npm list @iobroker/adapter-core" - dort die beiden Schlingel entdeckt: telegram & spotify-premium. Wie in der Anleitung oben daher in die Verzeichnisse gewechselt:
cd /opt/iobroker/node_modules/iobroker.telegram/
bzw.
cd /opt/iobroker/node_modules/iobroker.spotify-premium/
dort jeweils ein
npm i @iobroker/adapter-core@3.1.4
ausgeführt.
Danach gecheckt:
cd /opt/iobroker/
"npm list @iobroker/adapter-core"- alles gut.
Nach reboot des Containers wieder alles krumm. Vermutlich Permissions :(
@manuxi hast du mal ein
iob fixgefahren?kein Support per PN! - Fragen im Forum stellen - es gibt fast nichts, was nicht auch für andere interessant ist.
Benutzt das Voting rechts unten im Beitrag wenn er euch geholfen hat.
der Installationsfixer: curl -fsL https://iobroker.net/fix.sh | bash -
-
@thomas-braun hab unter /opt/iobroker "npm list @iobroker/adapter-core" - dort die beiden Schlingel entdeckt: telegram & spotify-premium. Wie in der Anleitung oben daher in die Verzeichnisse gewechselt:
cd /opt/iobroker/node_modules/iobroker.telegram/
bzw.
cd /opt/iobroker/node_modules/iobroker.spotify-premium/
dort jeweils ein
npm i @iobroker/adapter-core@3.1.4
ausgeführt.
Danach gecheckt:
cd /opt/iobroker/
"npm list @iobroker/adapter-core"- alles gut.
Nach reboot des Containers wieder alles krumm. Vermutlich Permissions :(
Zeig mal konkret die vollständigen Ein- und Ausgaben aus der Konsole (in CodeTags eingebettet), keine freien Nacherzählungen.
-
@manuxi sagte in Lösung für Fehler: TypeError [ERR_INVALID_ARG_VALUE]:
@homoran nein. ist das sinnvoll?
Natürlich!
@manuxi sagte in Lösung für Fehler: TypeError [ERR_INVALID_ARG_VALUE]:
Vermutlich Permissions
die würden dadurch gefixt
-
Zeig mal konkret die vollständigen Ein- und Ausgaben aus der Konsole (in CodeTags eingebettet), keine freien Nacherzählungen.
@thomas-braun sagte in Lösung für Fehler: TypeError [ERR_INVALID_ARG_VALUE]:
Zeig mal konkret die vollständigen Ein- und Ausgaben aus der Konsole (in CodeTags eingebettet), keine freien Nacherzählungen.
Gerade schwierig, da keinen ssh-Zugriff. Aber die beiden scheinen gerade auch wieder zu Laufen. Mal schauen, was anch dem nächsten Reboot passiert.
-
@thomas-braun sagte in Lösung für Fehler: TypeError [ERR_INVALID_ARG_VALUE]:
Zeig mal konkret die vollständigen Ein- und Ausgaben aus der Konsole (in CodeTags eingebettet), keine freien Nacherzählungen.
Gerade schwierig, da keinen ssh-Zugriff. Aber die beiden scheinen gerade auch wieder zu Laufen. Mal schauen, was anch dem nächsten Reboot passiert.
Tja, ich schaue nicht jeden Tag in IoBroker rein, da wenig Zeit im Moment. Der telegram-Adapter spuckte aber die üblichen Meldungen aus, daher hab ich ihn gestern erstmal still gelegt. Mir ist allerdings nicht bewußt, dass mein iob einen Neustart hingelegt hätte. Heute dann alles noch ein weiteres mal, diesmal inkl. "iob fix":
iob fix:
root@iobroker-v9-prod:/opt/iobroker# iob fix The ioBroker fixer script is not specifically designed to run in Docker. Although it is generally safe to use, use it at your own risk and make sure to restart your container immediately after execution! Do you want to continue? [yes/no] yes library: loaded Library version=2024-01-04 ioBroker or some processes are still running: io.admin.0 [...37 weitere...] Please stop them first and try again! root@iobroker-v9-prod:/opt/iobroker# iob maintenance on You are now going to stop ioBroker and activate maintenance mode for this container. Do you want to continue [yes/no]? yes Activating maintenance mode... Stopping ioBroker............. Timeout reached. Killing remaining processes... 209 io.influxdb.0 353 io.hue.2 1925 io.trashschedule.0 18333 io.zigbee.0 Done. root@iobroker-v9-prod:/opt/iobroker# iob fix The ioBroker fixer script is not specifically designed to run in Docker. Although it is generally safe to use, use it at your own risk and make sure to restart your container immediately after execution! Do you want to continue? [yes/no] yes library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55,4 kB] Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48,0 kB] Get:4 https://deb.nodesource.com/node_18.x nodistro InRelease [12,1 kB] Get:6 http://deb.debian.org/debian bookworm-updates/main amd64 Packages.diff/Index [10,6 kB] Get:7 http://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-04-23-2036.10-F-2024-04-23-2036.10.pdiff [1.595 B] Get:7 http://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-04-23-2036.10-F-2024-04-23-2036.10.pdiff [1.595 B] Get:8 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [157 kB] Get:9 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [8.505 B] Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bookworm InRelease Fetched 293 kB in 2s (150 kB/s) Reading package lists... Done ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker sudo: unable to resolve host iobroker-v9-prod: Name or service not known sudo: unable to resolve host iobroker-v9-prod: Name or service not known Fixing directory permissions... This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing! ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! sudo: unable to resolve host iobroker-v9-prod: Name or service not known sudo: unable to resolve host iobroker-v9-prod: Name or service not known No relevant JSONL files found to compress, skip ========================================================================== Checking autostart (5/5) ========================================================================== Unsupported init system, cannot enable autostart! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Danach erstmal ein Neustart des Containers.
Fix-Versuch (sah bisher immer so aus; hab ein paar Ausgaben gekürzt mit [...]):
sudo docker exec -it a3f6715d46af /bin/bash root@iobroker-v9-prod:/opt/iobroker# npm list @iobroker/adapter-core sudo: unable to resolve host iobroker-v9-prod: Name or service not known npm ERR! code ELSPROBLEMS npm ERR! invalid: @iobroker/adapter-core@3.1.2 /opt/iobroker/node_modules/iobroker.spotify-premium/node_modules/@iobroker/adapter-core npm ERR! invalid: @iobroker/adapter-core@3.1.2 /opt/iobroker/node_modules/iobroker.telegram/node_modules/@iobroker/adapter-core iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.admin@6.13.16 │ ├── @iobroker/adapter-core@3.0.4 │ └─┬ @iobroker/socket-classes@1.5.0 │ └── @iobroker/adapter-core@3.0.4 deduped [...] ├─┬ iobroker.spotify-premium@1.4.0 │ └── @iobroker/adapter-core@3.1.2 invalid: "^3.1.4" from node_modules/iobroker.spotify-premium [...] ├─┬ iobroker.telegram@3.2.1 │ └── @iobroker/adapter-core@3.1.2 invalid: "^3.1.4" from node_modules/iobroker.telegram [...] npm ERR! A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2024-05-08T14_43_42_925Z-debug-0.log root@iobroker-v9-prod:/opt/iobroker# cd /opt/iobroker/node_modules/iobroker.telegram/ root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.telegram# npm i @iobroker/adapter-core@3.1.4 sudo: unable to resolve host iobroker-v9-prod: Name or service not known npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies 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 sinon@15.2.0: 16.1.1 added 813 packages, and changed 1 package in 54s 116 packages are looking for funding run `npm fund` for details root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.telegram# cd /opt/iobroker/node_modules/iobroker.spotify-premium/ root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.spotify-premium# npm i @iobroker/adapter-core@3.1.4 sudo: unable to resolve host iobroker-v9-prod: Name or service not known 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 sinon@15.2.0: 16.1.1 added 400 packages, and changed 1 package in 24s 65 packages are looking for funding run `npm fund` for details root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.spotify-premium# cd /opt/iobroker/ root@iobroker-v9-prod:/opt/iobroker# npm list @iobroker/adapter-core sudo: unable to resolve host iobroker-v9-prod: Name or service not known iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.admin@6.13.16 │ ├── @iobroker/adapter-core@3.0.4 │ └─┬ @iobroker/socket-classes@1.5.0 │ └── @iobroker/adapter-core@3.0.4 deduped [...] ├─┬ iobroker.spotify-premium@1.4.0 │ └── @iobroker/adapter-core@3.1.4 [...] ├─┬ iobroker.telegram@3.2.1 │ └── @iobroker/adapter-core@3.1.4 [...] root@iobroker-v9-prod:/opt/iobroker# -
Tja, ich schaue nicht jeden Tag in IoBroker rein, da wenig Zeit im Moment. Der telegram-Adapter spuckte aber die üblichen Meldungen aus, daher hab ich ihn gestern erstmal still gelegt. Mir ist allerdings nicht bewußt, dass mein iob einen Neustart hingelegt hätte. Heute dann alles noch ein weiteres mal, diesmal inkl. "iob fix":
iob fix:
root@iobroker-v9-prod:/opt/iobroker# iob fix The ioBroker fixer script is not specifically designed to run in Docker. Although it is generally safe to use, use it at your own risk and make sure to restart your container immediately after execution! Do you want to continue? [yes/no] yes library: loaded Library version=2024-01-04 ioBroker or some processes are still running: io.admin.0 [...37 weitere...] Please stop them first and try again! root@iobroker-v9-prod:/opt/iobroker# iob maintenance on You are now going to stop ioBroker and activate maintenance mode for this container. Do you want to continue [yes/no]? yes Activating maintenance mode... Stopping ioBroker............. Timeout reached. Killing remaining processes... 209 io.influxdb.0 353 io.hue.2 1925 io.trashschedule.0 18333 io.zigbee.0 Done. root@iobroker-v9-prod:/opt/iobroker# iob fix The ioBroker fixer script is not specifically designed to run in Docker. Although it is generally safe to use, use it at your own risk and make sure to restart your container immediately after execution! Do you want to continue? [yes/no] yes library: loaded Library version=2024-01-04 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2024-01-04 ========================================================================== ========================================================================== Installing prerequisites (1/5) ========================================================================== Hit:1 http://deb.debian.org/debian bookworm InRelease Get:2 http://deb.debian.org/debian bookworm-updates InRelease [55,4 kB] Get:3 http://deb.debian.org/debian-security bookworm-security InRelease [48,0 kB] Get:4 https://deb.nodesource.com/node_18.x nodistro InRelease [12,1 kB] Get:6 http://deb.debian.org/debian bookworm-updates/main amd64 Packages.diff/Index [10,6 kB] Get:7 http://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-04-23-2036.10-F-2024-04-23-2036.10.pdiff [1.595 B] Get:7 http://deb.debian.org/debian bookworm-updates/main amd64 Packages T-2024-04-23-2036.10-F-2024-04-23-2036.10.pdiff [1.595 B] Get:8 http://deb.debian.org/debian-security bookworm-security/main amd64 Packages [157 kB] Get:9 https://deb.nodesource.com/node_18.x nodistro/main amd64 Packages [8.505 B] Hit:5 https://packagecloud.io/ookla/speedtest-cli/debian bookworm InRelease Fetched 293 kB in 2s (150 kB/s) Reading package lists... Done ========================================================================== Checking ioBroker user and directory permissions (2/5) ========================================================================== Created /etc/sudoers.d/iobroker sudo: unable to resolve host iobroker-v9-prod: Name or service not known sudo: unable to resolve host iobroker-v9-prod: Name or service not known Fixing directory permissions... This system does not support setting default permissions. Do not use npm to manually install adapters unless you know what you are doing! ========================================================================== Check and cleanup npm temporary directories (3/5) ========================================================================== Done. ========================================================================== Database maintenance (4/5) ========================================================================== Checking for uncompressed JSONL databases... This might take a while! sudo: unable to resolve host iobroker-v9-prod: Name or service not known sudo: unable to resolve host iobroker-v9-prod: Name or service not known No relevant JSONL files found to compress, skip ========================================================================== Checking autostart (5/5) ========================================================================== Unsupported init system, cannot enable autostart! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Danach erstmal ein Neustart des Containers.
Fix-Versuch (sah bisher immer so aus; hab ein paar Ausgaben gekürzt mit [...]):
sudo docker exec -it a3f6715d46af /bin/bash root@iobroker-v9-prod:/opt/iobroker# npm list @iobroker/adapter-core sudo: unable to resolve host iobroker-v9-prod: Name or service not known npm ERR! code ELSPROBLEMS npm ERR! invalid: @iobroker/adapter-core@3.1.2 /opt/iobroker/node_modules/iobroker.spotify-premium/node_modules/@iobroker/adapter-core npm ERR! invalid: @iobroker/adapter-core@3.1.2 /opt/iobroker/node_modules/iobroker.telegram/node_modules/@iobroker/adapter-core iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.admin@6.13.16 │ ├── @iobroker/adapter-core@3.0.4 │ └─┬ @iobroker/socket-classes@1.5.0 │ └── @iobroker/adapter-core@3.0.4 deduped [...] ├─┬ iobroker.spotify-premium@1.4.0 │ └── @iobroker/adapter-core@3.1.2 invalid: "^3.1.4" from node_modules/iobroker.spotify-premium [...] ├─┬ iobroker.telegram@3.2.1 │ └── @iobroker/adapter-core@3.1.2 invalid: "^3.1.4" from node_modules/iobroker.telegram [...] npm ERR! A complete log of this run can be found in: /opt/iobroker/.npm/_logs/2024-05-08T14_43_42_925Z-debug-0.log root@iobroker-v9-prod:/opt/iobroker# cd /opt/iobroker/node_modules/iobroker.telegram/ root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.telegram# npm i @iobroker/adapter-core@3.1.4 sudo: unable to resolve host iobroker-v9-prod: Name or service not known npm WARN deprecated source-map-url@0.4.1: See https://github.com/lydell/source-map-url#deprecated npm WARN deprecated urix@0.1.0: Please see https://github.com/lydell/urix#deprecated npm WARN deprecated har-validator@5.1.5: this library is no longer supported npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated npm WARN deprecated source-map-resolve@0.5.3: See https://github.com/lydell/source-map-resolve#deprecated npm WARN deprecated chokidar@2.1.8: Chokidar 2 does not receive security updates since 2019. Upgrade to chokidar 3 with 15x fewer dependencies 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 sinon@15.2.0: 16.1.1 added 813 packages, and changed 1 package in 54s 116 packages are looking for funding run `npm fund` for details root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.telegram# cd /opt/iobroker/node_modules/iobroker.spotify-premium/ root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.spotify-premium# npm i @iobroker/adapter-core@3.1.4 sudo: unable to resolve host iobroker-v9-prod: Name or service not known 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 sinon@15.2.0: 16.1.1 added 400 packages, and changed 1 package in 24s 65 packages are looking for funding run `npm fund` for details root@iobroker-v9-prod:/opt/iobroker/node_modules/iobroker.spotify-premium# cd /opt/iobroker/ root@iobroker-v9-prod:/opt/iobroker# npm list @iobroker/adapter-core sudo: unable to resolve host iobroker-v9-prod: Name or service not known iobroker.inst@3.0.0 /opt/iobroker ├─┬ iobroker.admin@6.13.16 │ ├── @iobroker/adapter-core@3.0.4 │ └─┬ @iobroker/socket-classes@1.5.0 │ └── @iobroker/adapter-core@3.0.4 deduped [...] ├─┬ iobroker.spotify-premium@1.4.0 │ └── @iobroker/adapter-core@3.1.4 [...] ├─┬ iobroker.telegram@3.2.1 │ └── @iobroker/adapter-core@3.1.4 [...] root@iobroker-v9-prod:/opt/iobroker# -
Der Fehler ERR_INVALID_ARG_VALUE ist leider wieder da bei beiden Adaptern. Ich weiß von keinem Neustart.
Jemand eine Idee?
-
Ist bei mir auch wieder da. Zigbee.0 Instanz, Zigbee Adapter.
├─┬ iobroker.ws@2.6.1 │ └── @iobroker/adapter-core@3.1.4 ├─┬ iobroker.zigbee@1.10.3 │ ├── @iobroker/adapter-core@3.1.2 invalid: "^3.1.4" from node_modules/iobroker.zigbee │ └─┬ @iobroker/dm-utils@0.1.9 │ └── @iobroker/adapter-core@3.0.4 └─┬ iobroker.zwave2@3.1.0 └── @iobroker/adapter-core@2.6.8 deduped npm ERR! A complete log of this run can be found in: /home/iobroker/.npm/_logs/2024-06-01T09_01_46_582Z-debug-0.logHabe es mit der MEthode im Eingangspost natürlich beheben können aber es nervt schon wenn der Fehler immer wieder kommt. Gestern hatte ich den Server heruntergefahren und ein Backup vom System gemacht. Warum jetzt wieder 3.1.2 installiert wurde? Keine Ahnung.
-
Ich möchte gerne noch einmal das Thema hochholen, da ich den Workaround ständig neu machen muss wenn ich meinen Server neustarte. Wie kann ich dies dauerhaft korrigieren? Bei mir ist nach wie vor zigbee.0 betroffen
Mir würde auch helfen zu verstehen warum adapter-core 3.1.2 in der fehlerhaften Fassung immer wieder aufs neue verwendet wird? -
Ich möchte gerne noch einmal das Thema hochholen, da ich den Workaround ständig neu machen muss wenn ich meinen Server neustarte. Wie kann ich dies dauerhaft korrigieren? Bei mir ist nach wie vor zigbee.0 betroffen
Mir würde auch helfen zu verstehen warum adapter-core 3.1.2 in der fehlerhaften Fassung immer wieder aufs neue verwendet wird?@matzeit
Falls das Problem in Zusammenhang mit js-controller 6 in der stable 6.0.9 auftritt thematisiere das bitte um Topic https://forum.iobroker.net/topic/76153/js-controller-6-0-x-jetzt-für-alle-user-im-stable. Paralleldiskussionen bringen wenig und Foxriver ist im genannten Topic sehr present.Ansonsten aktualisisere zunächst auf 6.0.9.
252
Online32.4k
Benutzer81.4k
Themen1.3m
Beiträge