Filebeat pods are in CrashLoopBackOff status in RHOCP4

Issue

• Filebeat pods are in CrashLoopBackOff state and facing multiple restarts.

• The logs of Filebeat pods populates error messages related to cannot obtain lockfile .

{"log.level":"error","@timestamp":"2023-01-19T09:14:25.499Z","log.origin":{"file.name":"instance/beat.go","file.line":1057},"message":"Exiting: cannot obtain lockfile: connot start, data directory belongs to process with pid 9","service.name":"filebeat","ecs.version":"1.6.0"}
Exiting: cannot obtain lockfile: connot start, data directory belongs to process with pid 9