# Exiting: data path already locked by another beat

**URL:** <https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 25, 2020, 12:35pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854 "2020-02-25T12:35:57Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![artherdent](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@artherdent](https://discuss.elastic.co/u/artherdent)\
**Post date:** [February 25, 2020, 12:35pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854/1 "2020-02-25T12:35:57Z")

</div>

Hi, i am new to Elasticstack and am trying to configure filebeat to send logs to logstash-7.6.0. When running ./filebeat -e -c filebeat.yml -d "publish"  
i am recieving  
Exiting: data path already locked by another beat.  
I am using basic configuration

filebeat.inputs:

- type: log  
enabled: true  
paths:  
-/home/wayne/project/logstash-tutorial.log

output.logstash:  
hosts: ["localhost:5044"]

Any help would be appreciated

---

<div class="post-metadata">

**Author:** ![shaunak](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/shaunak/32/6643_2.png) [@shaunak](https://discuss.elastic.co/u/shaunak)\
**Post date:** [February 25, 2020, 1:21pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854/2 "2020-02-25T13:21:02Z")

</div>

Hi @artherdent,

Welcome to the Elastic community forums!

Do you have another instance of Filebeat running on the same host? Or did you perhaps start a Filebeat instance in the past that somehow got killed abruptly?

Thanks,

Shaunak

---

<div class="post-metadata">

**Author:** ![artherdent](https://avatars.discourse-cdn.com/v4/letter/a/a183cd/32.png) [@artherdent](https://discuss.elastic.co/u/artherdent)\
**Post date:** [February 25, 2020, 6:57pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854/3 "2020-02-25T18:57:52Z")

</div>

Hi, thank you, that must have been the issue, restarted everything and all good.

---

<div class="post-metadata">

**Author:** ![galtryn](https://avatars.discourse-cdn.com/v4/letter/g/e480ec/32.png) [@galtryn](https://discuss.elastic.co/u/galtryn)\
**Post date:** [March 6, 2020, 1:52pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854/4 "2020-03-06T13:52:13Z")

</div>

We have just installed filebeat 7.6.1 on a new server and only have one filebeat instance running along with metricbeat and packetbeat. We are also experiencing this issue and have not been able to resolve it.

---

<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:** [April 3, 2020, 1:52pm UTC](https://discuss.elastic.co/t/exiting-data-path-already-locked-by-another-beat/220854/5 "2020-04-03T13:52:16Z")

</div>

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