Error loading config file when running Heartbeat without --path.config flag

I installed Heartbeat using RPM.

Now, when I try to run it without any options it gives the following error:

[elastic@local-central bin]$ ./heartbeat
heartbeat2017/11/08 13:27:44.630019 beat.go:346: CRIT Exiting: error loading config file: stat heartbeat.yml: no 
such file or directory
Exiting: error loading config file: stat heartbeat.yml: no such file or directory

The yml file is in /etc/heartbeat (default path for RPM installations):

[elastic@local-central bin]$ ll /etc/heartbeat/
total 60
-rw-r--r--. 1 root root 29709 Oct  6 22:31 heartbeat.full.yml
-rw-r--r--. 1 root root  4996 Oct  6 22:31 heartbeat.template-es2x.json
-rw-r--r--. 1 root root  4164 Oct  6 22:31 heartbeat.template-es6x.json
-rw-r--r--. 1 root root  4164 Oct  6 22:31 heartbeat.template.json
-rw-------. 1 root root  3065 Nov  8 13:38 heartbeat.yml

As far as I can see the ownership and permissions are ok too. Anyhow, I tried using --strict.perms=false but that didn't help. I also added the -e and -d "*" flags but that doesn't give me more information.

The only way to get it to run is by explicitly setting the --path.config option and using sudo :

[elastic@local-central bin]$ sudo ./heartbeat --path.config /etc/heartbeat/

So I'm a bit confused now: am I supposed to leave my heartbeat.yml file in /etc/logstash (which is the default config directory for RPM installations according to the documentation) or will he go looking for it in the home directory (/usr/share/heartbeat/)?

Thanks in advance for clarifying this :slight_smile:

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