# Logstash restarts continuously with below error when enabling ilm

**URL:** <https://discuss.elastic.co/t/logstash-restarts-continuously-with-below-error-when-enabling-ilm/245934>\
**Category:** Logstash\
**Created:** [August 21, 2020, 3:35pm UTC](https://discuss.elastic.co/t/logstash-restarts-continuously-with-below-error-when-enabling-ilm/245934 "2020-08-21T15:35:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![sai\_kiran1](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sai_kiran1/32/44118_2.png) [@sai\_kiran1](https://discuss.elastic.co/u/sai_kiran1)\
**Post date:** [August 21, 2020, 3:35pm UTC](https://discuss.elastic.co/t/logstash-restarts-continuously-with-below-error-when-enabling-ilm/245934/1 "2020-08-21T15:35:44Z")

</div>

Hello,

Am working on ilm settings in elasticsearch output plugin(logstash plugin) and I see Logstash restarts continuously with below error.

`[2020-08-21T16:35:08,665][FATAL][logstash.runner] An unexpected error occurred! {:error=>#<LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError: LogStash::Outputs::ElasticSearch::HttpClient::Pool::BadResponseCodeError>, :backtrace=>["/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http_client/manticore_adapter.rb:80:in `perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:332:in `perform_request_to_url'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:319:in `block in perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:414:in `with_connection'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:318:in `perform\_request'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http\_client/pool.rb:326:in `block in Pool'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http_client.rb:341:in `exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/http\_client.rb:386:in `ilm_policy_exists?'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/ilm.rb:86:in `maybe\_create\_ilm\_policy'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/ilm.rb:11:in `setup_ilm'", "/usr/share/logstash/vendor/bundle/jruby/2.5.0/gems/logstash-output-elasticsearch-10.3.3-java/lib/logstash/outputs/elasticsearch/common.rb:54:in `block in setup\_after\_successful\_connection'"]}`

My logstash and template files are attached below :

Logstash Conf :

```auto
    input{
            udp {
                   port => 6571
           }
    }
    output {
            if [type] == "ilm_rollover" {
                    elasticsearch {
                                    template => "/etc/logstash/es_templates/ilm_rollover.json"
                                    template_name => "ilm_rollover.json"
                                    template_overwrite => true
                                    ilm_enabled => true
                                    ilm_rollover_alias => "ilm_rollover"
                                    ilm_pattern => "{now/d}-1"
                                    ilm_policy => "ilm_rollover"
                                    hosts => [" ***es_hosts***"]
                                    ssl => true
                                    cacert => "es.pem"
                            }
            }
    }

```

Template ilm\_rollover.json file :

```auto
     {
       "order": 0,
       "template": "ilm_rollover*",
       "settings": {
         "codec": "best_compression",
         "number_of_shards": "1",
         "number_of_replicas": "1",
         "index.routing.allocation.require.data": "hot"
     },
       "mappings": {
           "properties": {
                           "type": {
                                   "type": "keyword"
                           }
           }
       },
       "aliases": {}
   }

```

Thanks in advance..!

Regards,  
Sai

---

<div class="post-metadata">

**Author:** ![Badger](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/badger/32/25190_2.png) [@Badger](https://discuss.elastic.co/u/Badger)\
**Post date:** [August 21, 2020, 3:48pm UTC](https://discuss.elastic.co/t/logstash-restarts-continuously-with-below-error-when-enabling-ilm/245934/2 "2020-08-21T15:48:20Z")

</div>

Could that be [this](https://github.com/logstash-plugins/logstash-output-elasticsearch/issues/907) issue?

---

<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:** [September 18, 2020, 3:48pm UTC](https://discuss.elastic.co/t/logstash-restarts-continuously-with-below-error-when-enabling-ilm/245934/3 "2020-09-18T15:48:41Z")

</div>

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