EEM stopped talking to LDAP
Article ID: 107066
Updated On:
Products
CA Workload Automation AE - Business Agents (AutoSys)
CA Workload Automation AE - Scheduler (AutoSys)
Workload Automation Agent
Issue/Introduction
The EEM server was working fine with two nodes. After adding the third node the first two nodes fail to bind to LDAP.
Environment
EEMÂ Release: 12.6
EEM HA with three nodes
EEM HA with three nodes
Cause
While troubleshooting we found that the dxserver could not be started on the primary server.
The itechpoz_trace.log on the primary had the following error.
* [1] 20180717.093219.452 DSA_I2690 Multiwrite-DISP: Peer 'itechpoz-SECONDARY-SERVER' updated
* [64] 20180717.093320.505 DSA_E2735 Multiwrite-DISP: Unable to synchronize with peer 'itechpoz-THIRD-SERVER'
The itechpoz_trace.log on the primary had the following error.
* [1] 20180717.093219.452 DSA_I2690 Multiwrite-DISP: Peer 'itechpoz-SECONDARY-SERVER' updated
* [64] 20180717.093320.505 DSA_E2735 Multiwrite-DISP: Unable to synchronize with peer 'itechpoz-THIRD-SERVER'
Resolution
The primary server was not able to communicate with the THIRD server.
The server was using /etc/resolve.conf for ip resolution and it was blank.After updating the file manually and Restarting dxserver and now the EEM HA is working fine.
The server was using /etc/resolve.conf for ip resolution and it was blank.After updating the file manually and Restarting dxserver and now the EEM HA is working fine.
Feedback
Yes
No
Powered by
