Your message dated Sun, 28 Oct 2012 22:09:41 +0100
with message-id <[email protected]>
and subject line Closing very old bind9 bugs
has caused the Debian Bug report #223487,
regarding bind9: Dies silently
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
223487: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=223487
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: bind9
Version: 9.2.3-2
Severity: important
Bind dies mysteriously, killed by some signal.
I run bind with several primary and secondary zones. No DNSSEC, no
DNS dynamic updates. Sometimes, named just dies without any
message. From the BSD process accounting I can see that is was killed
(X flag in lastcomm), but that's it.
BTW, 9.2.3rc3 also had the same problem.
Also, named does not do any logging, which rules out "named dying when
log file reaches 2GB" reason.
I am running a debug version now and will try to catch the crash in
the debugger.
Phil.
--- End Message ---
--- Begin Message ---
Since this bug references a BIND 9 version that is even older than
oldstable (lenny) I'm closing it.
Please reopen if reproducible in newer versions.
--- End Message ---
