# Filebeat error on processing log file **URL:** \ **Category:** Beats\ **Tags:** filebeat\ **Created:** [May 15, 2019, 6:24pm UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252 "2019-05-15T18:24:16Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![ankitachow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankitachow/32/46246_2.png) [@ankitachow](https://discuss.elastic.co/u/ankitachow)\ **Post date:** [May 15, 2019, 6:24pm UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252/1 "2019-05-15T18:24:16Z")
I'm trying to ingest log from filebeat, parsed through logstash and ingest in Elasticsearch. To make the pipeline work, I didnt add the grok yet but the log file is not moving forward with below error I'm using 6.x version 2019-05-15T13:20:33.679-0500 INFO log/harvester.go:216 Harvester started for file: /var/log/SDP/events/EventLogFile.txt.0 2019-05-15T13:20:33.725-0500 ERROR logstash/async.go:235 Failed to publish events caused by: write tcp 127.0.0.1:23054-\>127.0.0.1:5044: write: connection reset by peer 2019-05-15T13:20:34.726-0500 ERROR pipeline/output.go:92 Failed to publish events: write tcp 127.0.0.1:23054-\>127.0.0.1:5044: write: connection reset by peer 2019-05-15T13:20:43.620-0500 INFO [monitoring] log/log.go:124 Non-zero metrics in the last 30s {"monitoring": {"metrics": {"beat":{"cpu":{"system":{"ticks":670,"time":675},"total":{"ticks":6380,"time":6391,"value":6380},"user":{"ticks":5710,"time":5716}},"info":{"ephemeral\_id":"7baa6f1d-01fd-4c42-b4b9-7867e6cf2083","uptime":{"ms":1740008}},"memstats":{"gc\_next":12478016,"memory\_alloc":9147128,"memory\_total":1016521112,"rss":10252288}},"filebeat":{"events":{"added":43656,"done":43656},"harvester":{"open\_files":2,"running":2,"started":1}},"libbeat":{"config":{"module":{"running":0}},"output":{"events":{"acked":43655,"batches":23,"failed":2048,"total":45703},"read":{"bytes":132},"write":{"bytes":3462886,"errors":1}},"pipeline":{"clients":1,"events":{"active":0,"filtered":1,"published":43655,"retry":4096,"total":43656},"queue":{"acked":43655}}},"registrar":{"states":{"current":11,"update":43656},"writes":23},"system":{"load":{"1":1.39,"15":0.67,"5":0.72,"norm":{"1":0.029,"15":0.014,"5":0.015}}}}}} ---
**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\ **Post date:** [May 23, 2019, 1:04am UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252/2 "2019-05-23T01:04:54Z")
> [@ankitachow](#): > > 2019-05-15T13:20:34.726-0500 ERROR pipeline/output.go:92 Failed to publish events: write tcp 127.0.0.1:23054-\>127.0.0.1:5044: write: connection reset by peer Looking at the above errors, are you sure that the configuration is valid? Are you connecting to the right host / port? ---
**Author:** ![ankitachow](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/ankitachow/32/46246_2.png) [@ankitachow](https://discuss.elastic.co/u/ankitachow)\ **Post date:** [May 23, 2019, 3:05pm UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252/3 "2019-05-23T15:05:54Z")
@pierhugues Yes. I checked that but upon running the logstash-beats updates, it started working fine. Another question is when I run logstash as a service I dont have to mention the pipeline whereas from standalone i.e. from bin/logstash I have to mention the pipeline can that be an issue? I did an rpm install so my bin is in /usr/share/logstash and the pipeline and .conf is in /etc/logstash ---
**Author:** ![pierhugues](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/pierhugues/32/48383_2.png) [@pierhugues](https://discuss.elastic.co/u/pierhugues)\ **Post date:** [May 23, 2019, 3:51pm UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252/4 "2019-05-23T15:51:12Z")
@ankitachow yes, by default when you start Logstash as a service we will just load all the configuration that we can find in the /etc/logstash and merge them in a single pipeline. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [June 20, 2019, 3:51pm UTC](https://discuss.elastic.co/t/filebeat-error-on-processing-log-file/181252/5 "2019-06-20T15:51:16Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.