# 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:** 18\
**Page:** 1

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [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/1 "2020-12-09T09:24:45Z")

</div>

Hi all,  
I configured metricbeat on my server for collecting both system & apache data with default module but only system data from host showed on kibana. The apache dashboard is empty data and don't know the reason.  
here is my apache.yml module:  
# Module: apache  
# Docs: [https://www.elastic.co/guide/en/beats/metricbeat/7.9/metricbeat-module-apache.html](https://www.elastic.co/guide/en/beats/metricbeat/7.9/metricbeat-module-apache.html)

```
- module: apache
  metricsets:
    - status
  period: 10s
  hosts: ["http://127.0.0.1"]
  #username: "user"
  #password: "secret"

```

What else I need to config or check to resolve the problem?  
Thanks

---

<div class="post-metadata">

**Author:** ![Mario\_Castro](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/mario_castro/32/35107_2.png) [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)\
**Post date:** [December 9, 2020, 10:37am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/2 "2020-12-09T10:37:34Z")

</div>

Hi @Minh_Ti_n_Tr_n 🙂

Which steps did you follow on the cli to activate the module? did you execute `metricbeat modules enable apache` for example? Can you also paste your `metricbeat.yml`?

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 4:20am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/3 "2020-12-10T04:20:30Z")

</div>

Yes I ran that command  
Here is metricbeat.yml  
###################### Metricbeat Configuration Example #######################

```
# This file is an example configuration file highlighting only the most common
# options. The metricbeat.reference.yml file from the same directory contains all the
# supported options with more comments. You can use it as a reference.
#
# You can find the full configuration reference here:
# https://www.elastic.co/guide/en/beats/metricbeat/index.html

# =========================== Modules configuration ============================

metricbeat.config.modules:
  # Glob pattern for configuration loading
  path: ${path.config}/modules.d/*.yml

  # Set to true to enable config reloading
  reload.enabled: false

  # Period on which files under path should be checked for changes
  #reload.period: 10s

# ======================= Elasticsearch template setting =======================

setup.template.settings:
  index.number_of_shards: 1
  index.codec: best_compression
  #_source.enabled: false

# ================================== General ===================================

# The name of the shipper that publishes the network data. It can be used to group
# all the transactions sent by a single shipper in the web interface.
#name:

# The tags of the shipper are included in their own field with each
# transaction published.
#tags: ["service-X", "web-tier"]

# Optional fields that you can specify to add additional information to the
# output.
#fields:
# env: staging

# ================================= Dashboards =================================
# These settings control loading the sample dashboards to the Kibana index. Loading
# the dashboards is disabled by default and can be enabled either by setting the
# options here or by using the `setup` command.
#setup.dashboards.enabled: false

# The URL from where to download the dashboards archive. By default this URL
# has a value which is computed based on the Beat name and version. For released
# versions, this URL points to the dashboard archive on the artifacts.elastic.co
# website.
#setup.dashboards.url:

# =================================== Kibana ===================================

# Starting with Beats version 6.0.0, the dashboards are loaded via the Kibana API.
# This requires a Kibana endpoint configuration.
setup.kibana:

  # Kibana Host
  # Scheme and port can be left out and will be set to the default (http and 5601)
  # In case you specify and additional path, the scheme is required: http://localhost:5601/path
  # IPv6 addresses should always be defined as: https://[2001:db8::1]:5601
  host: "https://192.168.87.47:443"
  ssl.verification_mode: "none"
  # Kibana Space ID
  # ID of the Kibana Space into which the dashboards should be loaded. By default,
  # the Default Space will be used.
  #space.id:

# =============================== Elastic Cloud ================================

# These settings simplify using Metricbeat with the Elastic Cloud (https://cloud.elastic.co/).

# The cloud.id setting overwrites the `output.elasticsearch.hosts` and
# `setup.kibana.host` options.
# You can find the `cloud.id` in the Elastic Cloud web UI.
#cloud.id:

# The cloud.auth setting overwrites the `output.elasticsearch.username` and
# `output.elasticsearch.password` settings. The format is `<user>:<pass>`.
#cloud.auth:

# ================================== Outputs ===================================

# Configure what output to use when sending the data collected by the beat.

# ---------------------------- Elasticsearch Output ----------------------------
output.elasticsearch:
  # Array of hosts to connect to.
  hosts: ["https://192.168.87.47:9200"]

  # Protocol - either `http` (default) or `https`.
  #protocol: "https"

  # Authentication credentials - either API key or username/password.
  #api_key: "id:api_key"
  username: "elastic"
  password: "<password>"
  ssl.verification_mode: "none"

# ------------------------------ Logstash Output -------------------------------
#output.logstash:
  # The Logstash hosts
  #hosts: ["localhost:5044"]

  # Optional SSL. By default is off.
  # List of root certificates for HTTPS server verifications
  #ssl.certificate_authorities: ["/etc/pki/root/ca.pem"]

  # Certificate for SSL client authentication
  #ssl.certificate: "/etc/pki/client/cert.pem"

  # Client Certificate Key
  #ssl.key: "/etc/pki/client/cert.key"

# ================================= Processors =================================

# Configure processors to enhance or manipulate events generated by the beat.

processors:
  - add_host_metadata: ~
  - add_cloud_metadata: ~
  - add_docker_metadata: ~
  - add_kubernetes_metadata: ~

# ================================== Logging ===================================

# Sets log level. The default log level is info.
# Available log levels are: error, warning, info, debug
#logging.level: debug

# At debug level, you can selectively enable logging only for some components.
# To enable all selectors use ["*"]. Examples of other selectors are "beat",
# "publish", "service".
#logging.selectors: ["*"]

# ============================= X-Pack Monitoring ==============================
# Metricbeat can export internal metrics to a central Elasticsearch monitoring
# cluster. This requires xpack monitoring to be enabled in Elasticsearch. The
# reporting is disabled by default.

# Set to true to enable the monitoring reporter.
#monitoring.enabled: false

# Sets the UUID of the Elasticsearch cluster under which monitoring data for this
# Metricbeat instance will appear in the Stack Monitoring UI. If output.elasticsearch
# is enabled, the UUID is derived from the Elasticsearch cluster referenced by output.elasticsearch.
#monitoring.cluster_uuid:

# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well.
# Note that the settings should point to your Elasticsearch *monitoring* cluster.
# Any setting that is not set is automatically inherited from the Elasticsearch
# output configuration, so if you have the Elasticsearch output configured such
# that it is pointing to your Elasticsearch monitoring cluster, you can simply
# uncomment the following line.
#monitoring.elasticsearch:

# ============================== Instrumentation ===============================

# Instrumentation support for the metricbeat.
#instrumentation:
    # Set to true to enable instrumentation of metricbeat.
    #enabled: false

    # Environment in which metricbeat is running on (eg: staging, production, etc.)
    #environment: ""

    # APM Server hosts to report instrumentation results to.
    #hosts:
    # - http://localhost:8200

    # API Key for the APM Server(s).
    # If api_key is set then secret_token will be ignored.
    #api_key:

    # Secret token for the APM Server(s).
    #secret_token:

# ================================= Migration ==================================

# This allows to enable 6.7 migration aliases
#migration.6_to_7.enabled: true
```

