No data has been received from Heartbeat yet

Elastic Stack Beats
1

Hello, could you help me.
Version 7.6.0, CentOS 7.
Doesn't work Uptime Monitor.

~]$ sudo heartbeat test config
Config OK

~]$ sudo heartbeat test output
elasticsearch: http://host_ip:9200...
parse url... OK
connection...
parse host... OK
dns lookup... OK
addresses: host_ip
dial up... OK
TLS... WARN secure connection disabled
talk to server... OK
version: 7.6.0

$ sudo heartbeat -e
2020-02-22T00:16:59.545+0400 INFO instance/beat.go:622 Home path: [/usr/share/heartbeat] Config path: [/etc/heartbeat] Data path: [/var/lib/heartbeat] Logs path: [/var/log/heartbeat]
2020-02-22T00:16:59.546+0400 INFO instance/beat.go:630 Beat ID: b6347f49-c06c-46fa-9f46-649f2f07bf7b
2020-02-22T00:16:59.551+0400 INFO instance/beat.go:380 heartbeat stopped.
2020-02-22T00:16:59.551+0400 ERROR instance/beat.go:933 Exiting: data path already locked by another beat
Exiting: data path already locked by another beat

2

Hi @IMagalashvili - Welcome to our community forums!

From the Heartbeat logs you provided: ERROR instance/beat.go:933 Exiting: data path already locked by another beat. This means that there is another instance of Heartbeat running. I am guessing that you are already running Heartbeat as a service. So before running Heartbeat with command line, you may want to stop the Heartbeat service or stop other Hearbeat instances that may be running on your system.

I hope that helps.

3

Thank you for replay!

I found the issue, there was an error in .yml file, which I found with "heartbeat test config /etc/heartbeat/heartbeat.yml" command. This was an issue, the data was not receive.

4

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