After upgrade to PAM 4.1.7 cannot add server in cluster

Products

• CA Privileged Access Manager (PAM)

Issue/Introduction

PAM Admin did an upgrade to PAM 4.1.7 and when attempting to add server into the cluster it was not successful.

Environment

PAM 4.1.7

Cause

Inside their Tomcat logs it was being flooded with the message:

[hz._hzInstance_1_ClusterManager.priority-generic-operation.thread-0] com.hazelcast.internal.cluster.impl.ClusterJoinManager.null [<IP Address>]:5900 [ClusterManager] [3.12] Could not create connection to possible master [<IP Address>]:5900

Observations:

• iptables --list on the primary server, had the necessary rules in place for remote primary to be allowing to connect
• nmap -sV -p 5900 <primary> -> showed no firewall issues
• name resolution worked both ways.

 

 

Resolution

Please open a support case with Broadcom support, who can possibly make DB changes on the backend of PAM