I am running my own dockerized setup to install all necessary Elastic-Stack components through debian packages in a "fresh" debian container.
Elasticsearch and the indices are starting fine in version 6.x
Starting with version 6 the kibana container does not start at all and exits immediately with the following error message:
kibana | FATAL "action.search.shard_count.limit" setting was not applied. Check for spelling errors and ensure that expected plugins are installed and enabled.
kibana exited with code 64
Tried many things to get it starting again:
- Setting a transient action.search.shard_count.limit
- Setting action.search.shard_count.limit to "null"
- Backing up old .kibana indices and starting with no .kibana index in order to start "with a clean slate"
The message still shows up and I have no clue where and how this setting gets involved.
Anything to be set in the cluster to start kibana again?