Install Kibana with Debian Packageedit

The Debian package for Kibana can be downloaded from our website or from our APT repository. It can be used to install Kibana on any Debian-based system such as Debian and Ubuntu.

The latest stable version of Kibana can be found on the Download Kibana page. Other versions can be found on the Past Releases page.

Import the Elastic PGP Keyedit

We sign all of our packages with the Elastic Signing Key (PGP key D88E42B4, available from with fingerprint:

4609 5ACC 8548 582C 1A26 99A9 D27D 666C D88E 42B4

Download and install the public signing key:

wget -qO - | sudo apt-key add -

Installing from the APT repositoryedit

You may need to install the apt-transport-https package on Debian before proceeding:

sudo apt-get install apt-transport-https

Save the repository definition to /etc/apt/sources.list.d/elastic-5.x.list:

echo "deb stable main" | sudo tee -a /etc/apt/sources.list.d/elastic-5.x.list

Do not use add-apt-repository as it will add a deb-src entry as well, but we do not provide a source package. If you have added the deb-src entry, you will see an error like the following:

Unable to find expected entry 'main/source/Sources' in Release file
(Wrong sources.list entry or malformed file)

Delete the deb-src entry from the /etc/apt/sources.list file and the installation should work as expected.

You can install the Kibana Debian package with:

sudo apt-get update && sudo apt-get install kibana

If two entries exist for the same Kibana repository, you will see an error like this during apt-get update:

Duplicate sources.list entry ...`

Examine /etc/apt/sources.list.d/kibana-5.x.list for the duplicate entry or locate the duplicate entry amongst the files in /etc/apt/sources.list.d/ and the /etc/apt/sources.list file.

Download and install the Debian package manuallyedit

The Debian package for Kibana v5.1.2 can be downloaded from the website and installed as follows:

64 bit:

sha1sum kibana-5.1.2-amd64.deb 
sudo dpkg -i kibana-5.1.2-amd64.deb

Compare the SHA produced by sha1sum or shasum with the published SHA.

32 bit:

sha1sum kibana-5.1.2-i386.deb 
sudo dpkg -i kibana-5.1.2-i386.deb

Compare the SHA produced by sha1sum or shasum with the published SHA.

SysV init vs systemdedit

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

Kibana can be started and stopped 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. Instead, this information will be written in the log files located in /var/log/kibana/.

Configuring Kibana via config fileedit

Kibana loads its configuration from the /etc/kibana/kibana.yml file by default. The format of this config file is explained in Configuring Kibana.

Directory layout of Debian packageedit

The Debian package places config files, logs, and the data directory in the appropriate locations for a Debian-based system:

Type Description Default Location Setting


Kibana home directory or $KIBANA_HOME



Binary scripts including kibana to start the Kibana server and kibana-plugin to install plugins



Configuration files including kibana.yml



The location of the data files written to disk by Kibana and its plugins



Transpiled source code. Certain administrative actions (e.g. plugin install) result in the source code being retranspiled on the fly.



Plugin files location. Each plugin will be contained in a subdirectory.