From owner-freebsd-isp@FreeBSD.ORG Sun Feb 29 13:35:09 2004 Return-Path: Delivered-To: freebsd-isp@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D741E16A567 for ; Sun, 29 Feb 2004 13:35:09 -0800 (PST) Received: from destiny.chrononomicon.com (mail.chrononomicon.com [65.193.73.208]) by mx1.FreeBSD.org (Postfix) with ESMTP id 72D6743D2D for ; Sun, 29 Feb 2004 13:35:09 -0800 (PST) (envelope-from bsilver@chrononomicon.com) Received: from [IPv6:::1] (destiny.chrononomicon.com [192.168.1.42]) by destiny.chrononomicon.com (Postfix) with ESMTP id C6E0C1FDFF for ; Sun, 29 Feb 2004 16:34:55 -0500 (EST) Mime-Version: 1.0 (Apple Message framework v612) Content-Transfer-Encoding: 7bit Message-Id: <1FD37066-6AFF-11D8-A3D1-000A956D2452@chrononomicon.com> Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed To: freebsd-isp@freebsd.org From: Bart Silverstrim Date: Sun, 29 Feb 2004 16:34:59 -0500 X-Mailer: Apple Mail (2.612) Subject: Cron Job failure with aaccli X-BeenThere: freebsd-isp@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Internet Services Providers List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 29 Feb 2004 21:35:10 -0000 Hello, I have a Dell 6250 with the perc3/di RAID controller in it and a fresh install of FreeBSD 4.9-release. I used the aaccli utility from the ports collection and a script I found when googling around for a cron script that worked with the sell utility. I modified the script so it would open the correct device and point to the right applications (the script was for a Linux installation with Sendmail; I am running FreeBSD with Postfix). You have to run a series of commands to create a "seed" file with the default, working RAID output from aaccli. This worked fine. I created a backup of it, altered a line in it to make a subsequent test look like something was wrong with the RAID system. I run the script itself from the shell, it emailed me an alert. I run the cron script from sh (because the redirect of output is in sh, not tcsh), it runs fine and emails an alert. Cron runs the script, aaccli hangs as if the input is getting munged? the script hangs in the process list and I have to kill aaccli for the script and aaccli to disappear from the process listing. I've checked by putting in a cron entry that just echos the shell in use to a file from cron and it is running with sh. If I run the cron script or the actual script from sh (as root I just run "/bin/sh" and run it from that prompt) they both run fine. So why is aaccli hanging when cron tries to run it? The link to the script I've adapted is http://public.www.planetmirror.com/pub/domsch/aacraid/ aacraid_monitoring_script.txt Anyone out there know what is causing it to hang?? -Bart Silverstrim