Re: socket.c:4524: unexpected error in BIND 9.4.3 P3
Good day, We've started seeing this bug on a couple servers, but I see no mention of it being fixed, so I don't know what version I should upgrade to. Nor can I find anything that lays out the impact/risk of this. Does anyone know the status of this bug? Thanks! From: bind-users-boun...@lists.isc.org bind-users-boun...@lists.isc.org To: bind-users@lists.isc.org Date: Jul 31 2009 - 7:49pm I have just reported this bug. Ticket number is [ISC-Bugs #20030]. Regards, Vu On Sat, Aug 1, 2009 at 4:06 AM, Paul Elist-bind-us...@dragon.net wrote: Le Vu, lev BTW, what can I do to help debugging this problem? If it doesn't lev involve with programming I will try. Submit this to ISC by emailing bind9-b...@isc.org. Thanks! ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users - This transmission (including any attachments) may contain confidential information, privileged material (including material protected by the solicitor-client or other applicable privileges), or constitute non-public information. Any use of this information by anyone other than the intended recipient is prohibited. If you have received this transmission in error, please immediately reply to the sender and delete this information from your system. Use, dissemination, distribution, or reproduction of this transmission by unintended recipients is not authorized and may be unlawful. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket.c:4524: unexpected error in BIND 9.4.3 P3
At Thu, 30 Jul 2009 22:16:47 +0700, Le Vu lev@gmail.com wrote: I have updated BIND from 9.4.2-P2 to 9.4.3-P3 to mitigate the Dynamic Update DOS attack. I have noted a lot of errors from socket.c (which I have never seen before with v9.4.2) Jul 30 06:25:18 DNS1 named[2]: socket.c:4524: unexpected error: Jul 30 06:25:18 DNS1 named[2]: 22/Invalid argument There are also some of these errors: Jul 30 07:26:17 DNS1 named[2]: sockmgr 0xb7f05008: maximum number of FD events (64) received BIND is compiled with following option on Centos 5.3 (another machine with RHEL 4.4 has these error too): ./configure --disable-openssl-version-check --with-openssl=no What should I do: - go back to 9.4.2-P2 and use iptables to filter DNS update packet - use another version of BIND - ignore the error If you didn't have a performance problem with 9.4.2-P2, please try rebuilding 9.4.3-P3 with --disable-epoll as a workaround. We've heard the problem you saw several times: https://lists.isc.org/pipermail/bind-users/2009-April/076026.html https://lists.isc.org/pipermail/bind-users/2009-May/076265.html but haven't figured out the cause of that. While it doesn't seem to be super rare, it doesn't seem to be so common...I myself have never seen this on my Linux test box, and many other Linux users apparently don't have this problem either (otherwise we'd have got this report much more frequently). If you're willing to help debug this problem (even if the workaround works), that would be great. Thanks, --- JINMEI, Tatuya Internet Systems Consortium, Inc. ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
Re: socket.c:4524: unexpected error in BIND 9.4.3 P3
Le Vu, lev BTW, what can I do to help debugging this problem? If it doesn't lev involve with programming I will try. Submit this to ISC by emailing bind9-b...@isc.org. Thanks! ___ bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
