Getting Error "Exiting: /usr/share/filebeat/data/filebeat.lock: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data)"

Elastic Stack Beats
1

Hi Everyone,

We have a central system to monitor logs for all the K8s clusters pods including specific label.
There are specific pods for which we want to setup a different pre-processing system but when we are deploying a different filebeat daemon set it is throwing us below error:
"Exiting: /usr/share/filebeat/data/filebeat.lock: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data)"

The error is expected, but has anybody faced this scenario and can help any alternative for this.
We have given below path in filebeat:-
paths:
- /var/log/containers/*${data.kubernetes.container.id}.log
And redirected our application log to stdout.

2

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