"Y"

yp_all RPC clnt_call (transport level) failure

Cause

At random times, a slave NIS server has a problem that causes ypbind(1M) to report: ypserver not responding and the machine must be rebooted. The syslog contains:

Dec 14 07:11:03 rahab syslog: yp_all - RPC clnt_call (transport level) failure:
RPC: Unable to receive; An event requires attention

Action

To workaround, increase the file descriptor limit in the yp startup script, /etc/rc2.d/S71rpc. Add this to the script before ypserv is started:

	ulimit -n 256

ypbind[int]: NIS server for domain "string" OK

Cause

This message appears after an "NIS server not responding" message to indicate that ypbind(1M) is able to communicate with an NIS server again.

Action

Proceed with your work. This message is purely informational.

ypbind[int]: NIS server not responding for domain "string"; still trying

Cause

This means that the NIS client daemon ypbind(1M) cannot communicate with an NIS server for the specified domain. This message appears when a workstation running the NIS naming service has become disconnected from the network, or when NIS servers are down or extremely slow to respond.

Action

If other NIS clients are behaving normally, check the Ethernet cabling on the workstation that is getting this message. On SPARC machines, disconnected network cabling also produces a series of "no carrier" messages. On x86 machines, the above message might be your only indication that network cabling is disconnected.

If many NIS clients on the network are giving this message, go to the NIS server in question and reboot or repair as necessary. To locate the NIS server for a domain, run the ypwhich(1) command. When the server machine comes back in operation, NIS clients give an "NIS server for domain OK" message.

See Also

For more information about ypbind(1M), see the section on administering secure NFS in the NFS Administration Guide.

ypwhich: can't communicate with ypbind

Cause

This message from the ypwhich(1) command indicates that the NIS binder process ypbind(1M) is not running on the local machine.

Action

If the system is not configured to use NIS, this message is normal and expected. Configure the system to use NIS if necessary.

If the system is configured to use NIS, but the ypbind(1M) process is not running, invoke the following command to start it up:

# /usr/lib/netsvc/yp/ypbind -broadcast