I hope that this is an appropriate post for this group. Please let me know if it should go elsewhere.
I am running NUT on RaspberryPi 3B+ [RPi] units using Buster. The NUT version is 2.7.4. I have two UPS's in two different physical locations. Each is attached to its own RPi. Both UPS's are APCs but of different models. I have one APC attached to an RPi w/NUT configured as a server with the following script entries: --------------------------------- *nut.confMODE=netserverups.conf[APCES850Server] driver=usbhid-ups port=auto desc=”APC ES850” serial=4B2037P49872 pollinterval=15 vendorid=051d[APCES750Client] driver=usbhid-ups port=auto desc=”APC ES750” serial=3B0907X16989 pollinterval=15 vendorid=051dupsmon.confMONITOR [email protected] <[email protected]> 1 upsmon LASTPASS masterMONITOR [email protected] <[email protected]> 1 upsremote LASTPASS slave* Usual entries for upsd.conf and upsd.users. ------------------------------- The other APC is attached to a different RPi w/NUT configured as a client with the following script entries: ------------------------------- *nut.confMODE=netclientups.conf[no entries]upsmon.confMONITOR [email protected] <[email protected]> 1 upsmon LASTPASS masterMONITOR [email protected] <[email protected]> 1 upsremote LASTPASS slave* ------------------------------ The server works fine. The client will not connect, throwing a "UPS [email protected] is unavailable"error. [Note that LASTPASS is just a placeholder for this note indicating the password source.] The passwords for upsmon and upsremote are the same. I have this feeling that there is something that I am not understanding about the server/client relationship. Suggestions would be very welcome. Thank you so much. -- Bill Cole Fredericksburg, VA
_______________________________________________ Nut-upsuser mailing list [email protected] https://alioth-lists.debian.net/cgi-bin/mailman/listinfo/nut-upsuser
