# Status : "kibana is not working" but it works on browser. Why? **URL:** \ **Category:** Kibana\ **Created:** [February 16, 2017, 2:15am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261 "2017-02-16T02:15:24Z")\ **Posts on this page:** 12\ **Page:** 1
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 16, 2017, 2:15am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/1 "2017-02-16T02:15:24Z")
I rebooted OS and kibana automatically restarted by demon. I checked status and it says `kibana is not working`. error log is as below ```auto {"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 ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 16, 2017, 6:35am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/2 "2017-02-16T06:35:03Z")
> [@tanimoto](#): > > "Port 5601 is already in use. Another instance of Kibana may be running!" That's why. ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 16, 2017, 6:43am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/3 "2017-02-16T06:43:33Z")
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. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 16, 2017, 6:56am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/4 "2017-02-16T06:56:24Z")
I'd check to make sure there isn't another process running somehow. ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 16, 2017, 7:12am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/5 "2017-02-16T07:12:18Z")
When I access 5601 port from browser, Kibana is working. also, ```auto 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?? ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 17, 2017, 3:56am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/6 "2017-02-17T03:56:01Z")
My question is `is it possible that kibana is working while service status says it is not working????` ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 17, 2017, 4:09am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/7 "2017-02-17T04:09:13Z")
What does `ps -ef|grep kibana` show? ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 17, 2017, 4:13am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/8 "2017-02-17T04:13:02Z")
> [@warkolm](#): > > What does ps -ef|grep kibana show ```auto [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. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [February 17, 2017, 4:14am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/9 "2017-02-17T04:14:32Z")
So it is running, you may want to kill that process and try again with service. ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 17, 2017, 5:32am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/10 "2017-02-17T05:32:35Z")
```auto [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? ---
**Author:** ![tanimoto](https://avatars.discourse-cdn.com/v4/letter/t/dec6dc/32.png) [@tanimoto](https://discuss.elastic.co/u/tanimoto)\ **Post date:** [February 17, 2017, 6:51am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/11 "2017-02-17T06:51:26Z")
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. ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [March 17, 2017, 6:51am UTC](https://discuss.elastic.co/t/status-kibana-is-not-working-but-it-works-on-browser-why/75261/12 "2017-03-17T06:51:53Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.