Nodes shown as Missing on replication leader only after cluster startup
search cancel

Nodes shown as Missing on replication leader only after cluster startup

book

Article ID: 279030

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM)

Issue/Introduction

You had to stop the cluster, e.g. to update the license. After turning the cluster back on, it is in a bad state. The replication leader (first node in the primary site) shows the other nodes as Missing on the Cluster Status page. The other primary site nodes show all nodes with a Green status, but none of them is marked as replication leader.

Environment

Observed once with 4.1.1.

Cause

Communication to port 8443 was broken on the replication leader.

Resolution

Upgrade to PAM 4.1.6 or a later release. PAM 4.1.6 added local monitoring of the 443 and 8443 ports. If the listener for either one is gone, the service listening on those ports will be restarted automatically.

As a temporary workaround, stop the cluster again, reboot the replication leader and then start it.