From owner-freebsd-stable@FreeBSD.ORG Tue Mar 15 16:52:33 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id DE76316A4CE for ; Tue, 15 Mar 2005 16:52:33 +0000 (GMT) Received: from dan.emsphone.com (dan.emsphone.com [199.67.51.101]) by mx1.FreeBSD.org (Postfix) with ESMTP id 82B7F43D2F for ; Tue, 15 Mar 2005 16:52:33 +0000 (GMT) (envelope-from dan@dan.emsphone.com) Received: (from dan@localhost) by dan.emsphone.com (8.13.1/8.13.1) id j2FGqU7M061789; Tue, 15 Mar 2005 10:52:30 -0600 (CST) (envelope-from dan) Date: Tue, 15 Mar 2005 10:52:30 -0600 From: Dan Nelson To: Niklas Saers Message-ID: <20050315165230.GB98412@dan.emsphone.com> References: <20050315131444.X11456@doriath.saers.com> <20050315171613.G58112@doriath.saers.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050315171613.G58112@doriath.saers.com> X-OS: FreeBSD 5.4-PRERELEASE X-message-flag: Outlook Error User-Agent: Mutt/1.5.8i cc: freebsd-stable@freebsd.org Subject: Re: Abort Trap for cron-jobs in 5.3 X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2005 16:52:34 -0000 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@allantgroup.com