Problem after installing a second orchestrator in PAM High Availablity
Article ID: 274738
Updated On:
Products
Issue/Introduction
After installing a second node for PAM HA, we can't access to the second node PAM homepage
Environment
Release : 4.4
Cause
Expected behavior
Resolution
Let's assume that we have two nodes and the first node is installed and started working as an active node
The second node is installed as a passive node and stated (It partially starts and monitors the active node.)
At this state, node1 configuration is
pam.disaster.support=true
original.installation.mode=Active
and Node2 configuration is
pam.disaster.support=true
original.installation.mode=Passive
Node 2 c2o.log shows, "Main Site is Reachable. Will ping again after"
State 2: Node1: crashed/not available, Node2: Active
Whenever node2 detects that node1 is not reachable, then it resumes further to start completely and starts recovering all the processes(which were executed on node1) from DB to execute them further and changes its configurations from passive to active.
Additional Information
The time to become active can be changed using the disaster.switch.time. Reference:
Feedback
