NIS (ypbind) will not stay up on server

[Joe_Higginbotha]

I have the firewall and security turned off all the way back from the install on the client and the server. If I go to the Server Configuration GUI and chedck the "yp" services I see that yppasswdd, ypserv, ypxfrd are all running but ypbind is stopped. I have these services set to be started in runlevels 3, 4, and 5.

I use the GUI to start ypbind on the NIS server. It replys ypbind has started but the configuration file shows ypbind is stopped.

The system log viewer shows the following:

ypbind: NIS server for domain xxx.yyy.com is not responding.

Any suggestions as to what I need to do?

[fallingrock]

Originally Posted by Joe_Higginbotha

ypbind: NIS server for domain xxx.yyy.com is not responding.

I found that the init script for ypbind has a bit of a problem ... it's assuming there will be a 15 second timeout when none occurrs.

I fixed the problem by adding a sleep 15s after the first check to see if NIS was active ...

     # the following fixes problems with the init scripts continuing
        # even when we are really not bound yet to a server, and then things
        # that need NIS fail.
        timeout=$NISTIMEOUT
        while [ $timeout -gt 0 ]; do
            /usr/sbin/rpcinfo -p | LC_ALL=C fgrep -q ypbind && \
                        /usr/bin/ypwhich > /dev/null 2>&1
            RETVAL=$?
            if [ $RETVAL -eq 0 ]; then
                break;
            fi
            echo -n "..."
                sleep 15s
            # ypwhich has a hardcode 15sec timeout
            # so subtract that from NISTIMEOUT to
            # to see of we should continue to wait
            timeout=`expr $timeout - 15`
        done

david