We have experienced a number of recurring issues during installs and upgrades of PMP on Linux.  The main one is that the files and directories are being installed with "root" as the owner instead of the PMP user, even when the install script is being run as PMP.  This results in the PMP service not starting up.  The first time we encountered this, we were informed to chown the directories to the correct user.  We have since had to do this for nearly every install and some upgrades.  It would be preferable that this were done by the install script so we don't have to continually troubleshoot startup problems with the PMP service.

Next, as a High Availability installation, the upgrade process is cumbersome and error prone, again causing problems with the secondary server starting up and with replication.  If the secondary server is currently working, why must we (basically) delete it and rebuild the secondary server from scratch?  If this process was an upgrade and not an outright replacement, the issues of missing files, certs, incorrect ownership of directories, etc. could be avoided.

Has anyone else encountered these problems, and have you found a way to resolve them?