Hello again-
Our issue is now appearing on multiple physical nameservers in our
domain running 9.5.1-P3.
The second server that is noticing this is Red Hat Enterprise Linux
Server release 5.3 (Tikanga) 64 bit, complied 9.5.1-P3 from src with
default configure options. So the problem seems to persist across
vastly different linux environments [the first server we saw this on was
Redhat AS 3].
I am not a heavy duty programmer but my understand based on src is that
this may be related to the inability to send a UDP response and is
perhaps a resource exhaustion issue. I'm not sure what ISC_R_NRESULTS
'invalid file' is trying to tell me. As before, the server seems to
recover, but DNS resolution does stop for about a minute.
-Michael
Michael Hare wrote:
I recently [8/1/2009] upgraded to 9.5.1P3. Last evening there were two
brief moments that the named process was not resolving out of cache.
This is a recursive only server that is basically opened to all clients,
mostly for historical reasons. The named process recovered on its own.
While I have seen references to old bugs/issues
https://lists.isc.org/mailman/htdig/bind-users/2005-January/055224.html
This seems to be something different. We're [still] on Red Hat
Enterprise Linux AS release 3. Any advice on what to investigate?
Thanks-
-Michael
Aug 17 01:24:53 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 01:24:53 named[20688]: general: error: internal_send:
144.92.162.225#57060: Invalid argument
Aug 17 01:24:53 named[20688]: client: warning: client
144.92.162.225#57060: error sending response: invalid file
Aug 17 01:24:53 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 01:24:53 named[20688]: general: error: internal_send:
216.180.219.44#11059: Invalid argument
Aug 17 01:24:53 named[20688]: client: warning: client
216.180.219.44#11059: error sending response: invalid file
...
...
Aug 17 01:25:17 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 01:25:17 named[20688]: general: error: internal_send:
143.215.143.11#32833: Invalid argument
Aug 17 01:25:17 named[20688]: client: warning: client
143.215.143.11#32833: error sending response: invalid file
Aug 17 01:25:17 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 01:25:17 named[20688]: general: error: internal_send:
128.104.22.33#57369: Invalid argument
Aug 17 01:25:17 named[20688]: client: warning: client
128.104.22.33#57369: error sending response: invalid file
Aug 17 01:25:57 named[20688]: general: warning: checkhints: unable to
get root NS rrset from cache: not found
Aug 17 02:38:54 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 02:38:54 named[20688]: general: error: internal_send:
144.92.166.12#9500: Invalid argument
Aug 17 02:38:54 named[20688]: client: warning: client
144.92.166.12#9500: error sending response: invalid file
Aug 17 02:38:54 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 02:38:54 named[20688]: general: error: internal_send:
144.92.166.12#14442: Invalid argument
Aug 17 02:38:54 named[20688]: client: warning: client
144.92.166.12#14442: error sending response: invalid file
...
...
Aug 17 02:39:23 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 02:39:23 named[20688]: general: error: internal_send:
202.108.181.80#50110: Invalid argument
Aug 17 02:39:23 named[20688]: client: warning: client
202.108.181.80#50110: error sending response: invalid file
Aug 17 02:39:23 named[20688]: general: error: socket.c:1577: unexpected
error:
Aug 17 02:39:23 named[20688]: general: error: internal_send:
202.108.181.80#37064: Invalid argument
Aug 17 02:39:23 named[20688]: client: warning: client
202.108.181.80#37064: error sending response: invalid file
_______________________________________________
bind-users mailing list
bind-users@lists.isc.org
https://lists.isc.org/mailman/listinfo/bind-users
