On Sep 30, 2010, at 8:20 AM, Roger Price wrote:

I'm using NUT 2.4.1 with openSUSE 11.2, my UPS is an MGE/Eaton Ellipse ASR 1500 USBS. The set-up is as described at http://rogerprice.org/NUT.html .

Since NUT uses TCP wrappers, I have the /etc/hosts.allow entry

upsd :    10.0.0/24, localhost, LOCAL, 127.0.0.1      : ALLOW

When I pull the plug from the wall to test my setup, I get the sequence of KDE notifications and finally a successful shutdown; just as one would expect from the configuration. :-)

However I cannot access upsc

rpr...@glacon2:~> upsc -l
Eaton-66781
rpr...@glacon2:~> upsc -L `upsc -l`
Error: No such host

The "-l" and "-L" options can be considered the "short" and "long" versions of the "list UPSes" option (where the long version also shows the description from ups.conf).

If I understand correctly, your second command line should be: upsc `upsc -l` (although this won't work if you add a second UPS).

and no log messages appear in /var/log/messages or /var/log/warn.

On system startup I get the following messages in /var/log/messages

 usbhid-ups[23704]: Startup successful
 upsd[23707]: listening on 127.0.0.1 port 3493
 upsd[23707]: listening on ::1 port 3493
 upsd[23707]: Connected to UPS [Eaton-66781]: usbhid-ups-Eaton-66781
 upsd[23708]: Startup successful
 upsmon[23711]: Startup successful
 upsmon[23712]: Login on UPS [eaton-66...@localhost] failed - got
                [ERR ACCESS-DENIED]

Your upsd user and password in upsmon.conf (on the MONITOR line) need to match an appropriately privileged user in upsd.users.

We're in the midst of overhauling the documentation, so if you see any formatting or factual errors on these pages, please let us know:

http://buildbot.networkupstools.org/~buildbot/docs/latest/man/upsmon.conf.html

http://buildbot.networkupstools.org/~buildbot/docs/latest/man/upsd.users.html

_______________________________________________
Nut-upsuser mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser

Reply via email to