# \[ERROR\]\[shield.authc.esnative\] error occurred while checking the native users for changes

**URL:** <https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542>\
**Category:** Elasticsearch\
**Created:** [April 10, 2018, 8:03pm UTC](https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542 "2018-04-10T20:03:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![ankumar](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@ankumar](https://discuss.elastic.co/u/ankumar)\
**Post date:** [April 10, 2018, 8:03pm UTC](https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542/1 "2018-04-10T20:03:06Z")

</div>

App team is seeing errors in app servers " None of the configured nodes were available:" at the same time we are seeing error message on all the nodes as below:. The issue resolved itself. I am just just curious is the errors on the app servers are related to the errors in ES logs.

[2018-04-10 10:07:00,544][ERROR][shield.authc.esnative] error occurred while checking the native users for changes  
Failed to execute phase [query\_fetch], all shards failed; shardFailures {RemoteTransportException[[indices:data/read/search[phase/query+fetch/scroll]]]; nested: SearchContextMissingException[No search context found for id [11633375]]; }  
at org.elasticsearch.action.search.SearchScrollQueryAndFetchAsyncAction.onPhaseFailure(SearchScrollQueryAndFetchAsyncAction.java:155)  
at org.elasticsearch.action.search.SearchScrollQueryAndFetchAsyncAction.access$300(SearchScrollQueryAndFetchAsyncAction.java:41)  
at org.elasticsearch.action.search.SearchScrollQueryAndFetchAsyncAction$1.onFailure(SearchScrollQueryAndFetchAsyncAction.java:142)  
at org.elasticsearch.action.ActionListenerResponseHandler.handleException(ActionListenerResponseHandler.java:46)  
at org.elasticsearch.transport.netty.MessageChannelHandler.handleException(MessageChannelHandler.java:212)  
at org.elasticsearch.transport.netty.MessageChannelHandler.handlerResponseError(MessageChannelHandler.java:202)  
at org.elasticsearch.transport.netty.MessageChannelHandler.messageReceived(MessageChannelHandler.java:136)  
at org.jboss.netty.channel.SimpleChannelUpstreamHandler.handleUpstream(SimpleChannelUpstreamHandler.java:70)  
at org.jboss.netty.channel.DefaultChannelPipeline.sendUpstream(DefaultChannelPipeline.java:564)  
at org.jboss.netty.channel.DefaultChannelPipeline$DefaultChannelHandlerContext.sendUpstream(DefaultChannelPipeline.java:791)

Can someone please help me in understanding this error ?

Thanks  
Anil

---

<div class="post-metadata">

**Author:** ![warkolm](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/warkolm/32/39224_2.png) [@warkolm](https://discuss.elastic.co/u/warkolm)\
**Post date:** [April 10, 2018, 8:04pm UTC](https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542/2 "2018-04-10T20:04:17Z")

</div>

If you are looking for assistance, simply posting an error from the logs without more context will not get you anywhere.

Please update your post so we can assist you.

---

<div class="post-metadata">

**Author:** ![ankumar](https://avatars.discourse-cdn.com/v4/letter/a/9fc29f/32.png) [@ankumar](https://discuss.elastic.co/u/ankumar)\
**Post date:** [April 10, 2018, 8:09pm UTC](https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542/3 "2018-04-10T20:09:09Z")

</div>

Updated the post with more details. Please help in understanding the issue.

---

<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:** [May 8, 2018, 8:09pm UTC](https://discuss.elastic.co/t/error-shield-authc-esnative-error-occurred-while-checking-the-native-users-for-changes/127542/4 "2018-05-08T20:09:15Z")

</div>

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