IManager cluster option on OES2 Linux cluster, caused hi util on the NetWare ldap server. 503 error service is unavailable

7 node OES2 mixed NetWare and Linux cluster. The problem occurred  in iManager when selecting the "Clusters" tab and then selecting the "Cluster Options" and searching for the cluster NDS object. When this search was conducted, the NetWare 6.5 sp7 Ldap server (outside the cluster) would go to 100% utilization and peg there for several minutes. Eventually, iManager would timeout on the search with a 503 error.. (service is  unavailable) This problem only happened if the master ip node in the cluster was running on a Linux box. If the master node were moved to a NetWare server in the cluster, the utilization problem on the Ldap server did not occur. Also, if the "Cluster Manager" option was selected in IManager instead of the "Cluster Options" tab, the problem did not occur, but the search finished successfully.

This appeared to be a problem with  the  cluster plug-in in iManager. The cluster plug-in in iManager makes a connection to owcimom and passes in the object to search for with the necessary parameters to conduct the search. Cimom then passes this information to ldap which passes it to eDirectory.  A coredump showed that ldap was doing a global search for the cluster object starting in the current ou container. It will search all sub containers as well from that level. Ldap should not be doing a global search through all scantiness because the cluster object is in that ou container already.

This was a problem in the clstrlib.py file. It was modified to do the search more economically. This clstrlib.py file has not been tested on OES1 and is not recommended. On each of the OES2 Linux nodes in the cluster:

1. Back up /opt/novell/ncs/bin/clstrlib.py.

2. Copy the attached file to /opt/Novell/ncs/bin/clstrlib.py.

3. You must chmod this file to have at least r and x permissions

4. Restart NCS.

 

09/22/2008  05:16 PM            76,869 clstrlib.py

 

This file is available from Novell support until it's put out on the channel.

How to put IManager into debug mode on OES2 Linux:

 

1) in iManager go to configure (one of the round buttons on the top).
2) go to iManager Server>configure iManager
3) go to the event logging tab
4) Select Errors, Warnings, and Debug Information messages
5) Make sure the Send log output to Debug.html File is checked.
6) Make sure you clear the old logs out so it starts new.
7) Select Save

8) Reproduce the problem

9) Send in the /var/opt/novell/iManager/nps/WEB-INF/logs/debug.html