Portal Index Issue after Upgrade from ArcGIS Enterprise 11.1 to 11.3 - invalid_alias_name_exception

Question

Hey community after upgrading the AGE environment we've got the issue that the Portal index couldn't be rebuild. You can see in the pic above that 123 users are missing. We cannot find them in the Portal UI. After executing the reindex, the log shows the following: Deleting Index ago-users Deleted Index ago-users Deleting Index ago-users Exception method [DELETE], host [https://localhost:7220], URI [/ago-users], status line [HTTP/1.1 404 Not Found] {"error":{"root_cause":[{"type":"index_not_found_exception","reason":"no such index [ago-users]","index":"ago-users","resource.id":"ago-users","resource.type":"index_or_alias","index_uuid":"_na_"}],"type":"index_not_found_exception","reason":"no such index [ago-users]","index":"ago-users","resource.id":"ago-users","resource.type":"index_or_alias","index_uuid":"_na_"},"status":404} Deleted Index ago-users Creating alias ago-users for index ago-users method [PUT], host [https://localhost:7220], URI [/ago-users/_alias/ago-users], status line [HTTP/1.1 400 Bad Request] {"error":{"root_cause":[{"type":"invalid_alias_name_exception","reason":"Invalid alias name [ago-users], an index exists with the same name as the alias","index":"ago-users","index_uuid":"qtOUCPcAQ9eJ3X6fCOhlrA"}],"type":"invalid_alias_name_exception","reason":"Invalid alias name [ago-users], an index exists with the same name as the alias","index":"ago-users","index_uuid":"qtOUCPcAQ9eJ3X6fCOhlrA"},"status":400} org.opensearch.client.ResponseException: method [PUT], host [https://localhost:7220], URI [/ago-users/_alias/ago-users], status line [HTTP/1.1 400 Bad Request] {"error":{"root_cause":[{"type":"invalid_alias_name_exception","reason":"Invalid alias name [ago-users], an index exists with the same name as the alias","index":"ago-users","index_uuid":"qtOUCPcAQ9eJ3X6fCOhlrA"}],"type":"invalid_alias_name_exception","reason":"Invalid alias name [ago-users], an index exists with the same name as the alias","index":"ago-users","index_uuid":"qtOUCPcAQ9eJ3X6fCOhlrA"},"status":400} at org.opensearch.client.RestClient.convertResponse(RestClient.java:376) at org.opensearch.client.RestClient.performRequest(RestClient.java:346) at org.opensearch.client.RestClient.performRequest(RestClient.java:321) at com.esri.gw.index.reindex.PortalElasticSearchManager.c(PortalElasticSearchManager.java:603) at.... What we've already done: 1. Reconfigure index >> >> no success 2. Reindex >> no success It seems to be are basic ElsaticSearch/OpenSearch Issue. Any ideas for a workaround? Thanks Max

MaxBöcke3 · Answer

At Port 7220, an opensearch cluster is running. The index is password-protected. A further approach is to compare the index content with the Postgresql content. Access to the Opensearch DB could be realized via curl requests. I guess, its an umlaut or special character issue... Can Esri provide the password - in the config file merely a bcrypt hash is stored...

Dan_Brumm · Answer

That is what they recommended to us as well. We are going to run ours tomorrow or next week.

MaxBöcke3 · Answer

We've also opened a Ticket at Esri Support. They recommend we should conduct an clean reinstallation of the portal application what isn't an really good approach from our point of view.

The admintool "Reconfigure" doesn't work. The process stops and the index can't be reconfigured and reindexed. Now we have to fiugure out if it's an error that prevents operation of the entire system.

Best Case is, that we get some proper information to fix the issue 🙂