# MetricBeat Unknown or unexpected state \<P\> for process with pid 25

**URL:** <https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512>\
**Category:** Elasticsearch\
**Tags:** elastic-stack-monitoring\
**Created:** [July 1, 2020, 3:06pm UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512 "2020-07-01T15:06:06Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![vamshisiddarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamshisiddarth/32/82759_2.png) [@vamshisiddarth](https://discuss.elastic.co/u/vamshisiddarth)\
**Post date:** [July 1, 2020, 3:06pm UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512/1 "2020-07-01T15:06:07Z")

</div>

We have deployed metricbeat on our kubernetes cluster and everything is working as expected. But, noticing the pods continuously log the below error for the metricbeat pods.

```bash
2020-07-01T14:46:07.826Z ERROR process_summary/process_summary.go:102 Unknown or unexpected state <P> for process with pid 25

```

Could someone let me know how can we fix this. We are currently running our Kubernetes cluster on Fedora CoreOS

---

<div class="post-metadata">

**Author:** ![val](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/val/32/138203_2.png) [@val](https://discuss.elastic.co/u/val)\
**Post date:** [July 2, 2020, 6:53am UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512/2 "2020-07-02T06:53:26Z")

</div>

It looks like this issue: [https://github.com/elastic/beats/issues/6305](https://github.com/elastic/beats/issues/6305)

What version of CoreOS and Metricbeat are you running?

---

<div class="post-metadata">

**Author:** ![vamshisiddarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamshisiddarth/32/82759_2.png) [@vamshisiddarth](https://discuss.elastic.co/u/vamshisiddarth)\
**Post date:** [July 2, 2020, 7:15am UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512/3 "2020-07-02T07:15:43Z")

</div>

Hello Val,

We are currently using "Fedora CoreOS 32.20200601.3.0" and  
[docker.elastic.co/beats/metricbeat:7.8.0](http://docker.elastic.co/beats/metricbeat:7.8.0) image for the Metricbeat.

---

<div class="post-metadata">

**Author:** ![vamshisiddarth](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vamshisiddarth/32/82759_2.png) [@vamshisiddarth](https://discuss.elastic.co/u/vamshisiddarth)\
**Post date:** [July 3, 2020, 6:06pm UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512/4 "2020-07-03T18:06:13Z")

</div>

Hey Val, could you please let me know how can I fix this. Thank you.

---

<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:** [July 31, 2020, 6:06pm UTC](https://discuss.elastic.co/t/metricbeat-unknown-or-unexpected-state-p-for-process-with-pid-25/239512/5 "2020-07-31T18:06:13Z")

</div>

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