You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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
The text was updated successfully, but these errors were encountered: