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 name
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: signatu
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
No, I don't think that this isn't issued with libs. Because all libs up to
date.
This problem happened 1-2 time in week.
I created downtime monitor script for named service. But this is not good
idea.
And which libs depencises uses bind 9.6?
--
Nadir Aliyev
ULTEL
ISP
-Origin
Hello, all.
I'm administrating 4 DNS servers running CentOS release 5.4 and Red Hat Enterprise Linux Server release 5.2. with BIND
version 9.6.1-P1. On 3 of them BIND crashed 7 times in last 10 days. There's nothing in log files, but we have core dump
file. I found this in the core dump:
#0
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 assert location looks more like it would have come from a BIND
9.4.3~ socket.c module.
Are you ma
6 matches
Mail list logo