# Part of the file bit 'daemonset pod' is CrashLoopBackOff

**URL:** <https://discuss.elastic.co/t/part-of-the-file-bit-daemonset-pod-is-crashloopbackoff/334261>\
**Category:** Beats\
**Tags:** docker, filebeat\
**Created:** [May 25, 2023, 12:09am UTC](https://discuss.elastic.co/t/part-of-the-file-bit-daemonset-pod-is-crashloopbackoff/334261 "2023-05-25T00:09:18Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![oliverpark999](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/oliverpark999/32/121408_2.png) [@oliverpark999](https://discuss.elastic.co/u/oliverpark999)\
**Post date:** [May 25, 2023, 12:09am UTC](https://discuss.elastic.co/t/part-of-the-file-bit-daemonset-pod-is-crashloopbackoff/334261/1 "2023-05-25T00:09:18Z")

</div>

I configured Filebeat + Logstash in Kubernetes environment.  
It is working normally, but some of the Filebeat 'demonsets' do not appear to be working normally.  
What kind of problem?

```auto
filebeat-1 1/1 Running 0                 
filebeat-2 1/1 Running 0                 
filebeat-3 1/1 Running 0                 
filebeat-4 1/1 Running 0                 
filebeat-5 1/1 Running 0                 
filebeat-6 1/1 Running 0                 
filebeat-7 1/1 Running 0                 
filebeat-8 0/1 CrashLoopBackOff 212 (75s ago)     
filebeat-9 0/1 OOMKilled 212 (5m17s ago)   
filebeat-10 1/1 Running 0                 
filebeat-11 1/1 Running 0                 
filebeat-12 1/1 Running 7 (17h ago)       
filebeat-13 1/1 Running 0                 
filebeat-14 1/1 Running 0                 
filebeat-15 1/1 Running 0                 

```

- Version : [docker.elastic.co/beats/filebeat-oss:8.4.0](http://docker.elastic.co/beats/filebeat-oss:8.4.0)

---

<div class="post-metadata">

**Author:** ![stephenb](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/stephenb/32/40856_2.png) [@stephenb](https://discuss.elastic.co/u/stephenb)\
**Post date:** [May 29, 2023, 12:52am UTC](https://discuss.elastic.co/t/part-of-the-file-bit-daemonset-pod-is-crashloopbackoff/334261/2 "2023-05-29T00:52:13Z")

</div>

Hi @oliverpark999 welcome to the community.

> [@oliverpark999](#):
>
> `OOMKilled`

Indicates that it filebeat ran Out Of Memory- OOM, you need to provide more resources to filebeat in the pod spec specifically memory.

Increase the memory, these are the defaults perhaps double the memory

```auto
        resources:
          limits:
            memory: 200Mi
          requests:
            cpu: 100m
            memory: 100Mi

```

Share your filebeat manifest.

---

<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 26, 2023, 2:52am UTC](https://discuss.elastic.co/t/part-of-the-file-bit-daemonset-pod-is-crashloopbackoff/334261/3 "2023-06-26T02:52:38Z")

</div>

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