# The logstash reload config manually not work

**URL:** <https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895>\
**Category:** Logstash\
**Created:** [January 12, 2024, 3:06am UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895 "2024-01-12T03:06:44Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jevonsnotes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jevonsnotes/32/130317_2.png) [@jevonsnotes](https://discuss.elastic.co/u/jevonsnotes)\
**Post date:** [January 12, 2024, 3:06am UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/1 "2024-01-12T03:06:44Z")

</div>

as the topic, i send the kill -SIGHUP xxx to the logstash ,but the config still same.

version 8.11.3  
linux: Linux CS-gxxt-tyzj-03 4.19.90-52.22.v2207.ky10.aarch64 #1 SMP Tue Mar 14 11:52:45 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

---

<div class="post-metadata">

**Author:** ![yago82](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yago82/32/97755_2.png) [@yago82](https://discuss.elastic.co/u/yago82)\
**Post date:** [January 12, 2024, 2:26pm UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/2 "2024-01-12T14:26:32Z")

</div>

> [@jevonsnotes](#):
>
> as the topic, i send the kill -SIGHUP xxx to the logstash ,but the config still same.
> 
> version 8.11.3  
> linux: Linux CS-gxxt-tyzj-03 4.19.90-52.22.v2207.ky10.aarch64 #1 SMP Tue Mar 14 11:52:45 CST 2023 aarch64 aarch64 aarch64 GNU/Linux

Hi,

The `kill -SIGHUP` command is used to reload the configuration in some applications, but in the case of Logstash, this is not the correct way to reload the configuration.

If you want to manually reload the configuration, you can send a `SIGHUP` signal to the Logstash process, but this requires the `--config.reload.automatic` option to be enabled.

bin/logstash --config.reload.automatic

Regards

---

<div class="post-metadata">

**Author:** ![leandrojmp](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/leandrojmp/32/107231_2.png) [@leandrojmp](https://discuss.elastic.co/u/leandrojmp)\
**Post date:** [January 12, 2024, 2:38pm UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/3 "2024-01-12T14:38:08Z")

</div>

> [@yago82](#):
>
> If you want to manually reload the configuration, you can send a `SIGHUP` signal to the Logstash process, but this requires the `--config.reload.automatic` option to be enabled.
> 
> bin/logstash --config.reload.automatic

Just to add that this only works when you run Logstash from the command line, if Logstash is running as a service, which is way more common, this setting needs to be added to `logstash.yml` and the service needs to be restarted once.

```auto
config.reload.automatic: true

```

---

<div class="post-metadata">

**Author:** ![jevonsnotes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jevonsnotes/32/130317_2.png) [@jevonsnotes](https://discuss.elastic.co/u/jevonsnotes)\
**Post date:** [January 15, 2024, 1:03am UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/4 "2024-01-15T01:03:18Z")

</div>

got it ,thks

---

<div class="post-metadata">

**Author:** ![jevonsnotes](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/jevonsnotes/32/130317_2.png) [@jevonsnotes](https://discuss.elastic.co/u/jevonsnotes)\
**Post date:** [January 15, 2024, 1:03am UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/5 "2024-01-15T01:03:54Z")

</div>

thks.

---

<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 12, 2024, 1:04am UTC](https://discuss.elastic.co/t/the-logstash-reload-config-manually-not-work/350895/6 "2024-02-12T01:04:14Z")

</div>

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