Windows Dienst lässt sich nicht mehr starten

[aleks-83]

Hi,

ich hatte Probleme mit meinem Sonos Adapter (Thread)
Daraufhin habe ich den Adapter deinstalliert und neu installiert.
Beim Starten des neu installierten Adapter bekam ich die Fehlermeldung:

host.NUC(NUC)  2019-10-11 13:23:53.162 info    instance system.adapter.sonos.0 started with pid 12228
Caught  2019-10-11 13:23:54.145 error   by controller[0]: ^
Caught  2019-10-11 13:23:54.145 error   by controller[0]: fs.js:114
Caught  2019-10-11 13:23:54.145 error   by controller[0]: throw err;
Caught  2019-10-11 13:23:54.145 error   by controller[1]:
Caught  2019-10-11 13:23:54.145 error   by controller[1]: at D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:640:
Caught  2019-10-11 13:23:54.145 error   by controller[1]: at Object.mkdirSync (fs.js:757:3)
Caught  2019-10-11 13:23:54.145 error   by controller[1]: Error: ENOENT: no such file or directory, mkdir 'D:\ioBroker\NUC\log\iobroker..yyyy-10-Fr.10/11\'
Caught  2019-10-11 13:23:54.145 error   by controller[2]: 20
Caught  2019-10-11 13:23:54.145 error   by controller[2]: at Array.reduce (<anonymous>)
Caught  2019-10-11 13:23:54.145 error   by controller[2]: at mkDirForFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:628:27)
Caught  2019-10-11 13:23:54.145 error   by controller[2]: at Object.FileStreamRotator.getStream (D:\ioBroker\NUC\node_module
Caught  2019-10-11 13:23:54.145 error   by controller[3]: at new DailyRotateFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\winston-daily-rotate-file
Caught  2019-10-11 13:23:54.145 error   by controller[3]: s\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:505:5)
Caught  2019-10-11 13:23:54.145 error   by controller[4]: \daily-rotate-file.js:80:57)
Caught  2019-10-11 13:23:54.145 error   by controller[4]: at logger (D:\ioBroker\NUC\node_modules\iobroker.js-controller\lib\logger.js:83:34)
Caught  2019-10-11 13:23:54.146 error   by controller[4]: at new Adapter (D:\ioBroker\NUC\node_modules\iobroker.js-controller\lib\adapter.js:129:53)
Caught  2019-10-11 13:23:54.146 error   by controller[4]: at Object.<anonymous> (D:\ioBroker\NUC\node_modules\iobroker.sonos\main.js:1851:5)
Caught  2019-10-11 13:23:54.146 error   by controller[4]: at startAdapter (D:\ioBroker\NUC\node_modules\iobroker.sonos\main.js:29:16)
host.NUC(NUC)  2019-10-11 13:23:54.146 error   instance system.adapter.sonos.0 terminated with code 1 ()

Das Problem war nicht behoben.

Dann habe ich den NUC mit (Windwos 10) neu gestartet.
In der ioBroker Kommandozeile habe ich dann gesehen dass ioBroker nicht gestartet ist.
In den Diensten lässt er sich starten, beendet sich aber sofort wieder.

Wenn ich jetzt versuche node JS zu starten

Spoiler

D:\ioBroker\NUC>node node_modules/iobroker.js-controller/controller.js --logs
fs.js:114
    throw err;
    ^

Error: ENOENT: no such file or directory, mkdir 'D:\ioBroker\NUC\log\iobroker..yyyy-10-Fr.10/11\'
    at Object.mkdirSync (fs.js:757:3)
    at D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:640:20
    at Array.reduce (<anonymous>)
    at mkDirForFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:628:27)
    at Object.FileStreamRotator.getStream (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:505:5)
    at new DailyRotateFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\winston-daily-rotate-file\daily-rotate-file.js:80:57)
    at logger (D:\ioBroker\NUC\node_modules\iobroker.js-controller\lib\logger.js:83:34)
    at init (D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js:2740:55)
    at Object.<anonymous> (D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js:2879:1)
    at Module._compile (internal/modules/cjs/loader.js:778:30)

was natürlich nicht geht, bekomme ich aber die selbe Fehlermeldung wie oben beim Starten vom Sonos Adapter.

Hilft euch das bei der Fehlersuche?
Ich komme alleine nicht klar.

@Stabilostick kannst du als Windows Experte hier helfen?

