VMware Identity Manager – problem with Analytics service


If you see this error on your VMware Identity Manager appliance dashboard it usually means there is an issue with ElasticSearch, in my case this was due to unassigned shards. Here are the steps I followed to fix the issue.

1.  SSH to the appliance or one of your appliances in the cluster. Login as root.

2.  Run the following command to determine if you have unassigned shards.

curl http://localhost:9200/_cluster/health?pretty

The output should look something like this:

cluster_name” : “horizon”,
“status” : “red”,
“timed_out” : false,
“number_of_nodes” : 3,
“number_of_data_nodes” : 3,
“active_primary_shards” : 176,
“active_shards” : 352,
“relocating_shards” : 0,
“initializing_shards” : 0,
“unassigned_shards” : 178,
“delayed_unassigned_shards” : 0,
“number_of_pending_tasks” : 0,
“number_of_in_flight_fetch” : 0

3. Run the following command to view the unassigned shards.

curl -XGET ‘http://localhost:9200/_cat/shards?h=index,shard,prirep,state,unassigned.reason’ | grep UNASSIGNED

4. Delete the unassigned shards by running the following command

curl -XDELETE ‘http://localhost:9200/v3_YYYY-MM-DD/

Once all the unassigned shards have been deleted refresh the dashboard and Analytics connection should be successful.

And running the curl http://localhost:9200/_cluster/health?pretty should report 0 unassigned shards and status: green.

Happy days!


Leave a Reply

Your email address will not be published. Required fields are marked *