Naming and Directory Services (DNS, NIS, and LDAP)

Object class violationError Number: 65Cause: An attempt has been made to write an LDAP entry that is invalid.Generally, this error is due to missing MUST attributes that can be caused by eitherof the following circumstances.■Bugs in the NISLDAPmapping file that create entries with missing attributes■ Attempts to add an AUXILIARY attribute to an object that does not existFor example, if a user name has not yet been created from the passwd.byxxxmap, an attempt to add auxiliary information to that user will fail.Solution: For bugs in the NISLDAPmapping file, check what was written in theserver error log to determine the nature of the problem.Can’t contact LDAP serverError Number: 81Cause: The ypserv file might be incorrectly configured to point to the wrongLDAP directory server. Alternatively, the directory server might not be running.Solution:■■Reconfigure the ypserv file to point to the correct LDAP directory server.To confirm that the LDAP server is running, become superuser, or assume anequivalent role, on the directory server and type:# pgrep -l slapdTimeoutError Number: 85Cause: An LDAP operation timed out, typically while updating a map from theDIT. The map might now contain out-of-date information.Solution: Increase the nisLDAPxxxTimeout attributes in the ypservconfiguration file.NIS-to-LDAP IssuesThe following problems could occur while running the N2L server. Possible causesand solutions are provided.Debugging the NISLDAPmapping FileThe mapping file, NISLDAPmapping, is complex. Many potential errors might causethe mapping to behave in unexpected ways. Use the following techniques to resolvesuch problems.Chapter 15 • Transitioning From NIS to LDAP (Overview/Tasks) 245