# Using kill -1 pid to force logstash to reload the configuration file does not take effect **URL:** \ **Category:** Logstash\ **Created:** [December 13, 2016, 4:51pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906 "2016-12-13T16:51:30Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![sockaddr\_in](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sockaddr_in/32/20854_2.png) [@sockaddr\_in](https://discuss.elastic.co/u/sockaddr_in)\ **Post date:** [December 13, 2016, 4:51pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/1 "2016-12-13T16:51:30Z")
I use the following method to make the logstash reload configuration file, but did not take effect, what is the reason? My logstash version: 5.1.1 The method comes from [https://www.elastic.co/guide/en/logstash/current/reloading-config.html#\_how\_automatic\_config\_reloading\_works](https://www.elastic.co/guide/en/logstash/current/reloading-config.html#_how_automatic_config_reloading_works) ![](https://us1.discourse-cdn.com/elastic/original/2X/d/dc63934702d200978cc6e836126759abd60b1960.png) ---
**Author:** ![marke72](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marke72/32/10832_2.png) [@marke72](https://discuss.elastic.co/u/marke72)\ **Post date:** [December 14, 2016, 3:45pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/2 "2016-12-14T15:45:33Z")
I have the same issue since updating to 5.1.1 I've been using this feature since it was released. But since updating to the latest version it has stopped working. I have to restart the service to get the new configuration loaded. ---
**Author:** ![sockaddr\_in](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sockaddr_in/32/20854_2.png) [@sockaddr\_in](https://discuss.elastic.co/u/sockaddr_in)\ **Post date:** [December 14, 2016, 4:06pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/3 "2016-12-14T16:06:08Z")
First，thank you very much! Meaning from 2.3 to 5.0 version can use the kill -1 command to send a SIGHUP signal to the logstash process to reload the configuration file? ---
**Author:** ![marke72](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marke72/32/10832_2.png) [@marke72](https://discuss.elastic.co/u/marke72)\ **Post date:** [December 14, 2016, 4:28pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/4 "2016-12-14T16:28:35Z")
It worked in the version before, 5.0.2, and every other version before that. But since I updated to 5.1.1, it's stopped working. In my logs it shows `[2016-12-14T08:40:13,897][WARN][logstash.runner] SIGHUP received.` every time I reload the process. That's normal even from before the update but it use to show a chunk of the configuration that was changed right after. Now it doesn't. It's like it doesn't see any change in the configuration or just doesn't look. ---
**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\ **Post date:** [December 14, 2016, 9:30pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/5 "2016-12-14T21:30:49Z")
It'd be worth raising this on Github - [github.com/elastic/logstash/issues](http://github.com/elastic/logstash/issues) 🙂 ---
**Author:** ![sockaddr\_in](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sockaddr_in/32/20854_2.png) [@sockaddr\_in](https://discuss.elastic.co/u/sockaddr_in)\ **Post date:** [December 15, 2016, 3:11am UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/6 "2016-12-15T03:11:11Z")
Today, I tried to use 5.0.0, it can really work, the version is indeed the problem, very grateful! ![](https://us1.discourse-cdn.com/elastic/original/2X/c/c4a6f525e9266309f46d453bd2e9cb456c79f1c4.png) ---
**Author:** ![sockaddr\_in](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sockaddr_in/32/20854_2.png) [@sockaddr\_in](https://discuss.elastic.co/u/sockaddr_in)\ **Post date:** [December 15, 2016, 3:13am UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/7 "2016-12-15T03:13:16Z")
Thank you:slight\_smile: ---
**Author:** ![marke72](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/marke72/32/10832_2.png) [@marke72](https://discuss.elastic.co/u/marke72)\ **Post date:** [December 15, 2016, 2:36pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/8 "2016-12-15T14:36:22Z")
Just opened an issue on github [#6417](https://github.com/elastic/logstash/issues/6417) ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [January 12, 2017, 2:36pm UTC](https://discuss.elastic.co/t/using-kill-1-pid-to-force-logstash-to-reload-the-configuration-file-does-not-take-effect/68906/9 "2017-01-12T14:36:31Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.