# ELK stack file beat configuration issue single.go:77: INFO Error publishing events (retrying): EOF

**URL:** <https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [April 25, 2018, 12:47pm UTC](https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493 "2018-04-25T12:47:35Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dazith\_Kj](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@Dazith\_Kj](https://discuss.elastic.co/u/Dazith_Kj)\
**Post date:** [April 25, 2018, 12:47pm UTC](https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493/1 "2018-04-25T12:47:35Z")

</div>

I have configured an ELK stack in my local environment by following up the below document (link to the document)

> **[How To Install Elasticsearch, Logstash, and Kibana (ELK Stack) on Ubuntu 14.04...](https://www.digitalocean.com/community/tutorials/how-to-install-elasticsearch-logstash-and-kibana-elk-stack-on-ubuntu-14-04#test-filebeat-installation)**
>
> In this tutorial, we will go over the installation of the Elasticsearch ELK Stack on Ubuntu 14.04—that is, Elasticsearch 2.2.x, Logstash 2.2.x, and Kibana 4…

As per the documentation and per my understanding I have successfully completed the implementation. However, file beat client is not publishing data to the elasticSearch

filebeat -c /etc/filebeat/filebeat.yml -e -v

> 2018/04/25 12:02:14.609792 geolite.go:24: INFO GeoIP disabled: No paths were set under output.geoip.paths  
> 2018/04/25 12:02:14.610560 logstash.go:106: INFO Max Retries set to: 3  
> 2018/04/25 12:02:14.611332 outputs.go:126: INFO Activated logstash as output plugin.  
> 2018/04/25 12:02:14.612172 publish.go:288: INFO Publisher name: localhost  
> 2018/04/25 12:02:14.613198 async.go:78: INFO Flush Interval set to: 1s  
> 2018/04/25 12:02:14.613502 async.go:84: INFO Max Bulk Size set to: 1  
> 2018/04/25 12:02:14.614102 beat.go:168: INFO Init Beat: filebeat; Version: 1.3.1  
> 2018/04/25 12:02:14.615784 beat.go:194: INFO filebeat sucessfully setup. Start running.  
> 2018/04/25 12:02:14.615835 registrar.go:68: INFO Registry file set to: /var/lib/filebeat/registry  
> 2018/04/25 12:02:14.615859 registrar.go:80: INFO Loading registrar data from /var/lib/filebeat/registry  
> 2018/04/25 12:02:14.616068 prospector.go:133: INFO Set ignore\_older duration to 0s  
> 2018/04/25 12:02:14.616082 prospector.go:133: INFO Set close\_older duration to 1h0m0s  
> 2018/04/25 12:02:14.616091 prospector.go:133: INFO Set scan\_frequency duration to 10s  
> 2018/04/25 12:02:14.616100 prospector.go:93: INFO Input type set to: log  
> 2018/04/25 12:02:14.616109 prospector.go:133: INFO Set backoff duration to 1s  
> 2018/04/25 12:02:14.616118 prospector.go:133: INFO Set max\_backoff duration to 10s  
> 2018/04/25 12:02:14.616124 prospector.go:113: INFO force\_close\_file is disabled  
> 2018/04/25 12:02:14.616139 prospector.go:143: INFO Starting prospector of type: log  
> 2018/04/25 12:02:14.619449 log.go:115: INFO Harvester started for file: /var/log/auth.log  
> 2018/04/25 12:02:14.619690 spooler.go:77: INFO Starting spooler: spool\_size: 2048; idle\_timeout: 5s  
> 2018/04/25 12:02:14.620954 log.go:115: INFO Harvester started for file: /var/log/syslog  
> 2018/04/25 12:02:14.623061 crawler.go:78: INFO All prospectors initialised with 7 states to persist  
> 2018/04/25 12:02:14.623102 registrar.go:87: INFO Starting Registrar  
> 2018/04/25 12:02:14.623140 publish.go:88: INFO Start sending events to output  
> 2018/04/25 12:02:14.795533 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:14.795847 single.go:154: INFO send fail  
> 2018/04/25 12:02:14.795946 single.go:161: INFO backoff retry: 1s  
> 2018/04/25 12:02:15.807622 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:15.808011 single.go:154: INFO send fail  
> 2018/04/25 12:02:15.808087 single.go:161: INFO backoff retry: 2s  
> 2018/04/25 12:02:17.824012 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:17.824411 single.go:154: INFO send fail  
> 2018/04/25 12:02:17.824480 single.go:161: INFO backoff retry: 4s  
> 2018/04/25 12:02:21.829173 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:21.829524 single.go:154: INFO send fail  
> 2018/04/25 12:02:21.829715 single.go:161: INFO backoff retry: 8s  
> 2018/04/25 12:02:29.836255 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:29.836625 single.go:154: INFO send fail  
> 2018/04/25 12:02:29.836691 single.go:161: INFO backoff retry: 16s  
> 2018/04/25 12:02:45.845455 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:02:45.845504 single.go:154: INFO send fail  
> 2018/04/25 12:02:45.845526 single.go:161: INFO backoff retry: 32s  
> 2018/04/25 12:03:17.852987 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:03:17.853040 single.go:154: INFO send fail  
> 2018/04/25 12:03:17.853056 single.go:161: INFO backoff retry: 1m0s  
> 2018/04/25 12:04:17.857764 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:04:17.857808 single.go:154: INFO send fail  
> 2018/04/25 12:04:17.857824 single.go:161: INFO backoff retry: 1m0s  
> 2018/04/25 12:05:17.882418 single.go:77: INFO Error publishing events (retrying): EOF  
> 2018/04/25 12:05:17.882437 single.go:154: INFO send fail  
> 2018/04/25 12:05:17.882445 single.go:161: INFO backoff retry

Because of the above issue logs are not publishing to the Elasticsearch. ☹

---

<div class="post-metadata">

**Author:** ![andrewkroh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/andrewkroh/32/3784_2.png) [@andrewkroh](https://discuss.elastic.co/u/andrewkroh)\
**Post date:** [April 25, 2018, 4:16pm UTC](https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493/2 "2018-04-25T16:16:47Z")

</div>

> [@Dazith\_Kj](#):
>
> 2018/04/25 12:02:14.614102 beat.go:168: INFO Init Beat: filebeat; Version: 1.3.1

It seems that you have installed a version of Filebeat that's very old (version 1.3.1 was released Sept. 15, 2016). The current version is [Filebeat 6.2.4](https://www.elastic.co/downloads/beats/filebeat).

I highly recommend that you follow the official [Filebeat Getting Started Guide](https://www.elastic.co/guide/en/beats/filebeat/current/filebeat-getting-started.html) using the latest version of Filebeat and the Elastic Stack.

Another option for trying out the whole Elastic Stack inside of Docker is [elastic/stack-docker](https://github.com/elastic/stack-docker). Just clone the repo and run `docker-compose up`.

---

<div class="post-metadata">

**Author:** ![Dazith\_Kj](https://avatars.discourse-cdn.com/v4/letter/d/b77776/32.png) [@Dazith\_Kj](https://discuss.elastic.co/u/Dazith_Kj)\
**Post date:** [April 27, 2018, 4:06pm UTC](https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493/3 "2018-04-27T16:06:54Z")

</div>

Thanks, @andrewkroh ! Once we updated the file beat to the said version. This worked like charm! 🙂

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [May 25, 2018, 4:06pm UTC](https://discuss.elastic.co/t/elk-stack-file-beat-configuration-issue-single-go-77-info-error-publishing-events-retrying-eof/129493/4 "2018-05-25T16:06:57Z")

</div>

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