Nut upsuser - Oct 2007 - trouble with ups mge evolution2200 and mandriva 2007 - nut 2.01

hello,
at first I'm sorry my english isn't perfect but I tried to be clear

I work with mandriva 2007 and with nut 2.0.1 installed with urpmi
my UPS is a MGE Evolution 2200 connected with RS232

in my ups.conf
I try to use mge-utalk driver and also mge-shut
both seem to work
I don't really known which I add to use

It's the first point.


As I saw on web site, I add maxage 25 in upsd.conf and DEADTIME 25 in
upsmon.conf
to avoid 
Data for UPS [mge at localhost] is stale - check driver
poll UPS [mge at localhost] failed - data stale
UPS [mge at localhost] data is no longer stale
Communications with ups mge at localhost established

it doesn't change any thing ; when I had these event in syslog my computer
stop even if I don't put this in upsmon.conf

It's the second point.


The third point
with my conf all the commands upsc, upsmon, upsrw etc etc ... are OK
the connection with driver is OK
but when the battery is ON DISCHARG, I've an event in syslog and after a
moment my computer stop
If I put a script in NOTIFYCMD parameter, this script isn't executed

what is wrong

upsmon.conf
MONITOR mge2200 at localhost 1 ups azerty master
MINSUPPLIES 1
SHUTDOWNCMD "/sbin/shutdown -h now"
NOTIFYCMD /etc/ups/upsalert 
POWERDOWNFLAG /etc/ups/killpower
NOTIFYMSG ONBATT "L'onduleur %s est sur batterie" 
NOTIFYMSG ONLINE "L'onduleur %s est aliment?"
NOTIFYFLAG ONBATT SYSLOG+EXEC
NOTIFYFLAG ONLINE SYSLOG+EXEC

thanks for your help




Sabine GOUDARD
Ecole Nationale Sup?rieure d'Architecture de St Etienne
Service Informatique
7 rue Etienne Dolet
42000 Saint-Etienne
mailto:sabine.goudard at st-etienne.archi.fr

> hello,
> at first I'm sorry my english isn't perfect but I tried to be clear
>
> I work with mandriva 2007 and with nut 2.0.1 installed with urpmi
> my UPS is a MGE Evolution 2200 connected with RS232
First of all, upgrade to nut-2.2.0. The version you have now is well past
its 'use by' date.
> in my ups.conf
> I try to use mge-utalk driver and also mge-shut
> both seem to work
> I don't really known which I add to use
>
> It's the first point.
We now (nut-2.2.0) recommend to use 'newmge-shut' or 'mge-shut'
drivers if
you use a serial connection and 'usbhid-ups' if you use a USB
connection.
You should only use mge-utalk if this is all your UPS supports.
> As I saw on web site, I add maxage 25 in upsd.conf and DEADTIME 25 in
> upsmon.conf
> to avoid
> Data for UPS [mge at localhost] is stale - check driver
> poll UPS [mge at localhost] failed - data stale
> UPS [mge at localhost] data is no longer stale
> Communications with ups mge at localhost established
>
> it doesn't change any thing ; when I had these event in syslog my
computer
> stop even if I don't put this in upsmon.conf
>
> It's the second point.
The advisory on the website is no longer applicable and should be removed.
This used to be needed in very old versions (well before nut-1.4.0). What
you're seeing is unrelated to this problem, therefor the fix doesn't
work.
A workaround for this was introduced in nut-2.0.5 and the final solution
will be in nut-2.2.1.
> The third point
> with my conf all the commands upsc, upsmon, upsrw etc etc ... are OK
> the connection with driver is OK
> but when the battery is ON DISCHARG, I've an event in syslog and after
a
> moment my computer stop
I'm not quite sure what kind of problem you have. Does the computer
shutdown cleanly (which is what should happen if the battery is getting
low) or does the UPS suddenly turn off (which would be bad)? In any case,
prior to shutting down, the upsmon client should mention that the UPS is
critical (UPS status flags "OB+LB"). Can you confirm that this is
reported?
> If I put a script in NOTIFYCMD parameter, this script isn't executed
>
> what is wrong
>
> upsmon.conf
> MONITOR mge2200 at localhost 1 ups azerty master
> MINSUPPLIES 1
> SHUTDOWNCMD "/sbin/shutdown -h now"
> NOTIFYCMD /etc/ups/upsalert
> POWERDOWNFLAG /etc/ups/killpower
> NOTIFYMSG ONBATT "L'onduleur %s est sur batterie"
> NOTIFYMSG ONLINE "L'onduleur %s est aliment?"
> NOTIFYFLAG ONBATT SYSLOG+EXEC
> NOTIFYFLAG ONLINE SYSLOG+EXEC
>
> thanks for your help
Most likely cause is a permissions problem. Is the STATEPATH directory
writable by the user running upsmon? Is the NOTIFYCMD executable by this
user? Also, please post the contents of this script.

Best regards, Arjen
-- 
Eindhoven - The Netherlands
Key fingerprint - 66 4E 03 2C 9D B5 CB 9B  7A FE 7E C1 EE 88 BC 57