Kibana Status Red due to Monitoring Plugin

[James_Tighe]

Hi Guys,

I am having a slight issue with my Kibana node for my Elasticstack.

It has been running fine for ages and I have not had any problems, but now Kibana will not load due to

plugin:monitoring@5.0.0 Elasticsearch is still initializing the Monitoring indices

I am not too sure what is happening to cause this. The cluster health is showing as red

{
"cluster_name" : "PEMLOGGING",
"status" : "red",
"timed_out" : false,
"number_of_nodes" : 2,
"number_of_data_nodes" : 2,
"active_primary_shards" : 103,
"active_shards" : 206,
"relocating_shards" : 0,
"initializing_shards" : 0,
"unassigned_shards" : 12,
"delayed_unassigned_shards" : 0,
"number_of_pending_tasks" : 0,
"number_of_in_flight_fetch" : 0,
"task_max_waiting_in_queue_millis" : 0,
"active_shards_percent_as_number" : 94.4954128440367
}

Upon investigation the unassigned shards appear to be the monitoring indices.

red open .monitoring-es-2-2017.02.24 y66ymNMhS7maAe-pThgOrA 1 1

All other nodes are fine and data is being sent to my cluster with no issues.

How can I fix the broken monitoring indices? I ideally need them to work and don't want to disable monitoring.

Kind Regards

James

[sujitthakalanth (Sujitha)]

Please verify that the versions of Elastic and kibana should be the same...

[James_Tighe]

Kibana is running 5.0.0 as is Elasticsearch.

I have not made any changes to the software or hardware other than extending disk via LVM, after which the cluster was running fine with no issues.

As stated the only indices that are red are the monitoring indices which is rather odd.