From owner-freebsd-questions@FreeBSD.ORG Wed Aug 10 17:34:39 2005 Return-Path: X-Original-To: freebsd-questions@freebsd.org Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 5585216A41F for ; Wed, 10 Aug 2005 17:34:39 +0000 (GMT) (envelope-from chad@shire.net) Received: from hobbiton.shire.net (hobbiton.shire.net [166.70.252.250]) by mx1.FreeBSD.org (Postfix) with ESMTP id 114BE43D45 for ; Wed, 10 Aug 2005 17:34:38 +0000 (GMT) (envelope-from chad@shire.net) Received: from [67.161.222.227] (helo=[192.168.99.68]) by hobbiton.shire.net with esmtpa (Exim 4.51) id 1E2uTI-000Pnh-NI for freebsd-questions@freebsd.org; Wed, 10 Aug 2005 11:34:37 -0600 Mime-Version: 1.0 (Apple Message framework v733) Content-Transfer-Encoding: 7bit Message-Id: <09A18BB6-3FE1-4E2D-867F-04AD1F9EFE27@shire.net> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: FreeBSD - Questions From: Chad Leigh -- Shire.Net LLC Date: Wed, 10 Aug 2005 11:34:32 -0600 X-Mailer: Apple Mail (2.733) X-SA-Exim-Connect-IP: 67.161.222.227 X-SA-Exim-Mail-From: chad@shire.net X-SA-Exim-Scanned: No (on hobbiton.shire.net); SAEximRunCond expanded to false Subject: (also 5.4) re: Abort Trap for cron-jobs in 5.3 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Aug 2005 17:34:39 -0000 a few months ago the following appeared in -stable " In the last episode (Mar 15), Niklas Saers said: > On Tue, 15 Mar 2005, Niklas Saers wrote: > > I've got four servers that all have the same problem: when jobs get > > started from Cron, they die after some time with an "Abort trap". > > Jobs that are dying are: > > > > /usr/libexec/atrun >> /var/log/cron 2>&1 /usr/bin/nice -10 /usr/ local/bin/zsh /root/bin/sendBarkMail.sh > /dev/null 2>&1 > > > > I also get this on virtually every shell-script that uses tar, leaving my > > filesystem littered with bsdtar.core files. > > > > Running these jobs from the command prompt works fine. Any suggestions on > > what may be causing them to die from cron? sendBarkMail.sh simply moves > > mails from one folder to another periodically > > Note to self: ask the question. ;-) > > What I'm wondering about is: what could be causing the Abort Trap's? > > World and kernel are a recent RELENG_5_3 compiled like described in > src/UPDATING. What's the stack trace from one of those cores? Also, try not redirecting stdout and stderr to /dev/null; you are probably discarding a valuable error message. -- Dan Nelson dnelson at allantgroup.com " I saw the same thing in 5.3 and newly upgraded to 5.4 and it is still happening. It seems to happen randomly. There is no output or error redirection and nothing useful in the output/error stream that I can see. Mostly inside of jails. > To: william@xxxxxxx.com > From: Cron Daemon > Date: Wed, 10 Aug 2005 11:55:04 -0400 > Subject: Cron /usr/libexec/atrun > > Abort trap Chad --- Chad Leigh -- Shire.Net LLC Your Web App and Email hosting provider chad@shire.net