Kibana isn't different from any other service. Run it via an init script, systemd, Upstart, or whatever your OS recommends. If you install the RPM or the Debian package this is taken care of.
Don't use nohup. Again, use an init script, systemd, Upstart, or whatever your operating system recommends. If you're planning on using this seriously don't take any shortcuts like nohup.
Still, Kibana should be visible in the process list. Perhaps it isn't starting up okay?
It is starting up when started through nohup. I am able to see the UI.
But its not shown in grep kibana.
I am able to see below process for the user which is starting kibana : ps -ef | grep -u user
user 23101 1 0 Mar01 ? 00:21:23 ./../node/bin/node ./../src/cli
I am able to see below process for the user which is starting kibana : ps -ef | grep -u user
user 23101 1 0 Mar01 ? 00:21:23 ./../node/bin/node ./../src/cli
It's not going to show up as kibana in the process list, because it's not a real binary, it's a node application. bin/kibana is just a bash script that started up the node process, so it'll show up in your process list as node.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.