Help needed please!!!!
Dhanasekaran
dhana at india.hp.com
Sat Jul 28 14:34:04 UTC 2001
Hello All,
I am getting an assertion failure in named.
Did anybody know why named is exiting with assertion failure??
Under what situation named will exit with such kind of
error??
I could able to see from the mail archive that couple
of folks faced the same problem. Also, I came to know
that it has been fixed in bind-9.1.X from one of them.
But, I would like to know more details about this in bind-9.0.0.
Any help would be highly appreciated!!
Here's the details.
Jul 24 11:06:53 tmach named[16226]: loading configuration from
'/etc/named.conf'
Jul 24 11:06:53 tmach named[16226]: the default for the 'auth-nxdomain'
option is now 'no'
Jul 24 11:06:55 tmach named[16226]: dispatch 4004a6f8: odd socket result
in udp_recv(): unexpected error
Jul 24 11:07:00 tmach named[16226]: dispatch 4004a6f8: odd socket result
in udp_recv(): host unreachable
Jul 24 11:07:00 tmach named[16226]: dispatch 4004a6f8: odd socket result
in udp_recv(): host unreachable
Jul 24 11:08:23 tmach named[16226]:
/ux/core/inet/src/bind.src/bind-9/bind-9.0.0/lib/dns/resolver.c:1683:
REQUIRE((((fctx->queries).head == 0L) ? isc_boolean_true :
isc_boolean_false)) failed
Jul 24 11:08:23 tmach named[16226]: exiting (due assertion failure)
Jul 24 11:07:38 tmach named[16226]: dispatch 4004a6f8: odd socket result
in udp_recv(): unexpected error
Jul 24 11:15:31 tmach above message repeats 3 times
Thanks in advance for your help!!!
With Regards,
D.Dhana.
More information about the bind-users
mailing list