# Kibana 6.4 shutdown abnormally

**URL:** <https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774>\
**Category:** Kibana\
**Created:** [September 17, 2018, 7:19am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774 "2018-09-17T07:19:28Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Chunbo\_Liao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chunbo_liao/32/48172_2.png) [@Chunbo\_Liao](https://discuss.elastic.co/u/Chunbo_Liao)\
**Post date:** [September 17, 2018, 7:19am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/1 "2018-09-17T07:19:29Z")

</div>

Hi,

I have update my Kibana to 6.4, and run with X-pack is open. after running one week, kibana shutdown abnormally.

and the error logs is as follow:

/home/11thone/elk/kibana/node\_modules/x-pack/plugins/monitoring/server/kibana\_monitoring/collectors/get\_ops\_stats\_collector.js:48  
this.log.info('Re-initializing Kibana Monitoring due to SIGHUP');  
^

TypeError: Cannot read property 'log' of undefined  
at process.on (/home/11thone/elk/kibana/node\_modules/x-pack/plugins/monitoring/server/kibana\_monitoring/collectors/get\_ops\_stats\_collector.js:38:10)  
at emitNone (events.js:111:20)  
at process.emit (events.js:208:7)  
at Signal.wrap.onsignal (internal/process.js:208:44)

could you give some commnets?

br  
Liao Chunbo

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [September 17, 2018, 8:14am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/2 "2018-09-17T08:14:57Z")

</div>

Hi @Chunbo_Liao,

As I replied [here](https://github.com/elastic/kibana/issues/23221) already, this issue has been fixed in [#22464](https://github.com/elastic/kibana/pull/22464) and will be available in Kibana 6.4.1 very soon.

Thanks,  
Oleg

---

<div class="post-metadata">

**Author:** ![Chunbo\_Liao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chunbo_liao/32/48172_2.png) [@Chunbo\_Liao](https://discuss.elastic.co/u/Chunbo_Liao)\
**Post date:** [September 19, 2018, 1:31am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/3 "2018-09-19T01:31:21Z")

</div>

Hi,

Is there a work around for this issue before upgrade to 6.4.1?

BR  
Liao Chunbo

---

<div class="post-metadata">

**Author:** ![azasypkin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/azasypkin/32/42216_2.png) [@azasypkin](https://discuss.elastic.co/u/azasypkin)\
**Post date:** [September 19, 2018, 6:20am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/4 "2018-09-19T06:20:21Z")

</div>

> [@Chunbo\_Liao](#):
>
> Is there a work around for this issue before upgrade to 6.4.1?

Unfortunately no, unless you disable `Monitoring` plugin that causes that. **But** you should never observe this issue if you don't specifically `SIGHUP` signal to the Kibana process (e.g. `kill -1 kibana_pid`).

Also Kibana 6.4.1 has been released yesterday and upgrade should be fast and easy.

---

<div class="post-metadata">

**Author:** ![Chunbo\_Liao](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/chunbo_liao/32/48172_2.png) [@Chunbo\_Liao](https://discuss.elastic.co/u/Chunbo_Liao)\
**Post date:** [September 19, 2018, 7:22am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/5 "2018-09-19T07:22:05Z")

</div>

Hi,

Yes, I have upgrade the kibana. thank you for your greate support.

BR  
Liao Chunbo

---

<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:** [October 17, 2018, 7:22am UTC](https://discuss.elastic.co/t/kibana-6-4-shutdown-abnormally/148774/6 "2018-10-17T07:22:07Z")

</div>

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