DOC HOME SITE MAP MAN PAGES GNU INFO SEARCH PRINT BOOK
 
Troubleshooting NIS

ypserv crashes

When the ypserv(1Mnis) process crashes almost immediately and does not stay up even with repeated activations, the debug process is virtually identical to that previously described in ``ypbind crashes''. Check for the existence of the rpcbind(1Mtcp) daemon on the server as follows:

ps -eaf | grep rpcbind

Start rpcbind if you do not find the daemon. If it is there, enter:

rpcinfo yp_server | grep ypserv

and look for output similar to the following:

   100004    2     tcp  0.0.0.0.12.168  ypserv  superuser
   100004    2     udp  0.0.0.0.4.8  ypserv  superuser
   100004    2  ticlts  B 00 00 00  ypserv  superuser
   100004    2  ticots   06 00 00 00  ypserv  superuser
   100004    2  ticotsord   06 00 00 00  ypserv  superuser
Your machine will have different port numbers. As in the case of ypbind, there should be one entry per transport. If a transport is missing, ypserv has been unable to register its services with it. Stop and start NIS using sh /etc/inid.d/nis stop and sh /etc/inid.d/nis start, and then run rpcinfo again. If ypserv is still unable to register over one or more transports, reboot the machine.
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004