Metricbeart as a windows service is too slow to start


(Trevor Dodds) #1

On windows, there is a delay on service start. If the server CPU is running at 100% the metricbeat service will never start. Filebeat does not have this issue.

Event ID 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.

Event 7009

A timeout was reached (30000 milliseconds) while waiting for the metricbeat service to connect.

The CPU performance below is perfectly normal.

Running from cmd window it's fine.


(Andrew Kroh) #2

Possibly the process is starved of CPU resources and cannot send the required signal in time.

This line must execute in a timely manger from what I understand of about the service control manager. https://github.com/elastic/beats/blob/5616c111d50a6960fde5df61a2cfef7c81ee1de7/libbeat/service/service_windows.go#L19-L19 Maybe you could drop some logger statements around that line to see what the timing is.


(system) #3

This topic was automatically closed after 21 days. New replies are no longer allowed.