Hi Charles,
Not getting error re login for upsmon now.
When turning off power I am getting the following failed error.
Sep 18 10:35:24 solus upsmon[685]:*UPS defender@localhost on battery*
Sep 18 10:35:32 solus upssched[1261]:*Failed to connect to parent and failed to create parent: No such file
or directory*
Sep 18 10:35:44 solus upsmon[685]:*UPS defender@localhost on line power*
Is this another permission issue.
upssched.conf root:nut 640
CMDSCRIPT /usr/etc/upsShutdownNow.sh
# mandatory fields that must be set before AT commands
PIPEFN /var/run/nut/upssched.pipe
LOCKFN /var/run/nut/upssched.lock
# the timers, here 120 sec after the ONBATT (ups on battery) event
AT ONBATT * START-TIMER onbatt 120
# cancel the countdown if power is back
AT ONLINE * CANCEL-TIMER onbatt
Note I didn't have /var/run/nut folder so created one.
On 17/09/17 22:12, Charles Lepple wrote:
On Sep 17, 2017, at 3:26 AM, MTS <mts5...@bigpond.com> wrote:
0.003814 Trying to connect to UPS [defender@localhost]
0.004327 Login on UPS [defender@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.
_______________________________________________
Nut-upsuser mailing list
Nut-upsuser@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/nut-upsuser
