When the ypbind Daemon Becomes Inoperable

Edit online

If the ypbind daemon repeatedly crashes immediately after it is started, look for a problem in some other part of the system.

Check for the presence of the portmap daemon by typing:
```
ps -ef | grep portmap
```
If the daemon is not running, reboot the system.
If the portmap daemon is running but does not operate reliably, check the network software.
Try to communicate with the portmap daemon on your machine from a different machine that is operating normally. From such a machine, type:
```
rpcinfo -p client
```
where client is the host name of the machine.

If the portmap daemon is up and running correctly, the output appears in a format similar to the following:

program   vers proto  port
100007     2    tcp   1024  ypbind
100007     2    udp   1028  ypbind
100007     1    tcp   1024  ypbind
100007     1    udp   1028  ypbind
100021     1    tcp   1026  nlockmgr
100024     1    udp   1052  status
100020     1    udp   1058  llockmgr
100020     1    tcp   1028  llockmgr
100021     2    tcp   1029  nlockmgr
100012     1    udp   1083  sprayd
100011     1    udp   1085  rquotad
100005     1    udp   1087  mountd
100008     1    udp   1089  walld
100002     1    udp   1091  rusersd
100002     2    udp   1091  rusersd
100001     1    udp   1094  rstatd
100001     2    udp   1094  rstatd
100001     3    udp   1094  rstatd

If the daemons are not listed, the ypbind daemon is unable to register its services. Reboot the machine.
If the daemons are listed, but they change each time you try to restart the ypbind daemon, reboot the system (even though the portmap daemon is up).