Re: bind9 trouble in -PRERELEASE
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', or because chroot precautions are being used. The way to work around this, assuming the box isn't being used by end-users for application development (thus needing their own corefiles for their apps), is to do the following in sysctl.conf: kern.sugid_coredump=1 kern.corefile=/some/absolute/path/%N.%P.core You can adjust these in realtime with sysctl as well. Be sure to specify an absolute path that the 'bind' account has write access to, and is big enough to fit a decent-sized coredump. If you have a large /var filesystem, /var/tmp is an OK place. Thank you for the tip. I have kern.corefile set to /tmp from the beginning but really no space left on that at that time. I'll reply to the list if I get the backtrace. - With best regards, |The Power to Serve Nguyen Tam Chinh| http://www.FreeBSD.org Loc: sp.cs.msu.su | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bind9 trouble in -PRERELEASE
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. The way to work around this, assuming the box isn't being used by end-users for application development (thus needing their own corefiles for their apps), is to do the following in sysctl.conf: kern.sugid_coredump=1 kern.corefile=/some/absolute/path/%N.%P.core You can adjust these in realtime with sysctl as well. Be sure to specify an absolute path that the 'bind' account has write access to, and is big enough to fit a decent-sized coredump. If you have a large /var filesystem, /var/tmp is an OK place. -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networkinghttp://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, USA | | Making life hard for others since 1977. PGP: 4BD6C0CB | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bind9 trouble in -PRERELEASE
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: INSIST(((unsigned char *)mem )[size] == 0xbe) failed Oct 31 11:34:49 cat9 named[500]: exiting (due to assertion failure) Oct 31 11:34:49 cat9 kernel: pid 500 (named), uid 53: exited on signal 6 The kernel and world (included bind9) were updated to 6.2-PRERELEASE of 30.10. Please advice if you have any further information. Thank you. Post a stack bactrace. I don't think that I can do a stack backtrace when named left no core after that. - With best regards, |The Power to Serve Nguyen Tam Chinh| http://www.FreeBSD.org Loc: sp.cs.msu.su | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: bind9 trouble in -PRERELEASE
> 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] == 0xbe) failed > Oct 31 11:34:49 cat9 named[500]: exiting (due to assertion failure) > Oct 31 11:34:49 cat9 kernel: pid 500 (named), uid 53: exited on signal 6 > > The kernel and world (included bind9) were updated to 6.2-PRERELEASE of > 30.10. > Please advice if you have any further information. > Thank you. Post a stack bactrace. > > - > With best regards, |The Power to Serve > Nguyen Tam Chinh| http://www.FreeBSD.org > Loc: sp.cs.msu.su | > ___ > freebsd-stable@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-stable > To unsubscribe, send any mail to "[EMAIL PROTECTED]" -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: [EMAIL PROTECTED] ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
bind9 trouble in -PRERELEASE
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] == 0xbe) failed Oct 31 11:34:49 cat9 named[500]: exiting (due to assertion failure) Oct 31 11:34:49 cat9 kernel: pid 500 (named), uid 53: exited on signal 6 The kernel and world (included bind9) were updated to 6.2-PRERELEASE of 30.10. Please advice if you have any further information. Thank you. - With best regards, |The Power to Serve Nguyen Tam Chinh| http://www.FreeBSD.org Loc: sp.cs.msu.su | ___ freebsd-stable@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-stable To unsubscribe, send any mail to "[EMAIL PROTECTED]"
