Koozali.org: home of the SME Server

Obsolete Releases => SME Server 9.x => Topic started by: Brave Dave on March 16, 2016, 01:18:55 AM

Title: Nut login Failed
Post by: Brave Dave on March 16, 2016, 01:18:55 AM

I've just installed SME 9 on a new server with a UPS

This appears in the log straight after the ups runs

Quote

upsmon[27707]: Login on UPS [UPS@localhost] failed - got [ERR ACCESS-DENIED]

but if I kill upsmon and run it with debug (upsmon -DDDDDDDDDDDDD)
if delivers that error, then continues and shows it is connected and monitoring

I think it's just log noise - possibly as upsmon tries to connect to IPv6

I'm just looking for someone to agree - maybe it's a note for the HowTo

Title: Re: Nut login Failed
Post by: Michail Pappas on March 18, 2016, 07:33:22 AM

Not an expert here, but a -DDDDDDDDDDD log, plus a config show nut output might help.

Title: Re: Nut login Failed
Post by: Brave Dave on March 18, 2016, 07:59:45 AM

Yes - sure - this is output, you can see it starts working, just delivers the message then carries on.

The /etc/ups/* files are as expected

Quote

config show nut
nut=service
    AdminPass= 47781907561333
    AdminUser=disabled
    MasterPass=<masterpass>
    Model=usbhid-ups
    SlavePass=<slavepass>
    access=localhost
    status=enabled

Quote

upsmon -DDDDDDDDDDDDDDDD
Network UPS Tools upsmon 2.6.5
kill: No such process
   0.000000     UPS: UPS@localhost (master) (power value 1)
   0.000053     Using power down flag file /etc/killpower
   0.000072     debug level is '16'
   0.041846     Trying to connect to UPS [UPS@localhost]
   0.042524     Login on UPS [UPS@localhost] failed - got [ERR ACCESS-DENIED]
   0.042553     Current power value: 1
   0.042557     Minimum power value: 1
   5.042722     pollups: UPS@localhost
   5.042751     get_var: UPS@localhost / status
   5.042954     parse_status: [OL]
   5.042970     parsing: [OL]
   5.042975     ups_on_line: UPS@localhost (first time)
   5.042980     Current power value: 1
   5.042984     Minimum power value: 1
  10.043100     pollups: UPS@localhost
  10.043130     get_var: UPS@localhost / status
  10.043345     parse_status: [OL]
  10.043371     parsing: [OL]
  10.043376     ups_on_line: UPS@localhost (no change)
  10.043382     Current power value: 1
  10.043387     Minimum power value: 1
^C  12.294316   Signal 2: exiting
  12.294344     Dropping connection to UPS [UPS@localhost]

It all seems to work as expected, if I turn power off to ups it sees the outage and monitors

Quote

Mar 18 16:57:10 k upsmon[6227]: UPS UPS@localhost on battery
Mar 18 16:57:10 k wall[6799]: wall: user nut broadcasted 1 lines (30 chars)
Mar 18 16:57:25 k upsmon[6227]: UPS UPS@localhost on line power
Mar 18 16:57:25 k wall[6831]: wall: user nut broadcasted 1 lines (33 chars)

Title: Re: Nut login Failed
Post by: Michail Pappas on March 18, 2016, 09:59:59 AM

Most likely it is indeed due to ipv6, see also https://forums.linuxmint.com/viewtopic.php?t=97487

IIRC, it is upsd that is listening for incoming requests. What's the content of your:

* /etc/ups/* (remove confidential stuff if you want to)
* /etc/hosts.allow  (remove confidential stuff if you want to)
* /etc/hosts.deny  (remove confidential stuff if you want to)

Title: Re: Nut login Failed
Post by: byte on March 18, 2016, 10:30:14 AM

Quote from: Michail Pappas on March 18, 2016, 09:59:59 AM

Most likely it is indeed due to ipv6, see also https://forums.linuxmint.com/viewtopic.php?t=97487

Michail, please open a bug ticket with your findings as I've seen various threads mention this log noise due to ipv6 too.

The dev team maybe able to suppress this log noise or advise otherwise.

Thanks,

Title: Re: Nut login Failed
Post by: Michail Pappas on March 18, 2016, 10:51:59 AM

I am not the one with the issue. Brave Dave should probably open a ticket.

EDIT: Missed the not above :D

Title: Re: Nut login Failed
Post by: Brave Dave on March 18, 2016, 11:03:56 AM

Thanks for confirming my thoughts Michail

Title: Re: Nut login Failed
Post by: byte on March 18, 2016, 02:49:12 PM

Quote from: Michail Pappas on March 18, 2016, 10:51:59 AM

I am not the one with the issue. Brave Dave should probably open a ticket.

EDIT: Missed the not above :D

:) - Thanks, Brave Dave....are you feeling brave enough to open a bug ticket for this please  :lol: