Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Filebeat lock #27

Open
Pete920 opened this issue Aug 19, 2024 · 0 comments
Open

Filebeat lock #27

Pete920 opened this issue Aug 19, 2024 · 0 comments

Comments

@Pete920
Copy link

Pete920 commented Aug 19, 2024

Hi,

After container started, i go into filebeat container and i can see filebeat.lock in DATA folder. And run ' filebeat -e -d "*" ' get below error message:
{"log.level":"error","@timestamp":"2024-08-19T06:23:12.949Z","log.origin":{"function":"github.com/elastic/beats/v7/libbeat/cmd/instance.handleError","file.name":"instance/beat.go","file.line":1345},"message":"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)","service.name":"filebeat","ecs.version":"1.6.0"}
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)

I am trying to use this cluster for netflow monitoring. Please kindly help with this issue.

paste filebeat.yml and docker-compose.yml here
filebeat.yml.txt

docker-compose.yml.txt

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant