Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data)

Muhammad_Junaid · February 19, 2025, 8:53am

Hi,
I have installed the filebeat to multiple EC2 machine and shipping logs to Elasticsearch. version is same for all instances. Service is working file and making connection to ELK stack but getting problem that logs are not showing in kibana and getting below error in filebeat server

Error:

ERROR	instance/beat.go:1027	Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).

Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data).

Topic		Replies	Views
Kibana is not getting any logs Beats filebeat	3	315	October 26, 2020
Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data) Beats	3	4340	October 4, 2022
[Solved] Data path already locked by another beat Beats filebeat	2	12708	February 21, 2021
Exiting: data path already locked by another beat Beats filebeat	4	5661	April 3, 2020
Multiple beats are not sharing the same data path Beats filebeat	2	928	June 17, 2022

Exiting: data path already locked by another beat. Please make sure that multiple beats are not sharing the same data path (path.data)

Error:

Related topics