Kibana 6.1.0. and newer starts with error

(Kim Kruse Hansen) #18

Hi Marius

You are shipping a .cache directory with every version from 6.1.0 , included in the download file.
In 6.0.1 there is no .cache directory. Looks like a packaking problem .

Isn't that the root cause of this problem?


(CJ Cenizal) #19

Great work, Kim-Kruse-Hansen! I'm so glad you were able to figure out a solution. Thank you for sharing it. And thank you for mentioning the .cache directory. We're looking into it.



Nice to hear that you've got it solved.

I've tried this, but it's not working for me. I've deleted optimize folder, I've take the optimize folder from 6.0.1, I've pushed LS to 6.1.1 and did this all again.
Always the same error.

@Marius_Dragomir & @cjcenizal:
What if I've put up my optimize folder and you could try running with it?

(Marius Dragomir) #21

We can give it a try, sure.



Hope this helps further.


Hi, it seems we still have this similar issue with 6.1.1 version. And removing the .cache in optimize doesn't seem to work either. See Kibana 6.1.1 Fatal Error at start

I don't have x-pack either.

(Kim Kruse Hansen) #24

Hi Mojster

I have been looking more into this issue over the last few days and I have a way to reproduce the error consistently now.

Do you have a scripted install of Kibana or are doing you it by hand every time ?



By hand.

I extract the archive, copy previous data folder and change the archive name, to match previous one.

(Kim Kruse Hansen) #26

In order to recreate this error , I deployed a new VM on Azure and installed the components manually. That worked first time and I was also able to install x-pack without any problems.

I also compared the contents of the Windows install package with the Linux Install package and they were pretty much similar.

Normally I have an install script, that deploys the components in the correct order. I also normally run the Kibana as a Windows Service.

I then tried going back to my original machine and installing it manually from a fresh command prompt, which also worked.

But to fast forward .....

The crucial thing , is the directory from where you launch Kibana for the first time. Or if you use x-pack , the directory from where you install x-pack. it has to be run from your Kibana root directory.

I use this directory structure

c:\elastic\install <<<<<<<<<<<<< all my install stuff is placed under here , scripts , packages etc

so I do the following

start a new command prompt in admin mode
create c:\elastic\kibana
robocopy from c:\elastic\install\kibana-6.1.1 to c:\elastic\kibana
********change directory to c:\elastic\kibana **********
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

Same thing for x-pack

start a new command prompt in admin mode
create c:\elastic\kibana
robocopy from c:\elastic\install\kibana-6.1.1 to c:\elastic\kibana
********change directory to c:\elastic\kibana **********
run bin\kibana-plugin install x-pack
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

I have incorporated this into my install scripts and they work fine now.

I dont know, what Elastic changed from 6..0.1 to 6.1.x , but maybe this can give them what they need.


Kibana 6.1.1 Fatal Error at start

Thanks. You've done quite a study on the case.

I'm starting it with Windows Service Wrapper. So this should be it.
I'll try it after our holidays on 3.1. and let you all know.


Tried to reproduce this at home, but it's always working.

So there is no other option, for me, than to wait till next year.


I've managed to get access to my working environment.

You're right. I've changed path from absolute to relative in my service configuration & it started to work.
Thanks again.

(Kim Kruse Hansen) #30


Thats good news. I have been upgrading some clusters myself today to 6.1.1 and my workaround seems to work so far.

@CJ , are you still monitoring this discussion?


(Samar Rizvi) #31

@Kim-Kruse-Hansen @fragatina @Mojster
I tried all of the above workarounds, but none worked. The drive where Windows is installed usually has permission issues with many apps. So, I copied Kibana to another drive (it was earlier in C: drive), and viola! Kibana works.

(Kim Kruse Hansen) #32


@Marius_Dragomir ,@cjcenizal

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 ?

Let us know


(Viorel Florian) #33

I tried starting kibana-6.1.1 and I am encountering the same issue under Windows 2008:

Error: Uncaught TypeError: (0 , _reactcss.handleHover) is not a function
(http://localhost:8280/bundles/kibana.bundle.js?v=16350:67) at window.onerror (http://localhost:8280/bundles/commons.bundle.js?v=16350:45:8728)

I tried deleting the optimize folder and starting kibana from the root directory:


with the command:


I even tried to weed-out a permission issue by setting the owner of the kibana folder to "Everyone".
Alas, the issue persists. Any thoughts?

(Tim Sullivan) #34

Hi, I came to this topic from Kibana 6.1.1 Fatal Error at start 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 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.

(Kim Kruse Hansen) #35

Hi Tim

Sorry , but there is no service running ,or no aborted plugin installation. This is always a brand new install.

There is something fundamental changed something n the Kibana installation starting from 6.1.0. I am using same installation scripts as from way back to 2.5.3.

First msg is always "Optimizing and caching ..."

I have found a way around this problem but as I am sure , you will notice , several other users are facing the same problem.

Only reliable way of getting it to work, once it has gone bad is to remove optimze directory and run bin\kibana from kibana root. Then you can start the service.




I'm running straight Kibana with no plugins and I'm not using X-Pack .
So my and @Kim-Kruse-Hansen issues are not listed on your list.

It's only a startup dir issue.

(Tim Sullivan) #37

Hi Kim,

Can you check the before and after permissions of the optimize directory and the files inside it? It may be that you're required to run bin/kibana manually so the Kibana service runs as a user with your interactive user privileges, and has the permission to properly create the optimize directory.

If that is the problem, check that the Kibana directory and all the files it contains are owned by the same user account used for running the Kibana service.

Sometimes the core Kibana files are owned by an interactive user account, but they need to be owned by the same user that runs the Kibana service, so that the service can write new files.