Cluster node fails to join cluster

  • 7009244
  • 25-Aug-2011
  • 30-Apr-2012

Environment

Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 2
Novell Open Enterprise Server 2 (OES 2) Linux Support Pack 3

Situation

Nodes fail to join the cluster
/var/log/boot.msg shows this error:

   FATAL: Error inserting vll (/lib/modules/2.6.16.60-0.62.1-smp/weak-updates/ncs/vll.ko):  Operation not permitted
failed

Modifying the ldap server list in the/etc/opt/novell/ncs/clstrlib.conf file to point to another LDAP server allows the node to join the cluster and update or pull the cluster information down through ldap.  However, pointing the ldap server to itself would always result in the failure to join the cluster and the "/opt/novell/ncs/bin/ncs-configd.py -init" script would simply return back to the prompt without updating cluster files in "/var/opt/novell/ncs/" directory. 

Resolution

Delete the LDAP group object for the nonworking server and recreate it.  Make sure to relink it to the LDAP Server object. 
Unloaded and reloaded NLDAP.  "nldap -u" to unload and "nldap -l" to load. 
This allows to point the clstrlib.conf "ldap setting" --> 'ldaps://<ip address of local host>:636" to itself and clustering to come up and join the cluster.  

See also TID 7006055 - Loading vll.ko gives a fatal error when starting Novell Cluster Services and TID 7006031 - NCS Fails Upon Startup for more details.

Additional Information

Troubleshooting:
Take a NDSTRACE +LDAP on both servers and output from ldaptest.py script and compare the output between the remote ldap server (which works) and the local ldap server (which fails).  In this case the only difference between the two outputs was the case of the "cn" attribute.  
Example:
"CN=cluster." was returned from local server ldap search which failed.
"cn=cluster." was returned from remote ldap search which worked.
Compare the LDAP Group objects between the working and nonworking servers and check if the nonworking LDAP Group object is missing the "CN --> cn " Attribute map along with several others.

Feedback service temporarily unavailable. For content questions or problems, please contact Support.