Hi all,
we have an installation of a high available portal 10.8.1 in windows with a federated ArcGIS Server. Everything works perfectly. We decided to upgrade to the latest version 10.9.1.
We started installing the portal software in both machines, as described here. Installing the software worked perfectly for both machines. We run the installation simultaneously as suggested in the link above.
The portal windows service restarted. Then we noticed that only the javaw.exe was running and no java.exe was running.
We followed the instuctions here to make sure that the C:\Program Files\ArcGIS\Portal\framework\runtime\tomcat\conf\server.xml is correctly set and that the indexes doesn't have any issue.
The portal logs have no error.
The elastic logs mention "can not be imported as a dangling index, as index with same name already exists in cluster metadata" for all the indexes.
The windows Event viewer mentions that "postmaster.pid does not exist".
We run a portal repair with the windows installation and we restart the whole machine but it didn't work.
Does anyone have a similar issue or any experience? Any help is appreciated :-).
Solved! Go to Solution.
Ok, we have found the solution for our issues. We had 2 different issues, one during the "Continue Upgrade" step and one during the "Post Upgrade" step.
Did you only run the setups, or did you continue the upgrade after the setup completed? Until you continue the portal upgrade, only the javaw.exe process will be running. That's expected. Once the upgrade is fully completed, all other processes will start.
Ahh good to know.
Only the setups. It is impossible to continue on the upgrade. I have deleted the cache from the browser (edge) and i just see a white page. Also i have noticed that somehow the user that is assigned to log on the portal service, has lost the rights to access the installation folder e.g. C:\Program Files\ArcGIS\Portal. It is a domain user, not a local machine user. I had to set them back up manually
Ok, we have found the solution for our issues. We had 2 different issues, one during the "Continue Upgrade" step and one during the "Post Upgrade" step.