Skip to content
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

Closed
andrewkroh opened this issue May 22, 2017 · 9 comments
Closed

Metricbeat Windows service fails to start at boot #4373

andrewkroh opened this issue May 22, 2017 · 9 comments

Comments

@andrewkroh
Copy link
Member

For confirmed bugs, please report:

  • Version: 5.4 (other versions appear to be affected)
  • Operating System: Windows 2012 R2
  • Steps to Reproduce:
    • Install metricbeat as a service, enable service, reboot.
    • Check the event log and see that the service failed to start due to a timeout.

Discuss:

@radoondas
Copy link
Member

Little information from setup might help as report from systems with this issue:
On the server with metricbeat 5.1.2 "Automatic Delayed Start" helped.
But on the server with metricbeat 5.4.0 didn't.

@Elufimov
Copy link
Contributor

We use delayed start as workaround on all beats.

@ismael-hasan
Copy link
Contributor

  • Version 5.2.2
  • WIndows 10
  • Steps to reproduce
    • Install Metricbeat as a service
    • Set startup to automatic
    • Restart

Upon restart, the service is not restarted; it seems it times out; Windows event logs show:

EventID 7009 - A timeout was reached (30000 milliseconds) while waiting for the metricbeat service to connect.
EventID 7000 - The metricbeat service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.

Using automatic delayed start solves the issue

@PhaedrusTheGreek
Copy link
Contributor

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:

The DataHub metricbeat service failed to start due to the following error: 
The service did not respond to the start or control request in a timely fashion.
A timeout was reached (30000 milliseconds) while waiting for the DataHub metricbeat service to connect.

andrewkroh added a commit to andrewkroh/beats that referenced this issue Jun 12, 2017
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74

Fixes elastic#4373
exekias pushed a commit that referenced this issue Jun 13, 2017
* 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
andrewkroh added a commit to andrewkroh/beats that referenced this issue Jun 13, 2017
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76

Fixes elastic#4373
andrewkroh added a commit to andrewkroh/beats that referenced this issue Jun 13, 2017
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76

Fixes elastic#4373
tsg pushed a commit that referenced this issue Jun 14, 2017
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76

Fixes #4373
@andrewkroh
Copy link
Member Author

These are PRs to the various release branches.

5.4 - #4499
5.5 - #4500
6.0 (master) - #4491

@ismael-hasan
Copy link
Contributor

Thank you @andrewkroh !

tsg pushed a commit that referenced this issue Jun 14, 2017
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76

Fixes #4373
@HusseinKothari26
Copy link

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.

@andrewkroh
Copy link
Member Author

@HusseinKothari26 Is there any log output from the Beat when it fails to startup?

@PhaedrusTheGreek
Copy link
Contributor

Any other issues circumstances might be due to this issue: #5453, where the reason for startup failure just isn't conveniently visible.

leweafan pushed a commit to leweafan/beats that referenced this issue Apr 28, 2023
Fixed Windows issue that caused a hang during `init()` if WMI wasn't ready. elastic/gosigar#74 elastic/gosigar#76

Fixes elastic#4373
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants