>Number: 158543 >Category: bin >Synopsis: bind spams logs with unexpected errors >Confidential: no >Severity: critical >Priority: low >Responsible: freebsd-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: sw-bug >Submitter-Id: current-users >Arrival-Date: Thu Jun 30 22:50:08 UTC 2011 >Closed-Date: >Last-Modified: >Originator: Marcin Wisnicki >Release: 8.2-STABLE >Organization: >Environment: FreeBSD ghost.pnet.one.pl 8.2-STABLE FreeBSD 8.2-STABLE #4: Sun Jun 26 15:10:04 CEST 2011 [email protected]:/home/obj/usr/src/sys/SERWER_DDB i386
>Description: When Internet connection is down (ppp), named fills /var/log/messages with thousands (dozens per second) of following errors: Jul 1 00:17:21 ghost named[4346]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1705: unexpected error: Jul 1 00:17:21 ghost named[4346]: internal_send: 2001:503:c27::2:30#53: Network is down Jul 1 00:17:21 ghost named[4346]: /usr/src/lib/bind/isc/../../../contrib/bind9/lib/isc/unix/socket.c:1705: unexpected error: Jul 1 00:17:21 ghost named[4346]: internal_send: 2001:503:c27::2:30#53: Network is down For all ipv6 addresses of root servers. This makes /var/log/messages grow so fast that it could fill entire /var before newsyslog kicks in and cause all kind of problems requiring manual intervention. Lack of Internet, even for extended period of time, shouldn't have such dramatic consequences. I'm therefore marking this bug as critical. I'm using 6to4 for IPv6, my named.conf is derived from default config (added local zones and forwarding to dns servers of my isp). >How-To-Repeat: 1. Disconnect from Internet 2. Restart named or try to lookup anything 3. Watch the logs or console >Fix: >Release-Note: >Audit-Trail: >Unformatted: _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-bugs To unsubscribe, send any mail to "[email protected]"
