# Metricbeart as a windows service is too slow to start

**URL:** <https://discuss.elastic.co/t/metricbeart-as-a-windows-service-is-too-slow-to-start/55084>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [July 8, 2016, 6:34pm UTC](https://discuss.elastic.co/t/metricbeart-as-a-windows-service-is-too-slow-to-start/55084 "2016-07-08T18:34:23Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Zfs](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/zfs/32/13370_2.png) [@Zfs](https://discuss.elastic.co/u/Zfs)\
**Post date:** [July 8, 2016, 6:34pm UTC](https://discuss.elastic.co/t/metricbeart-as-a-windows-service-is-too-slow-to-start/55084/1 "2016-07-08T18:34:23Z")

</div>

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.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/d/d7b5eb8ec26a2efc8dfb9c616d6559e8dffc28bc.png)

Running from cmd window it's fine.

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [July 8, 2016, 8:02pm UTC](https://discuss.elastic.co/t/metricbeart-as-a-windows-service-is-too-slow-to-start/55084/2 "2016-07-08T20:02:32Z")

</div>

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](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.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [July 29, 2016, 6:34pm UTC](https://discuss.elastic.co/t/metricbeart-as-a-windows-service-is-too-slow-to-start/55084/3 "2016-07-29T18:34:36Z")

</div>

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