Bug 31341

Summary:	bind exits with core dump and signal 6 every few days
Product:	Base System	Reporter:	Tentacle root <root>
Component:	bin	Assignee:	freebsd-bugs (Nobody) <bugs>
Status:	Closed FIXED
Severity:	Affects Only Me
Priority:	Normal
Version:	4.4-STABLE
Hardware:	Any
OS:	Any

Description Tentacle root 2001-10-17 18:50:00 UTC

	bind dies unexpectedly with a signal 6.  In the security check output:
 Oct 17 01:58:02 chaos named[28525]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274: INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
 Oct 17 01:58:02 chaos named[28525]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274: INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
 pid 28525 (named), uid 53: exited on signal 6
 Oct 17 01:58:02 chaos /kernel: pid 28525 (named), uid 53: exited on signal 6

Fix: 

Someone suggested "sysctl -w kern.timecounter.method=1"; I'm not sure this
works yet.
How-To-Repeat: 	Has happened twice, 4 days apart, so far.

Comment 1 Kris Kennaway 2002-01-06 03:54:48 UTC

On Wed, Oct 17, 2001 at 10:41:49AM -0700, Tentacle root wrote:

>  Oct 17 01:58:02 chaos named[28525]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274: INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
>  Oct 17 01:58:02 chaos named[28525]: /usr/src/usr.sbin/named/../../contrib/bind/bin/named/ns_maint.c:274: INSIST(zp->z_time == 0 || zp->z_time > tt.tv_sec) failed.
>  pid 28525 (named), uid 53: exited on signal 6
>  Oct 17 01:58:02 chaos /kernel: pid 28525 (named), uid 53: exited on signal 6
> 
> >How-To-Repeat:
> 	Has happened twice, 4 days apart, so far.
> >Fix:
>   Someone suggested "sysctl -w kern.timecounter.method=1"; I'm not sure this
> works yet.


Please consult the mailing list archives; this is almost certainly due
to a non-functional system clock.

Kris

Comment 2 Sheldon Hearn freebsd_committer

2002-01-07 14:44:53 UTC

State Changed
From-To: open->feedback

As per Kris' follow-up, we're waiting to hear from the originator 
whether it is indeed a system clock problem.

Comment 3 Tentacle root 2002-01-07 15:02:46 UTC

Unfortunately, I have no more data.  I moved the system to another machine for 
other reasons (really could use the upgrade to scsi), and there have been no 
further problems.
As a side note, changing the timecounter method did not appear to fix the 
problem.

hth

Comment 4 Sheldon Hearn freebsd_committer

2002-01-08 17:06:13 UTC

State Changed
From-To: feedback->closed

The originator is no longer available to assist in tracking the 
problem down.