<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Thanks for you answer.<br>
When the UPS comes offline upssched is now lauching the timer.
However when the UPS gets online the timer does not stop. <br>
Yet I think it is due to another problem: when it comes online my
UPS gets disconnected for a very short time, and it takes a few
seconds to have it back on usb and with an online status on nut. I
hope to receive pieces of advise from EATON regarding this issue.
This might be a physical problem coming from my ups.<br>
Best Regards.<br>
<br>
<br>
Le 08/09/2011 17:27, Arnaud Quette a écrit :
<blockquote
cite="mid:CAFm_bUjekZpbVeb5up32bSaF6qKPQ63CoSssh4SidaWQJjh0gg@mail.gmail.com"
type="cite">Hi,<br>
<br>
<div class="gmail_quote">2011/9/1 Dupdup Sys <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:dupdupsystems@gmail.com"
target="_blank">dupdupsystems@gmail.com</a>></span><br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hello,<br>
I am currently building a new server using debian amd64.
Therefore I need to use my UPS EATON Evolution 1550 on it,
using usbhid-ups driver.<br>
I installed nut with apt (version 2.4.3-1.1squeeze1) on debian
2.6.32-5 amd64.<br>
<br>
I can currently use nut with the drivers, upsc and upsmon: my
UPS is detected and works. Actually everything works except
upssched: I can shut down the server using upsmon -c fsd. I
didn't try yet but I think the automatic shutdown would work
either, the server should stop when the ups battery goes too
low.<br>
<br>
However I definetely can't make upssched running, which is
such a big deal because I would like to use the timer
functions to have a shutdown after ten minutes without
electricity.<br>
I created in /var/run/nut an upssched folder to contain the
upssched files, made chgrp nut.nut and chmod 755. My
upsmon.conf contains the NOTIFYCMD /sbin/upssched.<br>
<br>
Here comes the issue: I can't find any lead of upssched in
/var/log/daemon.log. While usbhid-ups, upsd and upsmon have
their entries in the logfile and are working, I can't find
anything about upssched in the logs. Thereby I do think that
upssched is inactive, but I am still wondering if the problem
is not in upsmon: I tried several permissions, tried to use an
other script in upsmon.conf, but didn't manage to have it
working.<br>
<br>
Do you have any idea on how this could be solve ?<br>
Best Regards.<br>
</blockquote>
</div>
<br>
upssched is only active when needed, ie when upsmon fires it
because of execution triggers.<br>
<br>
so you have to meet these conditions, ie switching on battery,
..., as you have defined in upsmon.conf or as done by default.<br>
<br>
note that /var/run/nut is created automatically when calling the
nut init script on Debian.<br>
<br>
cheers,<br clear="all">
Arnaud<br>
-- <br>
Linux / Unix Expert R&D - Eaton - <a moz-do-not-send="true"
href="http://powerquality.eaton.com" target="_blank">http://powerquality.eaton.com</a><br>
Network UPS Tools (NUT) Project Leader - <a
moz-do-not-send="true" href="http://www.networkupstools.org/"
target="_blank">http://www.networkupstools.org/</a><br>
Debian Developer - <a moz-do-not-send="true"
href="http://www.debian.org" target="_blank">http://www.debian.org</a><br>
Free Software Developer - <a moz-do-not-send="true"
href="http://arnaud.quette.free.fr/" target="_blank">http://arnaud.quette.free.fr/</a><br>
<br>
</blockquote>
<br>
</body>
</html>