Skip to main content

Hi,

After upgrading my CR on-premise server the home dashboard is playing the message that can’t connect to Elasticsearch server, everything is working fine - just the dashboard is not working.

 

The information available at \ProgramData\AA\Logs\ is informing that “999/1000” shard are open.

“ 17T14:22:49.070+00:00","audit_format_version":4,"audit_request_remote_address":"127.0.0.1","audit_request_privilege":"indices:admin/auto_create","audit_node_host_address":"127.0.0.1","audit_request_effective_user":"es_client","audit_trace_indices":_"metric_logs_20240401"],"audit_node_host_name":"localhost"} due to
org.opensearch.common.ValidationException: Validation Failed: 1: this action would add w10] total shards, but this cluster currently has e999]/h1000] maximum shards open;” 

 

Any suggestion is appreciated.

@aeugenio  check elastic search indexes, seems it reached to max 

https://localhost:47599 login with es_client with elastic search password 

check the count and see if indexes are more than 100, free up with some of old indexes and restart elastic service

 

@rbkadiyam I encountered a similar issue while upgrading from v29 to v32 as well. I followed Article #000007733 to check for the counts and any duplicates, but stopped short of deleting any indices. Would that be the next recommended step, based on the message below?

 

Error message in WebCR.log file

{"error":{"root_cause":c{"type":"validation_exception","reason":"Validation Failed: 1: this action would add l10] total shards, but this cluster currently has l999]/ 1000] maximum shards open;"}],"type":"validation_exception","reason":"Validation Failed: 1: this action would add l10] total shards, but this cluster currently has l999]/ 1000] maximum shards open;"},"status":400}

Please contact support at support@automationanywhere.com if you are still experiencing an error.

Reply


Terms & ConditionsCookie settings