Do_ypcall: clnt_call: RPC: Timed out

nisyp

faulters:

Despite much troubleshooting in my NIS/YP setup, rebooting systems, restarting & debugging ypbind, putting nscd to run, a group of newly purchased systems regularly spam my email with:

do_ypcall: clnt_call: RPC: Timed out
do_ypcall: clnt_call: RPC: Timed out
do_ypcall: clnt_call: RPC: Timed out

However, the users are (apparently) not affected by this – they can access network resources. Otherwise I would have a line of users in front of my door complaining… :).
This has been mostly an annoyance by now, but how can I get rid of it ?

Machines of other hardware specs (older, quad cores, duo cores) having exactly the same managed configuration just do well – almost never showing this kind of behavior.

I am on Fedora 17/64 on (pretty recent) Dell Optiplex 9010 machines with good RAM, disk etc.
The NIS/YP server is on CentOS, and other critical network resources that rely on it do just fine.

Any hints ? Thanks.

Best Answer

In my case system was doing hostlookup. In my /etc/nsswitch.conf file, hosts line was:

hosts: files nis dns

I have changed this hosts line to:

hosts: files dns [NOTFOUND=return]

I am always using DNS for host records, not NIS hosts.byname etc.