Process Automation - Error messages show: Master node of Domain Orchestrator not found

Products

• CA Process Automation Base

Issue/Introduction

We have installed a node2 of PAM to have a clustered setup behind a loadbalancer. On the node2 server the messages below are in the c2o log file. We are not sure what they mean and we need to know if they are important. 

2019-08-20 12:42:45,302 ERROR [com.optinuity.c2o.transport.Resolver] [        Timer-7] Error getting master node of Domain Orchestrator - Master node of Domain Orchestrator  not found

com.optinuity.c2o.util.C2OException: Master node of Domain Orchestrator  not found

at com.optinuity.c2o.transport.Resolver.getDomainMasterNode(Resolver.java:1044)

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:260)

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:216)

at com.optinuity.c2o.c2oserver.ServerManager.performConfigTimerOperation(ServerManager.java:3563)

at com.optinuity.c2o.c2oserver.ServerManager.access$1100(ServerManager.java:252)

at com.optinuity.c2o.c2oserver.ServerManager$9.run(ServerManager.java:2149)

at java.util.TimerThread.mainLoop(Timer.java:555)

at java.util.TimerThread.run(Timer.java:505)

2019-08-20 12:42:45,302 ERROR [com.optinuity.c2o.transport.Resolver] [        Timer-7] Error retrieving transport URL of domain master - 

com.optinuity.c2o.util.C2OException: Error getting master node of Domain Orchestrator - Master node of Domain Orchestrator  not found

at com.optinuity.c2o.transport.Resolver.getDomainMasterNode(Resolver.java:1049)

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:260)

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:216)

at com.optinuity.c2o.c2oserver.ServerManager.performConfigTimerOperation(ServerManager.java:3563)

at com.optinuity.c2o.c2oserver.ServerManager.access$1100(ServerManager.java:252)

at com.optinuity.c2o.c2oserver.ServerManager$9.run(ServerManager.java:2149)

at java.util.TimerThread.mainLoop(Timer.java:555)

at java.util.TimerThread.run(Timer.java:505)

2019-08-20 12:42:45,302 ERROR [com.optinuity.c2o.c2oserver.ServerManager] [        Timer-7] Exception occurred while sending the HEARTBEAT - 

com.optinuity.c2o.util.C2OException: Error retrieving transport URL of domain master : Error getting master node of Domain Orchestrator - Master node of Domain Orchestrator  not found

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:287)

at com.optinuity.c2o.transport.Resolver.getDomainTransportURL(Resolver.java:216)

at com.optinuity.c2o.c2oserver.ServerManager.performConfigTimerOperation(ServerManager.java:3563)

at com.optinuity.c2o.c2oserver.ServerManager.access$1100(ServerManager.java:252)

at com.optinuity.c2o.c2oserver.ServerManager$9.run(ServerManager.java:2149)

at java.util.TimerThread.mainLoop(Timer.java:555)

 

at java.util.TimerThread.run(Timer.java:505)

Environment

Release : 4.3

Component : Process Automation

Clustered orchestrator setup

Cause

This can happen when the first node of a cluster has not completely started before the other nodes in the cluster are started. 

From a browser, run the following URL:

 

http://servername:8080/itpam/genericNoSecurity?method=getDomainMasterNode

 

Change the servername (and port if necessary) to the server name of each node in the cluster.

If the result either shows different servers as the domain master or shows nothing as in the following:

 

Then follow the steps in this document to resolve the issue.

Resolution

Stop all nodes in the cluster and verify that there are no java processes running to make sure the orchestrator has completely stopped. 

If there are lingering java processes that you cannot account for, kill those processes.

Start the first node and wait for it to start. Log in to the first node using the direct URL (server name of the orchestrator, not the load balancer URL).

Once you can log in successfully to the first node, all other secondary nodes can be started.

Verify that you can log into each secondary node using the direct URL.

Once all nodes are up, run the http://servername:8080/itpam/genericNoSecurity?method=getDomainMasterNode  URL again for each server.

You should now see each response showing a single server (node 1) as the domain master node as the following: