# Logstash autorelaod even the config file not changed
**URL:** https://discuss.elastic.co/t/logstash-autorelaod-even-the-config-file-not-changed/328881
**Category:** Logstash
**Created:** [March 30, 2023, 4:35am UTC](https://discuss.elastic.co/t/logstash-autorelaod-even-the-config-file-not-changed/328881 "2023-03-30T04:35:16Z")
**Posts on this page:** 2
**Page:** 1
### Author:  [@kannan\_raj](https://discuss.elastic.co/u/kannan_raj)
#### Post date: [March 30, 2023, 4:35am UTC](https://discuss.elastic.co/t/logstash-autorelaod-even-the-config-file-not-changed/328881/1 "2023-03-30T04:35:16Z")
Hello Team,
We use the logstash to consume the messages from Kafka and indexing into Elasticsearch and we use the vault to drop the cert and keys to connect to Kafka and Elasticsearch. vault rotates the cert and key depends on the expiry date.
Now, these certs and keys will change depending on the expiry date and I have to reload the logstash pipeline. With auto-reload I think the logstash will look for any change in the config but in my case, the logstash config will not change.
I do not want to go with force reloading, because we have 100+ logstash and would be difficult to make it automatic.
```auto
kill -SIGHUP 14175
```
How can we make the logstash to reload the config file in this case?
Regards
Kannan P
---
### Author:  [@system](https://discuss.elastic.co/u/system)
#### Post date: [April 27, 2023, 4:35am UTC](https://discuss.elastic.co/t/logstash-autorelaod-even-the-config-file-not-changed/328881/2 "2023-04-27T04:35:27Z")
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.