# Find the source of index failures **URL:** \ **Category:** Graylog Central (peer support)\ **Created:** [June 21, 2022, 5:51pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414 "2022-06-21T17:51:44Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![hockeyfan0000](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@hockeyfan0000](https://community.graylog.org/u/hockeyfan0000)\ **Post date:** [June 21, 2022, 5:51pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/1 "2022-06-21T17:51:44Z")
I’ve got almost 25,000 index failures. I’m quite sure there’s a grok failure somewhere but there’s not enough information provided to track down the source. I see others have had the same problem as far back as 2018. Has there been any progress on this? I can resolve them if I know where to look. Any help is greatly appreciated. ---
**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\ **Post date:** [June 21, 2022, 8:26pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/2 "2022-06-21T20:26:05Z")
Can you post a bit more about what you are seeing? Relevant text from log files, screen shots… Where are you seeing the index failures? Post them so we can see the wording. `Here` are some tips on posting questions so that you give information about your environment - it includes commands to watch Graylog and Elasticsearch log files, among other tips and ideas… ---
**Author:** ![hockeyfan0000](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@hockeyfan0000](https://community.graylog.org/u/hockeyfan0000)\ **Post date:** [June 21, 2022, 9:14pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/3 "2022-06-21T21:14:17Z")
This is one of the failures. We’ve got somewhere around 30-40 Grok extractors and there’s just not enough information provided to know where to even start. Thank you for your help. a minute ago cor-logs\_2654 a52f04f1-f1a6-11ec-b98c-005056857e23 {“type”:“mapper\_parsing\_exception”,“reason”:“failed to parse field [Time] of type [date]”,“caused\_by”:{“type”:“illegal\_argument\_exception”,“reason”:“Invalid format: "17:10:56" is malformed at ":10:56"”}} ---
**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\ **Post date:** [June 22, 2022, 12:31pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/4 "2022-06-22T12:31:23Z")
There is no built in way to track that down that I know of - I had a similar issue where I needed to hunt down an error in my pipeline rules and I ended up dumping the rules into a Content Pack (System-\> Content Packs) and searching the resulting JSON file for key words associated with my issues… in your case it would be the field `Time` inside of a GROK. ---
**Author:** ![hockeyfan0000](https://avatars.discourse-cdn.com/v4/letter/h/b4bc9f/32.png) [@hockeyfan0000](https://community.graylog.org/u/hockeyfan0000)\ **Post date:** [June 22, 2022, 12:45pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/5 "2022-06-22T12:45:50Z")
Yup. This is something Graylog needs to fix. It’s going to take quite a while to look at all the extractors we’ve got. All Graylog would have to do is to provide the raw log with the error. That seems like a fix that would take a developer 10 minutes. Thank you for your replies. Cheers mate. ---
**Author:** ![tmacgbay](https://sea2.discourse-cdn.com/flex016/user_avatar/community.graylog.org/tmacgbay/32/3878_2.png) [@tmacgbay](https://community.graylog.org/u/tmacgbay)\ **Post date:** [June 22, 2022, 12:53pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/6 "2022-06-22T12:53:29Z")
> [@hockeyfan0000](#): > > This is something Graylog needs to fix You can post into [Github](https://github.com/Graylog2/graylog2-server/issues) – even though development always longer that you/I want, I know they do look at the posts and triage issues pretty quickly. I have seen some of my ideas come to (partial) fruition… 😃 ---
**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/graylog/original/3X/c/7/c7c09c6b5099570133d6502b83f50ba4430de5b6.png) [@system](https://community.graylog.org/u/system)\ **Post date:** [July 6, 2022, 12:54pm UTC](https://community.graylog.org/t/find-the-source-of-index-failures/24414/7 "2022-07-06T12:54:00Z")
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.