Build precise queries to find exactly what you need
Press ESC to close
Nagios World Conference 2026: Sept. 14-17 in St. Paul, MN | Learn More
@Cipher-0
Member Since: October 19, 2012
Favorites0
Views0
Projects1
Version 2 of the script bailed on line 13 in my Opsview Core installation.
Reviewed 13 years ago
I had a similar issue to mr.o below. In the Opsview Core host, the plig-in works perfectly. In Opsview from the console, it returns this: $ /usr/local/nagios/libexec/check_domain -d mit.edu -c 14 -w 60 RETURN CODE: 3 (UNKNOWN) OUTPUT: We do not support this domain (not integrated). Sorry. ERROR: [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator [: 89: edu: unexpected operator I was unable to get it functioning.
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!