Elasticsearch cluster red state

Hello all,

I am trying to reset elastic user password , while resting password with bin/elasticsearch-reset-password -u elastic command ,my cluster status changed from yellow state to red state . all master nodes are up and running and joined in cluster. kindly check below log ,and suggest me any solution.

**[2023-05-06T19:20:43,954][INFO ][o.e.x.s.a.RealmsAuthenticator] [master2] Authentication of [elastic] was terminated by realm [reserved] - failed to authenticate user [elastic]**
**[2023-05-06T19:21:05,109][INFO ][o.e.x.s.a.f.FileUserPasswdStore] [master2] users file [/etc/elasticsearch/users] changed. updating users...**
**[2023-05-06T19:21:05,112][INFO ][o.e.x.s.a.f.FileUserRolesStore] [master2] users roles file [/etc/elasticsearch/users_roles] changed. updating users roles...**
**[2023-05-06T19:21:09,058][INFO ][o.e.x.s.s.SecurityIndexManager] [master2] security index does not exist, creating [.security-7] with alias [.security]**
**[2023-05-06T19:21:09,128][INFO ][o.e.c.m.MetadataCreateIndexService] [master2] [.security-7] creating index, cause [api], templates [], shards [1]/[0]**
**[2023-05-06T19:21:09,143][INFO ][o.e.c.r.a.AllocationService] [master2] current.health="RED" message="Cluster health status changed from [YELLOW] to [RED] (reason: [index [.security-7] created])." previous.health="YELLOW" reason="index [.security-7] created"**
**[2023-05-06T19:21:45,130][INFO ][o.e.x.s.a.f.FileUserPasswdStore] [master2] users file [/etc/elasticsearch/users] changed. updating users...**
**[2023-05-06T19:21:45,131][INFO ][o.e.x.s.a.f.FileUserRolesStore] [master2] users roles file [/etc/elasticsearch/users_roles] changed. updating users roles...
ers roles...
[2023-05-06T19:22:39,342][WARN ][r.suppressed             ] [master2] path: /_security/user/elastic/_password, params: {pretty=, username=elastic}
org.elasticsearch.action.UnavailableShardsException: [.security-7][0] [1] shardIt, [0] active : Timeout waiting for [1m], request: indices:data/write/update
        at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction.retry(TransportInstanceSingleOperationAction.java:226) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction.doStart(TransportInstanceSingleOperationAction.java:181) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.action.support.single.instance.TransportInstanceSingleOperationAction$AsyncSingleAction$2.onTimeout(TransportInstanceSingleOperationAction.java:249) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.cluster.ClusterStateObserver$ContextPreservingListener.onTimeout(ClusterStateObserver.java:326) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.cluster.ClusterStateObserver$ObserverClusterStateListener.onTimeout(ClusterStateObserver.java:264) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.cluster.service.ClusterApplierService$NotifyTimeout.run(ClusterApplierService.java:643) ~[elasticsearch-8.7.1.jar:?]
        at org.elasticsearch.common.util.concurrent.ThreadContext$ContextPreservingRunnable.run(ThreadContext.java:891) ~[elasticsearch-8.7.1.jar:?]
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1144) ~[?:?]
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:642) ~[?:?]
        at java.lang.Thread.run(Thread.java:1623) ~[?:?]
**

Did you manually delete the security indices at all?

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