# Help: FATAL Port 5601 is already in use. Another instance of Kibana may be running! **URL:** \ **Category:** Kibana\ **Created:** [March 9, 2017, 8:50am UTC](https://discuss.elastic.co/t/help-fatal-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/77950 "2017-03-09T08:50:52Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![johnhrburns](https://avatars.discourse-cdn.com/v4/letter/j/97f17d/32.png) [@johnhrburns](https://discuss.elastic.co/u/johnhrburns)\ **Post date:** [March 9, 2017, 8:50am UTC](https://discuss.elastic.co/t/help-fatal-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/77950/1 "2017-03-09T08:50:52Z")
I have update my versions of elasticsearch and kibana, and installed with no problems using brew on my mac. However, when I try to execute 'bin/kibana' I get the following: > Johns-MacBook-Pro:kibana-5.2.2-darwin-x86\_64 johnhrburns$ bin/kibana > log [08:32:31.111] [info][status][plugin:kibana@5.2.2] Status changed from uninitialized to green - Ready > log [08:32:31.165] [info][status][plugin:elasticsearch@5.2.2] Status changed from uninitialized to yellow - Waiting for Elasticsearch > log [08:32:31.185] [info][status][plugin:console@5.2.2] Status changed from uninitialized to green - Ready > log [08:32:31.210] [info][status][plugin:elasticsearch@5.2.2] Status changed from yellow to green - Kibana index ready > log [08:32:31.308] [info][status][plugin:timelion@5.2.2] Status changed from uninitialized to green - Ready > log [08:32:31.313] [fatal] Port 5601 is already in use. Another instance of Kibana may be running! > FATAL Port 5601 is already in use. Another instance of Kibana may be running! When I try to find the PID and kill any other instance of Kibana I can't find anything: ``` Johns-MacBook-Pro:kibana-5.2.2-darwin-x86_64 johnhrburns$ ps -ef | grep kibana 501 9850 4747 0 9:38AM ttys000 0:00.00 grep kibana ``` Please help! Thanks! ---
**Author:** ![Brandon\_Kobel](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/brandon_kobel/32/14829_2.png) [@Brandon\_Kobel](https://discuss.elastic.co/u/Brandon_Kobel)\ **Post date:** [March 9, 2017, 12:40pm UTC](https://discuss.elastic.co/t/help-fatal-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/77950/2 "2017-03-09T12:40:50Z")
@johnhrburns you can use the following command to see the PID that is listening on port 5601 ```auto lsof -i :5601 ``` You could also use a derivate of your original approach looking for the process named 'node' ```auto ps -ef | grep node ``` but this has the potential to return processes besides the one you're looking for ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [April 6, 2017, 12:40pm UTC](https://discuss.elastic.co/t/help-fatal-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/77950/3 "2017-04-06T12:40:50Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.