On Mon, 3 Apr 2017, Spike wrote:
I'll see if I can implement it some time soon.
Hi Spike, I tested the heartbeat proposal on openSUSE 13.1 and 42.2, and
made some changes so that it would work. I wrote out some documentation
which includes the required changes, which you will find at
http:
thank you all for your input. Roger, I'm a nut noob and only marginally
understand the implementation (from your other email), but I really like
the idea of a heartbeat and design wise it makes a lot of sense. I'll see
if I can implement it some time soon.
thank you,
Spike
On Sat, Apr 1, 2017 at
On Sat, 1 Apr 2017, Stuart Gathman wrote:
On 04/01/2017 03:14 PM, Dan Craciun wrote:
On my Nagios monitoring system I use check_nut_plus (that in turn
calls upsc) to monitor the status (ups.status), load (ups.load),
battery charge (battery.charge) and runtime (battery.runtime).
If these return
On 04/01/2017 03:14 PM, Dan Craciun wrote:
> On my Nagios monitoring system I use check_nut_plus (that in turn
> calls upsc) to monitor the status (ups.status), load (ups.load),
> battery charge (battery.charge) and runtime (battery.runtime).
>
> If these return "unknown", it means upsd is no longe
On my Nagios monitoring system I use check_nut_plus (that in turn calls
upsc) to monitor the status (ups.status), load (ups.load), battery
charge (battery.charge) and runtime (battery.runtime).
If these return "unknown", it means upsd is no longer monitoring the
UPS. As long as you get data, upsd
Dear all,
I got nut going on one machine as standalone and on another 2 as
master/slave and would like to add some checks to nagios to make sure that
things are in order.
Most of the checks I've seen out there use upsc to check the ups. This is a
step forward compared to no monitoring, however as
6 matches
Mail list logo
