Upgrade from v3.2.0 to v3.2.X fails to occur


Article ID: 127163


Updated On:


CA Privileged Access Manager - Cloakware Password Authority (PA) PAM SAFENET LUNA HSM CA Privileged Access Manager (PAM)


We have a 3.2.0 PAM instance deployed in Azure and we are trying to upgrade it to version 3.2.X. The process seems to work fine but upon rebooting the instance as the last step in the upgrade, it shows that the appliance is still in 3.2.0.


This happens because enabling Diagnostics setting adds a new include directive to apache2.conf file in the PAM appliance. Since there is no new line at the end of apache2.conf file, this new directive gets added to the last line in apache2.conf file thus making it junk.

This is fixed in 3.2.4 where a new line is added to the end of apache2.conf file so that if the Diagnostics setting is enabled, the new directive is added in a new line.

However, this fix won't correct the existing PAM 3.2.x systems facing this issue as they will have become corrupted. Those need to be manually fixed by updating apache2.conf file.


CA PAM 3.2.0 to 3.2.2


Contact Broadcom support to have them access your appliance and add a newline to /etc/apache2/apache2.conf.