DE HAC Standby server does not start due to a handshake failure

Document ID:  TEC1850151
Last Modified Date:  08/01/2017
{{active ? 'Hide' : 'Show'}} Technical Document Details

Products

  • CA Workload Automation DE

Releases

  • CA Workload Automation DE:Release:11.3
  • CA Workload Automation DE:Release:11.3 SP1
  • CA Workload Automation DE:Release:11.3 SP2
  • CA Workload Automation DE:Release:11.3 SP3

Components

  • CA DSERIES WORKLOAD AUTOMATION:DSRIES
  • CA DSERIES WORKLOAD AUTOMATION HIGH AVAILABILITY:DSERHA
Introduction:

The host of the DE Primary server has got its DNS name changed, and after that the Standby server does not start due to the following error:

************************************************ 
* Server is shutting down... 
* Time:Thu Jul 06 15:15:18 MDT 2017 
************************************************* 
* Reason: Handshake from <DE Primary> returned guid (null) does not match current peer guid <DE Primary> shutting down. Two servers may already be running or server may not be configured properly. 
************************************************

Question:

Does the changed DNS name cause this problem?

Answer:

The Standby server performs a lookup of the Primary server via RMI registry by using the host and the port, and sends a handshake request using the peer server detail. 
If Primary is not reachable and the handshake request got into the SocketTimeout, it is considered as not matched group id, i.e. the 'guid (null)' as shown in the error. 

Hence, yes, if the DNS name of the Primary was changed it would be a reason for the issue.

Please help us improve!

Will this information enable you to resolve your issue?

Please tell us what we can do better.

{{feedbackText.length ? feedbackText.length : '0'}}/255

{{status}}

Not what you were looking for?

Search Again >

Product Information

Support by Product >

Communities

Join a Community >