Install Kibana with RPM
editInstall Kibana with RPM
editThe RPM for Kibana can be downloaded from our website or from our RPM repository. It can be used to install Kibana on any RPM-based system such as OpenSuSE, SLES, Centos, Red Hat, and Oracle Enterprise.
RPM install is not supported on distributions with old versions of RPM,
such as SLES 11 and CentOS 5. Please see Install Kibana with .tar.gz
instead.
This package is free to use under the Elastic license. It contains open source and free commercial features and access to paid commercial features. Start a 30-day trial to try out all of the paid commercial features. See the Subscriptions page for information about Elastic license levels.
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 Key
editWe 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
Installing from the RPM repository
editCreate 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-6.x] name=Kibana repository for 6.x packages baseurl=https://artifacts.elastic.co/packages/6.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:
Download and install the RPM manually
editThe RPM for Kibana v6.3.2 can be downloaded from the website and installed as follows:
wget https://artifacts.elastic.co/downloads/kibana/kibana-6.3.2-x86_64.rpm shasum -a 512 kibana-6.3.2-x86_64.rpm sudo rpm --install kibana-6.3.2-x86_64.rpm
Compare the SHA produced by |
Alternatively, you can download the following package, which contains only features that are available under the Apache 2.0 license: https://artifacts.elastic.co/downloads/kibana/kibana-oss-6.3.2-x86_64.rpm
SysV init
vs systemd
editKibana 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 init
editUse 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 systemd
editTo 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 file
editKibana 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 RPM
editThe RPM places config files, logs, and the data directory in the appropriate locations for an RPM-based system:
Type | Description | Default Location | Setting |
---|---|---|---|
home |
Kibana home directory or |
|
|
bin |
Binary scripts including |
|
|
config |
Configuration files including |
|
|
data |
The location of the data files written to disk by Kibana and its plugins |
|
|
optimize |
Transpiled source code. Certain administrative actions (e.g. plugin install) result in the source code being retranspiled on the fly. |
|
|
plugins |
Plugin files location. Each plugin will be contained in a subdirectory. |
|