# Filebeat Crash

**URL:** <https://discuss.elastic.co/t/filebeat-crash/133200>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [May 24, 2018, 5:16pm UTC](https://discuss.elastic.co/t/filebeat-crash/133200 "2018-05-24T17:16:31Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![surendrakotte](https://avatars.discourse-cdn.com/v4/letter/s/9dc877/32.png) [@surendrakotte](https://discuss.elastic.co/u/surendrakotte)\
**Post date:** [May 24, 2018, 5:16pm UTC](https://discuss.elastic.co/t/filebeat-crash/133200/1 "2018-05-24T17:16:31Z")

</div>

Hello All,

FileBeat [6.2.x] crashes, how to identify the reason/fix it?

Current config Filebeat write to ELastic search directly.

Thanks in advance!

---

<div class="post-metadata">

**Author:** ![adrisr](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/adrisr/32/25423_2.png) [@adrisr](https://discuss.elastic.co/u/adrisr)\
**Post date:** [May 25, 2018, 3:50am UTC](https://discuss.elastic.co/t/filebeat-crash/133200/2 "2018-05-25T03:50:24Z")

</div>

Hi,

In order to diagnose the crash it will be useful to have a look at the filebeat logs. Can you share them?

Also a little bit more information like the OS it is running on and the configuration (filebeat.yml)

Under Linux, logs are to be found at `/var/log/filebeat` and the configuration at `/etc/filebeat/filebeat.yml`

---

<div class="post-metadata">

**Author:** ![Debashis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/debashis/32/45290_2.png) [@Debashis](https://discuss.elastic.co/u/Debashis)\
**Post date:** [May 25, 2018, 4:38am UTC](https://discuss.elastic.co/t/filebeat-crash/133200/3 "2018-05-25T04:38:05Z")

</div>

Hi @surendrakotte,

To understand the logs of filebeat enable Debug log in filebeat.yml file

> In "/etc/filebeat/filebeat.yml" add following configuration
> 
> logging.level: debug  
> logging.selectors: ["\*"]

As per above you will get the Debug logs of Filebeat in /var/log/filebeat/filebeat

If you want to get more insight of debug logs of Filebeat then execute filebeat as per following

> [root@filebeat] #filebeat.sh -e -d "\*"
> 
> **Note :** _In this way you will get the detail debug log with dynamic source code trace information. I think it will help you to understand the problem and understand the internal logics of Filebeat more conveniently._

---

<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 22, 2018, 4:48am UTC](https://discuss.elastic.co/t/filebeat-crash/133200/4 "2018-06-22T04:48:34Z")

</div>

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