# \_grokparsefailure even if pattern matches

**URL:** <https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839>\
**Category:** Logstash\
**Created:** [February 3, 2017, 11:51am UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839 "2017-02-03T11:51:13Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jonasv](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jonasv](https://discuss.elastic.co/u/jonasv)\
**Post date:** [February 3, 2017, 11:51am UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/1 "2017-02-03T11:51:13Z")

</div>

I've got this pattern "03/Feb/2017:11:14:44 +0000" and I've got this regexp NGDATE (^....................) which if I try on any online regexp tool match 03/Feb/2017:11:14:44  
but for some reason I get \_grokparsefailure instead, why ?

My goal is to send 03/Feb/2017:11:14:44 to logstash by skipping +0000

Any ideas ?

Thanks

---

<div class="post-metadata">

**Author:** ![magnusbaeck](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/magnusbaeck/32/44943_2.png) [@magnusbaeck](https://discuss.elastic.co/u/magnusbaeck)\
**Post date:** [February 3, 2017, 2:06pm UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/2 "2017-02-03T14:06:25Z")

</div>

If you show us a minimal Logstash configuration example that exhibits the problem it'll be easier to help.

Another possibility is that you have an extra file in /etc/logstash/conf.d with a non-matching grok filter, i.e. the grok filter you think you're running works fine but you're unknowingly also getting another grok filter applied.

---

<div class="post-metadata">

**Author:** ![jonasv](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jonasv](https://discuss.elastic.co/u/jonasv)\
**Post date:** [February 3, 2017, 2:28pm UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/3 "2017-02-03T14:28:37Z")

</div>

Thank you, I managed to solve this myself.

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [February 5, 2017, 9:34am UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/4 "2017-02-05T09:34:17Z")

</div>

How did you solve it?  
Sharing may help others in future 🙂

---

<div class="post-metadata">

**Author:** ![jonasv](https://avatars.discourse-cdn.com/v4/letter/j/22d042/32.png) [@jonasv](https://discuss.elastic.co/u/jonasv)\
**Post date:** [February 7, 2017, 10:28am UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/5 "2017-02-07T10:28:32Z")

</div>

I had a chaos in my config file, I have established new one and this has helped me to fix this problem.

---

<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:** [March 7, 2017, 10:28am UTC](https://discuss.elastic.co/t/-grokparsefailure-even-if-pattern-matches/73839/6 "2017-03-07T10:28:43Z")

</div>

Closed on March 7, 2017, 10:28am UTC

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