Re: [Nut-upsuser] how do you test (nagios) that upsmon is connected?

2017-04-01 Thread Roger Price
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

Re: [Nut-upsuser] how do you test (nagios) that upsmon is connected?

2017-04-01 Thread Stuart Gathman
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

Re: [Nut-upsuser] how do you test (nagios) that upsmon is connected?

2017-04-01 Thread Dan Craciun
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

[Nut-upsuser] how do you test (nagios) that upsmon is connected?

2017-04-01 Thread Spike
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

[Nut-upsuser] usbhid-ups: Failed to open device, skipping. (Permission denied)

2017-04-01 Thread Sam Varshavchik
Having trouble configuring nut 2.7.4 on Fedora 25, with a new Tripp Lite UPS. I'm running XFCE, and XFCE's Power Manager sees the UPS just fine. lsusb gives: Bus 006 Device 002: ID 09ae:3016 Tripp Lite nut-scanner -U has no issues either: # nut-scanner -U Scanning USB bus. [nutdev1]