Status : "kibana is not working" but it works on browser. Why?

I rebooted OS and kibana automatically restarted by demon.
I checked status and it says kibana is not working.

error log is as below

{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["status","plugin:kibana@5.1.1","info"],"pid":2513,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["status","plugin:elasticsearch@5.1.1","info"],"pid":2513,"state":"yellow","message":"Status changed from uninitialized to yellow - Waiting for Elasticsearch","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["status","plugin:console@5.1.1","info"],"pid":2513,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["status","plugin:elasticsearch@5.1.1","info"],"pid":2513,"state":"green","message":"Status changed from yellow to green - Kibana index ready","prevState":"yellow","prevMsg":"Waiting for Elasticsearch"}
{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["status","plugin:timelion@5.1.1","info"],"pid":2513,"state":"green","message":"Status changed from uninitialized to green - Ready","prevState":"uninitialized","prevMsg":"uninitialized"}
{"type":"log","@timestamp":"2017-02-16T01:58:20Z","tags":["fatal"],"pid":2513,"message":"Port 5601 is already in use. Another instance of Kibana may be running!"}

But kibana seems working well on browser.
What does error mean?

And how can I get status back to kibana is working?

Kibana
Version: 5.1.1

Thanks

That's why.

Service status says Kibana is not working but error says another instance of kibana is using 5601 port.

I don't understand why.

I installed only one kibana.

I'd check to make sure there isn't another process running somehow.

When I access 5601 port from browser, Kibana is working.

also,

lsof -i:5601

COMMAND PID   USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
node    629 kibana   10u  IPv4  16752      0t0  TCP host:esmagent (LISTEN)

It's strange since Kibana is not working on status.

Is this possibly cache??

My question is
is it possible that kibana is working while service status says it is not working????

What does ps -ef|grep kibana show?

[root@host ~]# ps -ef| grep kibana
kibana     630     1  0  2月16 ?      00:02:07 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml
root     25265 25240  0 13:11 pts/0    00:00:00 grep --color=auto kibana
[root@host ~]# 
[root@host ~]# 
[root@host ~]# service kibana status
kibana is not running
[root@host ~]# 

This is what I got.

So it is running, you may want to kill that process and try again with service.

2 Likes
[root@host ~]# ps -ef| grep kibana
kibana     630     1  0  2月16 ?      00:02:08 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml
root     25366 25240  0 13:18 pts/0    00:00:00 grep --color=auto kibana
[root@host ~]# 
[root@host ~]# kill 630
[root@host ~]# 
[root@host ~]# ps -ef| grep kibana
kibana   25367     1 99 13:18 ?        00:00:02 /usr/share/kibana/bin/../node/bin/node --no-warnings /usr/share/kibana/bin/../src/cli -c /etc/kibana/kibana.yml
root     25421 25240  0 13:18 pts/0    00:00:00 grep --color=auto kibana
[root@host ~]# 

killed process but immediately other kibana process starts up.
Any file I should delete?

The problem was solved.

I'm using cent os 7 and it has both systemctl command and service command.

I used service command to start, stop and check status.
But kibana started by systemctl command.

That's why I was seeing kibana is not working when I check status by service command.

Anyways, thank you for your help.

2 Likes

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