[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Squeeze: sometimes, bind times out (backgrounded) at boot time



Joao Roscoe wrote:
> I have a bunch of squeeze boxes running with nis and autofs. All are working
> well, no performance issues. However, at boot time, sporadically, bind times
> out, and the machine goes up without nis.

Your words say "bind times out" and "nis" fails but what does bind
have to do with nis?  When NIS/YP was written it was written for
systems that did not use BIND nor even have it installed.  In a pure
NIS/YP system they used NIS/YP for host name resolution.  NIS by
itself does not depend upon BIND.  There isn't an intrinsic dependency
of one upon the other unless you have created one in your configuration.

> Since home folders are NFS via autofs, the machine becames useless,
> and a reboot is required (I know that restarting nis and autofs,
> will solve it, but that requires root access).

This reads to me that you have an NIS problem not a BIND problem.
Probably your BIND configuration is okay.  Instead look for your
problem in your NIS configuration.

> Is there any way to increase the timeout of bind at boot time?

First find the root cause of the problem.  It seems unlikely that it
is BIND.

What do you have in your /etc/yp.conf file?  Are you specifying to
find the nis server by broadcast, by IP address, or by server name?

Note that the default Debian yp.conf file contains this following warning:

  # IMPORTANT:    For the "ypserver", use IP addresses, or make sure that
  #               the host is in /etc/hosts. This file is only interpreted
  #               once, and if DNS isn't reachable yet the ypserver cannot
  #               be resolved and ypbind won't ever bind to the server.

It seems likely to me that you have placed host names in that file but
failed to heed the warning and place the host names in your
/etc/hosts.  But keeping host names in /etc/hosts isn't wonderful.
Neither is using IP addresses.  I recommend avoiding names there and
using the broadcast protocol to find the nis servers.

  domain example.com broadcast

That would allow a client to associate with any of the nis master and
slaves as they become available.

Bob

Attachment: signature.asc
Description: Digital signature


Reply to: