On Tue, Feb 17, 2015 at 08:05:56PM +0530, bhargav p wrote:
> >From the code browsing I can make this assertion failure happend in the
> destroy function(), why the named daemon wants to exit itself, is something
> unexpected happend?
I would guess it was a normal shutdown; if it had been an unexpe
You are running a really old version of BIND - 9.7.x, deprecated in ~2012.
It has numerous remotely exploitable, high severity security issues,
see:
https://kb.isc.org/article/AA-00913/0/BIND-9-Security-Vulnerability-Matrix.html
There seem to be a number of bugs that could have caused that crash,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
On 2/17/15 9:35 AM, bhargav p wrote:
> We observed the named crash with an assertion failure.
> Version I am using is : bind-9.7.1
While I can't directly address this crash, I'd strongly recommend that
you at least move to a supported version of
Hi,
We observed the named crash with an assertion failure.
This happend only once, and backtrace says it is corrupted stack. Named
daemon starteda again by itself after this. And no crash was seen after
this.
Version I am using is : bind-9.7.1
Backtrace:
#0 0xb729789f in raise () from /lib/l
On 2/17/2015 3:47 AM, Carsten Strotmann (sys4) wrote:
Hello John,
John Allen wrote:
Does anybody now if there are any developments in this standard and its
implementation. Particular reference to email.
people from Verisign have implemented an library+API, Thunderbird
integration and they had
5 matches
Mail list logo
