Filebeat stops sending logs to logstash, "message":"Harvester could not be started on existing file

Filebeat stops sending logs to logstash and needs a manual restart to resume. Logs for specific containers are stopped, while other container's logs are still going to logstash.

{"log.level":"error","@timestamp":"2023-10-15T10:31:33.130Z","log.logger":"input","log.origin":{"file.name":"log/input.go","file.line":581},"message":"Harvester could not be started on existing file: /var/log/containers/test-0_default_test-af0265487cd287889e9d4e3c079ec488036e8513bfe96e2b7442be7dffb5648a.log, Err: registry already stopped","service.name":"filebeat","input_id":"23baecfc-7cc6-42bf-9745-a5c5dcb32f63","source_file":"/var/log/containers/test-0_default_test-af0265487cd287889e9d4e3c079ec488036e8513bfe96e2b7442be7dffb5648a.log","state_id":"native::5676491-64768","finished":false,"os_id":"5676491-64768","old_source":"/var/log/containers/test-0_default_test-af0265487cd287889e9d4e3c079ec488036e8513bfe96e2b7442be7dffb5648a.log","old_finished":true,"old_os_id":"5676491-64768","ecs.version":"1.6.0"}

Is there any solution to this issue?

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