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
initscript for kibana 4 #1595
Comments
We do not plan to include an init script in the repository. Init scripts would be better off dynamically generated with something like pleaserun: https://github.com/jordansissel/pleaserun When we go to publish packages we'll generate the init scripts as part of the build process. |
I've written a debian one https://github.com/akabdog/scripts/blob/master/kibana4_init |
@rashidkpc Installation of yet another dependency (and one that seemingly must be installed via @akabdog Your init script works perfectly. Thank you very much for creating it. |
@akabdog Thanks for your script... works great so far |
I've written a Centos one Cheers, |
@xAway Works thanks |
@xAway thanks for the script. works for me on RHEL6. |
The debian init script above runs kibana as root, which is almost certainly not what you want. |
@keith4 Indeed. A small change to the two start-stop-daemon line is all that is needed to run the service as user nobody. |
This is a Kibana4 script for RHEL6 (or CentOS) that runs it as a non-root user: |
@cjcotton The script working well at CentOS 6.3 |
Created a version for Ubuntu (/Debian): |
As Debian 8 uses systemd a service unit is all that's needed. /lib/systemd/system/kibana.service:
|
@cjcotton By chance this works fine with RHEL 5.5? |
I have tried to execute the kibana as background service through initialization script for RHEL https://github.com/cjcotton/init-kibana. I was able to the message that service is started through /etc/init.d. But service is not actually starting in background. I am using kibana 4.1.1 version |
As kibana is not a web page anymore but an application, he should have an initscript
(can help on this if you want)
The text was updated successfully, but these errors were encountered: