13.07.2015 Views

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

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

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

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Problem: Object class violations occur.Cause: When the ypserv -i comm<strong>and</strong> is run, each <strong>NIS</strong> map is read <strong>and</strong> itscontents are written into the DIT. Several maps might contribute attributes to thesame DIT object. Generally, one map creates most of the object, including all theobject’s MUST attributes. Other maps contribute additional MAY attributes.Maps are processed in the same order that nis<strong>LDAP</strong>objectDN attributes appear inthe <strong>NIS</strong><strong>LDAP</strong>mapping file. If maps containing MAY attributes get processed beforemaps containing MUST attributes, then object class violations occur. See Error 65 in“Common <strong>LDAP</strong> Error Messages” on page 244 for more information about thiserror.Solution: Reorder the nis<strong>LDAP</strong>objectDN attributes so that maps are processed inthe correct order.As a temporary fix, rerun the ypserv -i comm<strong>and</strong> several times. Each time thecomm<strong>and</strong> is executed, more of the <strong>LDAP</strong> entry is built up.Note – Mapping in such a way that all of an object’s MUST attributes cannot be createdfrom at least one map is not supported.N2L Server Timeout IssueProblem: The server times out.Cause: When the N2L server refreshes a map, the result might be a large <strong>LDAP</strong>directory access. If the Sun Java System <strong>Directory</strong> Server is not correctlyconfigured, this operation might time out before completion.Solution: To avoid directory server timeouts, modify the Sun Java System<strong>Directory</strong> Server attributes manually or by running the idsconfig comm<strong>and</strong>. See“Common <strong>LDAP</strong> Error Messages” on page 244 <strong>and</strong> “<strong>NIS</strong>-to-<strong>LDAP</strong> Best PracticesWith Sun Java System <strong>Directory</strong> Server” on page 241 for details.N2L Lock File IssueProblem: The ypserv comm<strong>and</strong> starts but does not respond to <strong>NIS</strong> requests.Cause: The N2L server lock files are not correctly synchronizing access to the <strong>NIS</strong>maps. This should never happen.Solution: Type the following comm<strong>and</strong>s on the N2L server.# svcadm disable network/nis/server:default# rm /var/run/yp_maplock /var/run/yp_mapupdate# svcadm enable network/nis/server:defaultN2L Deadlock IssueProblem: The N2L server deadlocks.Chapter 15 • Transitioning From <strong>NIS</strong> to <strong>LDAP</strong> (Overview/Tasks) 247

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!