Install Kibana with RPM

We sign all of our packages with the Elastic Signing Key (PGP key D88E42B4, available from https://pgp.mit.edu) with fingerprint:

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

Download and install the public signing key:

rpm --import https://artifacts.elastic.co/GPG-KEY-elasticsearch

Create a file called kibana.repo in the /etc/yum.repos.d/ directory for RedHat based distributions, or in the /etc/zypp/repos.d/ directory for OpenSuSE based distributions, containing:

[kibana-5.x]
name=Kibana repository for 5.x packages
baseurl=https://artifacts.elastic.co/packages/5.x/yum
gpgcheck=1
gpgkey=https://artifacts.elastic.co/GPG-KEY-elasticsearch
enabled=1
autorefresh=1
type=rpm-md

And your repository is ready for use. You can now install Kibana with one of the following commands:

sudo yum install kibana 
sudo dnf install kibana 
sudo zypper install kibana 

	Use yum on CentOS and older Red Hat based distributions.
	Use dnf on Fedora and other newer Red Hat distributions.
	Use zypper on OpenSUSE based distributions

The RPM for Kibana v5.5.0 can be downloaded from the website and installed as follows:

64 bit:

wget https://artifacts.elastic.co/downloads/kibana/kibana-5.5.0-x86_64.rpm
sha1sum kibana-5.5.0-x86_64.rpm 
sudo rpm --install kibana-5.5.0-x86_64.rpm

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

32 bit:

wget https://artifacts.elastic.co/downloads/kibana/kibana-5.5.0-i686.rpm
sha1sum kibana-5.5.0-i686.rpm 
sudo rpm --install kibana-5.5.0-i686.rpm

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

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

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

sudo chkconfig --add kibana

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/.

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/.

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

The RPM places config files, logs, and the data directory in the appropriate locations for an RPM-based system: