# After switching Elasticsearch Output - Logstash says it cannot reach old Elasticsearch Output Host

**URL:** <https://discuss.elastic.co/t/after-switching-elasticsearch-output-logstash-says-it-cannot-reach-old-elasticsearch-output-host/268116>\
**Category:** Logstash\
**Created:** [March 23, 2021, 4:01pm UTC](https://discuss.elastic.co/t/after-switching-elasticsearch-output-logstash-says-it-cannot-reach-old-elasticsearch-output-host/268116 "2021-03-23T16:01:10Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Moritz\_Kiesewetter](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/moritz_kiesewetter/32/51243_2.png) [@Moritz\_Kiesewetter](https://discuss.elastic.co/u/Moritz_Kiesewetter)\
**Post date:** [March 23, 2021, 4:01pm UTC](https://discuss.elastic.co/t/after-switching-elasticsearch-output-logstash-says-it-cannot-reach-old-elasticsearch-output-host/268116/1 "2021-03-23T16:01:10Z")

</div>

Hello Community,  
we've recently added a Node to our Cluster - which is supposed to handle the all the Logs which are processed by Logstash.  
Information:

Elasticsearch 7.10  
Logstash 7.10  
OS: CentOS 7

So i reconfigured my Output Files in /etc/logstash/conf.d/ the following:

```
output {
  if [type] != "syslog" and [type] != "apache" {
    elasticsearch {
        hosts => ["http://mtxsuelk02.matrix.ag:9200"]
        index => "%{[@metadata][beat]}-%{+YYYY.MM.dd}"
        user => sysadmin
        password => *******
    }
  }
}

```

Now i restarted logstash - but there are no logs comming in. I checked the logs and there i can read the following error:

> [2021-03-23T15:43:37,839][WARN][logstash.outputs.elasticsearch][main] Attempted to resurrect connection to dead ES instance, but got an error. {:url=\>"[http://sysadmin:xxxxxx@OldOutputIP:9200/](http://sysadmin:xxxxxx@OldOutputIP:9200/)", :error\_type=\>LogStash::Outputs::Elasticsearch::HttpClient::Pool::HostUnreachableError, :error=\>"Elasticsearch Unreachable: [[http://sysadmin:xxxxxx@OldOutputIP:9200/](http://sysadmin:xxxxxx@OldOutputIP:9200/)][Manticore::ClientProtocolException] OldOutputIP:9200 failed to respond"}

But if i search for any kind of config which still holds the OldOutputIP via

`grep oldoutip *`

There's no output. So i'm wondering why logstash still tries to connect to the old Elasticsearch Host. The connection of course won't work - because we encrypted that instance.

Can anyone help me?

Thanks in advance.

Kind regards,  
Mo

---

<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 20, 2021, 4:01pm UTC](https://discuss.elastic.co/t/after-switching-elasticsearch-output-logstash-says-it-cannot-reach-old-elasticsearch-output-host/268116/2 "2021-04-20T16:01:27Z")

</div>

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