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

NIS-to-LDAP RestrictionsWhen the N2L server has been set up, the NIS source files are no longer used.Therefore, do not run ypmake on an N2L server. If ypmake is accidentally run, such asfor an existing cron job, the N2L service is unaffected. However, a warning is loggedsuggesting that yppush should be called explicitly.NIS-to-LDAP TroubleshootingThis section covers two areas of troubleshooting:■ “Common LDAP Error Messages” on page 244■ “NIS-to-LDAP Issues” on page 245Common LDAP Error MessagesSometimes the N2L server logs errors that relate to internal LDAP problems, resultingin LDAP-related error messages. Although the errors are nonfatal, they indicateproblems to investigate. For example, the N2L server might continue to operate, butprovide out-of-date or incomplete results.The following list includes some of the common LDAP error messages that you mightencounter when implementing the N2L service. Error descriptions, and possiblecauses and solutions for the errors, are included.Administrative limit exceededError Number: 11Cause: An LDAP search was made that was larger than allowed by the directoryserver’s nsslapd-sizelimit attribute. Only partial information will be returned.Solution: Increase the value of the nsslapd-sizelimit attribute, or implementa VLV index for the failing search.Invalid DN SyntaxError Number: 34Cause: An attempt has been made to write an LDAP entry with a DN that containsillegal characters. The N2L server attempts to escape illegal characters, such as the+ symbol, that are generated in DNs.Solution: Check the LDAP server error log to find out which illegal DNs werewritten, then modify the NISLDAPmapping file that generated the illegal DNs.244 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005