# Kibana 6.1.0. and newer starts with error

**URL:** <https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754>\
**Category:** Kibana\
**Created:** [December 14, 2017, 11:21am UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754 "2017-12-14T11:21:41Z")\
**Posts on this page:** 1\
**Showing post:** 34

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 2, 2018, 6:13pm UTC](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754/34 "2018-01-02T18:13:32Z")

</div>

> [@Kim-Kruse-Hansen](#):
>
> Any words on this issue? More people are facing the issue and we have a great way of reproducing and how to work around it. Will it be fixed in 6.1.2 ?

Hi, I came to this topic from [Kibana 6.1.1 Fatal Error at start](https://discuss.elastic.co/t/kibana-6-1-1-fatal-error-at-start/112986) and I think there are a few different issues going on. The few that I can think of are:

1. Installing or removing a plugin while Kibana is running. Kibana must be stopped when a plugin is installed. Kibana discovers all the plugins at startup time, so plugins have to be installed or removed while Kibana is not running.
2. X-Pack or some other plugin not being fully installed. If plugin installation gets aborted before it's finished then it may show as installed even though it is in a broken state. You can remove and try installing the plugin again. Make sure Kibana is restarted after the plugin is reinstalled. Sometimes removing the `optimize` directory and restarting Kibana could act as a shortcut.
3. Running a `bin/kibana-plugin install plugin-name` command from a different working directory. The plugin installer has to be run from the Kibana installation path.

> [@Kim-Kruse-Hansen](#):
>
> run bin\kibana  
> wait for it to launch on 5601  
> connect wit browser to verify that it works  
> shut it down  
> and then launch Kibana Service  
> and again  
> connect with browser to verify that it works

@Kim-Kruse-Hansen if this is what you need to do to run Kibana with X-Pack, it indicates to me that the Kibana Service you're launching is somehow starting Kibana without it running the optimizer first. (Sorry, but I'm not sure how that would happen.) So running `bin/kibana` manually up front does the optimization, and then Kibana can be restarted by the service successfully, because optimization was done. If you add any other plugins or change certain config settings (such as disabling a feature or changing the `server.basePath` setting) then you'd need to run `bin/kibana` manually again to force it do to the optimization again.

---

_[View the full topic](https://discuss.elastic.co/t/kibana-6-1-0-and-newer-starts-with-error/111754)._