Filebeat logs
Jump to navigation
Jump to search
Contents
ERROR
2020-08-11T00:03:08.244Z ERROR logstash/async.go:256 Failed to publish events caused by: read tcp 10.10.XX.xx:52732->10.10.yy.XX:5044: i/o timeout
2020-08-11T00:03:09.354Z ERROR pipeline/output.go:121 Failed to publish events: client is not connected
2020-08-11T08:25:13.378Z ERROR log/input.go:501 Harvester could not be started on new file: /var/lib/dcoker/containers/z2f539b9a4af9638273928b1e4600c1ce179ff061b9c9b13ddcffb15e7a3df/d0b2f539b8a4af9638273928b1e4600c1ce179ff061b9c9b13ddcffb15e7a3dt-json.log, Err: error setting up harvester: Harvester setup failed. Unexpected file opening error: file info is not identical with opened file. Aborting harvesting and retrying file later again
2020-08-11T23:22:45.111Z ERROR docker/watcher.go:303 Error watching for docker events: context deadline exceeded
2020-08-10T14:18:45.090Z ERROR log/input.go:250 File cleanup state update error: input outlet closed
2020-08-10T14:18:45.089Z ERROR log/input.go:501 Harvester could not be started on new file: /var/logs/xxx.log, Err: registry already stopped
WARN
2020-08-10T14:18:46.791Z WARN beater/filebeat.go:152 Filebeat is unable to load the Ingest Node pipelines for the configured modules because the Elasticsearch output is not configured/enabled. If you have already loaded the Ingest Node pipelines or are using Logstash pipelines, you can ignore this warning.
Related
See also
filebeat [ modules | test | setup | export ], filebeat --help- Filebeat,
filebeat.yml, Filebeat logs
Advertising:
