Data path already locked by another beat. Unable to start Harvester

Elastic Stack Beats
1

Hi ! i am getting following error when i used "filebeat -e" and unable to start the harvester. I don't have any other beat running. And I have filebeat.lock in /usr/share/filebeat/data. I removed it and redeployed it again, but it's the same after deployment no change. Can someone please help me with this.

2021-04-04T20:24:52.905Z INFO instance/beat.go:660 Home path: [/usr/share/filebeat] Config path: [/usr/share/filebeat] Data path: [/usr/share/filebeat/data] Logs path: [/usr/share/filebeat/logs]
2021-04-04T20:24:52.905Z INFO instance/beat.go:668 Beat ID: 51802400-14ef-4202-b176-4e3355cc4753
2021-04-04T20:24:52.906Z INFO instance/beat.go:405 filebeat stopped.
2021-04-04T20:24:52.906Z ERROR instance/beat.go:971 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).

2

Hi Shann.
Are you sure that there is no other filebeat running on the host?.
You could try to start th beat using another data path by setting the variable path.data to another value like /var/lib/data-filebeat in the filebeat.yaml .

3

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