# Filebeat -e running for a long time

**URL:** <https://discuss.elastic.co/t/filebeat-e-running-for-a-long-time/270292>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 15, 2021, 5:21pm UTC](https://discuss.elastic.co/t/filebeat-e-running-for-a-long-time/270292 "2021-04-15T17:21:08Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![thrak](https://avatars.discourse-cdn.com/v4/letter/t/d26b3c/32.png) [@thrak](https://discuss.elastic.co/u/thrak)\
**Post date:** [April 15, 2021, 5:21pm UTC](https://discuss.elastic.co/t/filebeat-e-running-for-a-long-time/270292/1 "2021-04-15T17:21:08Z")

</div>

Hello I am running a new installation of filebeat 7.12.0. I was initially getting an ILM error and so had the indices removed for filebeats.

Now when I run the filebeat -e setup, it seems to run for ever. I let it go for an hour and watched the indices documents continue to grow and the storage size grow, I believe we have it capped at 50MB. I let it run for an entire hour and it is still going. I am only dumping CentOS /var/logs/\*

I just keep seeing log/harvester

INFO [monitoring] log/log.go:144 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cgroup":{"cpuacct":{"total":{"ns":95859173}},"memory":{"mem":{"usage":{"bytes":-1454080}}}},"cpu":{"system":{"ticks":360,"time":{"ms":38}},"total":{"ticks":1140,"time":{"ms":96},"value":1140},"user":{"ticks":780,"time":{"ms":58}}},"handles":{"limit":{"hard":1048576,"soft":1048576},"open":17},"info":{"ephemeral\_id":"ba16b749-6a74-47c9-a102-34d0f09ea3de","uptime":{"ms":270135}},"memstats":{"gc\_next":23937200,"memory\_alloc":16485192,"memory\_total":118674968,"rss":59359232},"runtime":{"goroutines":64}},"filebeat":{"events":{"active":1,"added":15,"done":14},"harvester":{"open\_files":3,"running":3}},"libbeat":{"config":{"module":{"running":1}},"output":{"events":{"acked":14,"active":0,"batches":14,"total":14},"read":{"bytes":5140},"write":{"bytes":32088}},"pipeline":{"clients":3,"events":{"active":1,"published":15,"total":15},"queue":{"acked":14}}},"registrar":{"states":{"current":14,"update":14},"writes":{"success":14,"total":14}},"system":{"load":{"1":2.26,"15":2.55,"5":2.63,"norm":{"1":0.0628,"15":0.0708,"5":0.0731}}}}}}

Scrolling continuously, should I just let it continue. Is it because the filebeat indices where removed?

Thank you.

---

<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:** [April 19, 2021, 11:31pm UTC](https://discuss.elastic.co/t/filebeat-e-running-for-a-long-time/270292/2 "2021-04-19T23:31:10Z")

</div>

It sounds like you are simply calling Filebeat and it's running, rather than just the setup command.

Can you please share the command that you ran, as well as the output?

---

<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:** [May 18, 2021, 1:31am UTC](https://discuss.elastic.co/t/filebeat-e-running-for-a-long-time/270292/3 "2021-05-18T01:31:45Z")

</div>

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