# Error Running Curator Rollover method

**URL:** <https://discuss.elastic.co/t/error-running-curator-rollover-method/120719>\
**Category:** Elasticsearch\
**Created:** [February 20, 2018, 8:20pm UTC](https://discuss.elastic.co/t/error-running-curator-rollover-method/120719 "2018-02-20T20:20:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![hartfordfive](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/hartfordfive/32/44794_2.png) [@hartfordfive](https://discuss.elastic.co/u/hartfordfive)\
**Post date:** [February 20, 2018, 8:20pm UTC](https://discuss.elastic.co/t/error-running-curator-rollover-method/120719/1 "2018-02-20T20:20:45Z")

</div>

I'm currently collecting metricbeat data from many systems that gets stored in an index with the format of 'metricbeat-YYYY.mm.dd'. When I attempt to test my curator action to run a rollover, I get the following error:

```auto
curator.exceptions.ConfigurationError: Configuration: options: Location: Action ID "3", action "rollover": Bad Value: "(could not determine)", expected str for dictionary value @ data['new_index']. Check configuration file.

```

Below are some other relevant details of my current configurations

**Version of elasticsearch-curator** : 5.4  
**Version of Elasticsearch** : 6.1

**Elasticsearch output config that writes the metricbeat data:**

```auto
elasticsearch {
  id => "es_out_metricbeat"
  document_id => "%{[@metadata][fingerprint]}"
  hosts => ["http://localhost:9200"]
  index => "metricbeat-%{+YYYY.MM.dd}"
  manage_template => false
  upsert => true
}

```

**The first part of my metricbeat index template (mappings omitted due to size):**

```auto
{
  "order": 1,
  "index_patterns": [
    "metricbeat-*",
    "*-*-metricbeat-*",
    "metricbeat*"
  ],
  "settings": {
    "index": {
      "codec": "best_compression",
      "mapping": {
        "total_fields": {
          "limit": "10000"
        }
      },
      "refresh_interval": "10s",
      "number_of_routing_shards": "30",
      "number_of_shards": "1"
    }
  },
  "aliases": {
    "metricbeat": {}
  }
}

```

**My actions file contains:**

```auto
actions:
  1:
    action: rollover
    description: >-
      Rollover the metricbeat indices, which should be in the
      form of prefix-000001 (or similar), or prefix-YYYY.MM.DD-1.
    options:
      disable_action: False
      name: metricbeat
      conditions:
        max_age: 10s
      extra_settings:
        index.number_of_shards: 1
        index.number_of_replicas: 1
        aliases:
          metricbeat: {}
      continue_if_exception: False

```

Would anyone know what my issue might be? I appreciate any help!

---

<div class="post-metadata">

**Author:** ![theuntergeek](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/theuntergeek/32/44961_2.png) [@theuntergeek](https://discuss.elastic.co/u/theuntergeek)\
**Post date:** [February 27, 2018, 1:44am UTC](https://discuss.elastic.co/t/error-running-curator-rollover-method/120719/2 "2018-02-27T01:44:08Z")

</div>

For rollover, it automatically preserves the alias, so this part is redundant, and may result in a bad API call. If you were adding to another alias, then you'd add it here.

> [@hartfordfive](#):
>
> ```auto
> aliases:
> metricbeat: {}
> 
> ```

Beyond that, the action file provided doesn't match the error message. The error message says that `Action ID "3"` has a misconfiguration. But the pasted action file segment shows:

> [@hartfordfive](#):
>
> ```auto
> actions:
> 1:
> action: rollover
> description: >-
> 
> ```

Why the discrepancy? It appears there's a misconfiguration, but the pasted configuration seems different in at least that regard.

---

<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:** [March 27, 2018, 1:44am UTC](https://discuss.elastic.co/t/error-running-curator-rollover-method/120719/3 "2018-03-27T01:44:19Z")

</div>

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