Bind Exits with Assertion Failure

Brian Foddy bfoddy at visi.com
Thu May 12 18:17:32 UTC 2005


Using a recently installed Mandrake 10.1 server, running
Bind bind-9.3.0-3.1.101mdk.  The machine is hooked to a
residential DSL.  The server will frequently die with the
following errors in syslog:

4:04:44 windward named[26780]: socket.c:1627: INSIST(!sock->pending_send) 
failed
May 12 04:04:44 windward named[26780]: exiting (due to assertion failure)

It seems to die when the DSL connection has been disconnected.  Its
disconnected because of occasional voltage spikes during lightning
storms that will fry the phone line surge suppressor.  So anytime
an electrical storm is likely they will usually unhook the phone line;
many times over night.

Several hours later the named server will die as above.  There are only
3-4 machines behind the server that are relatively idle but there will be
some request traffic.  An old install of Redhat 7.3 with its named version
took this scenario without a problem.

I can post the named.conf file if needed.  Any suggestions or
additional debugging steps I can try?

Thanks,
Brian



More information about the bind-users mailing list