-
Notifications
You must be signed in to change notification settings - Fork 4.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Metricbeat Windows service fails to start at boot #4373
Comments
Little information from setup might help as report from systems with this issue: |
We use delayed start as workaround on all beats. |
Upon restart, the service is not restarted; it seems it times out; Windows event logs show:
Using automatic delayed start solves the issue |
I'm experiencing this issue with Metricbeat and Filebeat 5.4 under Windows, and setting the service the "Automatic Delayed Start" did not resolve the issue. From the Event Log:
|
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 Fixes elastic#4373
* Update gosigar to fix Windows service timeout Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 Fixes #4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes #4373
Thank you @andrewkroh ! |
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes #4373
I'm still facing the same issue. I tried installing metricbeat 5.4.3 and 5.5.0 but Metricbeat Windows service still fails to start. It seems this fix is not working. |
@HusseinKothari26 Is there any log output from the Beat when it fails to startup? |
Any other issues circumstances might be due to this issue: #5453, where the reason for startup failure just isn't conveniently visible. |
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76 Fixes elastic#4373
For confirmed bugs, please report:
Discuss:
The text was updated successfully, but these errors were encountered: