On Wed, Mar 16, 2016 at 07:16:36PM -0000, John Sopko wrote:
> We use nis ybind which is started out of /etc/init.d/nis which fails
> because rpcbind is not running.
Ok, but rpcbind should start as soon as nis asks for it.
What does 'systemctl status rpcbind.socket' show on boot (i.e. before you've
manually started rpcbind)?
Would ybind for some reason be trying to connect to rpcbind via localhost,
instead of using the UNIX socket (/run/rpcbind.sock)?
On Wed, Mar 16, 2016 at 07:16:36PM -0000, John Sopko wrote:
> We use nis ybind which is started out of /etc/init.d/nis which fails
> because rpcbind is not running.
Ok, but rpcbind should start as soon as nis asks for it.
What does 'systemctl status rpcbind.socket' show on boot (i.e. before you've
manually started rpcbind)?
Would ybind for some reason be trying to connect to rpcbind via localhost, sock)?
instead of using the UNIX socket (/run/rpcbind.