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

Check the crontab File and ypxfr Shell ScriptInspect the root crontab file, and check the ypxfr shell script it invokes.Typographical errors in these files can cause propagation problems. Failures to refer toa shell script within the /var/spool/cron/crontabs/root file, or failures to referto a map within any shell script can also cause errors.Check the ypservers MapAlso, make sure that the NIS slave server is listed in the ypservers map on themaster server for the domain. If it is not, the slave server still operates perfectly as aserver, but yppush does not propagate map changes to the slave server.Work AroundIf the NIS slave server problem is not obvious, you can work around it while youdebug using rcp or ftp to copy a recent version of the inconsistent map from anyhealthy NIS server. The following shows how to transfer the problem map.ypslave# rcp ypmaster:/var/yp/mydomain/map.\* /var/yp/mydomainThe * character has been escaped in the command line, so that it will be expanded onypmaster, instead of locally on ypslave.ypserv CrashesWhen the ypserv process crashes almost immediately, and does not stay up evenwith repeated activations, the debug process is virtually identical to that described in“ypbind Crashes” on page 117. Check for the existence of the rpcbind daemon asfollows.ypserver% ps -e | grep rpcbindReboot the server if you do not find the daemon. Otherwise, if the daemon is running,type the following and look for similar output.% rpcinfo -p ypserver% program vers proto port service100000 4 tcp 111 portmapper100000 3 tcp 111 portmapper100068 2 udp 32813 cmsd...100007 1 tcp 34900 ypbind100004 2 udp 731 ypserv100004 1 udp 731 ypserv100004 1 tcp 732 ypserv100004 2 tcp 32772 ypservYour machine might have different port numbers. The four entries representing theypserv process are the following.120 System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) • January 2005