-
Notifications
You must be signed in to change notification settings - Fork 8.3k
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
SystemD unit is written to non-standard location #16046
Comments
+1 |
I am facing this issue after upgrading kibana from 6.7 to 7.0. Suggest me any way to start Kibana as it is in the production environment. |
This is actually pretty annoying because this prevents masking the service:
To mask the service, systemd attempts to symlink Compare this to Elasticsearch, which correctly installs to
|
Generally packages should install service files to /usr/lib/systemd/system. The current location is typically used for services configured by the system maintainer. Closes elastic#16046 Closes elastic#27768
I have just installed Kibana 6.1 on a CentOS 7.3 box via Yum, and observed that the systemd unit has been installed to a non-standard location of
/etc/systemd/system/
.Standard packaging practise is for systemd unit files to be installed to
/lib/systemd/system/
.Also of relevance is #6579, as currently logs are spamming /var/log/messages, when they should really go into '/var/log/kibana'.
N.B: It appears that the install location was changed as part of #7276
Kibana version: 6.1.1
Elasticsearch version: 6.1.1
Server OS version: CentOS 7.3.1611
Original install method (e.g. download page, yum, from source, etc.): yum
Steps to reproduce:
The text was updated successfully, but these errors were encountered: