js-controller läßt sich nicht mehr stoppen (Windows)

[JBSullivan]

Wollte gerade den js-controller auf 3.3.5 hochziehen und musste leider feststellen, das sich iobroker unter WINDOWS nicht mehr stoppen lässt.

Der Windows Dienst sagt zwar, das der Controller aus ist, aber über "iobroker status" bekommt man die Meldung, das er noch läuft.

"iobroker stop" liefert die folgende Fehlermeldung.

Irgend eine Idee wie ich jetzt auf die Version 3.3.5 komme - oder besser noch zurück auf eine 3.2.x (wegen der ganzen Fehlermeldungen im LOG)

C:\iobroker\GLT>iobroker status
iobroker is running on this host.

Objects type: file
States  type: file

C:\iobroker\GLT>iobroker stop
2021-05-01 21:30:20,605 INFO  - Stopping the service with id 'iobroker(GLT)'
2021-05-01 21:30:20,664 FATAL - WMI Operation failure: ServiceCannotAcceptControl
WMI.WmiException: ServiceCannotAcceptControl
   bei WMI.WmiRoot.BaseHandler.CheckError(ManagementBaseObject result)
   bei WMI.WmiRoot.InstanceHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
   bei winsw.WrapperService.Run(String[] _args, ServiceDescriptor descriptor)
   bei winsw.WrapperService.Main(String[] args)
WMI.WmiException: ServiceCannotAcceptControl
   bei WMI.WmiRoot.BaseHandler.CheckError(ManagementBaseObject result)
   bei WMI.WmiRoot.InstanceHandler.Invoke(Object proxy, MethodInfo method, Object[] args)
   bei winsw.WrapperService.Run(String[] _args, ServiceDescriptor descriptor)
   bei winsw.WrapperService.Main(String[] args)

C:\iobroker\GLT>

[Apollon77]

Hattest DU das schon bei früheren Updates?

Bitte schau mal ob du ihn nach einem reboot stoppen kannst normal? und ob dann update geht

Bisher wurden bezüglich WIndows keine Probleme gemeldet.

[JBSullivan]

Nein, noch nie Probleme bei einem js-controller update gehabt, seit der Verwendung des Workarounds von @AlCalzone (löschen der node Module bei Update Versuchen)

Folgendes Szenario - ioBroker Windows Dienst gestoppt und PC neu gestartet.

ioBroker fährt nach Neustart im Hintergrund OHNE Anzeige in den Windows Diensten wieder hoch und ist Aktiv

In der Win Dienste Verwaltung wird er aber als nicht gestartet angezigt.

Nach dem Reboot läßt sich ioB aber über die Konsole stoppen aber NICHT aktualisieren (siehe unten).

Wie war nochmal der Konsolen Aufruf wenn ich den js-controller downgraden möchte?

`

C:\iobroker\GLT>iobroker upgrade self

  | Update js-controller from @3.3.4 to @3.3.5   | NPM version: 6.14.11   | npm install iobroker.js-controller@3.3.5 --loglevel error --unsafe-perm (System call)   | Trying to install "esbuild-windows-64" using npm   | Failed to install "esbuild-windows-64" using npm: Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false esbuild-windows-64@0.11.17   | npm ERR! code ETARGET   | npm ERR! notarget No matching version found for esbuild-windows-64@0.11.17.   | npm ERR! notarget In most cases you or one of your dependencies are requesting   | npm ERR! notarget a package version that doesn't exist.   | {1}   | npm ERR! A complete log of this run can be found in:   | npm ERR! C:\iobroker\GLT\env\npm-cache_logs\2021-05-01T19_56_28_311Z-debug.log   | {1}   | Trying to download "https://registry.npmjs.org/esbuild-windows-64/-/esbuild-windows-64-0.11.17.tgz"   | Install successful   | {1}

`

EDIT: Er hat sich upgedatet - bin auf die Error Meldungen reingefallen. Allerdings hat sich der js-controller nach dem upgrade nicht selbstständing gestartet - das hat er früher immer gemacht.

