after a period of time (sometimes 3 or 4 days), ypbind starts complaining that the NIS server is not responding. It will do this forever, until ypbind is restarted. Once restarted, ypbind immediatly sees the NIS master and has no problems. After a few days the problem will repeat itself.
Restarting makes yp work again to some degree, but processes that were doing NIS lookups get stuck (in D state it looks like via ps), and other processes (ie top) won't even start. So, in the end, we have to reboot to clear everything up on the FreeBSD machine.
The NIS master is a solaris machine.
This problem existed on 4.3 as well.
For bugs matching the following criteria:
Status: In Progress Changed: (is less than) 2014-06-01
Reset to default assignee and clear in-progress tags.
Mail being skipped
MARKED AS SPAM