@rubi007 said in Update js-controller @2.1.0 to @3.1.4 nix geht mehr:
Rechner neu gestattet und nichts geht mehr... kann mir vielleicht jemand weiterhelfen?
Sorry, leider kann ich auch nicht weiterhelfen. Aber auch bei mir gibt es ein ähnliches Fehlerbild.
Vielleicht hilft es ja einem iobroker Kenner der hier evtl. mit liest bei der Lösung des Problems,
wenn ich die Symptome die bei mir auftraten schildere.
Ausgangspunkt: iobroker Installation unter Windows 10 durchgeführt im Dezember 2019 mit Windows Installer 1.5.14b
Sämtliche default-Aktualisierungen der Adapter durchgeführt, letzter Stand des js-controllers 2.2.10
Plötzlich am 04.06.2020 kein Zugriff mehr auf den iobroker Admin möglich.
Da keine der üblichen unter https://www.iobroker.net/docu/index-26.htm?page_id=3928&lang=de beschriebenen Maßnahmen Erfolg brachten:
De-Installation und Neu-Installation mit Verwendung einer iobroker-data vom Februar 2020 (das aktuelle iobroker-data wurde vom Installer nicht akzeptiert "Es wurde keine Instanz des Admin-Adapters mit der Nummer 0 oder 1 gefunden" - Abbruch) unter Windows 10 durchgeführt mit Windows Installer 2.1.0b
iobroker restore
mit dem letzt-verfügbaren iobroker backup und
iobroker upgrade self
Gleiches Ergebnis wie bei Dir - kein Zugriff auf die Admin-Seite;
netstat -n -a -p TCP
ergab, dass Port 8081 nicht auf 0.0.0.0 gebunden wurde.
Nach mehreren vergeblichen Versuchen, die dazu führten, dass ich jetzt etliche ungenügend entfernte
wenn auch deaktivierte iobroker Dienste-Leichen in der Registry habe, ist es mir jetzt gelungen das System wieder ans Laufen zu bringen.
Das Vorgehen war wie eben beschrieben; mit dem Unterschied dass ich statt
iobroker upgrade self
mittels
npm install iobroker.js-controller@2.2.10
eine ältere Version statt 3.1.4 installiert habe.
Da die Installation aber weiterhin mit Fehlern durchlief habe ich dann noch
npm install
hinterher geschoben, was aber ebenfalls Fehler geworfen hat.
Spoiler
C:\Program Files\SmartHome4>iobroker stop
2020-06-07 23:18:34,121 INFO - Stopping the service with id 'iobroker(SmartHome4)'
C:\Program Files\SmartHome4>npm install iobroker.js-controller@2.2.10
> iobroker.js-controller@2.2.10 preinstall C:\Program Files\SmartHome4\node_modules\iobroker.js-controller
> node lib/preinstallCheck.js
NPM version: 6.11.3
> unix-dgram@2.0.3 install C:\Program Files\SmartHome4\node_modules\unix-dgram
> node-gyp rebuild
C:\Program Files\SmartHome4\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
unix_dgram.cc
win_delay_load_hook.cc
c:\program files\smarthome4\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": No such file or directory [C:\Pr
ogram Files\SmartHome4\node_modules\unix-dgram\build\unix_dgram.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:193:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Windows_NT 10.0.18363
gyp ERR! command "C:\\Program Files\\SmartHome4\\nodejs\\node.exe" "C:\\Program Files\\SmartHome4\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Program Files\SmartHome4\node_modules\unix-dgram
gyp ERR! node -v v10.17.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
> iobroker.js-controller@2.2.10 install C:\Program Files\SmartHome4\node_modules\iobroker.js-controller
> node iobroker.js setup first
The following notifications happened during sync:
- Ignoring Directory "tr-064.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "vis-lcars.admin" because officially not created as meta object. Please remove directory!
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.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 (node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
+ iobroker.js-controller@2.2.10
removed 136 packages, updated 1 package and audited 608 packages in 57.385s
found 35 vulnerabilities (32 low, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
C:\Program Files\SmartHome4>iobroker start all
C:\Program Files\SmartHome4>iobroker status
iobroker is not running on this host.
No iobroker host is running.
Objects type: file
States type: file
C:\Program Files\SmartHome4>iobroker start
2020-06-07 23:21:09,357 INFO - Starting the service with id 'iobroker(SmartHome4)'
C:\Program Files\SmartHome4>iobroker status
iobroker is running on this host.
At least one iobroker host is running.
Objects type: file
States type: file
C:\Program Files\SmartHome4>
C:\Program Files\SmartHome4>iobroker stop
2020-06-07 23:24:51,590 INFO - Stopping the service with id 'iobroker(SmartHome4)'
C:\Program Files\SmartHome4>npm install
> unix-dgram@2.0.3 install C:\Program Files\SmartHome4\node_modules\unix-dgram
> node-gyp rebuild
C:\Program Files\SmartHome4\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
unix_dgram.cc
win_delay_load_hook.cc
c:\program files\smarthome4\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": No such file or directory [C:\Pr
ogram Files\SmartHome4\node_modules\unix-dgram\build\unix_dgram.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:193:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Windows_NT 10.0.18363
gyp ERR! command "C:\\Program Files\\SmartHome4\\nodejs\\node.exe" "C:\\Program Files\\SmartHome4\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Program Files\SmartHome4\node_modules\unix-dgram
gyp ERR! node -v v10.17.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
> iobroker.inst@2.0.3 install C:\Program Files\SmartHome4
> node lib/checkVersions.js
NPM version: 6.11.3
> iobroker.inst@2.0.3 postinstall C:\Program Files\SmartHome4
> node lib/install.js
Write "iobroker start" to start the ioBroker
npm install node-windows@0.1.14 --production --save --prefix "C:/Program Files/SmartHome4"
> iobroker.js-controller@2.2.10 preinstall C:\Program Files\SmartHome4\node_modules\iobroker.js-controller
> node lib/preinstallCheck.js
NPM version: 6.11.3
C:\Program Files\SmartHome4\cert-info -> C:\Program Files\SmartHome4\node_modules\cert-info\bin\cert-info.js
C:\Program Files\SmartHome4\eckles -> C:\Program Files\SmartHome4\node_modules\eckles\bin\eckles.js
C:\Program Files\SmartHome4\mkdirp -> C:\Program Files\SmartHome4\node_modules\mkdirp\bin\cmd.js
C:\Program Files\SmartHome4\ncp -> C:\Program Files\SmartHome4\node_modules\ncp\bin\ncp
C:\Program Files\SmartHome4\rasha -> C:\Program Files\SmartHome4\node_modules\rasha\bin\rasha.js
C:\Program Files\SmartHome4\keypairs-install -> C:\Program Files\SmartHome4\node_modules\keypairs\bin\keypairs.js
C:\Program Files\SmartHome4\rsa-keygen-js -> C:\Program Files\SmartHome4\node_modules\rsa-compat\bin\rsa-keygen.js
C:\Program Files\SmartHome4\semver -> C:\Program Files\SmartHome4\node_modules\semver\bin\semver
C:\Program Files\SmartHome4\sshpk-conv -> C:\Program Files\SmartHome4\node_modules\sshpk\bin\sshpk-conv
C:\Program Files\SmartHome4\sshpk-sign -> C:\Program Files\SmartHome4\node_modules\sshpk\bin\sshpk-sign
C:\Program Files\SmartHome4\sshpk-verify -> C:\Program Files\SmartHome4\node_modules\sshpk\bin\sshpk-verify
C:\Program Files\SmartHome4\uuid -> C:\Program Files\SmartHome4\node_modules\uuid\bin\uuid
C:\Program Files\SmartHome4\rimraf -> C:\Program Files\SmartHome4\node_modules\rimraf\bin.js
C:\Program Files\SmartHome4\iobroker -> C:\Program Files\SmartHome4\node_modules\iobroker.js-controller\iobroker.js
> diskusage@1.1.3 install C:\Program Files\SmartHome4\node_modules\diskusage
> node-gyp rebuild
C:\Program Files\SmartHome4\node_modules\diskusage>if not defined npm_config_node_gyp (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
main.cpp
diskusage_win.cpp
win_delay_load_hook.cc
Bibliothek "C:\Program Files\SmartHome4\node_modules\diskusage\build\Release\diskusage.lib" und Objekt "C:\Program Files\SmartHome4\node_modules\diskusage\build\Release\diskusa
ge.exp" werden erstellt.
Code wird generiert.
All 262 functions were compiled because no usable IPDB/IOBJ from previous compilation was found.
Codegenerierung ist abgeschlossen.
diskusage.vcxproj -> C:\Program Files\SmartHome4\node_modules\diskusage\build\Release\\diskusage.node
> unix-dgram@2.0.3 install C:\Program Files\SmartHome4\node_modules\unix-dgram
> node-gyp rebuild
C:\Program Files\SmartHome4\node_modules\unix-dgram>if not defined npm_config_node_gyp (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\npm-lifecycle\node-gyp-bin\\..\..\node_modules\node-gyp\bin\node-gyp.js" rebuild ) else (node "C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\bin\node-gyp.js" rebuild )
Die Projekte in dieser Projektmappe werden nacheinander erstellt. Um eine parallele Erstellung zu ermöglichen, müssen Sie den Schalter "/m" hinzufügen.
unix_dgram.cc
win_delay_load_hook.cc
c:\program files\smarthome4\node_modules\unix-dgram\src\unix_dgram.cc(9): fatal error C1083: Datei (Include) kann nicht geöffnet werden: "unistd.h": No such file or directory [C:\Pr
ogram Files\SmartHome4\node_modules\unix-dgram\build\unix_dgram.vcxproj]
gyp ERR! build error
gyp ERR! stack Error: `C:\Program Files\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
gyp ERR! stack at ChildProcess.onExit (C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:193:23)
gyp ERR! stack at ChildProcess.emit (events.js:198:13)
gyp ERR! stack at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
gyp ERR! System Windows_NT 10.0.18363
gyp ERR! command "C:\\Program Files\\SmartHome4\\nodejs\\node.exe" "C:\\Program Files\\SmartHome4\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
gyp ERR! cwd C:\Program Files\SmartHome4\node_modules\unix-dgram
gyp ERR! node -v v10.17.0
gyp ERR! node-gyp -v v5.0.3
gyp ERR! not ok
> ursa-optional@0.9.10 install C:\Program Files\SmartHome4\node_modules\ursa-optional
> node rebuild.js
> iobroker.js-controller@2.2.10 install C:\Program Files\SmartHome4\node_modules\iobroker.js-controller
> node iobroker.js setup first
The following notifications happened during sync:
- Ignoring Directory "tr-064.admin" because officially not created as meta object. Please remove directory!
- Ignoring Directory "vis-lcars.admin" because officially not created as meta object. Please remove directory!
> acme-v2@1.8.6 postinstall C:\Program Files\SmartHome4\node_modules\acme-v2
> node scripts/postinstall
Greenlock and ACME.js v3 are on the way!
Watch for updates at https://indiegogo.com/at/greenlock
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 (node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
+ node-windows@0.1.14
added 308 packages from 290 contributors in 111.007s
This service is already installed.
ioBroker service installed. Write "serviceIoBroker start" to start the service and go to http://localhost:8081 to open the admin UI.
To see the outputs do not start the service, but write "node node_modules/iobroker.js-controller/controller"
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.3 (node_modules\fsevents):
npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.3: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"ia32"})
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 (node_modules\unix-dgram):
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.3 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
removed 11 packages and audited 610 packages in 143.118s
found 35 vulnerabilities (32 low, 3 high)
run `npm audit fix` to fix them, or `npm audit` for details
C:\Program Files\SmartHome4>iobroker start
C:\Program Files\SmartHome4>node node_modules/iobroker.js-controller/iobroker.js start
Starting iobroker controller daemon...
Nichtsdestotrotz lief der iobroker admin dann wieder (mit js-controller@2.2.10) und hat brav die Adapter aktualisiert.
Einziges Manko: Bei der Installation von diversen Adaptern erzeugt er Fehler im iobroker-log:
Spoiler
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.318 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.317 info iobroker not ok
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.316 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.315 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.312 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.311 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.310 info iobroker v5.0.3
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.309 info iobroker ERR! node-gyp -v
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.308 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.305 info iobroker ERR! node -v v10.17.0
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.304 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.302 info iobroker C:\Program Files\SmartHome4\node_modules\unix-dgram
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.293 info iobroker cwd
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.291 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.286 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.285 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.284 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.282 info iobroker "C:\\Program Files\\SmartHome4\\nodejs\\node.exe" "C:\\Program Files\\SmartHome4\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.269 info iobroker command
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.268 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.267 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.267 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.266 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.265 info iobroker Windows_NT 10.0.18363
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.264 info iobroker System
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.263 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.262 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.261 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.258 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.257 info iobroker at Process.ChildProcess._handle.onexit (internal/child_process.js:248:12)
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.255 info iobroker stack
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.255 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.252 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.251 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.250 info iobroker at ChildProcess.emit (events.js:198:13)
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.249 info iobroker stack
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.248 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.247 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.246 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.245 info iobroker at ChildProcess.onExit (C:\Program Files\SmartHome4\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:193:23)gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.244 info iobroker stack
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.231 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.230 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.229 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.228 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.227 info iobroker Error: `C:\Program Files\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.225 info iobroker stack
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.222 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.221 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.220 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.215 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.214 info iobroker build error
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.212 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.209 info iobroker ERR!
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.207 info iobroker
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:51.202 info iobroker gyp
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:07.850 info iobroker npm install iobroker.info@1.7.2 --loglevel error (System call)
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:07.850 info iobroker NPM version: 6.11.3
host.Jenss-Lifebook(SmartHome) 2020-06-08 08:57:05.958 info iobroker Update info from @1.5.6 to @1.7.2
Das könnte aber evtl. mit dem in
https://forum.iobroker.net/topic/34142/fehlermeldungen-bei-updates
geschilderten Problem zusammenhängen.
Jetzt werde ich mal abwarten, ob das System weiter stabil arbeitet und den Upgrade auf js-controller 3.1.4 vermeiden, in der Hoffnung, dass die iobroker core Entwickler oder die Entwickler des Windows-Installers eine Lösung finden.