Man kann ihn unter 3.3.5 auch wieder über die Win Dienste Verwaltung, als auch über die Konsole beenden und starten .

[Apollon77]

Ok, also mit 3.3.5 wieder alles gut??

[Stabilostick]

Würde mich auch interessieren.

Erkannt wird ja in der Windows Dienststeuerung nicht der ioBroker-Node-ChildProzess sondern vielmehr der Wrapper-Service, der Node dann hostet. Der Service hat übrigens in seinem Ordner auch log-Dateien. Was stand denn da drinnen?

Der WMI-Fehler im ersten Beitrag kommt z.B. wenn Du den ioBroker-Dienst stoppst, obwohl er gar nicht läuft. (WMI Operation failure: ServiceCannotAcceptControl). Oder Du hast zu geringe Rechte gehabt.

[JBSullivan]

Der Service hat übrigens in seinem Ordner auch log-Dateien. Was stand denn da drinnen?

Kannst du das genauer erklären wo ich da nach was suchen muss?

Der WMI-Fehler im ersten Beitrag kommt z.B. wenn Du den ioBroker-Dienst stoppst, obwohl er gar nicht läuft. (WMI Operation failure: ServiceCannotAcceptControl).

Das ist aber Widersprüchlich. Laut Windows läuft er nicht, lt. ioBroker läuft er. Das "iobroker stop" wirkt auf den Windows Dienst oder auf irgend etwas iobroker internes, was den Win Dienst mitnehmen sollte?

Oder Du hast zu geringe Rechte gehabt.

Nein ich habe überall unter Win Vollzugriff als Admin.

[Stabilostick]

1. Die Logs stehen im Ordner, in dem die Service Wrapper-Exe steht (also die iobroker.exe)
2. Der iobroker js-controller mit seinem Node.js-Prozess kann sowohl als als Childprozess des Service Wrappers (iobroker.exe) „als Quasi-Dienst“ - oder auch als eigenständiger Node.js-Prozess „in Kommandozeile“ laufen (in letzteren Fall macht er auch gerne mal ein oder mehrere schwarzes Fenster auf). Der laufende js-Controller sieht sich selbst, egal ob er als Dienst oder als einfacher Prozess läuft. Wenn ioBroker Status sagt, dass da was läuft, dann ist das auch so. Wenn Du iobroker start/stop/restart auf der Kommandozeile eingibst, werden diese Befehle in der iobroker.bat umgeleitet in Aufrufe an die iobroker.exe zur Dienststeuerung. Der Service Wapper weiß nichts von einem in der Kommandozeile gestarteten separaten js-Controller. Anschauen kannst Du Dir das z.B. mit dem empfehlenswerten kostenlosen Tool „ProcessExplorer“ von Microsoft/Sysinternals.

[JBSullivan]

OK, hier also die *. err LOG Datei von gestern Abend als das Spielchen begann -

`Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:179:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:146:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:179:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:146:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:179:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:146:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:179:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:146:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:179:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:146:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12)

This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12) This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason: Error: DB closed at close (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:183:25) at Socket. (C:\iobroker\GLT\node_modules\ioredis\built\redis\event_handler.js:150:20) at Object.onceWrapper (events.js:422:26) at Socket.emit (events.js:315:20) at Socket.EventEmitter.emit (domain.js:467:12) at TCP. (net.js:673:12)`

[Apollon77]

DB CLosed can happen if an adapter is doing requests after the db connection was closed already. This should also be found in normal log to see whcih adapter caused it. basically: ignore

[JBSullivan]

PUH - da habe ich aber im LOG suchen müssen, das ich den Zeitlichen Zusammenhang von gestern noch hin bekommen habe.

Hiermit hat es meiner Meinung nach angefangen

