Hello -stable: I just updated to -stable as of 2004/04/14 and named is not starting at bootup.>From /var/log/messages:Apr 15 07:38:14 <console.info> localhost /kernel: can't open '/etc/namedb/named.conf' But, if I become root & type "ndc start", named starts & seems to run as before. Any idea(s) what's happening here and/or how to fix? Thanks, -kc
On Thu, 2004-04-15 at 08:17, Kenneth W Cochran wrote:> Hello -stable: > > I just updated to -stable as of 2004/04/14 and named is not > starting at bootup. > > >From /var/log/messages: > > Apr 15 07:38:14 <console.info> localhost /kernel: can't open '/etc/namedb/named.conf' > > But, if I become root & type "ndc start", named starts & > seems to run as before. > > Any idea(s) what's happening here and/or how to fix? >Your /etc/rc.conf should contain the following 2 lines: named_enable="YES" # Run named, the DNS server (or NO). named_flags="-t /etc/namedb /etc/named.conf" This assumes that the location of named.conf is /etc/named/etc/named.conf> Thanks, > > -kc > _______________________________________________ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "freebsd-stable-unsubscribe@freebsd.org"
>Subject: Re: 4.10-BETA named (not) starting >From: Randy Rowe <rerowe@rerowe.com> >To: Kenneth W Cochran <kwc@theworld.com> >Cc: freebsd-stable@freebsd.org >Date: 15 Apr 2004 08:36:00 -0500 > >On Thu, 2004-04-15 at 08:17, Kenneth W Cochran wrote: >> Hello -stable: >> >> I just updated to -stable as of 2004/04/14 and named is not >> starting at bootup. >> >> >From /var/log/messages: >> >> Apr 15 07:38:14 <console.info> localhost /kernel: can't open '/etc/namedb/named.conf' >> >> But, if I become root & type "ndc start", named starts & >> seems to run as before. >> >> Any idea(s) what's happening here and/or how to fix? > >Your /etc/rc.conf should contain the following 2 lines: > >named_enable="YES" # Run named, the DNS server (or NO).Yes...>named_flags="-t /etc/namedb /etc/named.conf"This is what I have: named_flags="-u bind -g bind -t /etc/namedb" This has never been a problem before; shouldn't the config file default to /etc/namedb/named.conf? The message I'm getting is coming from the *kernel*. Wierd (so far...).>This assumes that the location of named.conf is >/etc/named/etc/named.confThat would be /etc/named/named.conf (spelling :) -kc
>Date: Thu, 15 Apr 2004 10:09:38 -0400 >From: Ken Smith <kensmith@cse.Buffalo.EDU> >To: Kenneth W Cochran <kwc@theworld.com> >Subject: Re: 4.10-BETA named (not) starting > >On Thu, Apr 15, 2004 at 09:17:09AM -0400, Kenneth W Cochran wrote: >> I just updated to -stable as of 2004/04/14 and named is not >> starting at bootup. >> >> >From /var/log/messages: >> >> Apr 15 07:38:14 <console.info> localhost /kernel: can't open '/etc/namedb/named.conf' >> >> But, if I become root & type "ndc start", named starts & >> seems to run as before. >> >> Any idea(s) what's happening here and/or how to fix? > >Just checking. Did you run 'mergemaster' as part of the upgrade?Yes; named config appeared to be unaffected. It would appear the the "can't open" message is a permission problem of some kind, but from the *kernel*? And that file is root:wheel 644. As mentioned, ndc saw it & started named just fine. Strange... -kc