---

<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:** [December 10, 2020, 5:26am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/4 "2020-12-10T05:26:58Z")

</div>

What is the output from `metricbeat modules list`?

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 6:18am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/5 "2020-12-10T06:18:16Z")

</div>

> [@warkolm](#):
>
> metricbeat modules list

Here

```
metricbeat modules list
Enabled:
apache
system

Disabled:
activemq
aerospike
appsearch
aws
azure
beat
beat-xpack
ceph
ceph-mgr
cloudfoundry
cockroachdb
consul
coredns
couchbase
couchdb
docker
dropwizard
elasticsearch
elasticsearch-xpack
envoyproxy
etcd
golang
googlecloud
graphite
haproxy
http
ibmmq
iis
istio
jolokia
kafka
kibana
kibana-xpack
kubernetes
kvm
linux
logstash
logstash-xpack
memcached
mongodb
mssql
munin
mysql
nats
nginx
openmetrics
oracle
php_fpm
postgresql
prometheus
rabbitmq
redis
redisenterprise
sql
stan
statsd
tomcat
traefik
uwsgi
vsphere
windows
zookeeper

```

---

<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:** [December 10, 2020, 6:19am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/6 "2020-12-10T06:19:24Z")

</div>

Thanks!  
Can you post your Metricbeat logs from startup onwards please?

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 6:33am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/7 "2020-12-10T06:33:21Z")

</div>

Sorry but I dont understand what logs from startup onwards is  
I will attach full metricbeat log

```
 systemctl status metricbeat -l
● metricbeat.service - Metricbeat is a lightweight shipper for metrics.
   Loaded: loaded (/lib/systemd/system/metricbeat.service; enabled; vendor preset: enabled)
   Active: active (running) since Thu 2020-12-10 06:31:15 UTC; 13s ago
     Docs: https://www.elastic.co/products/beats/metricbeat
 Main PID: 118846 (metricbeat)
    Tasks: 10 (limit: 9470)
   CGroup: /system.slice/metricbeat.service
           └─118846 /usr/share/metricbeat/bin/metricbeat --environment systemd -c /etc/metricbeat/metricbeat.yml --path.home /usr/share/metricbeat --path.con

Dec 10 06:31:16 server metricbeat[118846]: 2020-12-10T06:31:16.419Z INFO [index-management] idxmgmt/std.go:274 ILM policy success
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.419Z INFO [index-management] idxmgmt/std.go:407 Set setup.template
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.419Z INFO [index-management] idxmgmt/std.go:412 Set setup.template
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.419Z INFO [index-management] idxmgmt/std.go:446 Set settings.index
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.419Z INFO [index-management] idxmgmt/std.go:450 Set settings.index
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.421Z INFO template/load.go:89 Template metricbeat-7.9.3 already exists an
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.421Z INFO [index-management] idxmgmt/std.go:298 Loaded index templ
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.423Z INFO [index-management] idxmgmt/std.go:309 Write alias succes
Dec 10 06:31:16 eramba metricbeat[118846]: 2020-12-10T06:31:16.425Z INFO [publisher_pipeline_output] pipeline/output.go:151 Conne
Dec 10 06:31:25 eramba metricbeat[118846]: 2020-12-10T06:31:25.433Z INFO module/wrapper.go:259 Error fetching data for metricset apache.
lines 1-19/19 (END)
root@server:/var/log/metricbeat# cat metricbeat
2020-12-10T06:17:25.398Z INFO instance/beat.go:640 Home path: [/usr/share/metricbeat] Config path: [/etc/metricbeat] Data path: [/var/lib/metricbeat] Logs path: [/var/log/metricbeat]
2020-12-10T06:17:25.398Z INFO instance/beat.go:648 Beat ID: a5fe1b39-25bb-4dd8-a46f-95fcba08e5fa
```

