[Nut-upsuser] Master Works, Slave Does Not

Charles Lepple clepple at gmail.com
Sat Nov 8 16:00:39 UTC 2014

On Nov 8, 2014, at 10:34 AM, Steve Read <sd_read at hotmail.com> wrote:

> Thank you Charles, I am hoping fiddle with that sometime today or tomorrow.
> But I have another question, when you ask me to modify various files I am confused as to weather you mean on the server, client or both?
> So in your statement:
> "Instead, you want to listen on the wildcard address, so you will want to add "LISTEN" to /etc/nut/upsd.conf. After restarting NUT, netstat should look like this:"
> I think you mean the client?

Sorry if I didn't use consistent terminology, but starting from the standard TCP client/server definitions, NUT's upsd is the server process, running on the NUT master machine, and it listens on TCP port 3493. It is configured via upsd.conf.

The NUT upsmon process runs on the master as well as the slave, and it is a TCP client to upsd. Your previous upsmon.conf files should work (assuming the passwords match that of upsd.users on the master).

Put another way, with one UPS, one master, and one or more slaves, there is only one driver and one upsd on the master host. The slaves, therefore, do not need upsd.conf or the driver configuration file ups.conf, since they connect to the upsd process running on the master, and upsd distributes that information over the network.

I think part of the confusion is that the master/slave and server/client terms are not exactly synonymous, due to the usual need for the NUT master machine to shut down itself as well as the slave.

Charles Lepple
clepple at gmail

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/nut-upsuser/attachments/20141108/5bde9d99/attachment-0001.html>

More information about the Nut-upsuser mailing list