# Kibana server is not ready yet - throw er; // Unhandled 'error' event

**URL:** https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879
**Category:** Kibana
**Created:** [April 8, 2019, 3:54pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879 "2019-04-08T15:54:11Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![Milton\_Sam\_Moses](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milton_sam_moses/32/43420_2.png) [@Milton\_Sam\_Moses](https://discuss.elastic.co/u/Milton_Sam_Moses)
#### Post date: [April 8, 2019, 3:54pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/1 "2019-04-08T15:54:11Z")

</div>

Kibana wont start. Unable to determine the error.

-----error logs.  
root@dev-platops-eng02:/usr/share/kibana/node\_modules# /usr/share/kibana/bin/kibana --verbose  
events.js:174  
throw er; // Unhandled 'error' event  
^

Error: spawn /var/lib/kibana/headless\_shell-linux/headless\_shell EACCES  
at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:240:19)  
at onErrorNT (internal/child\_process.js:415:16)  
at process.\_tickCallback (internal/process/next\_tick.js:63:19)  
Emitted 'error' event at:  
at Process.ChildProcess.\_handle.onexit (internal/child\_process.js:246:12)  
at onErrorNT (internal/child\_process.js:415:16)  
at process.\_tickCallback (internal/process/next\_tick.js:63:19)

---

<div class="post-metadata">

### Author: ![joelgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joelgriffith/32/53738_2.png) [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)
#### Post date: [April 8, 2019, 5:18pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/2 "2019-04-08T17:18:57Z")

</div>

Hey @Milton_Sam_Moses! In more recent versions of Kibana, we do a quick check on start-up to see if we can launch an installed headless\_chrome binary. This is used inside our reporting functionality inside of the reporting plugin. Are you running with a trial or other license?

If so, could you verify the ownership of the headless\_shell file that Kibana can't access:

`ls -l /var/lib/kibana/headless_shell-linux/headless_shell`

The `EACCES` error generally has to do with the node process not being able to execute that file.

---

<div class="post-metadata">

### Author: ![Milton\_Sam\_Moses](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milton_sam_moses/32/43420_2.png) [@Milton\_Sam\_Moses](https://discuss.elastic.co/u/Milton_Sam_Moses)
#### Post date: [April 9, 2019, 9:08am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/3 "2019-04-09T09:08:52Z")

</div>

Hey, @joelgriffith. Thanks for your quick reply. I am running with trial.

root@dev-platops-eng02:~# ls -l /var/lib/kibana/headless\_shell-linux/headless\_shell

-rwxr-xr-x 1 kibana kibana 127410016 Apr 8 13:59 **/var/lib/kibana/headless\_shell-linux/headless\_shell**

---

<div class="post-metadata">

### Author: ![joelgriffith](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/joelgriffith/32/53738_2.png) [@joelgriffith](https://discuss.elastic.co/u/joelgriffith)
#### Post date: [April 9, 2019, 9:01pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/4 "2019-04-09T21:01:31Z")

</div>

Looks like permissions are set properly. Out of curiosity are you running Kibana as a different user? I see you're logged in as root, what's the command you're using to start Kibana?

---

<div class="post-metadata">

### Author: ![Milton\_Sam\_Moses](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/milton_sam_moses/32/43420_2.png) [@Milton\_Sam\_Moses](https://discuss.elastic.co/u/Milton_Sam_Moses)
#### Post date: [April 10, 2019, 6:51am UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/5 "2019-04-10T06:51:25Z")

</div>

sudo systemctl start kibana; tail -f /var/log/syslog

Hope this is the right way 🙈

---

<div class="post-metadata">

### Author: ![dudlo](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@dudlo](https://discuss.elastic.co/u/dudlo)
#### Post date: [April 15, 2019, 6:53pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/6 "2019-04-15T18:53:27Z")

</div>

+1 here for the exact same symptoms. We installed a fresh 6.6.2 Kibana, pretty much empty. Then we upgraded to 7.0.0. We see the exact same symptoms. kibana.log file is clean and happy; kibana.stderr shows only that error quoted here. /var/lib/kibana/headless\_shell-linux/headless\_shell permissions same as here (only newer date and binary size). We are stuck.

---

<div class="post-metadata">

### Author: ![dudlo](https://avatars.discourse-cdn.com/v4/letter/d/a587f6/32.png) [@dudlo](https://discuss.elastic.co/u/dudlo)
#### Post date: [April 18, 2019, 5:32pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/7 "2019-04-18T17:32:11Z")

</div>

I uninstalled and wiped the version, then I installed 7.0.0 version fresh. Still, the same error and symptoms. Kibana does not run; same error.

---

<div class="post-metadata">

### Author: ![Kaldayr](https://avatars.discourse-cdn.com/v4/letter/k/90ced4/32.png) [@Kaldayr](https://discuss.elastic.co/u/Kaldayr)
#### Post date: [April 24, 2019, 12:30pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/8 "2019-04-24T12:30:47Z")

</div>

Hello guys,

Don't know if this issue has been addressed already , but here's what worked for me.  
I had the same issue on my system (RHEL 7.4), and the origin was that the "/var" filesystem was flagged as "noexec" in the "/etc/fstab" system file:  
/dev/mapper/rootvg-var\_lv /var ext4 defaults,nodev, **noexec** 1 2

So if you're in the same case, two options : update the /etc/fstab file and remove the option (implies a hard reboot of the server), or move the Kibana "data" folder (usually /var/lib/kibana if installed through yum) elsewhere, and then add the following line to the /etc/kibana/kibana.yml file :  
path.data: /\<path\_to\_the\_new\_kibana\_data\_folder\>

Hope this helps,  
Regards.

---

<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: [May 22, 2019, 12:30pm UTC](https://discuss.elastic.co/t/kibana-server-is-not-ready-yet-throw-er-unhandled-error-event/175879/9 "2019-05-22T12:30:51Z")

</div>

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