In a message of Wed, 25 May 2016 20:24:41 +0200, Michael Biebl writes: >> Restarting rpc bind gets me back to restart nis successfull. >> >> # service rpcbind restart >> # service nis restart >> >> Reverting to rpcbind 0.2.1-6.1 solves the problem. Please notice >> that this happens only on systemd machines. Running sysvinit doesn't >> show this behaviour. > >Maybe the rpcbind.socket is simply not up yet.
>From what I found, this was not the case. The problem, as I wrote in https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=805167#54 is that the distributed rpcbind.socket only listens on unix-domain sockets, and nis talks udp, and thus won't trigger starting rpcbind proper. /Anders
