# Syslog out plugin connection error and UDP drops

**URL:** https://discuss.elastic.co/t/syslog-out-plugin-connection-error-and-udp-drops/195809
**Category:** Logstash
**Created:** [August 19, 2019, 8:57pm UTC](https://discuss.elastic.co/t/syslog-out-plugin-connection-error-and-udp-drops/195809 "2019-08-19T20:57:22Z")
**Posts on this page:** 2
**Page:** 1

<div class="post-metadata">

### Author: ![Jayanthi](https://avatars.discourse-cdn.com/v4/letter/j/58f4c7/32.png) [@Jayanthi](https://discuss.elastic.co/u/Jayanthi)
#### Post date: [August 19, 2019, 8:57pm UTC](https://discuss.elastic.co/t/syslog-out-plugin-connection-error-and-udp-drops/195809/1 "2019-08-19T20:57:23Z")

</div>

We have 4 logstash servers currently just taking ~4000/sec. Works fine almost all the time, but few times couple server have UDP drops.  
At the same time, i see following exception logged.

syslog tcp output exception: closing, reconnecting and resending event {:host=\>"xxx.xxx.xxx", :port=\>514, :exception=\>#\<SystemCallError: Unknown error (SystemCallError) - No message available\>

Trying to find, if the syslog tcp output exception is making the packets to pile up and cause UDP drops or is it other way around?

Logstash config  
4 servers - 4CPU,8 GB  
workers = \>8  
queue\_size =\> 50000  
pipeline.workers =\> 8  
batch\_size =\> 2000

---

<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: [September 16, 2019, 8:57pm UTC](https://discuss.elastic.co/t/syslog-out-plugin-connection-error-and-udp-drops/195809/2 "2019-09-16T20:57:24Z")

</div>

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