/etc/init.d/kibana status show kibana not running, but actually it is running

Elastic Stack Kibana
1

Hi All ,
Good morning
I am using the latest stable version of elaticsearch and kibana 7.4.2
Like to point out the status of kibana using
/etc/init.d/kibana status shows it as not running

root@apm:~# /etc/init.d/elasticsearch status
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-11-06 07:11:13 UTC; 3s ago
Docs: http://www.elastic.co
Main PID: 734 (java)
Tasks: 63 (limit: 3555)
CGroup: /system.slice/elasticsearch.service
├─ 734 /usr/share/elasticsearch/jdk/bin/java -Xms1g -Xmx1g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupanc…et
└─1167 /usr/share/elasticsearch/modules/x-pack-ml/platform/linux-x86_64/bin/controller

Nov 06 07:10:22 apm systemd[1]: Starting Elasticsearch...
Nov 06 07:10:27 apm elasticsearch[734]: OpenJDK 64-Bit Server VM warning: Option UseConcMarkSweepGC was deprecate…release.
Nov 06 07:11:13 apm systemd[1]: Started Elasticsearch.
Hint: Some lines were ellipsized, use -l to show in full.

/etc/init.d/kibana status
kibana is not running

systemctl status kibana
● kibana.service - Kibana
Loaded: loaded (/etc/systemd/system/kibana.service; enabled; vendor preset: enabled)
Active: active (running) since Wed 2019-11-06 07:10:22 UTC; 1min 28s ago
Main PID: 785 (node)
Tasks: 21 (limit: 3555)
CGroup: /system.slice/kibana.service
└─785 /usr/share/kibana/bin/../node/bin/node /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml

Nov 06 07:10:22 apm systemd[1]: Started Kibana.
Nov 06 07:11:00 apm kibana[785]: Could not create APM Agent configuration: No Living connections

How to reproduce the result
Do a fresh install and try out, you can see, I am using Ubuntu 18.04 update

1 Like
2

Active: active (running) since Wed 2019-11-06 07:10:22 UTC; 1min 28s ago

means it is running.

3

Hi ,
Please read my post,
I was mentioning 2 scenario, one in which you get status running and one in which status not running
systemctl gives status running
while

The post I posted for giving feedback, to the developers or product managers that there is wrong status display, as a user I was giving feedback

4

only if you started kibana with the init script you will be able the check the status this way.

that is because when started by systemd, the init script does not know the pid of the running process.

you have to check the status with the daemon used to start it.

5

Thanks
But if you check the status of elasticsearch and logstash it shows as running

/etc/init.d/elasticsearch status
/etc/init.d/logstash status
it shows running
All the services, including kibana , I started using systemctl

6

it is becoming clear to me that you didn't even look at the code and/or have no idea how init and systemd scripts work...

you can see elasticsearch status because both files /etc/init.d/elasticsearch and /usr/lib/systemd/system/elasticsearch.service look for the PID on the same path, while kibana is not configured like this.

/usr/lib/systemd/system/elasticsearch.service

Environment=PID_DIR=/var/run/elasticsearch
ExecStart=/usr/share/elasticsearch/bin/elasticsearch -p ${PID_DIR}/elasticsearch.pid

---

/etc/init.d/elasticsearch

PID_DIR="/var/run/elasticsearch"
prog="elasticsearch"
pidfile="$PID_DIR/${prog}.pid"
daemon --user elasticsearch --pidfile $pidfile $exec -p $pidfile -d
7

true, not much aware , nor me a programmer, just a novice Elasticsearch user, learning and observing new features

All I said was to bring it to the attention , while init.d status shows correctly for elasticsearch and logstash, it do not show the same with kibana

It is my feedback, may be usefull to the developers

8

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.