@apollon77
Ich hatte das gleiche Problem und habe mitgelesen 
Nach "npm install iobroker.js-controller@3.0.20" funktioniert bei mir wieder alles.
Vielen Dank!
C
Best posts made by ChristianS
-
RE: [gelöst] js-controller 3.0.19 upgrade Fehler - Iobroker totposted in ioBroker Allgemein
Latest posts made by ChristianS
-
RE: Test Adapter Vaillant multiMatic/senso und myVaillantposted in Tester
Hallo zusammen,
gestern das "myVaillant Connect" Modul installiert und die Vaillant App installiert....das sieht schonmal gut aus.
Dann bin ich auf diesen Adapter gestoßen, weil ich die Daten natürlich gerne auch im iobroker hätte.
Installation problemlos, Daten kommen an....vielen Dank @tombox für den Adapter!!!!Mag vielleicht jemand seine VIS für die Heizung teilen für ein paar Inspirationen?
@lesiflo Deine gefällt mir zum Beispiel sehr gut.Viele Grüße,
Christian -
RE: js-controller 3.2 jetzt im Latest!posted in ioBroker Allgemein
Aber das manuelle Löschen hat wirklich geholfen.
Ich musste folgende Files aus dem Verzeichnis /opt/iobroker/node_modules/iobroker.js-controller/node_modules/.bin/ löschen:iobroker
mime
mkdirp
semverDanach lief die Installation durch:
pi@ioBroker-Pi:/opt/iobroker $ iobroker upgrade self Update js-controller from @3.1.6 to @3.2.16 NPM version: 6.14.4 npm install iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call) Starting node restart.jsiobroker ließ sich starten und ....
pi@ioBroker-Pi:/opt/iobroker $ iobroker version 3.2.16Danke Euch für die Unterstützung!
Viele Grüße,
Christian -
RE: js-controller 3.2 jetzt im Latest!posted in ioBroker Allgemein
Leider ändert es nichts, wenn ich das Ganze aus dem /opt/iobroker Verzeichnis heraus mache.
Erstmal "normal":
pi@ioBroker-Pi:/opt/iobroker $ iobroker upgrade self Update js-controller from @3.1.6 to @3.2.16 NPM version: 6.14.4 npm install iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-26T21_24_38_839Z-debug.log Starting node restart.jsDann fix.sh inkl. nächstem Versuch:
pi@ioBroker-Pi:/opt/iobroker $ curl -sL https://iobroker.net/fix.sh | bash - library: loaded Library version=2021-01-23 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2020-12-07 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/3) ========================================================================== OK:1 http://archive.raspberrypi.org/debian stretch InRelease OK:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease OK:3 https://deb.nodesource.com/node_10.x stretch InRelease Paketlisten werden gelesen... Fertig Installed gcc-c++ ========================================================================== Checking ioBroker user and directory permissions (2/3) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Checking autostart (3/3) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@ioBroker-Pi:/opt/iobroker $ pi@ioBroker-Pi:/opt/iobroker $ pi@ioBroker-Pi:/opt/iobroker $ pi@ioBroker-Pi:/opt/iobroker $ iobroker upgrade self Update js-controller from @3.1.6 to @3.2.16 NPM version: 6.14.4 npm install iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefix "/opt/iobroker" (System call) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-26T21_28_21_744Z-debug.log Starting node restart.jsUnd dann noch "mit "sudo -H -u iobroker npm install iobroker.js-controller"
pi@ioBroker-Pi:/opt/iobroker $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-26T21_30_13_878Z-debug.logVersuche das jetzt mal mit dem manuellen Löschen, wie @Thomas-Braun gesagt hat.
Viele Grüße,
Christian -
RE: js-controller 3.2 jetzt im Latest!posted in ioBroker Allgemein
Hallo zusammen,
leider klappt mein Update von 3.1.6 auf 3.2.16 nicht.
Hab´s ausprobiert, wie beschrieben, aber auch nach dem fix funktioniert es genaus wenig wie mit "sudo -H -u iobroker npm install iobroker.js-controller":pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ curl -sL https://iobroker.net/f ix.sh | bash - library: loaded Library version=2021-01-23 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2020-12-07 You might need to enter your password a couple of times. ========================================================================== ========================================================================== Installing prerequisites (1/3) ========================================================================== Holen:1 http://archive.raspberrypi.org/debian stretch InRelease [25,3 kB] Holen:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease [15,0 kB] Holen:3 http://archive.raspberrypi.org/debian stretch/main armhf Packages [192 k B] Holen:4 http://archive.raspberrypi.org/debian stretch/ui armhf Packages [44,6 kB ] Holen:5 https://deb.nodesource.com/node_10.x stretch InRelease [4.585 B] Holen:6 http://mirrordirector.raspbian.org/raspbian stretch/main armhf Packages [11,7 MB] Holen:7 https://deb.nodesource.com/node_10.x stretch/main armhf Packages [765 B] Holen:8 http://mirrordirector.raspbian.org/raspbian stretch/non-free armhf Packa ges [98,9 kB] Es wurden 12,0 MB in 15 s geholt (766 kB/s). Paketlisten werden gelesen... Fertig Installed gcc-c++ Installed libcairo2-dev Installed libpango1.0-dev Installed libjpeg-dev Installed libgif-dev Installed librsvg2-dev ========================================================================== Checking ioBroker user and directory permissions (2/3) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Checking autostart (3/3) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ========================================================================== pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ iobroker upgrade self Update js-controller from @3.1.6 to @3.2.16 NPM version: 6.14.4 npm install iobroker.js-controller@3.2.16 --loglevel error --unsafe-perm --prefi x "/opt/iobroker" (System call) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-25T19_56_16_277Z-debug.log Starting node restart.js pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-25T19_58_22_934Z-debug.log pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $"Lösche" ich /opt/iobroker/node_modules/.bin/iobroker, kommt dann die Fehlermeldung:
pi@ioBroker-Pi:/opt/iobroker/node_modules/.bin $ sudo -H -u iobroker npm install iobroker.js-controller npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.3.1 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.3.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/iobroker.js-controller/node_modules/.bin/semver npm ERR! Refusing to delete /opt/iobroker/node_modules/iobroker.js-controller/node_modules/.bin/semver: is outside /opt/iobroker/node_modules/iobroker.js-controller/node_modules/semver and not a link npm ERR! File exists: /opt/iobroker/node_modules/iobroker.js-controller/node_modules/.bin/semver npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2021-03-25T20_09_00_166Z-debug.logHat jemand eine Idee? Was kann ich ausprobieren?
Viele Grüße und danke im Voraus,
Christian -
RE: [Vorlage] Generisches Fensteroffenskript + Visposted in JavaScript
@pittini
Was für ein supertolles Skript! Vielen Dank!
Hätte ich das früher gefunden, wären mir viele erfolglose Skriptversuche erspart gebliebenEine Frage hätte ich allerdings:
Kann man die Sprachnachrichten auch irgendwie gleichzeitig an mehrere Alexas schicken?Viele Grüße,
Christian -
RE: [gelöst] js-controller 3.0.19 upgrade Fehler - Iobroker totposted in ioBroker Allgemein
@apollon77
Ich hatte das gleiche Problem und habe mitgelesen
Nach "npm install iobroker.js-controller@3.0.20" funktioniert bei mir wieder alles.Vielen Dank!
-
RE: Update js-controller 1.5.14 auf 2.2.9 schlägt fehlposted in ioBroker Allgemein
Danke für die Hinweise.
Nach ein paar erfolglosen Versuchen habe ich mich für die Variante "Backup, Neuinstallation, Restore" von @wendy2702 entschieden.
Hat soweit funktioniert. Bin nun auf 2.2.9 und alle Adapter sind up to date.Aus irgendeinem Grund fehlen in meiner VIS nun einzelne Elemente, z.B. das Menü.
Aber das bekomme ich auch noch hin. Zur Not fahre ich das alte System nochmal hoch und exportiere die VIS da....müsste doch hoffentlich funktionieren.Danke nochmal und einen schönen Abend!
-
RE: Update js-controller 1.5.14 auf 2.2.9 schlägt fehlposted in ioBroker Allgemein
Danke!
Hab´s ausgeführt:
root@ioBroker-Pi:/opt/iobroker# curl -sL https://iobroker.net/fix.sh | bash - library: loaded Library version=2020-01-30 ========================================================================== Welcome to the ioBroker installation fixer! Script version: 2020-01-25 ========================================================================== ========================================================================== Installing prerequisites (1/3) ========================================================================== OK:1 http://archive.raspberrypi.org/debian stretch InRelease Holen:2 http://mirrordirector.raspbian.org/raspbian stretch InRelease [15,0 kB] OK:3 https://deb.nodesource.com/node_10.x stretch InRelease Es wurden 15,0 kB in 3 s geholt (4.608 B/s). Paketlisten werden gelesen... Fertig Installed gcc-c++ ========================================================================== Checking ioBroker user and directory permissions (2/3) ========================================================================== Created /etc/sudoers.d/iobroker Fixing directory permissions... ========================================================================== Checking autostart (3/3) ========================================================================== Enabling autostart... Autostart enabled! ========================================================================== Your installation was fixed successfully Run iobroker start to start ioBroker again! ==========================================================================Aber das Upgrade klappt trotzdem nicht:
root@ioBroker-Pi:/opt/iobroker# iobroker upgrade self Update js-controller from @1.5.14 to @2.2.9 NPM version: 6.13.4 npm install iobroker.js-controller@2.2.9 --unsafe-perm --production --save --prefix "/opt/iobroker" (System call) npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.4 (node_modules/iobroker.info/node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/node-gyp/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/request/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/request/node_modules/http-signature/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/npmlog/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/rc/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/request/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/request/node_modules/http-signature/package.json' npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-04-06T12_19_22_412Z-debug.log Host "ioBroker-Pi" (linux) updated Execute: chmod -R 777 /opt/iobroker Chmod finished. Restart controller Starting node restart.jsopen Request’s Past, Present and Future #3142
-
RE: Update js-controller 1.5.14 auf 2.2.9 schlägt fehlposted in ioBroker Allgemein
Hallo!
Vorab: Ich habe meine iobroker Installation vor etwa 3-3,5 Jahren durchgeführt, eine VIS erstellt und seitdem nur noch ab und zu ein paar Updates gemacht. Will sagen: Ich kenne mich nicht wirklich aus.
Ich stehe nun genau vor dem gleichen Problem, also dass das Update von 1.5.14 auf 2.2.9 fehlschlägt.
Insofern war ich sehr dankbar für diese tolle Anleitung. Leider funktioniert sie für mich an zwei Stellen nicht.- Ich habe anscheinend schon eine npm Version 6.11.3 installiert.
Beim npm Update passiert das hier:
root@ioBroker-Pi:/opt/iobroker# npm cache clean -f npm WARN using --force I sure hope you know what you are doing. ╭────────────────────────────────────────────────────────────────╮ │ │ │ New minor version of npm available! 6.11.3 → 6.14.1 │ │ Changelog: https://github.com/npm/cli/releases/tag/v6.14.1 │ │ Run npm install -g npm to update! │ │ │ ╰────────────────────────────────────────────────────────────────╯ root@ioBroker-Pi:/opt/iobroker# npm update npm -g npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/bin-links npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/chownr npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/deep-extend npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/env-paths npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/get-caller-file npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/glob npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/hosted-git-info npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/invert-kv npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/is-ci npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/is-retry-allowed npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/lcid npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/mimic-fn npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/minimist npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/mkdirp npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/nopt npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules/semver npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/npm-packlist npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/npm-registry-fetch npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/npm-profile npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/mem npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/os-locale npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/rc/node_modules/minimist npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/rc npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/registry-auth-token npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/rimraf npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/node-gyp npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/pacote npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/string_decoder npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/widest-line npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/yargs npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/libnpx npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/readable-stream npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/node-gyp/node_modules npm WARN checkPermissions Missing write access to /usr/lib/node_modules/npm/node_modules/rc/node_modules npm WARN checkPermissions Missing write access to /usr/lib/node_modules npm ERR! code EACCES npm ERR! syscall access npm ERR! path /usr/lib/node_modules/npm/node_modules/bin-links npm ERR! errno -13 npm ERR! Error: EACCES: permission denied, access '/usr/lib/node_modules/npm/node_modules/bin-links' npm ERR! { [Error: EACCES: permission denied, access '/usr/lib/node_modules/npm/node_modules/bin-links'] npm ERR! stack: npm ERR! 'Error: EACCES: permission denied, access \'/usr/lib/node_modules/npm/node_modules/bin-links\'', npm ERR! errno: -13, npm ERR! code: 'EACCES', npm ERR! syscall: 'access', npm ERR! path: '/usr/lib/node_modules/npm/node_modules/bin-links' } npm ERR! npm ERR! The operation was rejected by your operating system. npm ERR! It is likely you do not have the permissions to access this file as the current user npm ERR! npm ERR! If you believe this might be a permissions issue, please double-check the npm ERR! permissions of the file and its containing directories, or try running npm ERR! the command again as root/Administrator. npm ERR! A complete log of this run can be found in: npm ERR! /home/iobroker/.npm/_logs/2020-04-06T10_56_40_179Z-debug.log- Dann dachte ich....ach egal, 6.11.3 liegt ja recht nahe an den hier genannten 6.13.7, also weiter im Text....aber beim "iobroker upgrade self" passiert das hier:
root@ioBroker-Pi:/opt/iobroker# iobroker upgrade self Update js-controller from @1.5.14 to @2.2.9 NPM version: 6.13.4 npm install iobroker.js-controller@2.2.9 --unsafe-perm --production --save --prefix "/opt/iobroker" (System call) npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142 npm WARN deprecated json3@3.3.2: Please use the native JSON object instead of JSON 3 npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@~2.1.2 (node_modules/chokidar/node_modules/fsevents): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.2: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN optional SKIPPING OPTIONAL DEPENDENCY: osx-temperature-sensor@^1.0.4 (node_modules/iobroker.info/node_modules/osx-temperature-sensor): npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for osx-temperature-sensor@1.0.5: wanted {"os":"darwin","arch":"any"} (current: {"os":"linux","arch":"arm"}) npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/node-gyp/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/request/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/npm/node_modules/request/node_modules/http-signature/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/npmlog/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/rc/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/request/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/npmlog/node_modules/gauge/package.json' npm WARN enoent ENOENT: no such file or directory, open '/opt/iobroker/node_modules/serialport/node_modules/node-pre-gyp/node_modules/request/node_modules/http-signature/package.json' npm ERR! code EEXIST npm ERR! path /opt/iobroker/node_modules/.bin/iobroker npm ERR! Refusing to delete /opt/iobroker/node_modules/.bin/iobroker: is outside /opt/iobroker/node_modules/iobroker.js-controller and not a link npm ERR! File exists: /opt/iobroker/node_modules/.bin/iobroker npm ERR! Remove the existing file and try again, or run npm npm ERR! with --force to overwrite files recklessly. npm ERR! A complete log of this run can be found in: npm ERR! /root/.npm/_logs/2020-04-06T11_03_26_164Z-debug.log Host "ioBroker-Pi" (linux) updated Execute: chmod -R 777 /opt/iobroker Chmod finished. Restart controller Starting node restart.js root@ioBroker-Pi:/opt/iobroker#Nach Reboot ist die Version immer noch bei 1.5.14 und ich habe überhaupt keine Idee, was ich machen muss.
Vielleicht hat jemand einen Tipp für mich? Ich wäre sehr dankbar!Viele Grüße,
Christianopen Request’s Past, Present and Future #3142
- Ich habe anscheinend schon eine npm Version 6.11.3 installiert.
