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 -----Original Message----- Date: Wed, 30 Dec 2009 09:02:20 +0000 From: Cathy Almond <cat...@isc.org> Subject: Re: Bind crashs sometimes. To: bind-users@lists.isc.org Message-ID: <4b3b171c.2050...@isc.org> Content-Type: text/plain; charset=ISO-8859-1 Message: 6 Date: Wed, 30 Dec 2009 09:02:20 +0000 From: Cathy Almond <cat...@isc.org> Subject: Re: Bind crashs sometimes. To: bind-users@lists.isc.org Message-ID: <4b3b171c.2050...@isc.org> Content-Type: text/plain; charset=ISO-8859-1 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 maybe running half old - half new? Did your libs get updated? Nadir Aliyev wrote: > > > Hello All, > > I have serious problem, after upgrade to new version. > > > Sometimes named crashs. > > Here is log. > > Dec 30 00:26:02 ns1 > named[44042]: > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:2361: > INSIST(!sock->pending_accept) failed > Dec 30 00:26:02 ns1 kernel: Dec 30 > 00:26:02 ns1 named[44042]: > /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:2361: > INSIST(!sock->pending_accept) failed > Dec 30 00:26:02 ns1 named[44042]: > exiting (due to assertion failure) > Dec 30 00:26:02 ns1 kernel: Dec 30 > 00:26:02 ns1 named[44042]: exiting (due to assertion failure) > Dec 30 > 00:26:18 ns1 kernel: pid 44042 (named), uid 0: exited on signal 6 (core > dumped) > > I did not find any solution for this problem. > > Bind version: > bind96-9.6.1.2 > > OS: FreeBSD 7.2 > > -------------- > > Nadir Aliyev > > ULTEL > ISP > > > ------------------------------------------------------------------------ > > _______________________________________________ > bind-users mailing list > bind-users@lists.isc.org > https://lists.isc.org/mailman/listinfo/bind-users ------------------------------ Message: 7 Date: Wed, 30 Dec 2009 10:23:17 +0100 From: Dario Miculinic <dario.miculi...@t-com.hr> Subject: BIND 9.6.1-P1 crashing To: bind-users@lists.isc.org Message-ID: <4b3b1c05.7010...@t-com.hr> Content-Type: text/plain; charset=ISO-8859-1; format=flowed 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 0x080db986 in ttl_sooner (v1=0x0, v2=0x3385b628) at rbtdb.c:752 752 ttl_sooner(void *v1, void *v2) { (gdb) where #0 0x080db986 in ttl_sooner (v1=0x0, v2=0x3385b628) at rbtdb.c:752 #1 0x0819e708 in isc_heap_delete (heap=0xb0f751a8, index=2) at heap.c:218 #2 0x080e039f in free_rdataset (rbtdb=0xb0f70008, mctx=0x86c9e98, rdataset=0x3385b628) at rbtdb.c:1273 #3 0x080e04c3 in clean_stale_headers (rbtdb=0xb0f70008, mctx=0x86c9e98, top=0x7fa67700) at rbtdb.c:1331 #4 0x080e10c4 in decrement_reference (rbtdb=0xb0f70008, node=0x36c159f0, least_serial=0, nlock=isc_rwlocktype_read, tlock=isc_rwlocktype_none, pruning=isc_boolean_false) at rbtdb.c:1348 #5 0x080ea711 in detachnode (db=0xb0f70008, targetp=0xb4d1f404) at rbtdb.c:4877 #6 0x080ea9b1 in rdataset_disassociate (rdataset=0xb03f22d8) at rbtdb.c:7173 #7 0x0812e55a in dns_rdataset_disassociate (rdataset=0xb03f22d8) at rdataset.c:101 #8 0x080c7dfa in msgresetnames (msg=0xb03e1b60, first_section=<value optimized out>) at message.c:463 #9 0x080cb3c5 in msgreset (msg=0x0, everything=isc_boolean_false) at message.c:545 #10 0x080cbd05 in dns_message_reset (msg=0xb03e1b60, intent=1) at message.c:800 #11 0x0804dbfc in exit_check (client=0xb03fca70) at client.c:639 #12 0x0806007c in query_find (client=0xb03fca70, event=0x0, qtype=1) at query.c:4914 #13 0x08063490 in query_resume (task=0xad4f6bd0, event=0x98cbdb8) at query.c:3171 #14 0x081b9221 in run (uap=0xb7f2a008) at task.c:862 #15 0x0059645b in pthread_create@@GLIBC_2.1 () from /lib/libpthread.so.0 #16 0x004ee24e in profil_counter () from /lib/libc.so.6 I couldn't get core dump file from Red Hat server, but in every core dump file on CentOS ttl_sooner function is mentioned. Does anyone know what this could be and how to fix it? Thanks in advance. ------------------------------ _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users End of bind-users Digest, Vol 388, Issue 1 ****************************************** _______________________________________________ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
