Windows 10 Installation failed - nicht dringend

Stabilostick

Ich versuche das Problem einzukreisen. Wenn bei Dir als Starttyp „Automatisch“ steht (Screenshot), dann versucht Windows auch, den ioBroker zu starten. Jetzt gibt es mehrere Logs, in denen man nachschauen kann, warum es nicht klappt. Zum ersten mehrere Logdateien im iobroker\daemon-Ordner. Und die neueste Logdatei im log-Ordner. Hast du da Einträge/Fehler ab Neustartzeitpunkt?

klassisch

Interessanterweise genau so. Starttyp "Automatisch".

Habe ioBroker-Dienst ja automatisch gestartet, aber nirgends den Starttyp eingegeben.

Ich boote nochmals und warte laaange dann schaue ich nochmals rein.

klassisch

Habe neu gestartet.

ioBroker-Dienst steht auf Starttyp automatisch. Status ist weiss, keine Schrift.
ioBroker läuft nicht
ioBroke log hat den Start nicht vermerkt
Windows Ereignisanzeige, System:

"Fehler" mit den Eigenschaften: "Der Dienst "iobroker.exe" wurde aufgrund folgenden Fehlers nicht gestartet:

Der Dienst antwortete nicht rechtzeitig auf die Start- oder Steuerungsanforderung."

"Das Zeitlimit (30000 ms) wurde beim Verbindungsversuch mit dem Dienst iobroker.exe erreicht."

Also mein Rechner ist zu lahm.

Details in der xml Ansicht:

- <event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">- <system><provider name="Service Control Manager" guid="{555908d1-a6d7-4695-8e1e-26931d2012f4}" eventsourcename="Service Control Manager"><eventid qualifiers="49152">7000</eventid> 
  <version>0</version> 
  <level>2</level> 
  <task>0</task> 
  <opcode>0</opcode> 
  <keywords>0x8080000000000000</keywords> 
  <timecreated systemtime="2018-09-17T10:31:41.847713500Z"><eventrecordid>1010</eventrecordid> 
  <correlation><execution processid="748" threadid="1296"><channel>System</channel> 
  <computer>JS-NB-03-WS7</computer></execution></correlation></timecreated></provider></system> 
- <eventdata><data name="param1">iobroker.exe</data> 
  <data name="param2">%%1053</data> 
  <binary>69006F00620072006F006B00650072002E006500780065000000</binary></eventdata></event>

In der Normalansicht

+ System 

  - Provider 

   [ Name]  Service Control Manager 
   [ Guid]  {555908d1-a6d7-4695-8e1e-26931d2012f4} 
   [ EventSourceName]  Service Control Manager 

  - EventID 7000 

   [ Qualifiers]  49152 

   Version 0 

   Level 2 

   Task 0 

   Opcode 0 

   Keywords 0x8080000000000000 

  - TimeCreated 

   [ SystemTime]  2018-09-17T10:31:41.847713500Z 

   EventRecordID 1010 

   Correlation 

  - Execution 

   [ ProcessID]  748 
   [ ThreadID]  1296 

   Channel System 

   Computer JS-NB-03-WS7 

   Security 

- EventData 

  param1 iobroker.exe 
  param2 %%1053 
   69006F00620072006F006B00650072002E006500780065000000 

--------------------------------------------------------------------------------

Binäre Daten:

In Wörtern

0000: 006F0069 00720062 006B006F 00720065 
0010: 0065002E 00650078 0000  

In Bytes

0000: 69 00 6F 00 62 00 72 00   i.o.b.r.
0008: 6F 00 6B 00 65 00 72 00   o.k.e.r.
0010: 2E 00 65 00 78 00 65 00   ..e.x.e.
0018: 00 00                     ..

klassisch

Und jetzt wirds ganz seltsam: Starte den Dienst manuell, und er wird als laufend ausgewiesen. Läuft aber nicht. Gleiche Fehlermeldung wie zuvor - Braucht zu lange zum Starten.

Stabilostick

Das hat bislang noch nichts mit einem lahmen Rechner zu tun. Was steht im Ordner daemon im ioBroker-Verzeichnis? Da sind wie geschrieben auch mehrere Logdateien drin.

klassisch

wrapper.log

2018-09-17 07:37:57 - Starting C:\Program Files\nodejs\node.exe  --harmony C:\ioBroker\node_modules\node-windows\lib\wrapper.js --file C:\ioBroker\controller.js --log "ioBroker wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n
2018-09-17 07:37:57 - Started 7904
2018-09-17 10:16:28 - Stopping iobroker.exe
2018-09-17 10:16:28 - ProcessKill 7904
2018-09-17 10:27:07 - Starting C:\Program Files\nodejs\node.exe  --harmony C:\ioBroker\node_modules\node-windows\lib\wrapper.js --file C:\ioBroker\controller.js --log "ioBroker wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n
2018-09-17 10:27:07 - Started 8028
2018-09-17 12:30:07 - Stopping iobroker.exe
2018-09-17 12:30:07 - ProcessKill 8028
2018-09-17 13:09:56 - Starting C:\Program Files\nodejs\node.exe  --harmony C:\ioBroker\node_modules\node-windows\lib\wrapper.js --file C:\ioBroker\controller.js --log "ioBroker wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n
2018-09-17 13:09:56 - Started 1512

