|
|
| named not starting during boot |

|
2007-02-26 19:24:25 |
Hi there,
named is not starting when I reboot a FreeBSD 6.2 server and
I cant
figure out why.
there are no error mesasges in /var/log/messages during the
boot process.
even when I manually start there are no error messages.
# grep named /etc/rc.conf
named_enable="YES"
# pkg_info | grep bind
bind9-9.3.4 Completely new version of the BIND DNS
suite with
updated D
# grep BIND messages
Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3
Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3
Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
# /etc/rc.d/named stop
# /etc/rc.d/named start
# grep BIND messages
Feb 26 11:50:53 access2 named[1704]: starting BIND 9.3.3
Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3
Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
Feb 26 17:23:46 access2 named[1005]: starting BIND 9.3.4 -c
/etc/namedb/named.conf
any clues please?
Cheers,
Noah
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |
  United States |
2007-02-26 20:18:44 |
Noah Garrett Wallach wrote:
> Hi there,
>
> named is not starting when I reboot a FreeBSD 6.2
server and I cant
> figure out why.
> there are no error mesasges in /var/log/messages during
the boot process.
>
> even when I manually start there are no error
messages.
Have you tried with "-fg" ? There are a lot of
really quick restarts in
that log snippet around "5:20" ....
<snip>
> any clues please?
Not really, most of the time I think I'm completely clueless
Kevin Kinsey
--
I've been there.
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |

|
2007-02-26 20:21:09 |
Kevin,
those were manual restarts.
cheers,
Noah
Kevin Kinsey wrote:
> Noah Garrett Wallach wrote:
>> Hi there,
>>
>> named is not starting when I reboot a FreeBSD 6.2
server and I cant
>> figure out why.
>> there are no error mesasges in /var/log/messages
during the boot
>> process.
>>
>> even when I manually start there are no error
messages.
>
> Have you tried with "-fg" ? There are a lot
of really quick restarts
> in that log snippet around "5:20" ....
>
> <snip>
>
>
>> any clues please?
>
> Not really, most of the time I think I'm completely
clueless
>
> Kevin Kinsey
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |
  Poland |
2007-02-27 07:52:27 |
>
> named is not starting when I reboot a FreeBSD 6.2
server and I cant figure
> out why.
> there are no error mesasges in /var/log/messages during
the boot process.
>
> even when I manually start there are no error
messages.
>
> # grep named /etc/rc.conf
> named_enable="YES"
> # pkg_info | grep bind
> bind9-9.3.4 Completely new version of the BIND
DNS suite with updated
why you are installing bind from ports - there is bind9 in
base system.
and it's controlled with named_enable.
have you configured right version in right (/etc/namedb)
directory?
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |
  United States |
2007-02-27 08:43:23 |
In the newer versions of bind you need to add to
/etc/rc.conf:
named_uid="username"
you want to run named as.
-Derek
At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote:
>Hi there,
>
>named is not starting when I reboot a FreeBSD 6.2 server
and I cant figure
>out why.
>there are no error mesasges in /var/log/messages during
the boot process.
>
>even when I manually start there are no error messages.
>
># grep named /etc/rc.conf
>named_enable="YES"
># pkg_info | grep bind
>bind9-9.3.4 Completely new version of the BIND
DNS suite with
>updated D
>
>
>
># grep BIND messages
>Feb 26 11:50:53 access2 named[1704]: starting BIND
9.3.3
>Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3
>Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
># /etc/rc.d/named stop
># /etc/rc.d/named start
># grep BIND messages
>Feb 26 11:50:53 access2 named[1704]: starting BIND
9.3.3
>Feb 26 14:07:19 access2 named[990]: starting BIND 9.3.3
>Feb 26 17:19:59 access2 named[966]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>Feb 26 17:20:07 access2 named[974]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>Feb 26 17:20:19 access2 named[981]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>Feb 26 17:23:46 access2 named[1005]: starting BIND 9.3.4
-c
>/etc/namedb/named.conf
>
>any clues please?
>
>Cheers,
>
>Noah
>_______________________________________________
>freebsd-questions freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>MailScanner thanks transtec Computers for their
support.
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |

|
2007-02-27 09:23:50 |
Wojciech Puchar wrote:
>> named is not starting when I reboot a FreeBSD 6.2
server and I cant
>>
> figure
>
>> out why.
>> there are no error mesasges in /var/log/messages
during the boot
>>
> process.
>
>> even when I manually start there are no error
messages.
>>
>> # grep named /etc/rc.conf
>> named_enable="YES"
>> # pkg_info | grep bind
>> bind9-9.3.4 Completely new version of the
BIND DNS suite with
>>
> updated
>
>
> why you are installing bind from ports - there is bind9
in base system.
> and it's controlled with named_enable.
>
because there are security exploits and keeping upto date
version is
important to me.
http://www.isc.org/index.pl?/sw/bind/bind-security.php
>
> have you configured right version in right
(/etc/namedb) directory?
>
I will check that.
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |
  United States |
2007-02-27 09:28:51 |
At 09:23 AM 02/27/2007, Noah Garrett Wallach wrote:
>Wojciech Puchar wrote:
>>>named is not starting when I reboot a FreeBSD
6.2 server and I cant
>>>
>>figure
>>>out why.
>>>there are no error mesasges in /var/log/messages
during the boot
>>>
>>process.
>>
>>>even when I manually start there are no error
messages.
>>>
>>># grep named /etc/rc.conf
>>>named_enable="YES"
>>># pkg_info | grep bind
>>>bind9-9.3.4 Completely new version of
the BIND DNS suite with
>>>
>>updated
>>
>>
>>why you are installing bind from ports - there is
bind9 in base
>>system. and it's controlled with named_enable.
>>
>
>because there are security exploits and keeping upto
date version is
>important to me.
>http://www.isc.org/index.pl?/sw/bind/bind-security.php
I actually rolled my own version of Bind (9.4.0) and have it
working
perfectly and starting under rc.conf
(I had to edit /etc/rc.d/named though)
-JD
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |

