Bug 29903 - [nis] ypbind(8) loses connection to NIS master and never recovers
Summary: [nis] ypbind(8) loses connection to NIS master and never recovers
Status: Open
Alias: None
Product: Base System
Classification: Unclassified
Component: bin (show other bugs)
Version: Unspecified
Hardware: Any Any
: Normal Affects Only Me
Assignee: freebsd-bugs (Nobody)
Depends on:
Reported: 2001-08-20 16:30 UTC by Chris McClellen
Modified: 2021-06-02 14:43 UTC (History)
2 users (show)

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Chris McClellen 2001-08-20 16:30:01 UTC
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.
Comment 1 Eitan Adler freebsd_committer freebsd_triage 2017-12-31 07:59:30 UTC
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
Comment 2 JackMease 2019-02-27 05:29:09 UTC
Comment 3 Openair 2021-06-02 14:43:35 UTC