# Metricbeat not able to apcahe module
**URL:** https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758
**Category:** Beats
**Tags:** metricbeat
**Created:** [October 17, 2018, 6:11am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758 "2018-10-17T06:11:24Z")
**Posts on this page:** 5
**Page:** 1
### Author:  [@sukarn001](https://discuss.elastic.co/u/sukarn001)
#### Post date: [October 17, 2018, 6:11am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758/1 "2018-10-17T06:11:24Z")
Hello,
I installed metricbeat from RPM in rhel7 64bit, I am able to start it as a service. however when I am running ./metricbeat modules list or any other command it is giving me error **Exiting: error loading config file: stat metricbeat.yml: no such file or directory**. I want to enable apache module but couldn't b'cos of this error.
I have also tried running command ./metricbeat -e -c /etc/metricbeat/metricbeat.yml, but then my complete terminal is getting blocked, it keeps showing output.
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [October 17, 2018, 7:54am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758/2 "2018-10-17T07:54:00Z")
Hi @sukarn001 🙂
When you run metricbeat without the `-c` flag, it looks in the current working directory for a file named `metricbeat.yml` to get the configuration. You can override this with the flag `-c` and make it point to, for example `/etc/metricbeat/metricbeat.yml` as you said.
Maybe you can share your configuration file? (`/etc/metricbeat/metricbeat.yml`)
Best regards
---
### Author:  [@sukarn001](https://discuss.elastic.co/u/sukarn001)
#### Post date: [October 17, 2018, 8:21am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758/3 "2018-10-17T08:21:35Z")
Hi,
Please find the metricbeat.yml file as follows:
```auto
###################### 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: true
# Period on which files under path should be checked for changes
reload.period: 30s
#==================== 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` CLI flag or the `setup` command.
#setup.dashboards.enabled: true
# 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: "localhost:5601"
#============================= 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: ["localhost:9200"]
# Optional protocol and basic auth credentials.
#protocol: "https"
#username: "elastic"
#password: "changeme"
#----------------------------- 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"
#================================ 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: ["*"]
#============================== Xpack 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.
#xpack.monitoring.enabled: false
# Uncomment to send the metrics to Elasticsearch. Most settings from the
# Elasticsearch output are accepted here as well. Any setting that is not set is
# automatically inherited from the Elasticsearch output configuration, so if you
# have the Elasticsearch output configured, you can simply uncomment the
# following line.
#xpack.monitoring.elasticsearch:
```
---
### Author:  [@Mario\_Castro](https://discuss.elastic.co/u/Mario_Castro)
#### Post date: [October 17, 2018, 8:53am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758/4 "2018-10-17T08:53:28Z")
If you installed metricbeat using RPM module you shouldn't refer to current working directory `./` when executing it. It should be on your path so that in can find the `modules.d` path that is referred in the configuration file `path: ${path.config}/modules.d/*.yml`
You can also add this at the end of your configuration file [https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-apache.html:](https://www.elastic.co/guide/en/beats/metricbeat/current/metricbeat-module-apache.html:)
```auto
metricbeat.modules:
- module: apache
metricsets: ["status"]
period: 10s
enabled: true
# Apache hosts
hosts: ["http://127.0.0.1"]
```
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [November 14, 2018, 8:53am UTC](https://discuss.elastic.co/t/metricbeat-not-able-to-apcahe-module/152758/5 "2018-11-14T08:53:29Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.