Kibana: Kibana RPM : conflict between service and systemctl

[mcorbin]

Kibana version: 5.1.2

Server OS version: Red Hat Enterprise Linux Server release 7.1

Original install method (e.g. download page, yum, from source, etc.): yum

Description of the problem including expected versus actual behavior:
service kibana status and systemctl status kibana does not return the same output.

Steps to reproduce:

1. Install Kibana using the rpm
2. systemctl daemon-reload
   3.

# service kibana start
# service kibana status
kibana is running
# systemctl status kibana
● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; disabled; vendor preset: disabled)
   Active: inactive (dead)
# service kibana stop
# systemctl start kibana
# systemctl status kibana
 ● kibana.service - Kibana
   Loaded: loaded (/etc/systemd/system/kibana.service; disabled; vendor preset: disabled)
   Active: active (running) since Thu 2017-01-26 10:44:01 CET; 1s ago
 Main PID: 14574 (node)
   CGroup: /system.slice/kibana.service
           └─14574 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share...
# service kibana status
kibana is not running

Kibana rpm creates a service script in /etc/init.d and an a systemd unit file in /etc/systemd/system. I think this is what cause the issue.

[pricecarl]

+1
Came across this is 5.2.0 rpm install on OEL7 too.

[claflico]

+1
5.2.1 on CentOS7.

[walidchenni]

+1
Came across this is 5.2.0 rpm install on RHEL7 too.

[howardjones]

Same with 5.2.2 and CentOS 7 here. Also, to make things more confusing, one logs to /var/log/kibana and the other logs to /var/log/messages via systemd.

[msteinhoff]

As a side note, the Kibana RPM package creates the systemd service unit file under /etc/systemd/system, but installed packages should place their files under /usr/lib/systemd/system.

[prupert]

As a side note, the Kibana RPM package creates the systemd service unit file under /etc/systemd/system, but installed packages should place their files under /usr/lib/systemd/system.

This is also reported at https://github.com/elastic/kibana/issues/16046

[dthvt]

Any movement on this?

[jbudz]

Starting in 8.0 we'll ship only the systemd service. Logs before the logger has started will output to the journal, logs after (most with a few exceptions) will go to /var/log/kibana/kibana.log