error.log

{ Error: spawn EROFS
    at ChildProcess.spawn (internal/child_process.js:313:11)
    at Object.exports.spawn (child_process.js:503:9)
    at Object.probe (C:\ioBroker\node_modules\iobroker.ping\lib\ping.js:58:17)
    at pingAll (C:\ioBroker\node_modules\iobroker.ping\main.js:98:10)
    at Timeout._onTimeout (C:\ioBroker\node_modules\iobroker.ping\main.js:107:17)
    at ontimeout (timers.js:498:11)
    at tryOnTimeout (timers.js:323:5)
    at Timer.listOnTimeout (timers.js:290:5) errno: 'EROFS', code: 'EROFS', syscall: 'spawn' }

lässt sich jetzt zeitlich nicht zuordnen, ebenso wie out.log

host.JS-NB-03-WS7 check instance "system.adapter.admin.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.discovery.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.ping.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.1" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rega.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.web.0" for host "JS-NB-03-WS7"
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
host.JS-NB-03-WS7 check instance "system.adapter.admin.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.discovery.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.ping.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.1" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rega.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.web.0" for host "JS-NB-03-WS7"
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
host.JS-NB-03-WS7 check instance "system.adapter.admin.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.discovery.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.ping.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.1" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rega.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.web.0" for host "JS-NB-03-WS7"
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
Cannot send diag info: ETIMEDOUT
Cannot download json from http://download.iobroker.net/sources-dist.json. Error: Error: ETIMEDOUT
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}

Soll ich mal alle Logs löschen und dann nochmals neu starten?

Stabilostick

Ja, Du kannst die Logfiles (ich glaube das waren drei Stück) einfach löschen. Die XML bitte nicht ;-)

klassisch

Habe jetzt

ioBroker Dienst gestoppt (habe ich bisher nicht gemacht)
logs gelöscht
Rechner neu gestartet
Siehe da, ioBroker startet automatisch.

err.log ist leer

wrapper.log

2018-09-17 14:46:30 - Starting C:\Program Files\nodejs\node.exe  --harmony C:\ioBroker\node_modules\node-windows\lib\wrapper.js --file C:\ioBroker\controller.js --log "ioBroker wrapper" --grow 0.25 --wait 1 --maxrestarts 3 --abortonerror n
2018-09-17 14:46:33 - Started 6632

out.log:

host.JS-NB-03-WS7 check instance "system.adapter.admin.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.discovery.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.ping.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rpc.1" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.hm-rega.0" for host "JS-NB-03-WS7"
host.JS-NB-03-WS7 check instance "system.adapter.web.0" for host "JS-NB-03-WS7"
Send diag info: {"uuid":"10dcfab0-9cdb-7aa8-fec0-0a9fa94958da","language":"de","country":"Germany","hosts":[{"version":"1.4.2","platform":"Javascript/Node.js","type":"win32"}],"node":"v8.12.0","arch":"x64","adapters":{"admin":{"version":"3.4.7","platform":"Javascript/Node.js"},"discovery":{"version":"1.2.1","platform":"Javascript/Node.js"},"ping":{"version":"1.3.2","platform":"Javascript/Node.js"},"hm-rpc":{"version":"1.7.6","platform":"Javascript/Node.js"},"hm-rega":{"version":"1.7.1","platform":"Javascript/Node.js"},"web":{"version":"2.4.1","platform":"Javascript/Node.js"}},"model":"Intel(R) Core(TM)2 Duo CPU     P7350  @ 2.00GHz","cpus":2,"mem":4289593344,"ostype":"Windows_NT","city":""}

Jetzt mache einen Neustart ohne den ioBroker zu stoppen und schaue mal, ob es daran liegt

Stabilostick

Daumen drück… [emoji1303]

klassisch

So, jetzt hat es sich "eingerüttelt", ohne daß ich was zur Ursache sagen könnte. iobroker startet brav, wie es sein sollte. Sieht man schon im Taskmanager an den node.js tasks

Homoran

Hallo klassisch!

Danke für deine Geduld!

Ich war das erste Versuchskaninchen, bei mir lief es auch nicht auf Anhieb.

@stabilostick: Irgendwelche neuen Erkenntnisse aus den logs?

Habe ich die auch noch?

Gruß

Rainer

Stabilostick

So soll es sein.

Wenn Du andere Dienste hast, auf denen ioBroker aufsetzt, kann man später auch noch Abhängigkeiten bei den Diensten einrichten (Startreihenfolge).

Und man kann auch noch den Starttyp auf „automatisch (verzögert)“ einstellen. Dann startet ioBroker, wenn alles andere läuft.

Aber lass es erst mal ruhig so.

klassisch

Wenn ich noch was testen soll, ruhig sagen. Ist ja noch ein Testsystem und zum Testen und Spielen da.

Community Forum

NEWS

Windows 10 Installation failed - nicht dringend

Support us

449

32.5k

81.7k

1.3m