Skip to Content
0
Former Member
Sep 08, 2016 at 05:03 AM

SAP ASE Cluster failed to start instance

46 Views

Hi,

One of our customer has newly implemented ASE-CE 16.0 SP01/EBF 24928 in a production setup. Recently they had a requirement to change the IP for both the nodes and post change, during startup of ASE Cluster the following error was reported.

file : SCC agent log on node1

[RMI TCP Connection(21)- <ipaddress>] - Error encountered in starting cluster <CLUSTER NAME>, instance <instance 2>

java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <HOSTNAME 2>; nested exception is:

java.net.ConnectException: Connection timed out]; nested exception is:

java.io.IOException: Failed to retrieve RMIServer stub: javax.naming.ServiceUnavailableException [Root exception is java.rmi.ConnectException: Connection refused to host: <HOSTNAME 2>; nested exception is:

java.net.ConnectException: Connection timed out]

file : ASE Instance 2 error log

kernel Instance '<instance 2>' (2) failed to get reply from coordinator '<instance 1>' (1) after sending JOIN request 15 times. Communication links may be down, or the cluster may have abruptly exited.

kernel ASE will check the quorum disk heartbeat values to determine if a cluster takeover is possible. This may take up to 1 second(s).

kernel Quorum heartbeat values have changed. Cluster takeover is not advised.

kernel ueshutdown: exiting

kernel Main thread performing final shutdown.

kernel Blocking call queue shutdown.

So basically the ASE 2nd Instance failed to start. Can anybody advice what is going wrong here.

Thanks.