named[4120]: socket.c:1100: unexpected error:

news.comcast.giganews.com nomadpgmr at comcast.net
Thu Feb 12 10:01:08 UTC 2004


While reoragnizing some rackspace we moved our DNS server last night and
then rebooted it again tonight, as part of switchign which UPS it is plugged
into.
After rebooting it tonight we started seeing the following errors.
Everything else on the server appears to be running OK.

I am running bind 9.2.1 on RH Linux 9. I have added the -d3 switch to get
more debugging information, but no error messages are showing. Anyone have
any idea what might cause this? The problem occured right after tonights
power down (shutdown -h now) and restart.

I am at my wits end as to what might be causing this. I am unable recognize
any clues that might point to the cause of this problem. Any assistance
would be appreciated.

Feb 12 01:00:18 ns1 named[4120]: running
Feb 12 01:00:20 ns1 named[4120]: socket.c:1100: unexpected error:
Feb 12 01:00:20 ns1 named[4120]: internal_send: 244.254.254.254#53: Invalid
argument
Feb 12 01:00:20 ns1 named[4120]: socket.c:1100: unexpected error:
Feb 12 01:00:20 ns1 named[4120]: internal_send: 244.254.254.254#53: Invalid
argument
Feb 12 01:00:20 ns1 named[4120]: socket.c:1100: unexpected error:
....
and on and on and on


I also set debugging to d3 and have the following information:

Feb 12 00:56:11.026 client 61.171.17.89#64225: UDP request
Feb 12 00:56:11.026 client 61.171.17.89#64225: request is not signed
Feb 12 00:56:11.026 client 61.171.17.89#64225: recursion available: approved
Feb 12 00:56:11.026 client 61.171.17.89#64225: query
Feb 12 00:56:11.026 client 61.171.17.89#64225: query (cache) approved
Feb 12 00:56:11.026 client 61.171.17.89#64225: send
Feb 12 00:56:11.026 client 61.171.17.89#64225: sendto
Feb 12 00:56:11.026 client 61.171.17.89#64225: senddone
Feb 12 00:56:11.026 client 61.171.17.89#64225: next
Feb 12 00:56:11.026 client 61.171.17.89#64225: endrequest
Feb 12 00:56:11.027 client @0x8721670: udprecv
Feb 12 00:56:11.031 resquery 0x87771e0 (fctx 0x87461e8): response
Feb 12 00:56:11.031 fctx 0x87461e8: noanswer_response
Feb 12 00:56:11.031 fctx 0x87461e8: cache_message
Feb 12 00:56:11.031 fctx 0x87461e8: cancelquery
Feb 12 00:56:11.031 fctx 0x87461e8: cancelqueries
Feb 12 00:56:11.031 fctx 0x87461e8: try
Feb 12 00:56:11.031 fctx 0x87461e8: cancelqueries
Feb 12 00:56:11.031 fctx 0x87461e8: getaddresses
Feb 12 00:56:11.031 fctx 0x87461e8: query
Feb 12 00:56:11.031 resquery 0x87445e0 (fctx 0x87461e8): send
Feb 12 00:56:11.032 socket.c:1100: unexpected error:
<<============ 1 Error appears here
Feb 12 00:56:11.032 internal_send: 244.254.254.254#53: Invalid argument
Feb 12 00:56:11.032 resquery 0x87445e0 (fctx 0x87461e8): sent
Feb 12 00:56:11.032 resquery 0x87445e0 (fctx 0x87461e8): senddone
Feb 12 00:56:11.032 fctx 0x87461e8: cancelquery
Feb 12 00:56:11.034 resquery 0x8774ef0 (fctx 0x874b138): response
Feb 12 00:56:11.034 fctx 0x874b138: answer_response
Feb 12 00:56:11.034 fctx 0x874b138: cache_message
Feb 12 00:56:11.034 fctx 0x874b138: cancelquery
Feb 12 00:56:11.035 fctx 0x874b138: done
Feb 12 00:56:11.035 fctx 0x874b138: stopeverything
Feb 12 00:56:11.035 fctx 0x874b138: cancelqueries
Feb 12 00:56:11.035 fctx 0x874b138: sendevents
Feb 12 00:56:11.035 fetch 0x8616de8 (fctx 0x874b138): destroyfetch
Feb 12 00:56:11.035 fctx 0x874b138: shutdown
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 DNS_EVENT_ADBMOREADDRESSES
Feb 12 00:56:11.035 resquery 0x8775168 (fctx 0x8763110): response




More information about the bind-users mailing list