Cluster Failover Node Launcher Displays Started, Instead its Stopped.
book
Article ID: 85018
calendar_today
Updated On:
Products
CA Automic Dollar Universe
Issue/Introduction
Affects Release version(s): 5
Error Message : In the launcher log file: ########################### Starting START_ORD.COM_KSH Starting on company : PP9100 Starting on area : X exec(): 0509-036 Cannot load program ./uxord because of the following errors: rtld: 0712-001 Symbol u_tcp_select_init was referenced from module uxord(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol u_get_lan_sigpipe_ign was referenced from module uxord(), but a runtime definition of the symbol was not found. rtld: 0712-001 Symbol u_init_lan_sigpipe_ign was referenced from module uxord(), but a runtime definition of the symbol was not found. ###########################
Description :The startup procedure on the failover node of a cluster is saying that the launcher is started, but we don't have any error in the universe.log and the launcher is stopped and in Idle status.
Environment
OS: IBM AIX OS Version: All Unix.
Cause
Cause type: By design Root Cause: The two nodes of the cluster have 2 different libraries versions. This occurs when the libraries of the 2 nodes are not shared and are installed in 2 different directories. (e.g: /usr/lib/libux_v533)
Resolution
Backup the libraries on the failover node, and copy the libraries from the main node to the faliover node, You will then be able to start the launcher on the failover node.