[Nut-upsuser] upsmon not authenticating (I've read the FAQ)

[Steve Ziuchkovski]

An update -

I ran a test by unplugging my UPS and letting it run down. The system shut
down as it should.

However, the /etc/killpower file was not created, and the UPS did not shut
off power as it should from the shutdown scripts. This may be because the
command to kill the output of the UPS isn't available, or that by not being
able to log in as master prevents this. The permissions on the hiddev0 file
are correct (I update them each boot). Running /usr/local/ups/bin/upscmd -l 
apc at localhost produces no
output.

Still have the problem with the syslog, too...

Steve
----- Original Message ----- 
From: "Steve Ziuchkovski" <smz at ziuchkovski.com>
To: <nut-upsuser at lists.alioth.debian.org>
Sent: Saturday, March 11, 2006 11:19 PM
Subject: Unable to get upsmon to connect to upsd


> Hello!
>
> I bought an APC Back-UPS XS, which has a USB interface. I've installed nut
> version 2.0.3, and configured with --with-user=nut --with-drivers=hidups.
> Configure ran great, make worked, installed great. I followed the
> instructions in INSTALL by creating a user "nut" in group "nut". The
> configuration files are owned by root.nut, mode 640. I have only one
> machine hooked to the UPS, and it's it's own master. I'm running Fedora
> Core 4.
>
> I'm able to load the driver and start upsd, and upsc allows me to
> successfully get status info from the UPS. Looks good!
>
> However, I have two problems. The major one is that upsmon will load, but
> the following appears in my syslog:
>
> ------------------------
> Mar 11 23:14:22 localhost upsmon[3256]: Startup successful
> Mar 11 23:14:22 localhost upsd[2971]: Connection from 127.0.0.1
> Mar 11 23:14:22 localhost upsd[2971]: Client apcuser at 127.0.0.1 logged into
> UPS [apc]
> Mar 11 23:14:22 localhost upsmon[3257]: Master privileges unavailable on
> UPS [apc at localhost]
> Mar 11 23:14:22 localhost upsmon[3257]: Reason: Access denied
> ------------------------
>
> I've checked and double checked my config files, and the username/password
> are right.
>
> Here's my upsd.conf:
>
> ------------------------
> ACL all 0.0.0.0/0
> ACL localhost 127.0.0.1/32
>
> ACCEPT localhost
> REJECT all
> ------------------------
>
> Here's upsd.users:
>
> ------------------------
> [apcuser]
>        password = removed
>        allowfrom localhost
>        upsmon master
> ------------------------
>
> Here's upsmon.conf:
>
> ------------------------
> POWERDOWNFLAG /etc/killpower
> MONITOR apc at localhost 1 apcuser removed master
> SHUTDOWNCMD "/sbin/shutdown -h now"
>
> ------------------------
>
> Any ideas?
>
>
> Also - I get the following every 4 seconds or so in my syslog:
>
> ------------------------
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x8500d1 (1)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840068 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x850043 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840073 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x85004b (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840065 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x8500db (0)
> Mar 11 23:17:50 localhost hidups[2968]: Ignoring x86 page event 0xff860080
> (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x8500d1 (1)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840068 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x850043 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840073 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x85004b (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840065 (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x8500db (0)
> Mar 11 23:17:50 localhost hidups[2968]: Ignoring x86 page event 0xff860080
> (0)
> Mar 11 23:17:50 localhost hidups[2968]: Unhandled event: 0x840058 (6)
> ------------------------
>
> I guess this is from USB messages that just aren't being handled due to
> the experimental driver. How do I turn this stuff off?
>
> Thanks!
>
> Steve Ziuchkovski
>