Hängt das vllt mit dem Update auf JS 2.0 zusammen was mir seit heute angeboten wird?
Bin aber noch auf 1.5.14

[sigi234]

Was kommt bei:

iobroker list instances
node -v
nodejs -v
npm -v

[sigi234]

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

In den Diensten lässt er sich starten, beendet sich aber sofort wieder.

Das habe ich auch manchmal, warum auch immer.

[aleks-83]

Und was hilft dann?

[sigi234]

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

Und was hilft dann?

Neustart von Windows.

[aleks-83]

@sigi234 sagte in Windows Dienst lässt sich nicht mehr starten:

Was kommt bei:

iobroker list instances
node -v
nodejs -v
npm -v

iobroker list instances:
Zählt alle meine Instanzen auf, aber keine mit einem + davor.

D:\ioBroker\NUC>node -v
v10.16.3

D:\ioBroker\NUC>nodejs -v
Der Befehl "nodejs" ist entweder falsch geschrieben oder
konnte nicht gefunden werden.

D:\ioBroker\NUC>npm -v
6.9.0

[aleks-83]

@sigi234 sagte in Windows Dienst lässt sich nicht mehr starten:

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

Und was hilft dann?

Neustart von Windows.

Hab ihn jetzt 3x neu gestartet. Bleibt dabei...

[aleks-83]

Bleibt mir wohl nur die Neuinstallation!?

Ist zwar mit der Migration im WIndows Installer von Stabilostick super einfach.
Aber einige Adapter funktionierten dann doch nicht ganz korrekt, sodass ich sie neu installieren musste.

[Stabilostick]

@aleks-83

Im Unterordner „daemon“ der ioBroker-Serverinstanz sind einige Logdateien hinterlegt, die den Dienst und dessen Start aufzeichnen. Was steht in den Logs drin, dass zum Zeitpunkt eines versuchten Dienststarts passt? Was sagt zu der Zeit das ioBroker-Log im Log-Ordner?

[aleks-83]

@Stabilostick
Danke für die Antowrt.

Ich habe gerade nochmal den Dienst gestartet und die Logfiles angesehen.

Es wurden nur im daemon Ordner logs erstellt.
Im ioBroker/log/ Ordner sind nur log files vom letzen erfolgreichen start des Brokers vom 11.10.

Hier aus dem daemon Ordner

In der iobroker.err.log (Download) wiederholt sich immer weider eine Meldung:

Spoiler

Error: ENOENT: no such file or directory, mkdir 'D:\ioBroker\NUC\log\iobroker..yyyy-10-Fr.10/11\'
   at Object.mkdirSync (fs.js:757:3)
   at D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:640:20
   at Array.reduce (<anonymous>)
   at mkDirForFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:628:27)
   at Object.FileStreamRotator.getStream (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\file-stream-rotator\FileStreamRotator.js:505:5)
   at new DailyRotateFile (D:\ioBroker\NUC\node_modules\iobroker.js-controller\node_modules\winston-daily-rotate-file\daily-rotate-file.js:80:57)
   at logger (D:\ioBroker\NUC\node_modules\iobroker.js-controller\lib\logger.js:83:34)
   at init (D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js:2740:55)
   at Object.<anonymous> (D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js:2879:1)
   at Module._compile (internal/modules/cjs/loader.js:778:30)
fs.js:114
   throw err;
   ^

iobroker.wrapper.log

Spoiler

2019-10-13 20:52:29,049 INFO  - Starting ServiceWrapper in the service mode
2019-10-13 20:52:29,093 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:52:29,100 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:52:29,135 INFO  - Started process 8256
2019-10-13 20:52:29,142 DEBUG - Forwarding logs of the process System.Diagnostics.Process (node) to winsw.RollingSizeTimeLogAppender
2019-10-13 20:52:40,830 INFO  - Starting ServiceWrapper in the service mode
2019-10-13 20:52:40,874 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:52:40,881 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:52:40,914 INFO  - Started process 10464
2019-10-13 20:52:40,923 DEBUG - Forwarding logs of the process System.Diagnostics.Process (node) to winsw.RollingSizeTimeLogAppender
2019-10-13 20:53:02,316 INFO  - Starting ServiceWrapper in the service mode
2019-10-13 20:53:02,363 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:53:02,369 INFO  - Starting "D:\ioBroker\NUC\nodejs\node.exe" "D:\ioBroker\NUC\node_modules\iobroker.js-controller\controller.js"
2019-10-13 20:53:02,434 INFO  - Started process 3992
2019-10-13 20:53:02,448 DEBUG - Forwarding logs of the process System.Diagnostics.Process (node) to winsw.RollingSizeTimeLogAppender

[Stabilostick]

@sigi234 sagte in Windows Dienst lässt sich nicht mehr starten:

Was kommt bei:

iobroker list instances
node -v
nodejs -v
npm -v

FYI: nodejs.exe braucht und gibt es auf Windows nicht.

[Stabilostick]

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

Ich habe gerade nochmal den Dienst gestartet und die Logfiles angesehen.

Da muss wohl nochmal TeamViewer ran.... Du hast noch die Nummer?

[sigi234]

@Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

@sigi234 sagte in Windows Dienst lässt sich nicht mehr starten:

Was kommt bei:

iobroker list instances
node -v
nodejs -v
npm -v

FYI: nodejs.exe braucht und gibt es auf Windows nicht.

...füge ich immer via Insert Canned Response automatisch ein.

[sigi234]

Hm, bei mir kommt immer das im err.Log

Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sigi/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json

[Stabilostick]

@sigi234

need ... more ... input. Welcher Adapter?

[sigi234]

@Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

@sigi234

need ... more ... input. Welcher Adapter?

Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
(node:6428) UnhandledPromiseRejectionWarning: FirebaseError: 5 NOT_FOUND: No document to update: projects/iobroker-iogo/databases/(default)/documents/users/A4JRhBHOt8Q3xR8SjK7Q3hW2U8K2/adapters/system_adapter_js-controller
    at new FirestoreError (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:354:28)
    at ClientDuplexStream.<anonymous> (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:22313:19)
    at ClientDuplexStream.emit (events.js:198:13)
    at ClientDuplexStream._emitStatusIfDone (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:234:12)
    at ClientDuplexStream._receiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:211:8)
    at Object.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1306:15)
    at InterceptingListener._callNext (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:618:8)
    at C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1123:18
(node:6428) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). (rejection id: 4)

Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
(node:6428) UnhandledPromiseRejectionWarning: FirebaseError: 5 NOT_FOUND: No document to update: projects/iobroker-iogo/databases/(default)/documents/users/A4JRhBHOt8Q3xR8SjK7Q3hW2U8K2/adapters/system_adapter_js-controller
    at new FirestoreError (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:354:28)
    at ClientDuplexStream.<anonymous> (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:22313:19)
    at ClientDuplexStream.emit (events.js:198:13)
    at ClientDuplexStream._emitStatusIfDone (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:234:12)
    at ClientDuplexStream._receiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:211:8)
    at Object.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1306:15)
    at InterceptingListener._callNext (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:618:8)
    at C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1123:18
(node:6428) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). (rejection id: 5)

Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
(node:6428) UnhandledPromiseRejectionWarning: FirebaseError: 5 NOT_FOUND: No document to update: projects/iobroker-iogo/databases/(default)/documents/users/A4JRhBHOt8Q3xR8SjK7Q3hW2U8K2/adapters/system_adapter_js-controller
    at new FirestoreError (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:354:28)
    at ClientDuplexStream.<anonymous> (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\@firebase\firestore\dist\index.node.cjs.js:22313:19)
    at ClientDuplexStream.emit (events.js:198:13)
    at ClientDuplexStream._emitStatusIfDone (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:234:12)
    at ClientDuplexStream._receiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client.js:211:8)
    at Object.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1306:15)
    at InterceptingListener._callNext (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:568:42)
    at InterceptingListener.onReceiveStatus (C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:618:8)
    at C:\Program Files\iobroker\Test\node_modules\iobroker.iogo\node_modules\grpc\src\client_interceptors.js:1123:18
