# Kibana Server stop via Kill Process

**URL:** <https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799>\
**Category:** Kibana\
**Created:** [March 4, 2019, 9:42pm UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799 "2019-03-04T21:42:56Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![clouduser](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@clouduser](https://discuss.elastic.co/u/clouduser)\
**Post date:** [March 4, 2019, 9:42pm UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799/1 "2019-03-04T21:42:56Z")

</div>

i modified the Kibana.yml and trying to restart the server. I dont have success in killing process

here is PS-elf

how do i kill kibana server and restart the kibana so it can pick new server.host value to connect with ElasticSearch

 ![kibana666](https://us1.discourse-cdn.com/elastic/original/3X/c/b/cb18f2d4e540a21dcb6fe11bc68690a3efbb01e9.gif)

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [March 5, 2019, 2:33am UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799/2 "2019-03-05T02:33:50Z")

</div>

Is this a docker container? If so, just restart the container.

The PID is what you want to send to the kill command, which you did originally. It doesn't appear to have actually worked, which is outside the realm of Kibana. Additionally, Kibana will handle a SIGHUP by reloading the configuration `kill -1 {PID}`

---

<div class="post-metadata">

**Author:** ![clouduser](https://avatars.discourse-cdn.com/v4/letter/c/e95f7d/32.png) [@clouduser](https://discuss.elastic.co/u/clouduser)\
**Post date:** [March 5, 2019, 3:54pm UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799/3 "2019-03-05T15:54:09Z")

</div>

I have deployed the docker image in kubernetes. If i restart the POD, the changes are gone.

any other options to stop the Kibana Server.

_Feature request to team_  
- Kindly include the stopServer command in future release of Kibana which is productive for end user instead of depending on Kill command.

Any options to restart the Kibana with my changes to Kibana.yml that runs on Kubernetes.

---

<div class="post-metadata">

**Author:** ![tylersmalley](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/tylersmalley/32/8833_2.png) [@tylersmalley](https://discuss.elastic.co/u/tylersmalley)\
**Post date:** [March 5, 2019, 8:54pm UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799/4 "2019-03-05T20:54:51Z")

</div>

Oh, ok - I understand the problem.

You need to either mount the kibana.yml as a volume, or probably the best route, would be to configure the hosts with an environment variable `ELATICSEARCH_HOSTS`. You should not be directly modifying elements inside the container and restarting processes within.

For more information: [https://www.elastic.co/guide/en/kibana/current/docker.html](https://www.elastic.co/guide/en/kibana/current/docker.html)

---

<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:** [April 2, 2019, 8:54pm UTC](https://discuss.elastic.co/t/kibana-server-stop-via-kill-process/170799/5 "2019-04-02T20:54:54Z")

</div>

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