# After upgrading to Kibana 5.x, the service is crashing randomly

**URL:** <https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729>\
**Category:** Kibana\
**Created:** [December 12, 2016, 3:15pm UTC](https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729 "2016-12-12T15:15:25Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Evan\_Ravenelle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evan_ravenelle/32/45404_2.png) [@Evan\_Ravenelle](https://discuss.elastic.co/u/Evan_Ravenelle)\
**Post date:** [December 12, 2016, 3:15pm UTC](https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729/1 "2016-12-12T15:15:25Z")

</div>

I'm not sure what is causing the problem, but since upgrading to Kibana 5.x, I find that the service will crash at random times. I don't have any indication as to what is wrong, because no errors are written to the log. How can I improve the Kibana internal logging to identify the source of the problem, or otherwise stop the application from crashing?

---

<div class="post-metadata">

**Author:** ![jbudz](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jbudz/32/45922_2.png) [@jbudz](https://discuss.elastic.co/u/jbudz)\
**Post date:** [December 12, 2016, 3:49pm UTC](https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729/2 "2016-12-12T15:49:34Z")

</div>

What's your indicator for the service crashing? And which download of kibana are you using? If you're using sysv there should be a corresponding kibana.stderr.log. One option is to enable verbose logging in kibana.yml, `logging.verbose: true`

---

<div class="post-metadata">

**Author:** ![Evan\_Ravenelle](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/evan_ravenelle/32/45404_2.png) [@Evan\_Ravenelle](https://discuss.elastic.co/u/Evan_Ravenelle)\
**Post date:** [December 12, 2016, 4:18pm UTC](https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729/3 "2016-12-12T16:18:38Z")

</div>

The indicator is that the service isn't running and I get a message from one of my developers telling me they can't get to it. There is a corresponding kibana.stderr, but nothing is being written to it (0 bytes since I upgraded). I'll try setting verbose logging and see if it improves.

---

<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:** [January 9, 2017, 4:19pm UTC](https://discuss.elastic.co/t/after-upgrading-to-kibana-5-x-the-service-is-crashing-randomly/68729/4 "2017-01-09T16:19:03Z")

</div>

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