|
2007-02-27 11:21:17 |
Hi there,
I dont have a user name named. I have a user named bind.
so bind is
what I am going with.
named_enable="YES"
named_uid="bind"
named_program="/usr/local/sbin/named"
named_flags="-c /etc/namedb/named.conf"
named_chrootdir="/var/named"
cheers,
Noah
Derek Ragona wrote:
> In the newer versions of bind you need to add to
/etc/rc.conf:
> named_uid="username"
> you want to run named as.
>
> -Derek
>
> At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote:
>> Hi there,
>>
>> named is not starting when I reboot a FreeBSD 6.2
server and I cant
>> figure out why.
>> there are no error mesasges in /var/log/messages
during the boot
>> process.
>>
>> even when I manually start there are no error
messages.
>>
>> # grep named /etc/rc.conf
>> named_enable="YES"
>> # pkg_info | grep bind
>> bind9-9.3.4 Completely new version of the
BIND DNS suite with
>> updated D
>>
>>
>>
>> # grep BIND messages
>> Feb 26 11:50:53 access2 named[1704]: starting BIND
9.3.3
>> Feb 26 14:07:19 access2 named[990]: starting BIND
9.3.3
>> Feb 26 17:19:59 access2 named[966]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> Feb 26 17:20:07 access2 named[974]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> Feb 26 17:20:19 access2 named[981]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> # /etc/rc.d/named stop
>> # /etc/rc.d/named start
>> # grep BIND messages
>> Feb 26 11:50:53 access2 named[1704]: starting BIND
9.3.3
>> Feb 26 14:07:19 access2 named[990]: starting BIND
9.3.3
>> Feb 26 17:19:59 access2 named[966]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> Feb 26 17:20:07 access2 named[974]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> Feb 26 17:20:19 access2 named[981]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>> Feb 26 17:23:46 access2 named[1005]: starting BIND
9.3.4 -c
>> /etc/namedb/named.conf
>>
>> any clues please?
>>
>> Cheers,
>>
>> Noah
>> _______________________________________________
>> freebsd-questions freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
>> To unsubscribe, send any mail to
>> "freebsd-questions-unsubscribe freebsd.org"
>>
>> --
>> This message has been scanned for viruses and
>> dangerous content by MailScanner, and is
>> believed to be clean.
>> MailScanner thanks transtec Computers for their
support.
>>
>
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|
| Re: named not starting during boot |
  United States |
2007-02-27 11:39:19 |
I was using "username" as an example. You can use
bind, root, or any valid
user. That user should own the directory you plan to use
for the chroot,
or the namedb starting point.
Most likely you have a chroot problem, you need to be sure
you have that
file tree setup correctly.
-Derek
At 11:21 AM 2/27/2007, Noah Garrett Wallach wrote:
>Hi there,
>
>I dont have a user name named. I have a user named
bind. so bind is what
>I am going with.
>
>named_enable="YES"
>named_uid="bind"
>named_program="/usr/local/sbin/named"
>named_flags="-c /etc/namedb/named.conf"
>named_chrootdir="/var/named"
>
>
>cheers,
>
>Noah
>
>
>Derek Ragona wrote:
>>In the newer versions of bind you need to add to
/etc/rc.conf:
>>named_uid="username"
>>you want to run named as.
>>
>> -Derek
>>
>>At 07:24 PM 2/26/2007, Noah Garrett Wallach wrote:
>>>Hi there,
>>>
>>>named is not starting when I reboot a FreeBSD
6.2 server and I cant
>>>figure out why.
>>>there are no error mesasges in /var/log/messages
during the boot process.
>>>
>>>even when I manually start there are no error
messages.
>>>
>>># grep named /etc/rc.conf
>>>named_enable="YES"
>>># pkg_info | grep bind
>>>bind9-9.3.4 Completely new version of
the BIND DNS suite with
>>>updated D
>>>
>>>
>>>
>>># grep BIND messages
>>>Feb 26 11:50:53 access2 named[1704]: starting
BIND 9.3.3
>>>Feb 26 14:07:19 access2 named[990]: starting
BIND 9.3.3
>>>Feb 26 17:19:59 access2 named[966]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>Feb 26 17:20:07 access2 named[974]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>Feb 26 17:20:19 access2 named[981]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>># /etc/rc.d/named stop
>>># /etc/rc.d/named start
>>># grep BIND messages
>>>Feb 26 11:50:53 access2 named[1704]: starting
BIND 9.3.3
>>>Feb 26 14:07:19 access2 named[990]: starting
BIND 9.3.3
>>>Feb 26 17:19:59 access2 named[966]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>Feb 26 17:20:07 access2 named[974]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>Feb 26 17:20:19 access2 named[981]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>Feb 26 17:23:46 access2 named[1005]: starting
BIND 9.3.4 -c
>>>/etc/namedb/named.conf
>>>
>>>any clues please?
>>>
>>>Cheers,
>>>
>>>Noah
>>>_______________________________________________
>>>freebsd-questions freebsd.org mailing list
>>>http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
>>>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
>>>
>>>--
>>>This message has been scanned for viruses and
>>>dangerous content by MailScanner, and is
>>>believed to be clean.
>>>MailScanner thanks transtec Computers for their
support.
>_______________________________________________
>freebsd-questions freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
>To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>MailScanner thanks transtec Computers for their
support.
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
_______________________________________________
freebsd-questions freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-que
stions
To unsubscribe, send any mail to
"freebsd-questions-unsubscribe freebsd.org"
|
|