New node not accessible after install in PAM HA environment
search cancel

New node not accessible after install in PAM HA environment

book

Article ID: 274738

calendar_today

Updated On: 05-19-2025

Products

CA Process Automation Base Process Automation Manager

Issue/Introduction

After installing a second node for PAM HA, the PAM homepage of the second node is not accessible.

Environment

Release: Process Automation Manager 4.4

Cause

This is by design. It's expected behavior for the second node to be inaccessible since it's not completely started. It will be accessible once it becomes active. 

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 the 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 setting.