On Wed, 9 Feb 2022, William Cole via Nut-upsuser wrote:
In your last post you had suggested that I run the NUT-report bash script that
you had posted to your web site.
########### /etc/nut/ups.conf ###########
maxretry = 3
[1LRES850]
driver=usbhid-ups
port=auto
desc="LR APC ES850"
serial=4B2037P49871
pollinterval=15
vendorid=051d
########### /etc/nut/upsd.conf ###########
LISTEN 192.168.1.235 3493
LISTEN 192.168.1.236 3493
As Matus Uhlar said, you dont need these if you also listen to 0.0.0.0.
LISTEN 0.0.0.0 3493
MAXAGE 25
########### /etc/nut/upsd.users ###########
[admin]
password = $
actions = SET
instcmds = ALL
[upsmon]
password = $
upsmon master
[upsremote]
****u**** word = $
upsmon slave
########### /etc/nut/upsmon.conf ###########
MONITOR [email protected] 1 upsmon $ master
MONITOR [email protected] 1 upsremote $ slave
I assume that you ran the nut-report script on 192.168.1.235. You reported that
upsmon on "235" cannot contact upsd on "235". Can you access upsd on "235"
using a command such as "upsc 1LRES8500" ?
If so, what happens if you run command "upsc [email protected]" on "235"?
Roger
_______________________________________________
Nut-upsuser mailing list
[email protected]
https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
