# Kibana parse\_exception: No processor type exists with name \[inference\]

**URL:** <https://discuss.elastic.co/t/kibana-parse-exception-no-processor-type-exists-with-name-inference/380929>\
**Category:** Kibana\
**Created:** [August 11, 2025, 7:02am UTC](https://discuss.elastic.co/t/kibana-parse-exception-no-processor-type-exists-with-name-inference/380929 "2025-08-11T07:02:00Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![Tortoise](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tortoise/32/147587_2.png) [@Tortoise](https://discuss.elastic.co/u/Tortoise)\
**Post date:** [August 12, 2025, 3:15am UTC](https://discuss.elastic.co/t/kibana-parse-exception-no-processor-type-exists-with-name-inference/380929/2 "2025-08-12T03:15:47Z")

</div>

Hello @msconsults

Could you please review below post and confirm if you also receive same error about “Kibana is shutting down” in the logs?

> [@Kibana stuck in a crash loop](https://discuss.elastic.co/t/kibana-stuck-in-a-crash-loop/364834/14):
>
> Not sure what is the issue, I don't think Kibana would crash for this error as it is not a FATAL error. But the following lines suggests that something in your system requested a shutdown of the Kibana service and not the service itself crashing. I do not use Kubernetes EKS or Helm, but how does it health check the service? Can it be killing it because of an error in the logs?

Thanks!!

---

_[View the full topic](https://discuss.elastic.co/t/kibana-parse-exception-no-processor-type-exists-with-name-inference/380929)._