# Data path already locked by another beat

**URL:** <https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [February 18, 2020, 7:11pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852 "2020-02-18T19:11:38Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![yodog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yodog/32/4822_2.png) [@yodog](https://discuss.elastic.co/u/yodog)\
**Post date:** [February 18, 2020, 7:11pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/1 "2020-02-18T19:11:38Z")

</div>

after upgrading from 7.5.1 to 7.6.0 my filebeat breaks with error `data path already locked by another beat`

i have two instances of filebeat running for a very long time, one reading a specific set of files and sending to logstash, and the other one reading another set of files and sending to elasticsearch.

could not find this `breaking change` on the docs below.

[https://www.elastic.co/guide/en/beats/libbeat/7.6/breaking-changes-7.6.html](https://www.elastic.co/guide/en/beats/libbeat/7.6/breaking-changes-7.6.html)  
and  
[https://www.elastic.co/guide/en/beats/libbeat/7.6/release-notes-7.6.0.html](https://www.elastic.co/guide/en/beats/libbeat/7.6/release-notes-7.6.0.html)

---

<div class="post-metadata">

**Author:** ![yodog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yodog/32/4822_2.png) [@yodog](https://discuss.elastic.co/u/yodog)\
**Post date:** [February 19, 2020, 12:26pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/2 "2020-02-19T12:26:10Z")

</div>

**filebeat.elasticsearch.yml**

```
filebeat.registry.path: registry.elasticsearch

processors:
- add_host_metadata:
    netinfo.enabled: true

filebeat.config.modules:
  path: ${path.config}/modules.d/*.yml
  reload.enabled: true
  reload.period: 1h

filebeat.modules:
- module: apache
  access:
    var.paths: ["/var/log/apache2/*/access.log"]
  error:
    var.paths: ["/var/log/apache2/*/error.log"]

output.elasticsearch:
  compression_level : 5
  hosts : elastic-zmb-pool
  loadbalance : true
  worker : 2
```

---

<div class="post-metadata">

**Author:** ![yodog](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yodog/32/4822_2.png) [@yodog](https://discuss.elastic.co/u/yodog)\
**Post date:** [February 19, 2020, 12:26pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/3 "2020-02-19T12:26:41Z")

</div>

**filebeat.logstash.yml**

```
filebeat.registry.path: registry.logstash

processors:
- add_host_metadata:
    netinfo.enabled: true

filebeat.inputs:
- type : log
  enabled : true
  exclude_files : ['.gz$']
  fields_under_root : true
  tags : ["zimbra"]
  paths:
    - /opt/zimbra/log/access_log.*
    - /opt/zimbra/log/audit.log
    - /opt/zimbra/log/mailbox.log
    - /opt/zimbra/log/nginx.log
    - /opt/zimbra/log/nginx.access.log
    - /opt/zimbra/log/sync.log
    - /var/log/zimbra.log

output.logstash:
  hosts : elastic-zmb-pool
  loadbalance : true
```

---

<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 19, 2020, 3:29pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/4 "2020-02-19T15:29:55Z")

</div>

Hmmm, you're right that this [important breaking change](https://github.com/elastic/beats/pull/14069) is not in the release notes or breaking changes doc for 7.6.0. I'm terribly sorry about that and am [working](https://github.com/elastic/beats/pull/16424) to get it documented ASAP!

As for fixing your setup to account for this change, please edit both your Filebeat configuration files and add a `path.data` setting. Make sure to set it's values to unique directory locations. Then you should set `filebeat.registry.path` to start with `${path.data}/`.

Shaunak

---

<div class="post-metadata">

**Author:** ![florinsfetea](https://avatars.discourse-cdn.com/v4/letter/f/9fc29f/32.png) [@florinsfetea](https://discuss.elastic.co/u/florinsfetea)\
**Post date:** [February 24, 2020, 9:11am UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/5 "2020-02-24T09:11:20Z")

</div>

Are you referring here to this path.data?  
[https://www.elastic.co/guide/en/beats/filebeat/master/configuration-path.html#\_data](https://www.elastic.co/guide/en/beats/filebeat/master/configuration-path.html#_data)

---

<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 24, 2020, 7:09pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/6 "2020-02-24T19:09:00Z")

</div>

That's correct @florinsfetea.

---

<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:** [March 23, 2020, 7:09pm UTC](https://discuss.elastic.co/t/data-path-already-locked-by-another-beat/219852/7 "2020-03-23T19:09:01Z")

</div>

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