# Setup lifecycle of "monitoring" plugin wasn't completed in 30 sec

**URL:** <https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504>\
**Category:** Kibana\
**Tags:** docker\
**Created:** [June 17, 2020, 4:07pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504 "2020-06-17T16:07:15Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![amwilliams](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@amwilliams](https://discuss.elastic.co/u/amwilliams)\
**Post date:** [June 17, 2020, 4:07pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/1 "2020-06-17T16:07:15Z")

</div>

Hi All,  
I am receiving an error when I start up the kibana docker image.  
I have tried to remove the package "monitoring" but it does not exist.  
I am running the 7.7.1 image.

```auto
{"type":"log","@timestamp":"2020-06-17T15:52:15Z","tags":["fatal","root"],"pid":9,"message":"Error: Setup lifecycle of \"monitoring\" plugin wasn't completed in 30sec. Consider disabling the plugin and re-start.\n at Timeout.setTimeout (/usr/share/kibana/src/core/utils/promise.js:31:90)\n at ontimeout (timers.js:436:11)\n at tryOnTimeout (timers.js:300:5)\n at listOnTimeout (timers.js:263:5)\n at Timer.processTimers (timers.js:223:10)"}

```

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [June 17, 2020, 7:55pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/2 "2020-06-17T19:55:43Z")

</div>

What image are you using, is it from [https://www.docker.elastic.co](https://www.docker.elastic.co)? What environment variables are you passing?

---

<div class="post-metadata">

**Author:** ![Swapnil\_Kashid](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/swapnil_kashid/32/70801_2.png) [@Swapnil\_Kashid](https://discuss.elastic.co/u/Swapnil_Kashid)\
**Post date:** [June 22, 2020, 9:40am UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/3 "2020-06-22T09:40:43Z")

</div>

I also having same issue, Image is from [[https://www.docker.elastic.com](https://www.docker.elastic.com)] with version 7.7,1

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [June 23, 2020, 1:23pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/4 "2020-06-23T13:23:20Z")

</div>

@Swapnil_Kashid can you provide the `kibana.yml` you are providing, if any, and any environmental variables you're passing to the container?

---

<div class="post-metadata">

**Author:** ![amwilliams](https://avatars.discourse-cdn.com/v4/letter/a/a6a055/32.png) [@amwilliams](https://discuss.elastic.co/u/amwilliams)\
**Post date:** [June 23, 2020, 1:46pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/5 "2020-06-23T13:46:24Z")

</div>

So I was able to resolve this issue. I had a few different things going on but I set the environment variable in the Pod: MONITORING\_ENABLED to "false". Also, ended up having some DNS confusion with the ELASTICSEARCH\_HOSTS env variable which I was able to resolve after some research.

---

<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:** [July 21, 2020, 1:46pm UTC](https://discuss.elastic.co/t/setup-lifecycle-of-monitoring-plugin-wasnt-completed-in-30-sec/237504/6 "2020-07-21T13:46:25Z")

</div>

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