Hi @RandyBonds_Jr_
I'm guessing you are currently attempting to upgrade portal while logged in to the machine as !arcgis user.
My best guess is that the postgres upgrade is issuing pg_upgrade commands in a manner that doesn't explicitly specify a user, meaning it will simply try to use the current logged in user. Upon initial install of Portal, the postgres installation would likely have done something similar and created a username based on the current logged in user in its database.
I can think of a few ways to get around your current issue, but only the first in the below list may be considered supported.
- Login to the Portal machine with the initial user that installed Portal, then run the upgrade. Might help if this user is part of the local Administrators group on the machine.
- Create a new user in the postgres database to match what's missing in the error logs.
- Set Trust Authentication in pg_hba.conf file. Doing this can be used to effectively bypass database authentication regardless of the username supplied.
I would say option number 1 is your best bet without Support guidance. Support may not endorse the other 2 options.
Timo