# Filebeat is down after start

**URL:** <https://discuss.elastic.co/t/filebeat-is-down-after-start/297390>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 16, 2022, 3:36pm UTC](https://discuss.elastic.co/t/filebeat-is-down-after-start/297390 "2022-02-16T15:36:53Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ocervera](https://avatars.discourse-cdn.com/v4/letter/o/ecccb3/32.png) [@ocervera](https://discuss.elastic.co/u/ocervera)\
**Post date:** [February 16, 2022, 3:36pm UTC](https://discuss.elastic.co/t/filebeat-is-down-after-start/297390/1 "2022-02-16T15:36:53Z")

</div>

Hello,

I have installed in a Centos, Wazuh Manager+ Filebeat and the latter seems to work fine but after a while the filebeat.service suddenly stops working.

systemctl status filebeat.service shows:

```auto
× filebeat.service - Filebeat sends log files to Logstash or directly to Elasticsearch.
     Loaded: loaded (/usr/lib/systemd/system/filebeat.service; enabled; vendor preset: disabled)
     Active: failed (Result: exit-code) since Wed 2022-02-16 16:18:01 CET; 37s ago
       Docs: https://www.elastic.co/products/beats/filebeat
    Process: 3236 ExecStart=/usr/share/filebeat/bin/filebeat --environment systemd $BEAT_LOG_OPTS $BEAT_CONFIG_OPTS $BE>
   Main PID: 3236 (code=exited, status=2)
        CPU: 47ms

feb 16 16:18:01 localhost.localdomain filebeat[3236]: rip 0x7f99eec3f43c
feb 16 16:18:01 localhost.localdomain filebeat[3236]: rflags 0x246
feb 16 16:18:01 localhost.localdomain filebeat[3236]: cs 0x33
feb 16 16:18:01 localhost.localdomain filebeat[3236]: fs 0x0
feb 16 16:18:01 localhost.localdomain filebeat[3236]: gs 0x0
feb 16 16:18:01 localhost.localdomain systemd[1]: filebeat.service: Scheduled restart job, restart counter is at 7.
feb 16 16:18:01 localhost.localdomain systemd[1]: Stopped Filebeat sends log files to Logstash or directly to Elasticse>
feb 16 16:18:01 localhost.localdomain systemd[1]: filebeat.service: Start request repeated too quickly.
feb 16 16:18:01 localhost.localdomain systemd[1]: filebeat.service: Failed with result 'exit-code'.
feb 16 16:18:01 localhost.localdomain systemd[1]: Failed to start Filebeat sends log files to Logstash or directly to E

```

If I manually start the service again, filebeat status is UP and seems to work fine but after a few minutes it goes down again. I have reinstalled the whole server and same result, I don't know where to look so any help would be much appreciated.

Thank you ver much

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 17, 2022, 1:14am UTC](https://discuss.elastic.co/t/filebeat-is-down-after-start/297390/2 "2022-02-17T01:14:03Z")

</div>

Welcome to our community! 😃

You need to start by looking in `/var/log/filebeat` and posting anything relevant please.

---

<div class="post-metadata">

**Author:** ![ocervera](https://avatars.discourse-cdn.com/v4/letter/o/ecccb3/32.png) [@ocervera](https://discuss.elastic.co/u/ocervera)\
**Post date:** [March 3, 2022, 11:14am UTC](https://discuss.elastic.co/t/filebeat-is-down-after-start/297390/3 "2022-03-03T11:14:37Z")

</div>

Hi @warkolm, thank you for your anwser and welcome. Sorry for my late response... There is no relevant info in /var/log/filebeat but if you could please take a look at the following link, it is an extract of /var/log/messages  
[https://bit.ly/3pv9xl5](https://bit.ly/3pv9xl5)

Best regards

---

<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:** [March 31, 2022, 11:14am UTC](https://discuss.elastic.co/t/filebeat-is-down-after-start/297390/4 "2022-03-31T11:14:45Z")

</div>

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