[Nut-upsuser] trouble with ups mge evolution2200 and mandriva 2007 - nut 2. 2 + PSP
sabine.goudard at st-etienne.archi.fr
Tue Nov 13 16:07:19 UTC 2007
I have another question
if I don't use the script uspssched-cmd but a script made by myself (only
with a echo "...")
I have a recturn code 127 ou return code 1 on exec-cmd parameter
what does it means ?
thanks a lot for your help
De : goudard sabine
Envoyé : mardi 13 novembre 2007 11:24
À : 'aquette.dev at gmail.com'
Cc : 'nut-upsuser at lists.alioth.debian.org'
Objet : trouble with ups mge evolution2200 and mandriva 2007 - nut 2.2 +
I'll be back with my MGE Evolution 2200 connected with RS232
I upgrade nut 2.0.1 in nut 2.2 + psp
as you ask me
PSP autodetect my UPS and autoconfigure NUT.
not really diffcult !
So I didn't change anything but I always have in my syslog these event
Nov 13 11:09:22 mezenc upsmon: Poll UPS [mgeups at localhost] failed -
Nov 13 11:09:27 mezenc upsmon: Poll UPS [mgeups at localhost] failed -
and my server shut down
what can I do ?
Thanks for your help
De: Arnaud Quette
A: goudard sabine
Cc: Arjen de Korte; nut-upsuser at lists.alioth.debian.org
Date: 25/10/2007 23:06
Objet: Re: [Nut-upsuser] trouble with ups mge evolution2200 and mandriva
2007 - nut 2.01
I'll add some more comments to Arjen's answer.
2007/10/16, Arjen de Korte <nut+users at de-korte.org>:
> > 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
> its 'use by' date.
this is true.
You can find 2.2.0 packages, along with the MGE PSP here:
urpmi.addmedia mgeups http://opensource.mgeups.com/stable/mdvlinux/
The PSP will autodetect your UPS and autoconfigure NUT.
So you might prefer it.
> > 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'
I've just made a statement about this: use mge-shut for the moment!
> you use a serial connection and 'usbhid-ups' if you use a USB
> 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
> > 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
> > 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
> This used to be needed in very old versions (well before nut-1.4.0).
> you're seeing is unrelated to this problem, therefor the fix doesn't
> A workaround for this was introduced in nut-2.0.5 and the final
> will be in nut-2.2.1.
exactly. Moreover, this website is under heavy rewrite / update (part
of the MGE UPS dismantling, and the MGE Office Protection Systems
you should try to set pollinterval=10 in ups.conf
the default value (2 seconds) was fine with dumb / non verbose
protocols, but tends to overload unnecessarily the bus on both the
host and device side. Moreover, this kind of smart units supports
notification (the UPS sends info by itself, so less need to read
> > 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
> > 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
> low) or does the UPS suddenly turn off (which would be bad)? In any
> prior to shutting down, the upsmon client should mention that the UPS
> critical (UPS status flags "OB+LB"). Can you confirm that this is
> > 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
> user? Also, please post the contents of this script.
I agree with Arjen's audit.
You should really give a try to the PSP, since it deals with all these
Then get back to us if the problem still exists.
Free Software Developer - http://arnaud.quette.free.fr/
Debian Developer - http://people.debian.org/~aquette/
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Ubuntu Media Center (UMC) Project Leader -
More information about the Nut-upsuser