2021-05-01 21:31:31.974  - info: host.GLT(GLT) iobroker.js-controller version 3.3.4 js-controller starting
2021-05-01 21:31:31.979  - info: host.GLT(GLT) Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-05-01 21:31:31.979  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.16.0
2021-05-01 21:31:31.979  - info: host.GLT(GLT) ip addresses: 2a02:8108:9440:50e4:fd70:a681:5ffd:7bb7 2a02:8108:9440:50e4:28e0:20d4:41c9:5727 2a02:8108:9440:50e4:39ff:5bfa:20cc:9168 2a02:8108:9440:50e4:9597:336f:4b33:f00d 2a02:8108:9440:50e4:c4ca:d71e:89b9:c649 2a02:8108:9440:50e4:dc3c:3ad1:d5e7:51e5 2a02:8108:9440:50e4:e581:5c75:90a5:8412 2a02:8108:9440:50e4:edee:4276:5da2:9792 fe80::fd70:a681:5ffd:7bb7 10.122.60.87 fe80::419a:e058:356:a8a8 10.8.0.1
2021-05-01 21:31:32.637  - info: host.GLT(GLT)-Server  Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-05-01 21:31:42.103  - info: host.GLT(GLT) received SIGINT
2021-05-01 21:31:42.110  - info: host.GLT(GLT) terminated. Could not reset alive status for instances

Dann ging es hier weiter - hoffe das hilft ein wenig

