BSDI 4.1 - named 9.0.1
Jim Reid
jim at rfc1035.com
Thu Dec 21 17:49:55 UTC 2000
>>>>> "Carl" == Carl Duescher <carld at clublouie.com> writes:
Carl> else has seen this / come up with a solution. We have a
Carl> BSDI 4.1 box running BIND 9.0.1, as of late it starting
Carl> crashing with the following:
Carl> Dec 19 16:55:04 mailhost named[20331]: timer.c:367: unexpected error:
Carl> Dec 19 16:55:05 mailhost named[20331]: isc_time_now() failed: unexpected error
Carl>
Carl> Dec 20 15:12:22 mailhost named[20331]: stdtime.c:40: INSIST(tv.tv_usec >= 0 && tv.tv_usec < 1000000) failed
Carl> Dec 20 15:12:22 mailhost named[20331]: exiting (due assertion failure)
This is a bug in BSD/OS. The kernel returns any old rubbish in the
tv_usec element of the timeval struct used in the gettimeofday()
system call. Negative numbers of microseconds or more than 1 million
microseconds are not sensible values for tv_usec. BIND9 checks for and
objects to those nonsense numbers of microseconds: hence the assertion
failure above. You'll have to ask BSDI for a patch.
More information about the bind-users
mailing list