# Failing to execute IndicesStatsAction 5.2.2

**URL:** <https://discuss.elastic.co/t/failing-to-execute-indicesstatsaction-5-2-2/80735>\
**Category:** Elasticsearch\
**Created:** [March 30, 2017, 7:15pm UTC](https://discuss.elastic.co/t/failing-to-execute-indicesstatsaction-5-2-2/80735 "2017-03-30T19:15:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![nhend](https://avatars.discourse-cdn.com/v4/letter/n/96bed5/32.png) [@nhend](https://discuss.elastic.co/u/nhend)\
**Post date:** [March 30, 2017, 7:15pm UTC](https://discuss.elastic.co/t/failing-to-execute-indicesstatsaction-5-2-2/80735/1 "2017-03-30T19:15:04Z")

</div>

[o.e.c.InternalClusterInfoService] Failed to execute IndicesStatsAction for ClusterInfoUpdateJob because it is unable to authenticate the user. I have a custom authentication extension in x-pack and it is failing on that. I had the same sort of setup in my 2.3.3 cluster (with a custom auth), and everything seems to be running smoothly

I have tried enabling file and native realms and changed the orders in my elasticsearch.yml file but it is still hitting my custom auth and failing.

---

<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:** [April 27, 2017, 7:15pm UTC](https://discuss.elastic.co/t/failing-to-execute-indicesstatsaction-5-2-2/80735/2 "2017-04-27T19:15:26Z")

</div>

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