Hi, Jonathan.
I was so hoping that I could post back that using VMs with lowercase hostnames fixed our issues. We have spent almost two weeks recreating our system using new VMs with lowercase names. And, this morning I found the full restore using our new secondary server failed. It reported one of the same errors we saw on an earlier attempt -
Failed to restore the Portal for ArcGIS:
Url: https://<primary server domain name>/<portal wa>.
{"error":{"code":500,"details":null,"message":"Failed to import site. Failed to delete the database directory."}}
We cannot log into the Portal. There are no items in the content area. Portal admin only allows us to Upgrade. There are several dbnnnnnnnnnnnn directories in the arcgisportal directory.
The catalina log does have errors relating to a token:
17-Jun-2020 21:09:52.685 SEVERE [https-jsse-nio-7443-exec-10] com.esri.commons.web.rest.providers.BaseProvider.getValue Token Required.
It also has one noting a servlet error relating to the request and form parameters not being what is expected for the URI
https://<primary server domain name>/arcgis/portaladmin/importSite/?
"...contains form parameters in the request body but the request body has been consumed by the servlet or a servlet filter accessing the request parameters. Only resource methods using @FormParam will work as expected. Resource methods consuming the request body by other means will not work as expected.
17-Jun-2020 21:20:29.783 SEVERE [https-jsse-nio-7443-exec-8] com.sun.jersey.spi.container.ContainerResponse.mapMappableContainerException The RuntimeException could not be mapped to a response, re-throwing to the HTTP container
com.esri.arcgis.portal.admin.core.PortalException: The portal site has not been initialized. Please create a new site and try again."
The localhost log in the tomcat directory says the portal site has not been initialized. Please create a new site and try again.
The postgresql log has at least three errors stating that a particular .ready file is not found, for example:
2020-06-17 18:23:23 PDT: [4732]: LOG: could not create archive status file "pg_wal/archive_status/00000001000000000000002E.ready": No such file or directory
Looking in the Event Viewer for errors logged prior to the postgres errors, we found one event that stated the "Z:\arcgisportal\db is not a database cluster directory" and one that stated, "pg_ctl: server does not shut down".
There is an event regarding listening on a localhost ipv6 port. Does ipv6 need to be enabled for Enterprise? It is not on our VMs.
We do have a support request logged (#02547962), but I have not heard from the analyst since 6/3 when he emailed to say he was determining if he could create a test environment to test the uppercase host name issue.
I will send an update to our support analyst with the latest error information to find out if he has learned anything new.
Do you have any suggestions on additional things to try? Are there any other logs I should investigate?
Your input and feedback has been extremely helpful throughout this effort. Thanks for any suggestions or ideas you can provide.
Best, Dixie.