[67563] in North American Network Operators' Group
Interesting BIND error
daemon@ATHENA.MIT.EDU (Brian Wallingford)
Thu Feb 12 16:58:45 2004
Date: Thu, 12 Feb 2004 16:52:26 -0500 (EST)
From: Brian Wallingford <brian@meganet.net>
To: nanog@merit.edu
Errors-To: owner-nanog-outgoing@merit.edu
We've been seeing the following on all of our (9.2.1) authoritative
nameservers since approximately 10am today. Googling has turned up
nothing; I'm currently trying to glean some useful netflow data. Just
wondering if this is local, or if others have suddenly seen the same.
Seems harmless enough, but the logging is eating a disproportionate amount
of cpu.
Feb 12 16:25:07 ns1 named[3150]: internal_send: 244.254.254.254#53:
Invalid argument
Feb 12 16:25:07 ns1 named[3150]: socket.c:1100: unexpected error:
Feb 12 16:25:07 ns1 named[3150]: internal_send: 244.254.254.254#53:
Invalid argument
Feb 12 16:25:07 ns1 named[3150]: socket.c:1100: unexpected error:
Feb 12 16:25:07 ns1 named[3150]: internal_send: 244.254.254.254#53:
Invalid argument
Feb 12 16:25:07 ns1 named[3150]: socket.c:1100: unexpected error:
Feb 12 16:25:07 ns1 named[3150]: internal_send: 244.254.254.254#53:
Invalid argument
From socket.c:
#undef ALWAYS_HARD
/*
* The other error types depend on whether or not the
* socket is UDP or TCP. If it is UDP, some errors
* that we expect to be fatal under TCP are merely
* annoying, and are really soft errors.
*
* However, these soft errors are still returned as
* a status.
*/
isc_sockaddr_format(&dev->address, addrbuf,
sizeof(addrbuf));
isc__strerror(send_errno, strbuf, sizeof(strbuf));
UNEXPECTED_ERROR(__FILE__, __LINE__, "internal_send: %s:
%s",
addrbuf, strbuf);
dev->result = isc__errno2result(send_errno);
return (DOIO_HARD);
