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

Console Message Displays When ypserv -ir (or -Ir) RunsProblem: A simple message is displayed on the console and the server exits (adetailed description is written to syslog).Cause: The syntax of the mapping file might be incorrect.Solution: Check and correct the syntax in the NISLDAPmapping file.NIS Daemon Exits at StartupProblem: When ypserv or other NIS daemons run, an LDAP-related errormessage is logged and the daemon exits.Cause: The cause might be one of the following:■■The LDAP server cannot be contacted.An entry found in an NIS map or in the DIT is incompatible with the mappingspecified.■ An attempt to read or write to the LDAP server returns an error.Solution: Examine the error log on the LDAP server. See the LDAP errors that arelisted in “Common LDAP Error Messages” on page 244.Unexpected Results From NIS OperationsProblem: NIS operations do not return the expected results, but no errors arelogged.Cause: Incorrect entries might exist in the LDAP or NIS maps, which results inmappings not completing as intended.Solution: Check and correct entries in the LDAP DIT and in the N2L versions ofthe NIS maps.1. Check that the correct entries exist in the LDAP DIT, and correct the entries asneeded.If you are using the Sun Java System Directory Server, start the managementconsole by running directoryserver startconsole.2. Check that the N2L versions of the NIS maps in the /var/yp directory containthe expected entries by comparing the newly generated map to the originalmap. Correct entries as needed.# cd /var/yp/domainname# makedbm -u test.byname# makedbm -u LDAP_test.bynameBe aware of the following when checking the output for the maps:■■The order of entries might not be the same in both files.Use the sort command before comparing output.The use of white space might not be the same in both files.Use the diff -b command when comparing output.Processing Order of NIS Maps246 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005