# Syslog input filter parse failure

**URL:** <https://discuss.elastic.co/t/syslog-input-filter-parse-failure/158803>\
**Category:** Logstash\
**Created:** [November 29, 2018, 5:48pm UTC](https://discuss.elastic.co/t/syslog-input-filter-parse-failure/158803 "2018-11-29T17:48:46Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![rugenl](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/rugenl/32/12887_2.png) [@rugenl](https://discuss.elastic.co/u/rugenl)\
**Post date:** [November 29, 2018, 5:48pm UTC](https://discuss.elastic.co/t/syslog-input-filter-parse-failure/158803/1 "2018-11-29T17:48:46Z")

</div>

I'm getting a parse failure on all logs from Cisco ironport appliances. I see a syslog PRI field of \<38\>. RFC 3164 tables seem to say 3 is daemons but 8 is invalid.

Another method described here [https://gist.github.com/marvin/1017480/8fff5fcf7fefab7bfc94817e2241784c2c512c8b](https://gist.github.com/marvin/1017480/8fff5fcf7fefab7bfc94817e2241784c2c512c8b)

says 38/8 = 4 remainder 6, so AUTH.INFO, which is what WireShark shows.

Is it possible that the syslog input plugin isn't groking PRI correctly?

input {  
syslog {  
port =\> 514  
codec =\> plain {  
charset =\> "ISO-8859-1"  
}  
}  
}

---

<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:** [December 27, 2018, 5:48pm UTC](https://discuss.elastic.co/t/syslog-input-filter-parse-failure/158803/2 "2018-12-27T17:48:46Z")

</div>

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