From owner-freebsd-bugs  Sat Mar 14 09:30:03 1998
Return-Path: <owner-freebsd-bugs@FreeBSD.ORG>
Received: (from majordom@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA06168
          for freebsd-bugs-outgoing; Sat, 14 Mar 1998 09:30:03 -0800 (PST)
          (envelope-from owner-freebsd-bugs@FreeBSD.ORG)
Received: (from gnats@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA06160;
          Sat, 14 Mar 1998 09:30:01 -0800 (PST)
          (envelope-from gnats)
Received: (from nobody@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id JAA05780;
          Sat, 14 Mar 1998 09:28:10 -0800 (PST)
          (envelope-from nobody)
Message-Id: <199803141728.JAA05780@hub.freebsd.org>
Date: Sat, 14 Mar 1998 09:28:10 -0800 (PST)
From: null.angel@null.angel.nu
To: freebsd-gnats-submit@FreeBSD.ORG
X-Send-Pr-Version: www-1.0
Subject: bin/6005: -CURRENT cron dies after short periods of times (2-4 hours)
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


>Number:         6005
>Category:       bin
>Synopsis:       -CURRENT cron dies after short periods of times (2-4 hours)
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          open
>Quarter:
>Keywords:
>Date-Required:
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sat Mar 14 09:30:01 PST 1998
>Last-Modified:
>Originator:     Thomas Stromberg
>Organization:
RTCI, Inc.
>Release:        FreeBSD 3.0-CURRENT
>Environment:
FreeBSD nineveh.angel.nu 3.0-CURRENT FreeBSD 3.0-CURRENT #2: Fri Mar 13 12:20:39 GMT 1998     null.angel@nineveh.angel.nu:/usr/src/sys/compile/nebuchadazzar  i386
>Description:
(in reference to previous pr on -CURRENT's crontab). 

I did notice that cron actually died while trying to execute my entries:

*/1 * * * * /www/null.angel.nu/desktop/dumpme (shell script).
and
*/1 * * * * /usr/X11R6/bin/xwd -display localhost:0.0 -out /tmp/dump.xwd -silent -root; /usr/local/bin/convert -quality 50 /tmp/dump.xwd /tmp/dump.jpg; mv /tmp/dump.jpg /www/null.angel.nu/de....

The cronned jobs went fine for 2-4 hours (seemed random), and then suddenly stop. 
/var/cron/log would log that it had executed these jobs, but later I found:

Mar 14 10:48:00 nineveh /kernel: pid 7118 (cron), uid 0: exited on signal 11
Mar 14 10:48:00 nineveh /kernel: pid 7119 (cron), uid 0: exited on signal 11
Mar 14 10:47:00 nineveh /kernel: pid 7113 (cron), uid 0: exited on signal 11
Mar 14 10:47:00 nineveh /kernel: pid 7114 (cron), uid 0: exited on signal 11
Mar 14 10:46:00 nineveh /kernel: pid 7110 (cron), uid 0: exited on signal 11
Mar 14 10:46:00 nineveh /kernel: pid 7109 (cron), uid 0: exited on signal 11
Mar 14 10:45:00 nineveh /kernel: pid 7103 (cron), uid 0: exited on signal 11
Mar 14 10:45:00 nineveh /kernel: pid 7102 (cron), uid 0: exited on signal 11
Mar 14 10:44:00 nineveh /kernel: pid 7099 (cron), uid 0: exited on signal 11
Mar 14 10:43:00 nineveh /kernel: pid 7089 (cron), uid 0: exited on signal 11
Mar 14 10:42:00 nineveh /kernel: pid 7086 (cron), uid 0: exited on signal 11  

It would stay this way until kill -9'ing cron and restarting it. 

>How-To-Repeat:
try cron entries such as:
*/1 * * * * /www/null.angel.nu/desktop/dumpme (shell script)
*/1 * * * * /usr/X11R6/bin/xwd -display localhost:0.0 -out /tmp/dump.xwd -silent -root; /usr/local/bin/convert -quality 50 /tmp/dump.xwd /tmp/dump.jpg; mv /tmp/dump.jpg /www/nu

>Fix:
killall -9 cron
cron

:(
>Audit-Trail:
>Unformatted:

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message