# Metricbeat only run system module instead of running both system and apache module

**URL:** <https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098>\
**Category:** Beats\
**Tags:** metricbeat\
**Created:** [December 9, 2020, 9:24am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098 "2020-12-09T09:24:45Z")\
**Posts on this page:** 1\
**Showing post:** 16

<div class="post-metadata">

**Author:** ![borna\_talebi](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/borna_talebi/32/76317_2.png) [@borna\_talebi](https://discuss.elastic.co/u/borna_talebi)\
**Post date:** [December 14, 2020, 7:40am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/16 "2020-12-14T07:40:15Z")

</div>

So are you positive that there aren't any other beats running?  
What's the output of `lslocks | grep /var/lib/metricbeat/` ?  
Is the output PID matches your current metricbeat PID?

---

_[View the full topic](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098)._