Filebeat not sending data to logstash getting EOF and tcp io timeout

Hi Team,

I am trying to send logs using filebeat to logstash. It was working fine, but then suddenly stopped working and is no longer working now. Can you kindly help me fix this.

2017/03/02 16:37:37.620616 beat.go:177: INFO Setup Beat: filebeat; Version: 5.1.2
2017/03/02 16:37:37.620760 logstash.go:90: INFO Max Retries set to: 3
2017/03/02 16:37:37.620773 logp.go:219: INFO Metrics logging every 30s
2017/03/02 16:37:37.620942 outputs.go:106: INFO Activated logstash as output plugin.
2017/03/02 16:37:37.622240 publish.go:291: INFO Publisher name: tstr500242
2017/03/02 16:37:37.632345 async.go:63: INFO Flush Interval set to: 1s
2017/03/02 16:37:37.632380 async.go:64: INFO Max Bulk Size set to: 2048
2017/03/02 16:37:37.632869 beat.go:207: INFO filebeat start running.
2017/03/02 16:37:37.633065 registrar.go:85: INFO Registry file set to: /u/tstr500242/wmqiadm/filebeat/filebeat-5.1.2-linux-x86_64/data/registry
2017/03/02 16:37:37.633138 registrar.go:106: INFO Loading registrar data from /u/tstr500242/wmqiadm/filebeat/filebeat-5.1.2-linux-x86_64/data/registry
2017/03/02 16:37:37.634438 registrar.go:123: INFO States Loaded from registrar: 4
2017/03/02 16:37:37.634515 crawler.go:34: INFO Loading Prospectors: 1
2017/03/02 16:37:37.634729 registrar.go:236: INFO Starting Registrar
2017/03/02 16:37:37.634749 prospector_log.go:57: INFO Prospector with previous states loaded: 2
2017/03/02 16:37:37.634877 sync.go:41: INFO Start sending events to output
2017/03/02 16:37:37.634985 crawler.go:46: INFO Loading Prospectors completed. Number of prospectors: 1
2017/03/02 16:37:37.635025 crawler.go:61: INFO All prospectors are initialised and running with 4 states to persist
2017/03/02 16:37:37.635057 spooler.go:63: INFO Starting spooler: spool_size: 2048; idle_timeout: 5s
2017/03/02 16:37:37.635081 prospector.go:111: INFO Starting prospector of type: log
2017/03/02 16:37:37.635644 log.go:84: INFO Harvester started for file: /u/wmb/brokerlog/tinyBroker.log
2017/03/02 16:37:47.709450 sync.go:85: ERR Failed to publish events caused by: EOF
2017/03/02 16:37:47.709526 single.go:91: INFO Error publishing events (retrying): EOF
2017/03/02 16:38:07.621191 logp.go:230: INFO Non-zero metrics in the last 30s: filebeat.harvester.open_files=1 filebeat.harvester.running=1 libbeat.logstash.publish.read_errors=1 libbeat.logstash.publish.write_bytes=746 libbeat.logstash.published_but_not_acked_events=2 libbeat.publisher.published_events=2 filebeat.harvester.started=1 libbeat.logstash.call_count.PublishEvents=2
2017/03/02 16:38:18.732019 sync.go:85: ERR Failed to publish events caused by: read tcp 10.246.113.88:59932->10.74.66.29:5044: i/o timeout
2017/03/02 16:38:18.732068 single.go:91: INFO Error publishing events (retrying): read tcp 10.246.113.88:59932->10.74.66.29:5044: i/o timeout
2017/03/02 16:38:25.833157 sync.go:85: ERR Failed to publish events caused by: EOF
2017/03/02 16:38:25.833201 single.go:91: INFO Error publishing events (retrying): EOF
2017/03/02 16:38:37.621177 logp.go:230: INFO Non-zero metrics in the last 30s: libbeat.logstash.published_but_not_acked_events=4 libbeat.logstash.call_count.PublishEvents=2 libbeat.logstash.publish.read_errors=2 libbeat.logstash.publish.write_bytes=586
2017/03/02 16:38:59.888940 sync.go:85: ERR Failed to publish events caused by: read tcp 10.246.113.88:60616->10.74.66.29:5044: i/o timeout
2017/03/02 16:38:59.888987 single.go:91: INFO Error publishing events (retrying): read tcp 10.246.113.88:60616->10.74.66.29:5044: i/o timeout
2017/03/02 16:39:07.621185 logp.go:230: INFO Non-zero metrics in the last 30s: libbeat.logstash.publish.read_errors=1 libbeat.logstash.published_but_not_acked_events=2
2017/03/02 16:39:12.932352 sync.go:85: ERR Failed to publish events caused by: EOF
2017/03/02 16:39:12.932399 single.go:91: INFO Error publishing events (retrying): EOF

Regards,
Sanchita

There seems to be an issue with your connection to LS which can have different reasons. Best do a quick search for Failed to publish events caused by: EOF in the forum and you will find lots of threads with similar problems and solutions to it.

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