Agent starting multiple instances of filebeat or metricbeat and goes into tight restart loop for the beat process.
More than 50% of agent runs fail while starting multiple beats processes due to the conflict on data path, which results in the tight restart loop for the beat.
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).
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).
This is documented here as well:
elastic/beats#32673 (comment)
Running off of the latest V2 branch:
https://github.com/elastic/elastic-agent/tree/feature-arch-v2
Steps to reproduce:
- Enroll the agent from the command line
- Run the agent from the command line
Agent starting multiple instances of filebeat or metricbeat and goes into tight restart loop for the beat process.
More than 50% of agent runs fail while starting multiple beats processes due to the conflict on data path, which results in the tight restart loop for the beat.
This is documented here as well:
elastic/beats#32673 (comment)
Running off of the latest V2 branch:
https://github.com/elastic/elastic-agent/tree/feature-arch-v2
Steps to reproduce: