Kibana Service Failed to start

Elastic Stack Kibana
1 
 kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: disabled)
   Active: failed (Result: start-limit) since Mon 2019-07-22 11:56:13 PDT; 9min ago
  Process: 25855 ExecStart=/usr/share/kibana/bin/kibana -c /etc/kibana/kibana.yml (code=exited, status=1/FAILURE)
 Main PID: 25855 (code=exited, status=1/FAILURE)

Jul 22 11:56:13 systemd[1]: kibana.service: main process exited, code=exited, status=1/FAILURE
Jul 22 11:56:13 systemd[1]: Unit kibana.service entered failed state.
Jul 22 11:56:13 systemd[1]: kibana.service failed.
Jul 22 11:56:13 systemd[1]: kibana.service holdoff time over, scheduling restart.
Jul 22 11:56:13 systemd[1]: start request repeated too quickly for kibana.service
Jul 22 11:56:13 systemd[1]: Failed to start Kibana.
Jul 22 11:56:13 systemd[1]: Unit kibana.service entered failed state.
Jul 22 11:56:13 systemd[1]: kibana.service failed.

This is the following error I am receiving when starting up Kibana. I believe it has to something to do with permissions, however I am unsure how to go about fixing this.

2

Hello,

You can't start Kibana service as root.

Can you please check how you are doing it?

Thanks,
Bhavya

3

Hi @userR

Which OS and version of Kibana are you running?

Thanks,
Liza

4

@LizaD
Version 7.2 and GNU/Linux 64

5

Kibana is on a server where root access is necessary to accessing the folder. Is there any other way to go about starting it?

6

@jbudz can we please get some help here?

Thanks,
Bhavya

7

Hello userR,

Did you install Kibana as root?

Thanks,
Bhavya

8

Yes, it looks like I did. Will I have to reinstall it?

9

A fresh purge and install will help, by resetting the permissions if you want the quick fix. We can debug if you want too - can you share the output of journalctl -fu kibana.service and if there's any log files at /var/log/kibana?

10 
journalctl -fu kibana.service

-- Logs begin at Mon 2019-07-08 07:33:17 PDT. --

Jul 22 11:56:13 kibana[25855]: fs.js:115

Jul 22 11:56:13 systemd[1]: **kibana.service: main process exited, code=exited, status=1/FAILURE**

Jul 22 11:56:13 systemd[1]: **Unit kibana.service entered failed state.**

Jul 22 11:56:13 systemd[1]: **kibana.service failed.**

Jul 22 11:56:13 systemd[1]: kibana.service holdoff time over, scheduling restart.

Jul 22 11:56:13 systemd[1]: **start request repeated too quickly for kibana.service**

Jul 22 11:56:13 systemd[1]: **Failed to start Kibana.**

Jul 22 11:56:13 systemd[1]: **Unit kibana.service entered failed state.**

Jul 22 11:56:13 systemd[1]: **kibana.service failed.**

Jul 22 13:33:27 systemd[1]: Stopped Kibana.

I do not see any kibana log files.

11

Can you scroll up a little, we caught just the tail end of the error, but it does look like it's permissions related :slight_smile:

Jul 22 11:56:13 elkproj kibana[25855]: fs.js:115
12 
Jul 22 15:02:08 kibana[519]: Error: EACCES: permission denied, open '/usr/share/kibana/optimize/.babelcache.json'

Jul 22 15:02:08 kibana[519]: at Object.openSync (fs.js:439:3)

Jul 22 15:02:08 kibana[519]: at Object.writeFileSync (fs.js:1190:35)

Jul 22 15:02:08 kibana[519]: at save (/usr/share/kibana/node_modules/@babel/register/lib/cache.js:52:15)

Jul 22 15:02:08 kibana[519]: at process._tickCallback (internal/process/next_tick.js:61:11)

Jul 22 15:02:08 systemd[1]: **kibana.service: main process exited, code=exited, status=1/FAILURE**

@jbudz my bad! It's outputted above.

13

cool. this is usually caused by installing a plugin as root. it's a tough fix on the kibana side and something we're working on.

in the interim we usually recommend installing plugins as the kibana user sudo -u kibana bin/kibana-plugin install...

you can fix this in the meantime with sudo chmown kibana:kibana /usr/share/kibana/optimize/.babelcache.json

2 Likes
14

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