# onPreFetchPhase listener \[org.elasticsearch.xpack.security.authz.SecuritySearchOperationListener@X\] failed

**URL:** <https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004>\
**Category:** Elasticsearch\
**Tags:** docker\
**Created:** [October 5, 2020, 2:07pm UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004 "2020-10-05T14:07:05Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [October 5, 2020, 2:07pm UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004/1 "2020-10-05T14:07:05Z")

</div>

Hello World!

I'm using Elastic Stack 6.8.12 and running into following issue:

elasticsearch' logs:

> XXXX | [2020-10-05T00:22:46,990][WARN][o.e.i.s.IndexShard] [XXXXX] [4] onPreFetchPhase listener [org.elasticsearch.xpack.security.authz.SecuritySearchOperationListener@50e79b24] failed  
> XXXX | org.elasticsearch.ElasticsearchSecurityException: [406] expected scroll indices access control

I cut line as it's extremely long (~5000 characters long).

I get numerous lines, one after another to the point where I run out of space (due to excessive logs).

Please advise.

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [October 6, 2020, 4:16pm UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004/2 "2020-10-06T16:16:08Z")

</div>

as the "band aid" solution, one can turn off logging completely ... 😟

---

<div class="post-metadata">

**Author:** ![Albert\_Zaharovits](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/albert_zaharovits/32/24390_2.png) [@Albert\_Zaharovits](https://discuss.elastic.co/u/Albert_Zaharovits)\
**Post date:** [October 29, 2020, 7:29am UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004/5 "2020-10-29T07:29:24Z")

</div>

@alexus The culprit is an annoying buggy consistency check. In 6.8.12 you can safely turn that logger off , eg:

> PUT /\_cluster/settings  
> {  
> "persistent": {  
> "logger.org.elasticsearch.xpack.security.authz.SecuritySearchOperrationListener": "off"  
> }  
> }

More options about logger configuration [Logging | Elasticsearch Guide [8.11] | Elastic](https://www.elastic.co/guide/en/elasticsearch/reference/current/logging.html)

**Alternatively you can upgrade to 6.8.13 where this issue is fixed altogether and no logging configuration is necessary.**

---

<div class="post-metadata">

**Author:** ![alexus](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/alexus/32/12696_2.png) [@alexus](https://discuss.elastic.co/u/alexus)\
**Post date:** [October 30, 2020, 6:17pm UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004/6 "2020-10-30T18:17:55Z")

</div>

Thank you! I confirm in 6.8.13 issue is resolved!

---

<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:** [November 27, 2020, 6:17pm UTC](https://discuss.elastic.co/t/onprefetchphase-listener-org-elasticsearch-xpack-security-authz-securitysearchoperationlistener-x-failed/251004/7 "2020-11-27T18:17:55Z")

</div>

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