# Kibana - Port 5601 is already in use. Another instance of Kibana may be running!

**URL:** <https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804>\
**Category:** Kibana\
**Created:** [January 5, 2020, 2:09pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804 "2020-01-05T14:09:57Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![Vinoth\_kumar\_Ramasam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinoth_kumar_ramasam/32/60294_2.png) [@Vinoth\_kumar\_Ramasam](https://discuss.elastic.co/u/Vinoth_kumar_Ramasam)\
**Post date:** [January 5, 2020, 2:09pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/1 "2020-01-05T14:09:57Z")

</div>

Im trying to setup ELK stack version 7.5.1 in my 64 bit windows machine. But, im always keep on getting the following error whenever i tried to start Kibana. Also, I checked using netstat -ano | findstr 5601. It returned no results. I just followed the steps given in the official website. Also, i have configured the elastic search hosts in the kibana yml config file.

C:\Softwares\ELK\kibana-7.5.1-windows-x86\_64\bin\>netstat -ano | findstr :5601

C:\Softwares\ELK\kibana-7.5.1-windows-x86\_64\bin\>netstat -ano | findstr 5601

**Error Log :-**  
log [13:46:29.336] [info][status][plugin:reporting@7.5.1] Status changed from uninitialized to green - Ready  
log [13:46:29.378] [info][listening] Server running at [http://localhost:5601](http://localhost:5601)  
log [13:46:29.436] [fatal][root] Error: Port 5601 is already in use. Another instance of Kibana may be running!  
at Root.shutdown (C:\Softwares\ELK\kibana-7.5.1-windows-x86\_64\src\core\serv  
er\root\index.js:67:18)  
at Root.start (C:\Softwares\ELK\kibana-7.5.1-windows-x86\_64\src\core\server  
root\index.js:57:18)  
at process.\_tickCallback (internal/process/next\_tick.js:68:7)  
log [13:46:29.458] [info][plugins-system] Stopping all plugins.  
log [13:46:29.459] [info][data][plugins] Stopping plugin  
log [13:46:29.460] [info][plugins][translations] Stopping plugin  
log [13:46:29.461] [info][plugins][spaces] Stopping plugin  
log [13:46:29.462] [info][features][plugins] Stopping plugin  
log [13:46:29.463] [info][plugins][timelion] Stopping plugin  
log [13:46:29.464] [info][code][plugins] Stopping plugin  
log [13:46:29.465] [info][licensing][plugins] Stopping plugin  
log [13:46:29.467] [info][plugins][security] Stopping plugin

FATAL Error: Port 5601 is already in use. Another instance of Kibana may be running!

Its throwing the same error though no other process is using this 5601. Same happens when i give different port number.

Please help me to resolve this. Any help is much appreciated!! Thanks in advance.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 8, 2020, 5:48pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/2 "2020-01-08T17:48:11Z")

</div>

Something seems wrong, because if the server couldn't start, I don't think you would see

```auto
log [13:46:29.378] [info][listening] Server running at http://localhost:5601

```

What command are you using to start Kibana, or is this installed as a service?

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 8, 2020, 5:57pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/3 "2020-01-08T17:57:58Z")

</div>

Based on some tests I did, it looks like your log file is a merge of multiple instances of Kibana.

> [@Vinoth\_kumar\_Ramasam](#):
>
> I just followed the steps given in the official website.

Can you share more information about what setup steps you followed?

---

<div class="post-metadata">

**Author:** ![Vinoth\_kumar\_Ramasam](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/vinoth_kumar_ramasam/32/60294_2.png) [@Vinoth\_kumar\_Ramasam](https://discuss.elastic.co/u/Vinoth_kumar_Ramasam)\
**Post date:** [January 8, 2020, 6:15pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/4 "2020-01-08T18:15:42Z")

</div>

Thanks for your response. I downloaded the kibana set up for Windows and unzipped it. Then, I modified the kibana.yml for elastic Search host. Finally, initiated the kibana.bat from the command prompt.

One more thing I noted is that, same steps working fine in Windows 10 and I can launch the Kibana successfully. But, it's not working in Windows 8.1. not sure that could be a reason but just want to highlight that.

---

<div class="post-metadata">

**Author:** ![tsullivan](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tsullivan/32/31077_2.png) [@tsullivan](https://discuss.elastic.co/u/tsullivan)\
**Post date:** [January 10, 2020, 4:36pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/5 "2020-01-10T16:36:51Z")

</div>

That is strange. It sounds like it could be a bug with the launching script.

Would you mind filing an issue on this behavior at [https://github.com/elastic/kibana/issues/new?template=Bug\_report.md](https://github.com/elastic/kibana/issues/new?template=Bug_report.md)?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [February 7, 2020, 4:41pm UTC](https://discuss.elastic.co/t/kibana-port-5601-is-already-in-use-another-instance-of-kibana-may-be-running/213804/6 "2020-02-07T16:41:57Z")

</div>

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