# Logstash doesn't reload config if ip is wrong 5.0.0

**URL:** <https://discuss.elastic.co/t/logstash-doesnt-reload-config-if-ip-is-wrong-5-0-0/64376>\
**Category:** Logstash\
**Created:** [October 30, 2016, 3:10pm UTC](https://discuss.elastic.co/t/logstash-doesnt-reload-config-if-ip-is-wrong-5-0-0/64376 "2016-10-30T15:10:35Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![glagidse](https://avatars.discourse-cdn.com/v4/letter/g/b4bc9f/32.png) [@glagidse](https://discuss.elastic.co/u/glagidse)\
**Post date:** [October 30, 2016, 3:10pm UTC](https://discuss.elastic.co/t/logstash-doesnt-reload-config-if-ip-is-wrong-5-0-0/64376/1 "2016-10-30T15:10:35Z")

</div>

My config file:

```
# The # character at the beginning of a line indicates a comment. Use
# comments to describe your configuration.
input {
    beats {
        host => "localhost"
        port => "5044"
    }
}
# The filter part of this file is commented out to indicate that it is
# optional.
filter {
    grok {
        match => { "message" => "%{COMBINEDAPACHELOG}" }
    }
    geoip {
        source => "clientip"
    }
}
output {
    elasticsearch {
        hosts => ["192.168.0.102:9200"]
    }
}

```

If hosts ip is correct, then everything is fine, but if it is wrong, then it keeps trying to check the health of elasticsearch and doesn't reload the config file if it's changed. This is on a windows machine.

---

<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:** [July 6, 2017, 4:31am UTC](https://discuss.elastic.co/t/logstash-doesnt-reload-config-if-ip-is-wrong-5-0-0/64376/2 "2017-07-06T04:31:59Z")

</div>

Closed on July 6, 2017, 4:31am UTC