# Kibana process automatically respawns when killed

**URL:** <https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826>\
**Category:** Kibana\
**Created:** [October 9, 2019, 12:09pm UTC](https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826 "2019-10-09T12:09:07Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dan\_Healy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_healy/32/55607_2.png) [@Dan\_Healy](https://discuss.elastic.co/u/Dan_Healy)\
**Post date:** [October 9, 2019, 12:09pm UTC](https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826/1 "2019-10-09T12:09:08Z")

</div>

I have a fresh clean install of CentOS 7, ES 7.4 and Kibana 7.4. I have disabled SELinux and firewalld for now.  
I installed ES and Kibana according to the guide ([https://www.elastic.co/guide/en/kibana/7.4/install.html](https://www.elastic.co/guide/en/kibana/7.4/install.html)).

When I start Kibana (service kibana start) the error log says that another instance is already started. When I check the /var/run/kibana.pid, it shows a different PID then when I run 'ps -aux | grep kibana'. If I kill the running PID, it's automatically respawned with a new PID.

For the life of me, I cannot find out why the process is being respawned. If I change the pid file to match the running process, then run "service kibana stop", the PID is removed and again respawned.

---

<div class="post-metadata">

**Author:** ![Dan\_Healy](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dan_healy/32/55607_2.png) [@Dan\_Healy](https://discuss.elastic.co/u/Dan_Healy)\
**Post date:** [October 9, 2019, 12:19pm UTC](https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826/2 "2019-10-09T12:19:02Z")

</div>

I fixed it but I'm not sure why it worked. Apparently "service kibana stop" and "systemctl stop kibana" does different things. When I run the latter, it works to stop the running process. I found that the PID is controlled by systemctl, so I ran "systemctl status " and it showed as kibana.service.

---

<div class="post-metadata">

**Author:** ![cjcenizal](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/cjcenizal/32/11216_2.png) [@cjcenizal](https://discuss.elastic.co/u/cjcenizal)\
**Post date:** [October 9, 2019, 6:40pm UTC](https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826/3 "2019-10-09T18:40:03Z")

</div>

Thanks for sharing your solution, Dan.

---

<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:** [November 6, 2019, 6:40pm UTC](https://discuss.elastic.co/t/kibana-process-automatically-respawns-when-killed/202826/4 "2019-11-06T18:40:08Z")

</div>

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