At 01:43 AM 1/11/2008, Derrick Ryalls wrote:
On Jan 10, 2008 3:52 PM, Kurt Buff <[EMAIL PROTECTED]> wrote:
>
> On Jan 10, 2008 3:14 PM, Bob Johnson <[EMAIL PROTECTED]> wrote:
> > On 1/10/08, Derrick Ryalls <[EMAIL PROTECTED]> 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 [EMAIL PROTECTED] 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" [EMAIL PROTECTED]
================================================
-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.
_______________________________________________
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
