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

Note – For security reasons, the use of the -ypset and -ypsetme options should belimited to debugging purposes under controlled circumstances. Use of the -ypsetand -ypsetme options can result in serious security breaches because while thedaemons are running, anyone can alter server bindings causing trouble for others andpermitting unauthorized access to sensitive data. If you must start ypbind with theseoptions, once you have fixed the problem you should kill ypbind and restart it againwithout those options.ypbind CrashesIf ypbind crashes almost immediately each time it is started, look for a problem insome other part of the system. Check for the presence of the rpcbind daemon bytyping the following.% ps -e | grep rpcbindIf rpcbind is not present or does not stay up or behaves strangely, consult your RPCdocumentation.You might be able to communicate with rpcbind on the problematic client from amachine operating normally. From the functioning machine, type the following.% rpcinfo clientIf rpcbind on the problematic machine is fine, rpcinfo produces the followingoutput.program version netid address service owner...100007 2 udp 0.0.0.0.2.219 ypbind superuser100007 1 udp 0.0.0.0.2.219 ypbind superuser100007 1 tcp 0.0.0.0.2.220 ypbind superuser100007 2 tcp 0.0.0.0.128.4 ypbind superuser100007 2 ticotsord \000\000\020H ypbind superuser100007 2 ticots \000\000\020K ypbind superuser...Your machine will have different addresses. If the addresses are not displayed,ypbind has been unable to register its services. Reboot the machine and run rpcinfoagain. If the ypbind processes are there and they change each time you try to restartthe NIS service, reboot the system, even if the rpcbind daemon is running.NIS Problems Affecting Many ClientsIf only one or two clients are experiencing symptoms that indicate NIS bindingdifficulty, the problems probably are on those clients. See “NIS Problems Affecting OneClient” on page 114. If many NIS clients are failing to bind properly, the problemprobably exists on one or more of the NIS servers.Chapter 7 • NIS Troubleshooting 117