# Failed to publish long multiline events

**URL:** <https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296>\
**Category:** Beats\
**Tags:** filebeat\
**Created:** [September 13, 2017, 6:54am UTC](https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296 "2017-09-13T06:54:02Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![glipinski](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@glipinski](https://discuss.elastic.co/u/glipinski)\
**Post date:** [September 13, 2017, 6:54am UTC](https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296/1 "2017-09-13T06:54:02Z")

</div>

Hi,

I am trying to send logs from Filebeat to Logstash

Filebeat 5.5.2 (Centos 6.9)  
Logstash 5.5.2 (Windows Server 2008)

But I am getting an error:

`INFO Error publishing events (retrying): read tcp ******->***** :5044: wsarecv: An established connection was aborted by the software in your host machine.`

**Error occures only for long events** (i.e. 30000 characters) for short events logs are successfuly send to logstash -\> elasticsearch and are visible in kibana.

Filebeat configuration:

```
filebeat.prospectors:

- input_type: log
  paths:
    - D:\Logs\*
  multiline.pattern: '(--+)'
  multiline.negate: true
  multiline.match: after
  multiline.max_lines: 10000
  max_bytes: 10000000
  ignore_older: 24h

output.logstash:
  hosts: ["IP.ADD.RE.SS:5044"]

logging.level: debug

```

Logstash Pipeline:

```
input {
  beats {
    port => 5044
    client_inactivity_timeout => 60
  }
}

output {
  elasticsearch {
    hosts => ["IP.AD.DR.ESS:9200"]
    index => "test-%{+YYYY.MM.dd}"
    user => someuser
    password => somepassword
  }
}
```

---

<div class="post-metadata">

**Author:** ![steffens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/steffens/32/79630_2.png) [@steffens](https://discuss.elastic.co/u/steffens)\
**Post date:** [September 13, 2017, 12:12pm UTC](https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296/2 "2017-09-13T12:12:02Z")

</div>

Hmm... That's interesting. I wonder if it's logstash or windows closing the connection. What happens if you set `bulk_max_size: 1`. This ensures at most one event being send to Logstash at a time (just for testing purposes). Also try to increase `client_inactivity_timeout: 7200`. Maybe it is the timer in Logstash only being reset after having parsed an event.

---

<div class="post-metadata">

**Author:** ![glipinski](https://avatars.discourse-cdn.com/v4/letter/g/c5a1d2/32.png) [@glipinski](https://discuss.elastic.co/u/glipinski)\
**Post date:** [September 15, 2017, 8:37am UTC](https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296/3 "2017-09-15T08:37:48Z")

</div>

Hi,

Thanks for response.  
Logstash and Filebeat configuration weren't an issue.  
**Traffic was terminated on firewall 🙂**  
Now all events are successfully send to Logstash.  
I am not using max\_bytes, client\_inactivity\_timeout anymore

---

<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:** [October 13, 2017, 8:37am UTC](https://discuss.elastic.co/t/failed-to-publish-long-multiline-events/100296/4 "2017-10-13T08:37:55Z")

</div>

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