# Problem with start Kibana 4.3

**URL:** <https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676>\
**Category:** Kibana\
**Created:** [December 8, 2015, 10:19pm UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676 "2015-12-08T22:19:21Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![seedar](https://avatars.discourse-cdn.com/v4/letter/s/d2c977/32.png) [@seedar](https://discuss.elastic.co/u/seedar)\
**Post date:** [December 8, 2015, 10:19pm UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676/1 "2015-12-08T22:19:21Z")

</div>

Hi everyone,

At the beginning I want to say that the software ELK is completely new for me.  
At the moment already I started the Logstash and Elasticsearch and everything looks ok but when trying to run Kibana I have the following message.

 ![](https://us1.discourse-cdn.com/elastic/original/2X/3/3cc879fcf5ae181615d7f7be4fd3b39494c0e5f7.png)

Logs for Kibana show the following messages:

_\> log [22:27:19.509] [debug][plugins] Scanning `/opt/kibana-4.3.0-linux-x64/installedPlugins` for plugins_  
_\> log [22:27:19.518] [debug][plugins] Scanning `/opt/kibana-4.3.0-linux-x64/src/plugins` for plugins_  
_\> log [22:27:19.842] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/elasticsearch/index.js_  
_\> log [22:27:19.848] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/kbn\_vislib\_vis\_types/index.js_  
_\> log [22:27:19.854] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/kibana/index.js_  
_\> log [22:27:19.859] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/markdown\_vis/index.js_  
_\> log [22:27:19.863] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/metric\_vis/index.js_  
_\> log [22:27:19.869] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/spyModes/index.js_  
_\> log [22:27:19.876] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/statusPage/index.js_  
_\> log [22:27:19.881] [debug][plugins] Found plugin at /opt/kibana-4.3.0-linux-x64/src/plugins/table\_vis/index.js_  
_\> log [22:27:20.383] [debug][optimize] All bundles are cached and ready to go!_  
_\> log [22:27:20.388] [debug][plugins] Initializing plugin kibana_  
_\> log [22:27:20.394] [info][status][plugin:kibana] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.396] [debug][plugins] Initializing plugin elasticsearch_  
_\> log [22:27:20.456] [info][status][plugin:elasticsearch] Status changed from uninitialized to yellow - Waiting for Elasticsearch_  
_\> log [22:27:20.473] [debug][plugins] Initializing plugin kbn\_vislib\_vis\_types_  
_\> log [22:27:20.486] [debug][plugin] Checking Elasticsearch version_  
_\> log [22:27:20.489] [info][status][plugin:kbn\_vislib\_vis\_types] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.491] [debug][plugins] Initializing plugin markdown\_vis_  
_\> log [22:27:20.501] [info][status][plugin:markdown\_vis] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.503] [debug][plugins] Initializing plugin metric\_vis_  
_\> log [22:27:20.517] [info][status][plugin:metric\_vis] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.520] [debug][plugins] Initializing plugin spyModes_  
_\> log [22:27:20.526] [info][status][plugin:spyModes] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.527] [debug][plugins] Initializing plugin statusPage_  
_\> log [22:27:20.533] [info][status][plugin:elasticsearch] Status changed from yellow to green - Kibana index ready_  
_\> log [22:27:20.536] [info][status][plugin:statusPage] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.537] [debug][plugins] Initializing plugin table\_vis_  
_\> log [22:27:20.544] [info][status][plugin:table\_vis] Status changed from uninitialized to green - Ready_  
_\> log [22:27:20.569] [info][listening] Server running at [http://0.0.0.0:5601](http://0.0.0.0:5601)_  
....  
_\> respons [22:27:51.468] GET / 200 112ms - 9.0B_  
_\> respons [22:27:51.841] GET /app/kibana 200 161ms - 9.0B_  
_\> respons [22:27:51.957] GET /bundles/commons.style.css 304 11ms - 9.0B_  
_\> respons [22:27:51.960] GET /bundles/kibana.style.css 304 11ms - 9.0B_  
_\> respons [22:27:51.969] GET /bundles/commons.bundle.js 304 2ms - 9.0B_  
_\> respons [22:27:52.169] GET /favicon.ico 404 17ms - 9.0B_  
_\> respons [22:27:52.171] GET /bundles/kibana.bundle.js 304 20ms - 9.0B_  
_\> log [22:27:53.281] [debug][plugin] Checking Elasticsearch version_  
_\> respons [22:27:53.357] GET /bundles/node\_modules/font-awesome/fonts/fontawesome-webfont.woff 304 3ms - 9.0B_  
_\> ops [22:27:54.422] memory: 70.0MB uptime: 0:00:38 load: [0.72 0.26 0.09] delay: 0.645_  
_\> log [22:27:55.798] [debug][plugin] Checking Elasticsearch version_  
_\> log [22:27:58.312] [debug][plugin] Checking Elasticsearch version_  
_\> ops [22:27:59.423] memory: 70.5MB uptime: 0:00:43 load: [0.66 0.25 0.09] delay: 0.478_  
_...._

What could be causing of this situation?

BTW Is it normal that every 2 seconds a message "[debug][plugin] Checking Elasticsearch version" appears?

My environment

Red Hat Enterprise Linux Server release 6.7  
java version "1.8.0\_65" (RPM)  
logstash-2.1.0-1.noarch (RPM)  
elasticsearch-2.1.0-1.noarch (RPM)  
kibana-4.3.0

Regards

Seedar

---

<div class="post-metadata">

**Author:** ![tbragin](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tbragin/32/45166_2.png) [@tbragin](https://discuss.elastic.co/u/tbragin)\
**Post date:** [December 9, 2015, 4:30am UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676/2 "2015-12-09T04:30:09Z")

</div>

Strange - looks like a bug in Kibana, but it's not something we've seen recently. Could you submit this bug report on Github? The error isn't terribly specific, so the devs may ask for more info. Are you, by chance, running any plugins on the ES or Kibana side?

---

<div class="post-metadata">

**Author:** ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)\
**Post date:** [December 9, 2015, 7:05pm UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676/3 "2015-12-09T19:05:23Z")

</div>

After upgrading to 4.3.0, I'm seeing something similar: "Courier Fetch: unhandled error Error: Forbidden". It happens intermittently and it happens enough to be almost unusable.

---

<div class="post-metadata">

**Author:** ![erikstephens](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/erikstephens/32/5430_2.png) [@erikstephens](https://discuss.elastic.co/u/erikstephens)\
**Post date:** [December 9, 2015, 9:13pm UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676/4 "2015-12-09T21:13:58Z")

</div>

I think issue is on my end. Related to [Issue 4342: Increased performance for wildcard indices](https://github.com/elastic/kibana/issues/4342) in case anyone sees something similar. Probably not related to original poster.

---

<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 6, 2017, 2:06pm UTC](https://discuss.elastic.co/t/problem-with-start-kibana-4-3/36676/5 "2017-07-06T14:06:56Z")

</div>