2021-05-01 21:43:21.878  - info: host.GLT(GLT) iobroker restart
2021-05-01 21:43:22.493  - info: host.GLT(GLT) iobroker iobroker controller daemon is not running
2021-05-01 21:43:22.496  - info: host.GLT(GLT) iobroker Starting iobroker controller daemon...
2021-05-01 21:43:22.541  - info: host.GLT(GLT) iobroker exit 0
2021-05-01 21:43:23.740  - info: host.GLT(GLT) iobroker.js-controller version 3.3.4 js-controller starting
2021-05-01 21:43:23.743  - info: host.GLT(GLT) Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-05-01 21:43:23.744  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.16.0
2021-05-01 21:43:23.744  - info: host.GLT(GLT) ip addresses: 2a02:8108:9440:50e4:fd70:a681:5ffd:7bb7 2a02:8108:9440:50e4:28e0:20d4:41c9:5727 2a02:8108:9440:50e4:39ff:5bfa:20cc:9168 2a02:8108:9440:50e4:9597:336f:4b33:f00d 2a02:8108:9440:50e4:c4ca:d71e:89b9:c649 2a02:8108:9440:50e4:dc3c:3ad1:d5e7:51e5 2a02:8108:9440:50e4:e581:5c75:90a5:8412 2a02:8108:9440:50e4:edee:4276:5da2:9792 fe80::fd70:a681:5ffd:7bb7 10.122.60.87 fe80::419a:e058:356:a8a8 10.8.0.1
2021-05-01 21:43:24.200  - info: host.GLT(GLT)-Server  Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-05-01 21:43:42.256  - error: snmp.0 (6004) [10.122.60.87] Error session.get: RequestTimedOutError: Request timed out
2021-05-01 21:43:53.765  - error: host.GLT(GLT) No connection to databases possible, restart
2021-05-01 21:43:53.769  - info: host.GLT(GLT) iobroker _restart
2021-05-01 21:43:54.235  - info: host.GLT(GLT) iobroker Starting node restart.js
2021-05-01 21:43:56.483  - info: host.GLT(GLT) iobroker.js-controller version 3.3.4 js-controller starting
2021-05-01 21:43:56.486  - info: host.GLT(GLT) Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-05-01 21:43:56.487  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.16.0
2021-05-01 21:43:56.487  - info: host.GLT(GLT) ip addresses: 2a02:8108:9440:50e4:fd70:a681:5ffd:7bb7 2a02:8108:9440:50e4:28e0:20d4:41c9:5727 2a02:8108:9440:50e4:39ff:5bfa:20cc:9168 2a02:8108:9440:50e4:9597:336f:4b33:f00d 2a02:8108:9440:50e4:c4ca:d71e:89b9:c649 2a02:8108:9440:50e4:dc3c:3ad1:d5e7:51e5 2a02:8108:9440:50e4:e581:5c75:90a5:8412 2a02:8108:9440:50e4:edee:4276:5da2:9792 fe80::fd70:a681:5ffd:7bb7 10.122.60.87 fe80::419a:e058:356:a8a8 10.8.0.1
2021-05-01 21:43:56.888  - info: host.GLT(GLT)-Server  Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-05-01 21:44:12.246  - error: snmp.0 (6004) [10.122.60.87] Error session.get: RequestTimedOutError: Request timed out
2021-05-01 21:44:23.003  - info: javascript.0 (10332) script.js.Aktiv.Sonnenverlauf: Sonne: Azimut: 308.8°
2021-05-01 21:44:23.003  - info: javascript.0 (10332) script.js.Aktiv.Sonnenverlauf: Sonne: Elevation: -8.4°
2021-05-01 21:44:23.004  - info: javascript.0 (10332) script.js.Aktiv.Sonnenverlauf: Mond: Azimut: 82.4°
2021-05-01 21:44:23.004  - info: javascript.0 (10332) script.js.Aktiv.Sonnenverlauf: Mond: Elevation: -37.4°
2021-05-01 21:44:26.504  - error: host.GLT(GLT) No connection to databases possible, restart
2021-05-01 21:44:26.508  - info: host.GLT(GLT) iobroker _restart
2021-05-01 21:44:26.976  - info: host.GLT(GLT) iobroker Starting node restart.js
2021-05-01 21:44:28.831  - info: host.GLT(GLT) iobroker.js-controller version 3.3.4 js-controller starting
2021-05-01 21:44:28.836  - info: host.GLT(GLT) Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-05-01 21:44:28.837  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.16.0
2021-05-01 21:44:28.837  - info: host.GLT(GLT) ip addresses: 2a02:8108:9440:50e4:fd70:a681:5ffd:7bb7 2a02:8108:9440:50e4:28e0:20d4:41c9:5727 2a02:8108:9440:50e4:39ff:5bfa:20cc:9168 2a02:8108:9440:50e4:9597:336f:4b33:f00d 2a02:8108:9440:50e4:c4ca:d71e:89b9:c649 2a02:8108:9440:50e4:dc3c:3ad1:d5e7:51e5 2a02:8108:9440:50e4:e581:5c75:90a5:8412 2a02:8108:9440:50e4:edee:4276:5da2:9792 fe80::fd70:a681:5ffd:7bb7 10.122.60.87 fe80::419a:e058:356:a8a8 10.8.0.1
2021-05-01 21:44:29.419  - info: host.GLT(GLT)-Server  Error inMem-objects listening on port 9001: Error: listen EADDRINUSE: address already in use 127.0.0.1:9001
2021-05-01 21:44:42.247  - error: snmp.0 (6004) [10.122.60.87] Error session.get: RequestTimedOutError: Request timed out
2021-05-01 21:44:58.857  - error: host.GLT(GLT) No connection to databases possible, restart
2021-05-01 21:44:58.861  - info: host.GLT(GLT) iobroker _restart
2021-05-01 21:44:59.720  - info: host.GLT(GLT) iobroker Starting node restart.js
2021-05-01 21:45:00.055  - info: host.GLT(GLT) instance system.adapter.daswetter.0 started with pid 14636
2021-05-01 21:45:02.425  - info: host.GLT(GLT) iobroker.js-controller version 3.3.4 js-controller starting
2021-05-01 21:45:02.431  - info: host.GLT(GLT) Copyright (c) 2014-2021 bluefox, 2014 hobbyquaker
2021-05-01 21:45:02.431  - info: host.GLT(GLT) hostname: GLT(GLT), node: v14.16.0
2021-05-01 21:45:02.432  - info: host.GLT(GLT) ip addresses: 2a02:8108:9440:50e4:fd70:a681:5ffd:7bb7 2a02:8108:9440:50e4:28e0:20d4:41c9:5727 2a02:8108:9440:50e4:39ff:5bfa:20cc:9168 2a02:8108:9440:50e4:9597:336f:4b33:f00d 2a02:8108:9440:50e4:c4ca:d71e:89b9:c649 2a02:8108:9440:50e4:dc3c:3ad1:d5e7:51e5 2a02:8108:9440:50e4:e581:5c75:90a5:8412 2a02:8108:9440:50e4:edee:4276:5da2:9792 fe80::fd70:a681:5ffd:7bb7 10.122.60.87 fe80::419a:e058:356:a8a8 10.8.0.1
2021-05-01 21:45:02.527  - info: daswetter.0 (14636) starting. Version 3.0.5 in C:/iobroker/GLT/node_modules/iobroker.daswetter, node: v14.16.0, js-controller: 3.3.4
2021-05-01 21:45:02.719  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_1.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:02.725  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_1.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:02.844  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_2.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:02.850  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_2.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:02.943  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_3.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:02.949  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_3.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.025  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_4.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.031  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_4.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.102  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_5.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.108  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_5.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.188  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_6.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.195  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_6.Wetter_Symbol_id" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.283  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_7.Wetter_Symbol_id2" has wrong type "number" but has to be "string"
2021-05-01 21:45:03.289  - warn: daswetter.0 (14636) State value to set for "daswetter.0.NextDays.Location_1.Day_7.Wetter_Symbol_id" has wrong type "number" but has to be "string"

