We have repeatedly tried to upgrade Portal 10.9.1 to 11.2 with no luck. We've opened a support ticket with no solution as of yet.
The process:
- We take a backup
- We run the 11.2 setup, when prompted for the Windows Service Account, it is grayed out with what is the portal is currently running at (our_domain\!arcgis). We enter the password, etc, and everything is great.
- When on the next upgrade step (the web based part), the PostgreSQL upgrade fails, we see two items in the logs that seem to point to the issue:
- Copying old pg_xact to new server *failure*
- FATAL: role "!arcgis" does not exist
Checking cluster versions ok
Checking database user is the install user ok
Checking database connection settings ok
Checking for prepared transactions ok
Checking for system-defined composite types in user tables ok
Checking for reg* data types in user tables ok
Checking for contrib/isn with bigint-passing mismatch ok
Checking for user-defined encoding conversions ok
Checking for user-defined postfix operators ok
Checking for incompatible polymorphic functions ok
Creating dump of global objects ok
Creating dump of database schemas
gwdb
postgres
template1
ok
Checking for presence of required libraries ok
Checking database user is the install user ok
Checking for prepared transactions ok
Checking for new cluster tablespace directories ok
If pg_upgrade fails after this point, you must re-initdb the
new cluster before continuing.
Performing Upgrade
------------------
Analyzing all rows in the new cluster ok
Freezing all rows in the new cluster ok
Deleting files from new pg_xact ok
Copying old pg_xact to new server
*failure*
Consult the last few lines of "pg_upgrade_utility.log" for
the probable cause of the failure.
Failure, exiting
It appears that the copying failure is causing the issue of the incorrect user being used. Looks like it is defaulting to using the OS user when it later tries to start the DB.
Anyone seen this?
