windows_exporter service failed to start on reboot

[Abhishek-Kraj]

Hi,

After updates and rebooting the server, the windows_exporter service was not running

The windows_exporter service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.

Delayed start
sc config windows_exporter start= delayed-auto

Restart option
sc failure windows_exporter actions= restart/60000/restart/60000/""/60000 reset= 86400

No Help on above configuration

[daveaowen]

Try setting WMI as a dependency on the service, and up the 'Restart service after' to 5 minutes. This worked for me.

[gillg]

This issues is very anoying, I had the same and finally I created a scheduled task "start-service" every hour to be sure it runs.

There is no log, no crash event, nothing to troubleshoot...

[tbiles]

I upgraded all my test systems to 0.18.1 on Monday in preparation for patch Tuesday. There is no real change in the inconsistent restart behavior after Windows update related reboots. This is consistent with prior releases. Service delay start was enabled around 0.16.1 timeframe which improved it from almost 100% failure to 50-60% success.

1 - 2008R2 - started
4 - 2012R2 - 3 started, 1 failed
1 - 2016 - started
1 - 2019 Core - failed
3 - 2019 Standard - 1 started, 2 failed

[tbiles]

Based on another thread, I switched all my windows_exporter test systems to depend on Winmgmt instead of the WMI service. After patch Tuesday reboots overnight, I had similar results, so the dependency service setting doesn't seem to have any affect on reliability from what I can see.

1 - 2008R2 - failed
4 - 2012R2 - 3 started, 1 failed
1 - 2016 - started
1 2019 Core - started
3 - 2019 Standard - 1 started, 2 failed

[gillg]

In theory should be solved by #1047
But I'm not 100% sure.

I have the feeling to always experience some issues after reboot on servers with a high load at boot.

[github-actions]

This issue has been marked as stale because it has been open for 90 days with no activity. This thread will be automatically closed in 30 days if no further activity occurs.