Server sychronization after power fail and NIS

jerry.feldman at algorithmics.com jerry.feldman at algorithmics.com
Thu Sep 4 13:45:49 UTC 2008


We have a number of servers in our office (RHEL 4 U6) and we don't have
a UPS. The problem is that when there is a power failure, some of the
servers fail to acquire the NIS bind, and ypbind exits. I can certainly
write a cron script to test if ypbind is running, and if not restart it,
but I would like to be able to have the ypbind daemon wait or retry. The
problem is one of timing:
Sep  4 06:29:00 asystem ypbind: Setting NIS domain name ypXXX:
succeeded
Sep  4 06:29:01 asystem ypbind: ypbind startup succeeded
Sep  4 06:29:24 asystem rpc.statd[20919]: Can't notify xx.xx.xx.xx,
giving up.
Sep  4 06:29:58 asystem ypbind: ypbind shutdown succeeded
Sep  4 06:29:58 asystem ypbind: attempting to contact yp server failed



--
Jerry Feldman <Jerry.Feldman at algorithmics.com>
Algorithmics (US), Inc
Suite 2-400
275 Grove St.
Newton, MA 02466
617-663-5220
617-663-5391 (fax) 



 
--------------------------------------------------------------------------
This email and any files transmitted with it are confidential and proprietary to Algorithmics Incorporated and its affiliates ("Algorithmics"). If received in error, use is prohibited. Please destroy, and notify sender. Sender does not waive confidentiality or privilege. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. Algorithmics does not accept liability for any errors or omissions. Any commitment intended to bind Algorithmics must be reduced to writing and signed by an authorized signatory.
--------------------------------------------------------------------------





More information about the redhat-list mailing list