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

Elastic Stack Elasticsearch
1

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

2

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.

3

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

4

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