(node:6428) UnhandledPromiseRejectionWarning: Unhandled promise rejection. 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(). (rejection id: 6)

Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
{ Error [ERR_UNHANDLED_ERROR]: Unhandled error. ('1811161726216929086534298f17edb7')
    at MerossCloud.emit (events.js:187:17)
    at MerossCloudDevice.devices.(anonymous function).on (C:\Program Files\iobroker\Test\node_modules\iobroker.meross\node_modules\meross-cloud\index.js:126:30)
    at MerossCloudDevice.emit (events.js:203:15)
    at MqttClient.client.on (C:\Program Files\iobroker\Test\node_modules\iobroker.meross\node_modules\meross-cloud\index.js:249:18)
    at MqttClient.emit (events.js:198:13)
    at TLSSocket.handleTLSerrors (C:\Program Files\iobroker\Test\node_modules\iobroker.meross\node_modules\mqtt\lib\connect\tls.js:26:18)
    at TLSSocket.emit (events.js:203:15)
    at emitErrorNT (internal/streams/destroy.js:91:8)
    at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
    at process._tickCallback (internal/process/next_tick.js:63:19) context: '1811161726216929086534298f17edb7' }

Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json
Cannot parse "/Adapter_Icons/vis-views.json
Cannot parse "/Bilder/vis-views.json
Cannot parse "/Meine_Icons/vis-views.json
Cannot parse "/Mond/vis-views.json
Cannot parse "/Netzwerk/vis-views.json
Cannot parse "/Radiosender/vis-views.json
Cannot parse "/Sonstige/vis-views.json
Cannot parse "/Staubsauger/vis-views.json
Cannot parse "/Tankstellen_logos/vis-views.json
Cannot parse "/VIS/vis-views.json
Cannot parse "/Wetter_HD/vis-views.json
Cannot parse "/Wettericons/vis-views.json
Cannot parse "/fire/vis-views.json

[aleks-83]

@Stabilostick sagte in Windows Dienst lässt sich nicht mehr starten:

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

Ich habe gerade nochmal den Dienst gestartet und die Logfiles angesehen.

Da muss wohl nochmal TeamViewer ran.... Du hast noch die Nummer?

Schreibe dir im Chat.

[aleks-83]

OK, also @Stabilostick hat sich meinen NUC mal angesehen.
Vielen Dank nochmal dafür !

Der Dienst wird wohl korrekt gestartet, aber direkt wieder beendet weil ioBroker die logfile nicht erstellen kann.
Laut Error Log versucht der ioBroker ein log zu erstellen mit dem Namen:

D:\ioBroker\NUC\log\iobroker..yyyy-10-Mo.10/14\

Wobei NUC der Instanzen-Namen ist.
Alles hinter iobroker. macht aber irgendiwe keinen Sinn und steht auch so nicht in meiner ioBroker Konfig.
Wie sich das bei mir eingeschlichen hat, kann ich mir nicht erklären.

Das Ende vom Lied ist halt ne Neuinstallation.
Aber diese geht ja wirklich einfach und automatisiert dank dem Windows Installer.

[aleks-83]

Was mir gerade noch aufgefallen ist bei der Neueinrichtung:

Als er alle Adapter aus der Migration installiert hatte, habe ich per admin Adapter gesagt er soll alle Adapter updaten.
Dann hat er versucht NPM upzugraden.
Das ging schief.

Spoiler

