[Nut-upsuser] Monitoring slaves via dummy-ups

[Roger Price]

On Fri, 4 Sep 2020, Dan Langille wrote:

> I wondered how folks monitored slaves.

A NUT solution is to use a "heartbeat" generated in each slave and monitored in 
say the master or elsewhere.

> The goal: confirm the slaves have contact with the master.

On your Github site:  Goal: allow host to shutdown when needed.

These are not the same goals

In NUT, for the shutdown process, this involves upsmon in the master system 
setting state FSD in each slave's upsd.

It's internal to NUT.  What other contact do you want to check?

> In my case, I am using Nagios and the check_ups plugin. It seems to work fine 
> but being new to nut, I'm seeking confirmation that this is a sane approach.

On your Github site: Each host is monitored via the Nagios check_ups plugin.

Do you want to use NUT to manage system shutdowns on power failure?, or is 
Nagios sufficient for you?

> Running on each host is:

> [dan at slocum:~] $ ps auwwx | grep ups
> root      46270    0.0  0.0   11332    2868  -  Ss   19:49        0:00.00 
> /usr/local/sbin/upsmon localhost
> uucp      46271    0.0  0.0   11596    2896  -  S    19:49        0:00.00 
> /usr/local/sbin/upsmon localhost
> uucp      56305    0.0  0.0   11668    2952  -  Ss   20:07        1:05.11 
> /usr/local/libexec/nut/dummy-ups -a repeater
> uucp      75564    0.0  0.0   11668    2952  -  Ss   20:14        1:02.33 
> /usr/local/libexec/nut/dummy-ups -a ups02
> uucp      75566    0.0  0.0  110004    2936  -  Ss   20:14        0:02.01 
> /usr/local/sbin/upsd

Running NUT as uucp is surprising.  Do you have a user "nut"?

I suggest you set up a working NUT configuration, and then ask the question "Do 
I need Nagios for UPS management?"

Roger