On Thu, Sep 30, 2010 at 10:16 AM, Roger Price <[email protected]> wrote: > On Thu, 30 Sep 2010, Charles Lepple wrote: [...] >>> On system startup I get the following messages in /var/log/messages >>> ... >>> 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. > > My upsmon.conf MONITOR line is > > MONITOR eaton-66...@localhost 1 upsmaster sekret master > > and upsd.users says > > [upsmaster] > password = sekret > upsmon master > > so the user and password match. Is this enough to be "appropriately > privileged", or do I need more?
My mistake, that part looks good. It looks like the same "ERR ACCESS-DENIED" code is returned for a problem with upsd.users/upsmon.conf versus a TCP wrappers match failure. What if you run 'tcpdchk' against your hosts.allow file? I am not terribly familiar with TCP wrappers, and your configuration looked reasonable, but it's possible that there is a problem with the syntax. -- - Charles Lepple _______________________________________________ Nut-upsuser mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/nut-upsuser