... Hier wurden Adapter geupdatet ...
Adapter "xs1" is not installed.
Adapter "yahka" is not installed.
Adapter "yamaha" is not installed.
Adapter "yeelight-2" is not installed.
Adapter "yr" is not installed.
Adapter "zigbee" is not installed.
Adapter "zont" is not installed.
Adapter "zwave" is not installed.
Adapter "zwave2" is not installed.
Update js-controller from @1.5.14 to @2.0.29
2019-10-14 20:36:35.125 - warn: host.NUC(NUCmaster) instance system.adapter.web.0 terminated due to SIGTERM
2019-10-14 20:36:35.125 - info: host.NUC(NUCmaster) instance system.adapter.web.0 terminated with code null ()
2019-10-14 20:36:37.511 - info: host.NUC(NUCmaster) instance system.adapter.web.0 started with pid 6360
2019-10-14 20:36:38.566 - info: iobroker NPM version: 6.9.0
2019-10-14 20:36:38.566 - info: iobroker npm install iobroker.js-controller@2.0.29 --unsafe-perm --production --save --prefix "D:/ioBroker/NUCmaster" (System call)
2019-10-14 20:36:39.571 - info: web.0 starting. Version 2.4.5 in D:/ioBroker/NUCmaster/node_modules/iobroker.web, node: v10.16.3
2019-10-14 20:36:41.833 - info: web.0 socket.io server listening on port 8083
2019-10-14 20:36:41.838 - info: web.0 http server listening on port 8083
2019-10-14 20:37:33.190 - info: iobroker gyp
2019-10-14 20:37:33.191 - info: iobroker ERR!
2019-10-14 20:37:33.193 - info: iobroker
2019-10-14 20:37:33.199 - info: iobroker build error
2019-10-14 20:37:33.200 - info: iobroker
2019-10-14 20:37:33.229 - info: iobroker gyp ERR! stack Error: `C:\Program Files (x86)\Microsoft Visual Studio\2017\BuildTools\MSBuild\15.0\Bin\MSBuild.exe` failed with exit code: 1gyp ERR! stack at ChildProcess.onExit (D:\ioBroker\NUCmaster\nodejs\node_modules\npm\node_modules\node-gyp\lib\build.js:262: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.18362
2019-10-14 20:37:33.235 - info: iobroker gyp ERR! command "D:\\ioBroker\\NUCmaster\\nodejs\\node.exe" "D:\\ioBroker\\NUCmaster\\nodejs\\node_modules\\npm\\node_modules\\node-gyp\\bin\\node-gyp.js" "rebuild"gyp
2019-10-14 20:37:33.237 - info: iobroker ERR!
2019-10-14 20:37:33.241 - info: iobroker cwd D:\ioBroker\NUCmaster\node_modules\iobroker.js-controller\node_modules\unix-dgramgyp ERR!
2019-10-14 20:37:33.242 - info: iobroker node -v v10.16.3gyp ERR! node-gyp -v v3.8.0
gyp ERR! not ok
2019-10-14 20:38:12.125 - info: iobroker npm
2019-10-14 20:38:12.126 - info: iobroker
2019-10-14 20:38:12.130 - info: iobroker WARN
2019-10-14 20:38:12.133 - info: iobroker
2019-10-14 20:38:12.140 - info: iobroker optional
2019-10-14 20:38:12.144 - info: iobroker SKIPPING OPTIONAL DEPENDENCY: fsevents@2.1.1 (node_modules\iobroker.js-controller\node_modules\fsevents):
2019-10-14 20:38:12.165 - info: iobroker npm
2019-10-14 20:38:12.176 - info: iobroker
2019-10-14 20:38:12.180 - info: iobroker WARN
2019-10-14 20:38:12.181 - info: iobroker
2019-10-14 20:38:12.182 - info: iobroker notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
2019-10-14 20:38:12.183 - info: iobroker npm
2019-10-14 20:38:12.187 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 (node_modules\iobroker.js-controller\node_modules\unix-dgram):npm WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 install: `node-gyp rebuild`
npm WARN optional SKIPPING OPTIONAL DEPENDENCY: Exit status 1
2019-10-14 20:38:12.256 - info: iobroker Host "NUC(NUCmaster)" (win32) updated
2019-10-14 20:38:12.256 - info: iobroker Starting node restart.js
2019-10-14 20:38:12.343 - info: iobroker exit 0
2019-10-14 20:39:43.348 - info: host.NUC(NUCmaster) Update repository "latest" under "http://download.iobroker.net/sources-dist-latest.json"

Kann es sein dass er das beim letzten Update auch versucht hat, und mir die Zeile mit dem mkdir zerschossen hat?

Ich habe den NUC jetzt aber schon neu gestartet.
Der Dienst startet noch ganz normal.

Dann werde ich den button "Alle Adapter updaten" erst mal meiden.

EDIT:
Der Admin zeigt mir aber an ich hätte die 2.0.29

[Stabilostick]

@aleks-83 sagte in Windows Dienst lässt sich nicht mehr starten:

Dann hat er versucht NPM upzugraden.
Das ging schief.

Nein, hat er nicht.

Du hast den neuesten js-controller installiert aus Latest. Dabei ist der Buildvorgang für die optionale Komponente "unix-dgram", die sowieso nur auf Linux funktioniert, fehlgeschlagen. "fsevents" braucht es nur auf Apple-Rechnern. Also alles kein Problem und kein Grund zur Sorge:

2019-10-14 20:38:12.182 - info: iobroker notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for fsevents@2.1.1: wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})

2019-10-14 20:38:12.187 - info: iobroker WARN optional SKIPPING OPTIONAL DEPENDENCY: unix-dgram@2.0.2 (node_modules\iobroker.js-controller\node_modules\unix-dgram)

2019-10-14 20:38:12.343 - info: iobroker exit 0

Das ist das Wichtige am Ende. 0 = alles Ok.