# Filebeat Service Timeout on Linux Server

**URL:** <https://discuss.elastic.co/t/filebeat-service-timeout-on-linux-server/180600>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 10, 2019, 5:42pm UTC](https://discuss.elastic.co/t/filebeat-service-timeout-on-linux-server/180600 "2019-05-10T17:42:10Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![danielmoon](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@danielmoon](https://discuss.elastic.co/u/danielmoon)\
**Post date:** [May 10, 2019, 5:42pm UTC](https://discuss.elastic.co/t/filebeat-service-timeout-on-linux-server/180600/1 "2019-05-10T17:42:10Z")

</div>

Hi, I'm running into as issue with starting the filebeat service.  
Whenever I start the service `sudo systemctl start filebeat`

Filebeat begins working, but the command never finishes executing.  
After about a 20 minute period the something (the os probably) kills the service because it never finished starting.

Does anyone know why this might be happening?

Everything is /var/log/messages, and /var/log/filebeat point to the timeout being the issue, but I can't figure out why it's timing out.

---

<div class="post-metadata">

**Author:** ![danielmoon](https://avatars.discourse-cdn.com/v4/letter/d/278dde/32.png) [@danielmoon](https://discuss.elastic.co/u/danielmoon)\
**Post date:** [May 13, 2019, 4:15pm UTC](https://discuss.elastic.co/t/filebeat-service-timeout-on-linux-server/180600/2 "2019-05-13T16:15:10Z")

</div>

Found out my issue, the filebeat.service unit needed to be changed from 'forking' to 'simple'  
/etc/systemd/system/filebeat.service

Thanks to everyone for their help.

---

<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:** [June 10, 2019, 4:15pm UTC](https://discuss.elastic.co/t/filebeat-service-timeout-on-linux-server/180600/3 "2019-06-10T16:15:11Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.
