I´m trying to upgrade my server to 10.5.1 and I´m following the steps on url . Everytime I´m getting an error on Step 8
"Choose to Continue Portal Upgrade. .....Specify the user name, password, email, and identity question and answer of the initial administrator account. ...."
Here I´m running a federate/hosted server + Portal and Datastore on Linux (single machine).
I ran portaldiag to check and here the result.
Portal for ArcGIS 10.5.1 Diagnostic Tool
DIAG000: Check for installation as root [PASSED]
DIAG001: Check for 64-bit architecture [PASSED]
DIAG002: Check OS version [PASSED]
DIAG003: Check hostname for invalid characters [PASSED]
DIAG005: Check system limits [PASSED]
DIAG004: Check installed packages [PASSED]
DIAG016: Check Portal for ArcGIS ports [PASSED]
DIAG024: Check localhost resolution [PASSED]
DIAG029: Check file system type [PASSED]
DIAG020: Check hostname IP address mismatches [PASSED]
DIAG026: Check processes of Portal for ArcGIS core services [PASSED]
DIAG028: Check data directory [PASSED]
There were 0 failure(s) and 0 warning(s) found:
<Msg time="2017-10-16T12:26:22,906" type="SEVERE" code="209024" source="Portal Admin" process="27847" thread="12" methodName="" machine="smart.....oa.pt" user="" elapsed="">The process of creating a new site failed. Reverting site creation. Migration failed. Index Service configuration failed.</Msg>
<Msg time="2017-10-16T12:27:26,38" type="VERBOSE" code="217063" source="Portal" process="27764" thread="1" methodName="" machine="smart.....oa.pt" user="" elapsed="">The process monitor did not find the connection to the configuration store. The site may not have been initialized. After the site is initialized, the check for database processes will be reattempted.</Msg>
LOG: database system was shut down at 2017-10-16 04:25:49 PDT
LOG: connection received: host=xxxx port=58282
LOG: connection authorized: user=xx database=xx
LOG: disconnection: session time: 0:00:00.010 user=xx database=xx host=xxx port=5xxx
LOG: received fast shutdown request
LOG: aborting any active transactions
FATAL: terminating connection due to administrator command
LOG: disconnection: session time: 0:00:00.314 user=xx database=xx host=xx port=5xxx
LOG: autovacuum launcher shutting down
LOG: shutting down
LOG: database system is shut down
I'm getting a similar PostgreSQL error, however, mine is not the result of a migration. I started debugging today with the latest ArcGIS Enterprise 10.5.1 Linux single-machine deployment AMI found here. It worked fine for a couple hours as I rebuilt my server, loaded data, rebooted a couple times, and then the error appeared again:
$ tail -f /var/log/postgresql/postgresql-9.5-main.log
2017-11-26 22:22:57 UTC [21857-2] LOG: received fast shutdown request
2017-11-26 22:22:57 UTC [21857-3] LOG: aborting any active transactions
2017-11-26 22:22:57 UTC [450-21] user@db FATAL: terminating connection due to administrator command
2017-11-26 22:22:57 UTC [14000-5] user@db FATAL: terminating connection due to administrator command
2017-11-26 22:22:57 UTC [13231-5] user@db FATAL: terminating connection due to administrator command
2017-11-26 22:22:57 UTC [31819-8] user@db FATAL: terminating connection due to administrator command
2017-11-26 22:22:57 UTC [5160-3] user@db FATAL: terminating connection due to administrator command
2017-11-26 22:22:57 UTC [21862-2] LOG: autovacuum launcher shutting down
2017-11-26 22:22:57 UTC [21859-1] LOG: shutting down
2017-11-26 22:22:57 UTC [21859-2] LOG: database system is shut down
After this error occurred, PostgreSQL will not start again automatically on port 5432 even if I reboot the server. This only impacts my local PostgreSQL datastore, but Portal and ArcGIS Server keep running fine (since they appear to be running PostgreSQL on different ports: 9876 and 7654).
$ ps axf | grep 'postgres -D'
1728 ? S 0:00 /arcgis/datastore/framework/runtime/pgsql/bin/postgres -D /gisdata/arcgisdatastore/pgdata -p 9876
3137 ? S 0:00 /arcgis/portal/framework/runtime/pgsql/bin/postgres -D /gisdata/arcgisportal/db -p 7654
I have both a Dev and Test ArcGIS Enterprise instance running in Amazon AWS. Both instances had been running fine for several months, but my PostgreSQL database stopped working on both servers at the same time last week. I did not do any upgrades. I just rebooted the EC2 instances, and they both stopped working. I did noticed from looking back at an old snapshot that PostgreSQL had been upgraded somehow from 9.5.7 to 9.5.10. When I launched the new AMI today, it was already at 9.5.10 when I started, so I have no idea what changed or auto-upgraded in the last few hours. After doing some research, if I temporarily start the database using the following command, everything 'seems' to function correctly again (NOT an actual fix!):
$ sudo su postgres -c '/usr/lib/postgresql/9.5/bin/pg_ctl start -D /gisdata/data/pgdata/main'
Does anyone know what could be happening here or how to auto-launch this database again when the server boots? I know these AMIs are supposed to be a black box that you don't touch, but I don't know what else to try. I'm going to have to move the database to RDS for development (additional cost) or switch to a Windows server (additional cost).
Resolution: I switched to Amazon RDS for my primary PostgreSQL data store. It's worth the extra cost (more stable, automatic backups, dashboards, easy access to logs, etc..).
Did you ever figure out why it stopped working? I'm seeing a similar issue trying to install Portal on a Windows machine. At some point last month it went from working to not working, and I didn't make any changes.