# Filebeat getting after few hours of starting

**URL:** <https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 17, 2020, 2:08pm UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990 "2020-09-17T14:08:48Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shefali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shefali/32/63414_2.png) [@Shefali](https://discuss.elastic.co/u/Shefali)\
**Post date:** [September 17, 2020, 2:08pm UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/1 "2020-09-17T14:08:48Z")

</div>

Having this issue on production. We have installed filebeat using tar file. After starting, in few hours it's stopping without any error. On our other lower environment we have installed using rpm and never seen this issue. Kindly let me know, what can be the problem?

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [September 17, 2020, 2:46pm UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/2 "2020-09-17T14:46:00Z")

</div>

Hm.. it's really weird. You can try to enable debug logging on one of your production instances. Which version of filebeat did you install?

---

<div class="post-metadata">

**Author:** ![Shefali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shefali/32/63414_2.png) [@Shefali](https://discuss.elastic.co/u/Shefali)\
**Post date:** [September 18, 2020, 6:26am UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/3 "2020-09-18T06:26:22Z")

</div>

version 7.5

---

<div class="post-metadata">

**Author:** ![Shefali](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shefali/32/63414_2.png) [@Shefali](https://discuss.elastic.co/u/Shefali)\
**Post date:** [September 18, 2020, 6:30am UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/4 "2020-09-18T06:30:42Z")

</div>

As we are running using nohup, i didn't see any error in nohup.out, when filebeat stops. Normally when we kill the filebeat process, the same logs generated in nohup. There is no change i see there. Will check after enabling debug log once.

---

<div class="post-metadata">

**Author:** ![mtojek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mtojek/32/63863_2.png) [@mtojek](https://discuss.elastic.co/u/mtojek)\
**Post date:** [September 18, 2020, 8:05am UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/5 "2020-09-18T08:05:15Z")

</div>

Is there any chance that you can try with the latest version? 7.5 is getting old.

---

<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:** [October 16, 2020, 10:05am UTC](https://discuss.elastic.co/t/filebeat-getting-after-few-hours-of-starting/248990/6 "2020-10-16T10:05:36Z")

</div>

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