[Apollon77]

Und welcher controller war VOR dem update auf dem system? Also 3.3.4 ist das "neue". was war es davor?

@Stabilostick also sollten wir einfach wie bei Linux den Befehl aufrufgen ... bei windows halt "iobroker.bat restart" ?!

[Stabilostick]

@Stabilostick also sollten wir einfach wie bei Linux den Befehl aufrufgen ... bei windows halt "iobroker.bat restart" ?!

Ja.

[Apollon77]

Ok, upcoming controller 3.3.6 will have this: https://github.com/ioBroker/ioBroker.js-controller/commit/ac6969acc8511a81a790ecfb0a6e28d5f0eec7ca ... so we can test with this again, but before this test makes sense @JBSullivan needs to then downgrade to controller 3.3.1 (direct npm command or such, reboot and then try upgrade to 3.3.6 ... (just to prepare mentally) ;-)

[Apollon77]

Ok, 3.3.6 geht raus. Ich update das repo, kann aber bissl dauern, am besten "ipbroker update" und warten bis 3.3.6 da angezeigt wird

@JBSullivan

• Bitte auf 3.3.1 downgraden (npm i iobroker.js-controller@3.3.1 im korrekten ioBroker verzeichnis)
• Dann am besten rebooten damit er so sauber läuft und vom standard servcie gestartet wurde und so
• dann iobroker upgrade self machen
• er sollte danach gesgartet werden ... aber so das stoppen normal geht ...

[JBSullivan]

Ich bin von 3.2.16 auf 3.3.2->3.3.4 und aktuell auf 3.3.5 gegangen.

im korrekten ioBroker verzeichnis

der Satz verunsichert mich gerade wieder. Ich habe üblicherweise immer nur "C:\iobroker\GLT>iobroker upgrade self" aufgerufen und dann ging alles automatisch.

Ist das bei "npm i" anders?

[JBSullivan]

So, Schritt 1 erledigt. - Starte jetzt den ganzen PC neu um zu gucken ob ioB automatisch mit 3.3.1 hochfährt.

Danach stoppen über den Windows Dienst oder die Konsole - was ist gewünscht?

