PAM Upgrade to 4.2.1/4.2.0 was not successful

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

Privileged Access Management (PAM) Admin successfully upgraded 3 out of their 4 server to 4.2.1/4.2.0.   However one server, which the attempted to upgrade 3 times consistently fails with the following errors in VMware Console log:

In PAM Console see the following messages:

Starting PAM. . .

Waiting for MySQL to get in running state...

Waiting for MySQL to get in running state for x minutes.

Eventually, the PAM Splash screen will come up, but you will not be able to get to any PAM UI's.

Cause

On a very minor subset of PAM servers the permissions and/or file structure of our PAM DB is incorrect.

Resolution

You will have to revert the snapshot of the PAM Appliance to its original PAM Version.

Then open up a support case, in which Support will have to SSH into the PAM Appliance and fix the permissions/symbolic links of our PAM DB.