Metricbeart as a windows service is too slow to start

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.

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. Maybe you could drop some logger statements around that line to see what the timing is.

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