`C:\iobroker\GLT>npm i iobroker.js-controller@3.3.1 npm WARN deprecated request@2.88.2: request has been deprecated, see https://github.com/request/request/issues/3142

iobroker.js-controller@3.3.1 preinstall C:\iobroker\GLT\node_modules\iobroker.js-controller node lib/preinstallCheck.js

NPM version: 7.11.2

iobroker.js-controller@3.3.1 install C:\iobroker\GLT\node_modules\iobroker.js-controller node iobroker.js setup first

object _design/system updated

The following notifications happened during sync:

• Ignoring Directory "heatingcontrol.admin" because officially not created as meta object. Please remove directory!
• Ignoring Directory "ping.admin" because officially not created as meta object. Please remove directory!
• Ignoring Directory "vis-test" because officially not created as meta object. Please remove directory!

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":"win32","arch":"x64"}) npm WARN jscs-loader@0.3.0 requires a peer of jscs@^3.0.3 but none is installed. You must install peer dependencies yourself. npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/common@>= 5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN xmlhttprequest-ts@1.0.1 requires a peer of @angular/core@>= 5.0.0 but none is installed. You must install peer dependencies yourself. npm WARN typedoc@0.20.28 requires a peer of typescript@3.9.x || 4.0.x || 4.1.x but none is installed. You must install peer dependencies yourself. npm WARN typedoc@0.20.28 requires a peer of typescript@3.9.x || 4.0.x || 4.1.x but none is installed. You must install peer dependencies yourself.

• iobroker.js-controller@3.3.1 added 3 packages from 2 contributors, removed 2 packages, updated 2 packages and audited 2536 packages in 64.881s

138 packages are looking for funding run npm fund for details

found 114 vulnerabilities (17 low, 52 moderate, 45 high) run npm audit fix to fix them, or npm audit for details

C:\iobroker\GLT>iobroker info Platform : Windows os : win32 Architecture : x64 CPUs : 4 Speed : 1995 MHz Model : Intel(R) Core(TM) i3-5005U CPU @ 2.00GHz RAM : 7.9 GB System uptime : 22:58:54 Node.js : v14.16.0 Disk size : 118.1 GiB Disk free : 30.8 GiB adapters count : 411 NPM : v6.14.11

C:\iobroker\GLT>iobroker version 3.3.1`

[JBSullivan]

3.3.1 ist installiert, jedoch startet ioB wieder im "Hintergrund" und ist in der Windows Dienst Ebene unsichtbar.

[JBSullivan]

3.3.6 ist drauf und startet den js-controler wieder selbstständig (schwarzes DOS Fenster poppte kurzzeit auf - das war ja vorher auch nicht mehr der Fall) und nimmt auch die Windows Dienst Anzeige mit.

Sieht so aus, als könnten wir an das Update Problem unter Windows einen Harken dran machen

[JBSullivan]

Leider bleibt der EBUSY Fehler weiterhin bestehen. Hätte ja sein können, das dass damit auch Geschichte ist. Bleibt zum Adapter Update nur der Weg über die Konsole.

• iobroker stop
• iobroker upgrade
• die zum update angebotenen Adapter mit (Y) bestätigen
• iobroker start

hmmmm lustig -

Er hat mir das Update für den Tankerkönig auf dem oben beschriebenen Weg 2x hintereinander angeboten.

`This upgrade of "tankerkoenig" will introduce the following changes:

-> 2.0.11: "ack flag" and "wrong type" issues coming up due to js-controller upgrade 3.3 were fixed

Would you like to upgrade tankerkoenig from @2.0.10 to @2.0.11 now? [(y)es, (n)o]: y Update tankerkoenig from @2.0.10 to @2.0.11 NPM version: 6.14.11 npm install iobroker.tankerkoenig@2.0.11 --loglevel error (System call) upload [3] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/words.js words.js application/javascript Update "system.adapter.tankerkoenig.0" upload [2] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/tankerkoenig.png tankerkoenig.png image/png upload [1] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/index_m.html index_m.html text/html upload [0] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/index.html index.html text/html Adapter "tankerkoenig" updated

This upgrade of "tankerkoenig" will introduce the following changes:

-> 2.0.11: "ack flag" and "wrong type" issues coming up due to js-controller upgrade 3.3 were fixed

Would you like to upgrade tankerkoenig from @2.0.10 to @2.0.11 now? [(y)es, (n)o]: y Update tankerkoenig from @2.0.10 to @2.0.11 NPM version: 6.14.11 npm install iobroker.tankerkoenig@2.0.11 --loglevel error (System call) upload [3] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/words.js words.js application/javascript upload [2] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/tankerkoenig.png tankerkoenig.png image/png upload [1] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/index_m.html index_m.html text/html upload [0] tankerkoenig.admin C:/iobroker/GLT/node_modules/iobroker.tankerkoenig/admin/index.html index.html text/html Adapter "tankerkoenig" updated

C:\iobroker\GLT>`

[Apollon77]

Super, klingt gut, kommt gleich noch 3.3.7 ... soltest DU schnell nehmen :-)

EBUSY muss man echt googeln

[JBSullivan]

OK, habe ich gemacht hat auch funktioniert, aber wieder mit der folgenden Meldung.

`C:\iobroker\GLT>iobroker upgrade self Update js-controller from @3.3.6 to @3.3.7 NPM version: 6.14.11 npm install iobroker.js-controller@3.3.7 --loglevel error --unsafe-perm (System call) Trying to install "esbuild-windows-64" using npm Failed to install "esbuild-windows-64" using npm: Command failed: npm install --loglevel=error --prefer-offline --no-audit --progress=false esbuild-windows-64@0.11.18 npm ERR! code ETARGET npm ERR! notarget No matching version found for esbuild-windows-64@0.11.18. npm ERR! notarget In most cases you or one of your dependencies are requesting npm ERR! notarget a package version that doesn't exist.

npm ERR! A complete log of this run can be found in: npm ERR! C:\iobroker\GLT\env\npm-cache_logs\2021-05-03T05_23_33_313Z-debug.log

Trying to download "https://registry.npmjs.org/esbuild-windows-64/-/esbuild-windows-64-0.11.18.tgz" Install successful

C:\iobroker\GLT>`

[Apollon77]

Versuchst Du es bjtte nochmal? Das sceint ein Fehlerin einer dependency zu sein ... hoffentlich nur temporär

[sjfm-design]

hatte die selben meldungen, es ein 2. x versucht, woody@ioBroker:~$ iobroker upgrade self Host "ioBroker" is up to date. woody@ioBroker:~$ scheint trotzdem zu passen

[JBSullivan]

EBUSY muss man echt googeln

Habe ich in der Zwischenzeit gemacht, aber alles was dabei rauskommt ist jenseits meiner Kenntnisse :) Allerdings war EBUSY bei ioBroker im Jahr 2017 unter dem Discovery Adapter schon einmal ein Thema - 8. Such Treffer von oben.

Was interessant ist, das Problem scheint nicht jedes Adapter Update zu betreffen. Heute Morgen z.B. Trash-Scheduler - keine Chance über den Admin den Adapter zu aktualisieren.

Jetzt heute Nachmittag, der ZigBee Adapter bereitete keine Probleme aus der Admin Adapter Liste heraus :?

https://www.google.com/search?q=EBUSY+node+Windows&newwindow=1&biw=1366&bih=663&sxsrf=ALeKk01ScpEE03ojbOX9khDwiFbACkEhRg%3A1620146225746&ei=MXiRYI3_LI2QkwXXwbeQAQ&oq=EBUSY+node+Windows&gs_lcp=Cgdnd3Mtd2l6EAM6BwgAEEcQsAM6BwgjELACECdQ3UBYzUVggUhoAXACeACAAWOIAYsEkgEBNpgBAKABAaoBB2d3cy13aXrIAQjAAQE&sclient=gws-wiz&ved=0ahUKEwjN25OCu7DwAhUNyKQKHdfgDRIQ4dUDCA4&uact=5

[Apollon77]

Ok, EBUSY fixen wir anders (#1436 ) ... close here