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.sea...@infracaninophile.co.uk>
Subject: Re: Bind crashs sometimes.
To: Cathy Almond <cat...@isc.org>
Cc: bind-us...@isc.org
Message-ID: <4b3b2aad.5060...@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.
> Nadir Aliyev wrote:
>>
>>
>> Hello All,
>>
>> I have serious problem, after upgrade to new version.
>>
>>
>> Sometimes named crashs.
>>
>> Here is log.
>>
>> Dec 30 00:26:02 ns1
>> named[44042]:
>> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:2361:
>> INSIST(!sock->pending_accept) failed
>> Dec 30 00:26:02 ns1 kernel: Dec 30
>> 00:26:02 ns1 named[44042]:
>> /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:2361:
>> INSIST(!sock->pending_accept) failed
>> Dec 30 00:26:02 ns1 named[44042]:
>> exiting (due to assertion failure)
>> Dec 30 00:26:02 ns1 kernel: Dec 30
>> 00:26:02 ns1 named[44042]: exiting (due to assertion failure)
>> Dec 30
>> 00:26:18 ns1 kernel: pid 44042 (named), uid 0: exited on signal 6 (core
>> dumped)
>>
>> I did not find any solution for this problem.
>>
>> Bind version:
>> bind96-9.6.1.2
>>
>> OS: FreeBSD 7.2
>>
>> --------------
>>
>> Nadir Aliyev
>>
>> ULTEL
>> ISP
--
Dr Matthew J Seaman MA, D.Phil. 7 Priory Courtyard
Flat 3
PGP: http://www.infracaninophile.co.uk/pgpkey Ramsgate
Kent, CT11 9PW
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 259 bytes
Desc: OpenPGP digital signature
URL:
<https://lists.isc.org/pipermail/bind-users/attachments/20091230/23a43196/at
tachment-0001.bin>
------------------------------
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
End of bind-users Digest, Vol 388, Issue 2
******************************************
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
