Hello,
I have a server with busy local DNS (bind 9.3.2-P1, listen on localhost).
The bind9 got strange problem and gone away for the last some days:
Oct 31 11:34:49 cat9 named[500]:
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/mem.c:628:
INSIST(((unsigned char *)mem
)[size] ==
Hello,
I have a server with busy local DNS (bind 9.3.2-P1, listen on localhost).
The bind9 got strange problem and gone away for the last some days:
Oct 31 11:34:49 cat9 named[500]:
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/mem.c:628:
INSIST(((unsigned char *)mem
)[size]
On Thu, 2 Nov 2006, Mark Andrews wrote:
Hello,
I have a server with busy local DNS (bind 9.3.2-P1, listen on localhost).
The bind9 got strange problem and gone away for the last some days:
Oct 31 11:34:49 cat9 named[500]:
/usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/mem.c:628:
On Wed, Nov 01, 2006 at 11:40:39PM +0300, Nguyen Tam Chinh wrote:
I don't think that I can do a stack backtrace when named left no core
after that.
No core is being left either due to limits (limit/ulimit) being
imposed on the user or group 'bind', or because chroot precautions
are being used.
On Wed, 1 Nov 2006, Jeremy Chadwick wrote:
On Wed, Nov 01, 2006 at 11:40:39PM +0300, Nguyen Tam Chinh wrote:
I don't think that I can do a stack backtrace when named left no core
after that.
No core is being left either due to limits (limit/ulimit) being
imposed on the user or group 'bind',
