Search Exchange
Search All Sites
Nagios Live Webinars
Let our experts show you how Nagios can help your organization.Login
New ListingsDirectory Tree
check_ups_alarm
Meet The New Nagios Core Services Platform
Built on over 25 years of monitoring experience, the Nagios Core Services Platform provides insightful monitoring dashboards, time-saving monitoring wizards, and unmatched ease of use. Use it for free indefinitely.
Monitoring Made Magically Better
- Nagios Core on Overdrive
- Powerful Monitoring Dashboards
- Time-Saving Configuration Wizards
- Open Source Powered Monitoring On Steroids
- And So Much More!
Checks the following properties of an NPower UPS:
Battery Status - The current status of the battery
Battery Minutes Remaining - How long it can run on batteries
Battery Runtime (Seconds) - How long the UPS has been running on batteries
Battery Temperature - The temperature of the battery
Input Line Bads - The number of times the utility power has gone away
Output Load Percent - The load on the UPS
Alarm Count - Current number of alarms present
Battery Status - The current status of the battery
Battery Minutes Remaining - How long it can run on batteries
Battery Runtime (Seconds) - How long the UPS has been running on batteries
Battery Temperature - The temperature of the battery
Input Line Bads - The number of times the utility power has gone away
Output Load Percent - The load on the UPS
Alarm Count - Current number of alarms present
Reviews (3)
Great plugin
If you get the following error:
Insecure dependency in printf while running with -T switch at ./check_ups_alarm.pl line 266.
Edit the script and on Line 1 change
#!/usr/bin/perl -wT
to
#!/usr/bin/perl
Then above
use scrict;
Add the following line
use warnings;
use scrict;
This corrects the error and I can now run all of the checks.
Thanks
Chris
If you get the following error:
Insecure dependency in printf while running with -T switch at ./check_ups_alarm.pl line 266.
Edit the script and on Line 1 change
#!/usr/bin/perl -wT
to
#!/usr/bin/perl
Then above
use scrict;
Add the following line
use warnings;
use scrict;
This corrects the error and I can now run all of the checks.
Thanks
Chris
byCipher-0, March 14, 2013
I use it with Opsview Core (latest release as of this writing). I ended up removing taint checking as I was getting the script bailing with a failed check on line 268.
If you're getting "255 out of bounds" as a result check the following:
* Your Nagios console IP address has been added to the SNMP v1 access list of the UPS unit; you can add it as a FQDN but that means DNS has to be configured on each UPS.
* The SNMP community name is right. I created a new attribute in Opsview for this.
* When you've changed the unit settings, go through the restart process on the UPS. My results were inconsistent until I did.
Two of the checks I wasn't able to get working:
batteryTemperature - not supported on our units. Oops.
outputLoadPercent - the OID appears to be incorrect. I'm still tracking it down.
Overall, good work!
If you're getting "255 out of bounds" as a result check the following:
* Your Nagios console IP address has been added to the SNMP v1 access list of the UPS unit; you can add it as a FQDN but that means DNS has to be configured on each UPS.
* The SNMP community name is right. I created a new attribute in Opsview for this.
* When you've changed the unit settings, go through the restart process on the UPS. My results were inconsistent until I did.
Two of the checks I wasn't able to get working:
batteryTemperature - not supported on our units. Oops.
outputLoadPercent - the OID appears to be incorrect. I'm still tracking it down.
Overall, good work!
bythechinchman, January 29, 2013
Has anyone been able to get this to work through the app. I'm able to get this to work fine through the command line, but when running through nagios i get Return Code 255 Out of Bounds. When i run with echo $ at the end on command line i get the same output as if i don't put it there.
Any help would be greatly appreciated
Any help would be greatly appreciated
