[prev in list] [next in list] [prev in thread] [next in thread] 

List:       bind-users
Subject:    Re: Bind crashs sometimes
From:       Doug Barton <dougb () dougbarton ! us>
Date:       2009-12-30 21:41:32
Message-ID: 4B3BC90C.2020507 () dougbarton ! us
[Download RAW message or body]

Nadir,

If it's crashing, it's not working normally. :)

The advice Matthew gave is the right solution, but let's do some more
digging. Do the following:

/etc/rc.d/named stop
ps -ax | grep named

You may see a syslog line for the logging socket in the chroot
directory but you should not see a named process running. If you DO
see a named process running, something is desperately wrong and you
should paste the results of your ps command so that we can see what's
happening.

Now do this (after making the rc.conf changes that Matthew suggested:

cd /usr/sbin
mv named named-943
/etc/rc.d/named start

If you get any errors, we need to see them. If not, then do this:

rndc status

You should see something like this:

# rndc status
version: 9.6.1-P2
...
server is up and running

If you do not, let us know.


Doug


Nadir M. Aliyev wrote:
> Yes, your right I installed freebsd version from ports (dns/bind96)
> 
> My named (bind) works normally, and I am sure that no other instances
> running and bind runs with default configuration /etc/named/named.conf
> (/var/named/etc/namedb/named.conf)
> 
> 
> 
> 
> -----Original Message-----
> Message: 2
> Date: Wed, 30 Dec 2009 10:25:49 +0000
> From: Matthew Seaman <m.seaman@infracaninophile.co.uk>
> Subject: Re: Bind crashs sometimes.
> To: Cathy Almond <cathya@isc.org>
> Cc: bind-users@isc.org
> Message-ID: <4B3B2AAD.5060108@infracaninophile.co.uk>
> Content-Type: text/plain; charset="iso-8859-1"; Format="flowed"
> 
> Cathy Almond wrote:
>> If you're running a BIND 9,6,1~ variant (I don't recognise
>> "bind96-9.6.1.2" as an ISC version string), the assert line number does
>> not tally with the source code for bind9/lib/isc/unix/socket.c.
> 
> That's the FreeBSD package name & version for bind-9.6.1-P2 but...
> 
>> That assert location looks more like it would have come from a BIND
>> 9.4.3~ socket.c module.
>>
>> Are you maybe running half old - half new?  Did your libs get updated?
> 
> ... the paths in the output indicate Nadir is running the version of
> named bundled with the base FreeBSD system, which is bind-9.4.3-P2 on
> FreeBSD-7.2.
> 
> Nasdir, if you've installed dns/bind96 from ports, then add the following
> to /etc/rc.conf:
> 
> named_enable="YES"
> named_program="/usr/local/sbin/named"
> named_flags="-c /etc/namedb/named.conf"
> 
> Make sure that there are no instances of named running[*]:
> 
>    # ps -ax -o pid,comm | grep named | cut -d ' ' -f 1 | xargs kill
> 
> and restart named by:
> 
>    # /etc/rc.d/named start
> 
> This will run the ports version of named using named.conf and any zone data
> etc. from /etc/namedb/ (Well, it runs chrooted by default, so it's really
> /var/named/etc/namedb but there's a handy sym-link)
> 
> 	Cheers,
> 
> 	Matthew
> 
> [*] You should really stop the base system named /before/ installing the
> port
> and editing rc.conf, but this will work if you forgot to do that.


-- 

	Improve the effectiveness of your Internet presence with
	a domain name makeover!    http://SupersetSolutions.com/

_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
[prev in list] [next in list] [prev in thread] [next in thread]