# Metricbeat service get stopped after service start

**URL:** <https://discuss.elastic.co/t/metricbeat-service-get-stopped-after-service-start/336567>\
**Category:** Metrics\
**Created:** [June 21, 2023, 11:00am UTC](https://discuss.elastic.co/t/metricbeat-service-get-stopped-after-service-start/336567 "2023-06-21T11:00:51Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Wolfram\_Haussig](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/wolfram_haussig/32/70528_2.png) [@Wolfram\_Haussig](https://discuss.elastic.co/u/Wolfram_Haussig)\
**Post date:** [June 22, 2023, 6:00am UTC](https://discuss.elastic.co/t/metricbeat-service-get-stopped-after-service-start/336567/2 "2023-06-22T06:00:53Z")

</div>

Hi,

I found a similar issue [here](https://github.com/elastic/apm-server/issues/6238) regarding the apm-server, so you could try this workaround first and disable [seccomp](https://www.elastic.co/guide/en/beats/metricbeat/current/linux-seccomp.html):

```yml
seccomp:
  enabled: false

```

Best regards  
Wolfram

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-service-get-stopped-after-service-start/336567)._