---

<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:** [December 10, 2020, 6:34am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/8 "2020-12-10T06:34:22Z")

</div>

> [@Minh\_Ti\_n\_Tr\_n](#):
>
> `Error fetching data for metricset apache`

That's relevant. Is there more in `/var/log/metricbeat` that might reference apache?

---

<div class="post-metadata">

**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\
**Post date:** [December 10, 2020, 6:37am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/9 "2020-12-10T06:37:03Z")

</div>

What is the result of

```auto
curl http://127.0.0.1/status

```

It should be a lots of metrics there, if not, please check the apache configuration of server-status

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 6:39am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/10 "2020-12-10T06:39:17Z")

</div>

no more log relate to apache ☹

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 6:40am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/11 "2020-12-10T06:40:29Z")

</div>

```
curl http://127.0.0.1/status
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>302 Found</title>
</head><body>
<h1>Found</h1>
<p>The document has moved <a href="https://stagingdomain.com/status">here</a>.</p>
<hr>
<address>Apache/2.4.29 (Ubuntu) Server at 127.0.0.1 Port 80</address>
</body></html>

```

this is curl result

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 10, 2020, 9:14am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/12 "2020-12-10T09:14:53Z")

</div>

Some more information

```
    # metricbeat -e
    2020-12-10T09:08:53.492Z INFO instance/beat.go:640 Home path: [/usr/share/metricbeat] Config path: [/etc/metricbeat] Data path: [/var/lib/metricbeat] Logs path: [/var/log/metricbeat]
    2020-12-10T09:08:53.492Z INFO instance/beat.go:648 Beat ID: a5fe1b39-25bb-4dd8-a46f-95fcba08e5fa
    2020-12-10T09:08:53.494Z INFO instance/beat.go:387 metricbeat stopped.
    2020-12-10T09:08:53.495Z ERROR instance/beat.go:951 Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
    Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
```

---

<div class="post-metadata">

**Author:** ![fadjar340](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/fadjar340/32/43610_2.png) [@fadjar340](https://discuss.elastic.co/u/fadjar340)\
**Post date:** [December 10, 2020, 11:05am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/13 "2020-12-10T11:05:51Z")

</div>

You need to set the apache server-status to get the complete metric of Apache.

> **[How do I enable the server-status page on my server? | Media Temple Community](https://mediatemple.net/community/products/dv/204404734/how-do-i-enable-the-server-status-page-on-my-server)**

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 11, 2020, 2:12am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/14 "2020-12-11T02:12:46Z")

</div>

Still have problem with the locked data path

```
2020-12-11T02:11:56.202Z ERROR instance/beat.go:951 Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).
```

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 14, 2020, 6:48am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/15 "2020-12-14T06:48:49Z")

</div>

Still not have any solution! ☹

---

<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?

---

<div class="post-metadata">

**Author:** ![Minh\_Ti\_n\_Tr\_n](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/minh_ti_n_tr_n/32/60754_2.png) [@Minh\_Ti\_n\_Tr\_n](https://discuss.elastic.co/u/Minh_Ti_n_Tr_n)\
**Post date:** [December 15, 2020, 9:05am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/17 "2020-12-15T09:05:20Z")

</div>

Below is the result. They are match

```
root@server:/home/tienmtran# ps ax | grep metric
 70894 ? Ssl 58:00 /usr/share/metricbeat/bin/metricbeat --environment systemd -c /etc/metricbeat/metricbeat.yml --path.home /usr/share/metricbeat --path.config /etc/metricbeat --path.data /var/lib/metricbeat --path.logs /var/log/metricbeat
111098 pts/0 S+ 0:00 grep --color=auto metric
root@server:/home/tienmtran# lslocks | grep /var/lib/metricbeat/
metricbeat 70894 FLOCK 0B WRITE 0 0 0 /var/lib/metricbeat/metricbeat.lock
```

---

<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:** [January 12, 2021, 11:05am UTC](https://discuss.elastic.co/t/metricbeat-only-run-system-module-instead-of-running-both-system-and-apache-module/258098/18 "2021-01-12T11:05:23Z")

</div>

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