Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kibana 4.3.0 needs small systemd change to start #65

Closed
mvernimmen-CG opened this issue Dec 1, 2015 · 2 comments
Closed

kibana 4.3.0 needs small systemd change to start #65

mvernimmen-CG opened this issue Dec 1, 2015 · 2 comments

Comments

@mvernimmen-CG
Copy link

On CentOS 7.1 Kibana 4.3.0 doesn't start logs the following in /var/log/kibana/kibana.log:
{"type":"log","@timestamp":"2015-12-01T14:03:56+00:00","tags":["fatal"],"pid":15654,"level":"fatal","message":"EACCES, open '/var/run/kibana.pid'","error":{"message":"EACCES, open '/var/run/kibana.pid'","name":"Error","stack":"Error: EACCES, open '/var/run/kibana.pid'\n at Error (native)","code":"EACCES"}}

In other words, the kibana user doesn't (and shouldn't) have write access to /var/run
To fix this, '/usr/lib/systemd/system/kibana.service' needs to have 'RuntimeDirectory=kibana' set. But that only fixes it for systems with systemd>=211, which CentOS 7 does not have at this moment.

A workaround is to either run kibana as root (not a good idea) or to add this to kibana.service:
ExecStartPre=/usr/bin/install -o kibana -g kibana -d /var/run/kibana
PIDFile=/var/run/kibana/kibana.pid

Probably in both cases the kibana.yml needs to be set to /var/run/kibana/kibana.pid instead of the default.

@atopian
Copy link
Contributor

atopian commented Dec 14, 2015

I have a PR to fix this at #67

@jlambert121
Copy link
Owner

Closed with #67

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants