# No data has been received from Heartbeat yet
**URL:** https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448
**Category:** Beats
**Tags:** heartbeat
**Created:** [February 21, 2020, 8:20pm UTC](https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448 "2020-02-21T20:20:31Z")
**Posts on this page:** 4
**Page:** 1
### Author:  [@IMagalashvili](https://discuss.elastic.co/u/IMagalashvili)
#### Post date: [February 21, 2020, 8:20pm UTC](https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448/1 "2020-02-21T20:20:31Z")
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
---
### Author:  [@ropc](https://discuss.elastic.co/u/ropc)
#### Post date: [February 22, 2020, 2:09am UTC](https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448/2 "2020-02-22T02:09:17Z")
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](https://www.elastic.co/guide/en/beats/heartbeat/current/running-with-systemd.html#running-with-systemd). 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.
---
### Author:  [@IMagalashvili](https://discuss.elastic.co/u/IMagalashvili)
#### Post date: [February 26, 2020, 5:58am UTC](https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448/3 "2020-02-26T05:58:33Z")
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.
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [March 25, 2020, 5:58am UTC](https://discuss.elastic.co/t/no-data-has-been-received-from-heartbeat-yet/220448/4 "2020-03-25T05:58:34Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.