[Nut-upsuser] building on Solus

MTS mts5204 at bigpond.com
Mon Sep 18 01:22:40 UTC 2017

Hi Charles,

I finally succeeded in getting a successful shutdown. From upssched.conf:
# mandatory fields that must be set before AT commands
PIPEFN /var/run/nut/upssched.pipe
LOCKFN /var/run/nut/upssched.lock

I had to create /var/run/nut directory. Owned by ups, group nut.
Then it all worked fine.

Seems the only thing left to do is to try and follow the readme 
instructions in the scripts folder for the nut monitor.
It didn't install this, unlike the Linux Mint install which did.

On 17/09/17 22:12, Charles Lepple wrote:
> On Sep 17, 2017, at 3:26 AM, MTS <mts5204 at bigpond.com> wrote:
>>     0.003814    Trying to connect to UPS [defender at localhost]
>>     0.004327    Login on UPS [defender at localhost] failed - got [ERR ACCESS-DENIED]
> The MONITOR line in upsmon.conf needs to match a NUT user in upsd.users.
> http://networkupstools.org/docs/man/upsmon.conf.html
> http://networkupstools.org/docs/man/upsd.users.html
> Looks like you are using this as a master system (UPS is directly connected, and upsmon shuts down that system), so the appropriate NUT user needs "upsmon master" in upsd.users.
> Note that the NUT users listed in upsd.users do not need to correspond to actual system users - think of them more as roles. If you add a slave system that connects over the network, you might not want it to be able to shut down the master, so you would use a different NUT username with "upsmon slave" privileges.

More information about the Nut-upsuser mailing list