Problem occurs on i386 and alpha when trying to set up a slave server on executing the command ypinit -s hostname.hostdomain always get the error Can't enumerate maps from $MASTER. Please check that it is running. The script ypinit contains the lines # maps=`ypwhich -m | egrep $MASTER$| awk '{ printf("%s ",$1) }' -` maps=`$YPBINDIR/yphelper --maps $MASTER` but yphelper is broken The commneted out line is also broken and as an extra $ after master If this is changed to maps=`ypwhich -m | egrep $MASTER | awk '{ printf("%s ",$1) }' -` # maps=`$YPBINDIR/yphelper --maps $MASTER` and /usr/sbin/rpc.ypxfrd is manually started on the host machine then a slave server can be initialised
ypinit is working fine for me without the above change. Can you tell me more about the ypserver and what ypserv version it has running? Florian La Roche
I ran into the same problem. By using strace, I discovered yphelper was polling the first system listed in /etc/hosts, regardless of the NIS master passed to it on the command line. After I moved my NIS master to the first line of /etc/hosts (on the client machine), yphelper ran just fine. hth, -Doug
on alpha and i386 machines rpm -q ypserv ypserv-1.3.9-3 /usr/sbin/ypserv --version ypserv - NYS YP Server version 1.3.9 (with securenets)
I had the same yphelper failure, but was able to run "/usr/lib/yp/ypinit -s master_host" with no problems after flipping the comments around as detailed above. I was using the same ypserv version as listed above. Tim
I have the same problem between two RedHat 6.2 servers. I think the problem is mainly at the master server. When I pointed my slave server to an SCO OpenServer host (with NIS enabled), I indeed was able to configure the slave. But the same slave pointing to a RedHat 6.2 host (configured as a NIS master) would only generate the errors indicated in this report (namely, Can't enumerate maps from $MASTER. Please check that it is running.) It seems that this error has been reported/discussed on the Web for some time ( I did some browsing looking for a solution). When is it going to get fixed ?
FYI bug 26362 is also dealing with this issue (same state on 6.2 servers ypwhich workaround functions yphelper --maps doesn't)
*** This bug has been marked as a duplicate of 26362 ***
If anyone can reproduce this right now, please contact me.