rpcbind失败的可能原因：停止NetworkManager服务，等注册成功后再开启

niserver搭建时遇到此问题

以下参考https://linux.die.net/man/8/ypbind

ypbind finds the server for NIS domains and maintains the NIS binding information. The client (normaly the NIS routines in the standard C library) could get the information over RPC from ypbind or read the binding files. The binding files resides in the directory/var/yp/binding and are conventionally named[domainname].[version]. The supported versions are 1 and 2. There could be several such files since it is possible for an NIS client to be bound to more than one domain.

After a binding has been established, ypbindwill send YPPROC_DOMAIN requests to the current NIS server at 20 seconds intervals. If it doesn't get an response or the NIS server reports that he doesn't have this domain any longer, ypbind will search for a new NIS server. All 15 minutes ypbind will check to see if the current NIS server is the fastest. If it find a server which answers faster, it will switch to this server. You could tell ypbind to use network broadcasts to find a new server, what is insecure, or you could give it a list of known secure servers. In this case ypbind will send a ping to all servers and binds to first one which answers.

Unless the option -debug is used, ypbind detaches itself from the controlling terminal and puts itself into background. ypbind uses syslog(3) for logging errors and warnings. At startup or when receiving signal SIGHUP, ypbind parses the file /etc/yp.conf and tries to use the entries for its initial binding.

A broadcast entry in the configuration file will overwrite a ypserver/server entry and a ypserver/server entry broadcast. If all given server are down, ypbind will not switch to use broadcast. ypbind will try at first/etc/hosts and then DNS for resolving the hosts names from /etc/yp.conf. If ypbind couldn't reconfigure the search order, it will use only DNS. If DNS isn't available, you could only use IP-addresses in /etc/hosts.ypbind could only reconfigure the search order with glibc 2.x. If the -broadcast option is specified, ypbindwill ignore the configuration file. If the file does not exist or if there are no valid entries, ypbind exit.

This ypbind version listens for DBUS messages from NetworkManager. If no NetworkManager is running at startup, ypbind will behave as usual and assumes there is a working network connection. IfNetworkManager is running on the system, ypbind will only search and providde NIS informations, ifNetworkManager tells that a network connection is available. If NetworkManager establishes a connection,ypbind will reread all configuration files, registers at the local portmapper and try to search NIS servers. IfNetworkManager drops a connection, ypbind will unregister from portmapper.

以下内容参考http://www.sirena.org.uk/2007/03/27/nis-and-network-manager-in-debian-etch/

The version of NIS to be shipped with Debian 4.0 has support for Network Manager in ypbind,the program responsible for ensuring that NIS client systems can access a NIS server. Unfortunately Network Manager is targeted at client systems with dynamically assigned addresses and does not support some common network configurations, particularly static ones. When Network Manager is run on a computer with such a configuration it presents misleading information to NIS, causing NIS to think that it is not connected to a network and fail to connect to a server.

转载于:https://www.cnblogs.com/jonathanyue/p/9301294.html