Starting and stopping Kibanaedit

The method for starting and stopping Kibana varies depending on how you installed it.

Archive packages (.tar.gz)edit

If you installed Kibana on Linux or Darwin with a .tar.gz package, you can start and stop Kibana from the command line.

Running Kibana from the command lineedit

Kibana can be started from the command line as follows:

./bin/kibana

By default, Kibana runs in the foreground, prints its logs to the standard output (stdout), and can be stopped by pressing Ctrl-C.

Archive packages (.zip)edit

If you installed Kibana on Windows with a .zip package, you can stop and start Kibana from the command line.

Running Kibana from the command lineedit

Kibana can be started from the command line as follows:

.\bin\kibana.bat

By default, Kibana runs in the foreground, prints its logs to STDOUT, and can be stopped by pressing Ctrl-C.

Debian packagesedit

Kibana is not started automatically after installation. How to start and stop Kibana depends on whether your system uses SysV init or systemd (used by newer distributions). You can tell which is being used by running this command:

ps -p 1

Running Kibana with SysV initedit

Use the update-rc.d command to configure Kibana to start automatically when the system boots up:

sudo update-rc.d kibana defaults 95 10

You can start and stop Kibana using the service command:

sudo -i service kibana start
sudo -i service kibana stop

If Kibana fails to start for any reason, it will print the reason for failure to STDOUT. Log files can be found in /var/log/kibana/.

Running Kibana with systemdedit

To configure Kibana to start automatically when the system boots up, run the following commands:

sudo /bin/systemctl daemon-reload
sudo /bin/systemctl enable kibana.service

Kibana can be started and stopped as follows:

sudo systemctl start kibana.service
sudo systemctl stop kibana.service

These commands provide no feedback as to whether Kibana was started successfully or not. Log information can be accessed via journalctl -u kibana.service.

RPM packagesedit

Kibana is not started automatically after installation. How to start and stop Kibana depends on whether your system uses SysV init or systemd (used by newer distributions). You can tell which is being used by running this command:

ps -p 1

Running Kibana with SysV initedit

Use the chkconfig command to configure Kibana to start automatically when the system boots up:

sudo chkconfig --add kibana

You can start and stop Kibana using the service command:

sudo -i service kibana start
sudo -i service kibana stop

If Kibana fails to start for any reason, it will print the reason for failure to STDOUT. Log files can be found in /var/log/kibana/.

Running Kibana with systemdedit

To configure Kibana to start automatically when the system boots up, run the following commands:

sudo /bin/systemctl daemon-reload
sudo /bin/systemctl enable kibana.service

Kibana can be started and stopped as follows:

sudo systemctl start kibana.service
sudo systemctl stop kibana.service

These commands provide no feedback as to whether Kibana was started successfully or not. Log information can be accessed via journalctl -u kibana.service.

Homebrew packagesedit

If you installed Kibana with the Elastic Homebrew formulae, you can start and stop Kibana from the command line using brew services.

Running Kibana with brew servicesedit

With Homebrew, Kibana can be started and stopped as follows:

brew services start elastic/tap/kibana-full
brew services stop elastic/tap/kibana-full