bind 8.2.1 crashes and time is set to 1 jan 1970
jim at rfc1035.com
Thu Mar 2 18:18:11 UTC 2000
>>>>> "Marcel" == Marcel Janssen <maja at oce.nl> writes:
Marcel> All, my named 8.2.1 crashed with the following error codes
Marcel> My system clock went to ground zero 1-jan-1970.
Marcel> 01-Jan-1970 01:00:16.278 insist: critical: ns_main.c:521: INSIST(errno == EINTR): Invalid argument failed.
Marcel> 01-Jan-1970 01:00:16.278 panic: critical: ns_main.c:521: INSIST(errno == EINTR): Invalid argument failed.
The name server probably crashed because the time of day on your
system got zapped and this screwed up the assertion checking in the
name server's even handler.
It's probably more important to find out why the clock got
zeroed. [This shouldn't be a name server problem since named doesn't
set the system date.] Good UNIX systems don't allow the clock to be
put back when the system is in multi-user mode and you should be
running NTP to keep the system clock sync'ed to the real time of day.
BTW, you should upgrade to 8.2.2P5, the current version. Or wait a few
weeks for 8.2.3.
More information about the bind-users