# Getting \_grokparsefailure for an unkown reason

**URL:** <https://discuss.elastic.co/t/getting-grokparsefailure-for-an-unkown-reason/107556>\
**Category:** Logstash\
**Created:** [November 14, 2017, 2:06pm UTC](https://discuss.elastic.co/t/getting-grokparsefailure-for-an-unkown-reason/107556 "2017-11-14T14:06:42Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ou\_snaaksie](https://avatars.discourse-cdn.com/v4/letter/o/b487fb/32.png) [@ou\_snaaksie](https://discuss.elastic.co/u/ou_snaaksie)\
**Post date:** [November 14, 2017, 2:06pm UTC](https://discuss.elastic.co/t/getting-grokparsefailure-for-an-unkown-reason/107556/1 "2017-11-14T14:06:42Z")

</div>

I am tryinf to make a grok filter for the Synology NAS syslog messages, but I keep on getting a \_grokparsefailure even though my filter works according to [http://grokdebug.herokuapp.com/](http://grokdebug.herokuapp.com/).

Filter:  
`"<%{POSINT:syslog_pri}>%{SYSLOGTIMESTAMP:syslog_timestamp} %{SYSLOGHOST:syslog_hostname} %{WORD:program} %{GREEDYDATA:syslog_message}"`

And here is what a log message looks like:  
`<14>Nov 14 15:05:28 sflns001 Connection username:\tUser [USERNAME] logged in from [46.140.124.122] via [DSM].\n`

---

<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 12, 2017, 2:07pm UTC](https://discuss.elastic.co/t/getting-grokparsefailure-for-an-unkown-reason/107556/2 "2017-12-12T14:07:01Z")

</div>

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