[Nut-upsuser] NUT on CentOS (asterisk@home)

Arnaud Quette aquette.dev at gmail.com
Wed Aug 30 13:35:40 UTC 2006


Hi Davide,

2006/8/29, Davide Ferrari <davide.ferrari at atrapalo.com>:
> El Martes, 29 de Agosto de 2006 14:13, Doug Parsons escribió:
> > http://rpmfind.net/linux/rpm2html/search.php?query=nut
> >
> > And use the package for the Fedora Core 4. CentOS is of course a clone of
> > Redhat and this version is RHEL4 if I am correct. Most of the packages for
> > the Fedora Core 4 will work. It too is a clone but uses all the latest
> > packages of everything as a test bed for the leading edge.
> >
> > http://rpmfind.net//linux/RPM/fedora/updates/4/i386/nut-2.0.3-0.fc4.2.i386.
> >h tml
> >
> > Takes you straight to the package.
>
> Thanks for the suggestion...I was wrong with the CentOS version I suppose
> cause it happens to be a Fedora3 clone, so Fedora4 packages doesn't work, but
> with Fedora3 packages it gone smoothly.
>
> Now I'm stuck with getting the snmp driver working, I've installed net-snmp
> but here it is what I get:
>
> # /sbin/snmp-ups -DD -a sai
> Network UPS Tools - Multi-MIBS SNMP UPS driver 0.41 (2.0.2)
> Warning: This is an experimental driver.
> Some features may not function correctly.
>
> debug level is '2'
> SNMP UPS driver : entering upsdrv_initups()
> SNMP UPS driver : entering load_mib2nut(ietf)
> load_mib2nut: using ietf (RFC 1628) mib
> SNMP UPS driver : entering nut_snmp_init(snmp-ups, sai.atrapalo.com, public)
> ietf MIB wasn't found on sai.atrapalo.com
>
> The config file are taken exactly the same from a gentoo/ubuntu installation
> (see my previous post "NUT on Ubuntu Dapper")...it's due to an unsupported
> UPS in 2.0.2 version? It's the only difference between this and the other
> installations which are 2.0.3...
> It's a MGE UPS Comet Extreme with a SNMP Transverse card ref. 66074

I don't see any reason to this failure, according to your info.
moreover, snmp-ups hasn't received much attention for long, so the
problem shouldn't come from the version diff between 2.0.2 and 2.0.3.

since snmp-ups is based upon Net SNMP, the problem might sit here.
So, did you try some snmpwalk/snmpget from the same box to see if data
is reachable?

Arnaud
-- 
Linux / Unix Expert - MGE UPS SYSTEMS - R&D Dpt
Network UPS Tools (NUT) Project Leader - http://www.networkupstools.org/
Debian Developer - http://people.debian.org/~aquette/
OpenSource Developer - http://arnaud.quette.free.fr/



More information about the Nut-upsuser mailing list