From owner-freebsd-questions@FreeBSD.ORG Fri Jan 11 15:20:25 2008 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id D3FDB16A46C for ; Fri, 11 Jan 2008 15:20:25 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from betty.computinginnovations.com (mail.computinginnovations.com [64.81.227.250]) by mx1.freebsd.org (Postfix) with ESMTP id 617E413C47E for ; Fri, 11 Jan 2008 15:20:25 +0000 (UTC) (envelope-from derek@computinginnovations.com) Received: from p28.computinginnovations.com (dhcp-10-20-30-100.computinginnovations.com [10.20.30.100]) (authenticated bits=0) by betty.computinginnovations.com (8.13.8/8.13.8) with ESMTP id m0BFKEfQ078206; Fri, 11 Jan 2008 09:20:14 -0600 (CST) (envelope-from derek@computinginnovations.com) Message-Id: <6.0.0.22.2.20080111090620.0245e338@mail.computinginnovations.com> X-Sender: derek@mail.computinginnovations.com X-Mailer: QUALCOMM Windows Eudora Version 6.0.0.22 Date: Fri, 11 Jan 2008 09:19:54 -0600 To: "Derrick Ryalls" , "Kurt Buff" From: Derek Ragona In-Reply-To: References: <6.0.0.22.2.20080110025841.023a9bb8@mail.computinginnovations.com> <6.0.0.22.2.20080110155430.023d29d8@mail.computinginnovations.com> <54db43990801101514y317a2889l7ad18fa4ffce56be@mail.gmail.com> Mime-Version: 1.0 X-ComputingInnovations-MailScanner-Information: Please contact the ISP for more information X-ComputingInnovations-MailScanner: Found to be clean X-ComputingInnovations-MailScanner-From: derek@computinginnovations.com X-Spam-Status: No Content-Type: text/plain; charset="us-ascii"; format=flowed X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: Bob Johnson , FreeBSD Questions Subject: Re: Nut and RAID on FreeBSD 7.0 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: Fri, 11 Jan 2008 15:20:26 -0000 At 01:43 AM 1/11/2008, Derrick Ryalls wrote: >On Jan 10, 2008 3:52 PM, Kurt Buff wrote: > > > > On Jan 10, 2008 3:14 PM, Bob Johnson wrote: > > > On 1/10/08, Derrick Ryalls wrote: > > > > > > > > > > > Perhaps I need to re-evaluate my line of thinking. Light sometime > > > > flicker, but power almost never goes out. When it does it is either > > > > back on in less than 1 minute, or out for hours. If the UPS detects > > > > critical correctly and gives me at least a minute before death, then > > > > that should be plenty of time for the system to auto-shutdown. Guess > > > > I will have to do some experimentation tonight. > > > > > > While you experiment, keep in mind the following sequence of events: > > > > > > -- Power fails > > > -- UPS signals low battery > > > -- System shuts down > > > -- Power returns before UPS shuts itself down > > > --> System never reboots, because it never lost power. > > > > > > Getting around this is the tricky part. I haven't used NUT in about > > > seven years, but back then the recommendation was to shut down to > > > single user mode and run a script that delayed for some time longer > > > than the remaining battery life of the UPS, then rebooted the system. > > > There didn't seem to be an easy hook for running a script after > > > shutting down to single user mode (maybe there is now). > > > > > > I haven't looked at NUT recently, but I expect the various flags that > > > you are supposed to test are another way around this problem. > > > >Trying to test out the scripts, I ran into a road block. I see that >upsmon is working and detecting the events I wanted to detect from >these sorts of entries in /var/log/messages: > >Jan 10 23:28:57 frodo upsmon[80983]: UPS powercom@localhost on line power > >Plus a similar message for going to battery power. However, the >notify executable is having issues and is dumping dozens of lines like >this in /var/log/messages: > >Jan 10 23:28:09 frodo kernel: pid 81029 (upssched), uid 1005: exited >on signal 11 >Jan 10 23:28:09 frodo kernel: pid 81031 (upssched), uid 1005: exited >on signal 11 >Jan 10 23:28:10 frodo kernel: pid 81032 (upssched), uid 1005: exited >on signal 11 >Jan 10 23:28:10 frodo kernel: pid 81033 (upssched), uid 1005: exited >on signal 11 >Jan 10 23:28:11 frodo kernel: pid 81034 (upssched), uid 1005: exited >on signal 11 >Jan 10 23:28:11 frodo kernel: pid 81035 (upssched), uid 1005: exited >on signal 11 > >I tried giving the user the user in question (nutmon) a shell of >/bin/sh instead of /sbin/nologin but that didn't help. Any clues on >how to fix this? Executing upssched from the command line it tells me >not to execute directly (similar to what the man page states), and >manually executing the upsched-cmd shell script does work and the >script itself uses full paths for commands. What is in your notify command? I set my NOTIFYCMD in upsmon.conf to a simple shell script I created to send the message via sendmail, here is my script if that helps: ============================================ #!/usr/local/bin/ksh #set -x SENDMAIL=/usr/sbin/sendmail MAIL=/usr/bin/mail HOSTNAME=/bin/hostname MYHOSTNAME=`$HOSTNAME -s` echo $* | $MAIL -s "UPS Alert from $MYHOSTNAME" upsmon@computinginnovations.com ================================================ -Derek -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean. MailScanner thanks transtec Computers for their support.