Changes - j0ke.net Open Build Service

Changes of Revision 24

[-] [+]	Changed	check_openmanage.changes
@@ -1,4 +1,11 @@ ------------------------------------------------------------------- +Fri Jun 24 20:56:18 UTC 2011 - cs@linux-administrator.com + +- Update to version 3.6.8: + * Added workaround for a rare condition in which blade detection fails because the chassis IDs for the blade + and interconnect board have switched places in the BaseBoardType SNMP table. + +------------------------------------------------------------------- Sun May 15 16:15:45 UTC 2011 - cs@linux-administrator.com - Update to version 3.6.7:
[-] [+]	Changed	check_openmanage.spec ^
@@ -1,7 +1,7 @@ Summary: A Nagios plugin to check hardware health on Dell servers Name: check_openmanage Version: 3.6.8 -Release: 1%{?dist} +Release: 2%{?dist} License: GPL Group: Applications/System BuildRoot: %{_tmppath}/%{name}-%{version}-root @@ -24,14 +24,14 @@ %build gzip %{name}.8 -mkdir -p %{buildroot}/%{_libdir}/nagios/plugins/contrib +mkdir -p %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib mkdir -p %{buildroot}/%{_mandir}/man8 %install -install -d -m 0755 %{buildroot}/%{_libdir}/nagios/plugins/contrib -install -m 0755 %{name} %{buildroot}/%{_libdir}/nagios/plugins/contrib +install -d -m 0755 %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib +install -m 0755 %{name} %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib install -m 0755 %{name}.8.gz %{buildroot}/%{_mandir}/man8 -pushd %{buildroot}/%{_libdir}/nagios/plugins/contrib +pushd %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib ln -s %{name} %{name}_alertlog ln -s %{name} %{name}_batteries ln -s %{name} %{name}_cpu @@ -51,254 +51,10 @@ %files %defattr(-, root, root, -) -%{_libdir}/nagios/plugins/contrib/%{name}* -%dir %{_libdir}/nagios -%dir %{_libdir}/nagios/plugins -%dir %{_libdir}/nagios/plugins/contrib +%{_prefix}/lib/nagios/plugins/contrib/%{name}* +%dir %{_prefix}/lib/nagios +%dir %{_prefix}/lib/nagios/plugins +%dir %{_prefix}/lib/nagios/plugins/contrib %attr(0755, root, root) %{_mandir}/man8/%{name}.8* %changelog -* Tue Jun 07 2011 Carsten Schoene <cs@linux-administrator.com> - 3.6.8-1 -- update to version 3.6.8 - - Added workaround for a rare condition in which blade detection fails because the chassis IDs for the blade - and interconnect board have switched places in the BaseBoardType SNMP table. - -- changes in version 3.6.7 - - A regression wrt. non-certified drives were fixed. - The plugin failed to identify non-certified physical drives via SNMP. - - Added the ability to blacklist non-certified drives with the 'pdisk_cert' blacklisting keyword. - -- changes in version 3.6.6 - - Fixed typo in help output - - SD card check is now included if the parameter '--only chassis' is specified - - The plugin will issue a proper warning if a physical drive is uncertified, - instead of an unspecified warning. One or more uncertified drives will make - the controller go into a non-critical (warning) state. - - Slightly improved reporting of fan status - - Exit with value 3 (unknown) if printing debug, help or version info. - This is considered best practice for Nagios plugins. - - Workaround added for logical SAS connectors to external storage enclosures, - when using check_openmanage in local mode with OMSA 6.4.0 or later versions. - The output from omreport could contain lines that the plugin was unable to parse, - which would lead to internal errors. - -* Wed Feb 09 2011 Carsten Schoene <cs@linux-administrator.com> - 3.6.5-1 -- update to version 3.6.5 - - Fix counting of components when blacklisting is used. Components should be counted even if blacklisted - - Added some unsupported vdisk types to the list. The OMSA MIB identifies these, but lists them as unsupported - - Added option '-B' or '--show-blacklist' to show any blacklistings in the OK output - - Fixed a bug for checking voltage probes, if the reading is missing via SNMP - - Fixed a regression bug for a power monitoring corner case - -* Mon Dec 13 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.3-1 -- update to version 3.6.3 - - A few compatibility fixes for OMSA 6.4.0 were added - -* Thu Nov 25 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.2-1 -- update to version 3.6.2 - - Added support for IPv6 when checking via SNMP. IPv6 can be turned on with the option -6 or --ipv6. - The default is IPv4 if the option is not present. - - Added support for TCP when checking vis SNMP. The option --tcp can be used to turn on TCP. - The default transport protocol is UDP if the option is not present. - - The mode of operation (local or SNMP) is shown in the debug output. If SNMP is used, - the debug output will also show the SNMP protocol version, IP version and transport protocol (UDP or TCP). - - Amperage probe status via SNMP is of type "probe status", not regular status. This has been fixed. - - Massive overall robustness improvements to handle OMSA bugs where some information from OMSA is missing. - - Memory module enumeration via SNMP changed somewhat to reflect enumeration provided by omreport. - This ensures that the plugin's output is identical in SNMP or local mode wrt. dimms IDs. - - Fan enumeration via SNMP changed somewhat to reflect enumeration provided by omreport. - This ensures that the plugin's output is identical in SNMP or local mode wrt. fan IDs. - -* Tue Nov 02 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.1-1 -- update to version 3.6.1 - - Minor feature enhancements, Minor bugfixes - - Included new check for SD cards. Newer servers such as the R710 can have SD cards installed, these should be monitored. - The SD card check is on by default. A new blacklisting keyword "sd" has been added. The SD card check can be turned off with "--check sdcard=0". - - Handle special cases where power monitoring capability is disabled due to non-redundant and/or non-instrumented power supplies. - - For physical disks probed via SNMP, check that values for vendor, product ID and capacity is available before attempting to display those values. - - If a physical disk is in sufficiently bad condition, the vendor field reported by OMSA may be empty. - The plugin now handles this situation without throwing an internal error. - -* Tue Aug 31 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.0-1 -- update to version 3.6.0 - - Major feature enhancements, Minor bugfixes - - Storage is no longer allowed to be absent. If the plugin doesn't find a storage controller, it will give an alert. - For diskless systems or servers without a Dell controller that OMSA recognizes you will now have to specify "--no-storage" or "--check storage=0" to work around this. - - Added an option "--no-storage", which is equivalent to the general option "--check storage=0". - - Report the system revision (if applicable) wherever the model name is printed. E.g. "PowerEdge 2950 III" instead of "PowerEdge 2950". - - Small change in search path for omreport: The new location for OMSA 6.2.0 and later on Linux will be attempted first. - - Small bugfix for the "--check" parameter, if the argument is a filename. The file could not contain a linebreak, this has been fixed. - -* Sat Jul 17 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.10-1 -- update to version 3.5.10 - - Minor feature enhancements, Minor bugfixes - - If a physical disk is a hot spare, display this information in the debug output - - Report the bus protocol (e.g. SAS, SATA) and media type (e.g. HDD, SDD) for physical disks in the debug output, if applicable - - Minor fix for 100GB physical disks, write "100GB" instead of "99GB" - - SNMP: Use new features of OMSA 6.3.0 to display occupied and total slots in storage enclosures, - if applicable. This information is not available with omreport and check_openmanage will not display this info in local mode. - - SNMP: Added new processor IDs from the OMSA 6.3.0 MIBs - - SNMP: Use connection tables in a proper way to determine controller and enclosure IDs, - for use with physical disks and enclosure components (fan, temp sensors etc.). - This fixes a long standing bug for servers with more than one controller, if checked via SNMP. - - SNMP: Use the nexus ID as last resort to find the controller for physical disks. Workaround for older, broken OMSA versions. - - SNMP: Identify enclosures (e.g. '2:0:0') properly so that the reporting with SNMP corresponds to the same report with omreport. - - SNMP: added a couple of workarounds for pre-historic OMSA versions - -* Wed Jun 30 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.9-1 -- update to version 3.5.9 - - Minor feature enhancements, Minor bugfixes - - More fine-grained reporting of temperature warnings for enclosure temperature probes. - - Max/min temperature limits for enclosure temp probes are reported in the debug output - - Report enclosure temperature probes that are "Inactive" as ok - - Don't try to print out the reading of enclosure temperature probes if the reading doesn't exist or is not an integer - - Report enclosure EMMs that are "Not Installed" as ok, instead of critical - - Corrected typo in the PNP4Nagios template - -- changes in 3.5.8 - - Minor feature enhancements - - Remove reporting of which controller a logical drive is "attached" to, since this information can't be reliably extracted via SNMP. - - avoid collecting Lun ID via SNMP for virtual disks, we don't use it - - report total memory and number of dimms in the ok output - - difference in reporting if amperage probes have discrete readings - - workaround for broken amperage probes - - added workaround for bad temperature probes that yields no reading in SNMP mode - - get OMSA version via SNMP slightly more efficiently - -* Sat Mar 20 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.7-1 -- update to version 3.5.7 - - Minor feature enhancements, Minor bugfixes - - Added robustness for received SNMP values that are not defined in the MIB. - Instead of throwing a perl warning when this happens, the plugin will not report the undefined value. - - Defined "Replacing" as a defined state for physical disks in SNMP mode, - even though this state is not defined in the MIB. It is reported as such by omreport. - - Physical disk brand/model is now reported when the state of the disk is "Rebuilding" or "Replacing". - - The state of a physical disk is reported in parentheses when predictive failure is detected. - It is useful to know if a disk is online, offline, spare or even failed when predictive failure is reported. - - Handling of physical disk predictive failure has been improved overall. - - Refactoring of the perfdata code. In conformance with the plugin development guidelines, - the UOM (unit of measure) previously reported in the perfdata output has been removed. - - The -p or --perfdata option now takes an optional agrument "minimal", - which triggers shorter names for the perfomance data labels. - This shortens the output and is a workaround for systems where the amount of output exceeds the 1024 char limit of NRPE. - - The PNP4Nagios template has been updated. - Users of check_openmanage and PNP4Nagios are advised to upgrade. - This version of check_openmanage needs the new template. - - Lots of other small improvements and updates. - -* Tue Feb 23 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.6-1 -- update to version 3.5.6 - - New option --use-get_table is added as a workaround for SNMPv3 on Windows using net-snmp. - This option will make check_openmanage use the Net::SNMP function get_table() instead of get_entries() to collect information via SNMP. - - Include a blacklisting option ctrl_pdisk which takes the controller number as argument. - This blacklisting option only works with omreport and is a workaround for broken disk firmwares that contain illegal XML characters. - These characters makes openmanage barf and exit with an error. Thanks to Bas Couwenberg for a patch. - - If the blacklisting keyword "all" is supplied for a component type, that component type is not checked at all, i.e. the commands are never executed. - This will make check_openmanage execute faster if blacklisting is heavily used. - - Option --htmlinfo now has a shorter equivalent -I - - The option --short-state now has a shorter equivalent -S - -* Sat Jan 23 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.5-1 -- update to version 3.5.5 - - Fixed an SNMP bug where the plugin didn't handle OID indexes that were not sequential. Thanks to Gianluca Varenni for reporting. - - Fixed an SNMP bug when checking old hardware such as the PE 2650 and PE 750. The controller id for physical drives were - collected and displayed incorrectly. This release uses an additional OID to fetch this info, which would otherwise be unavailable. - Thanks to Gianluca Varenni for reporting this bug. - - Should use %snmp_probestatus, not %snmp_status when checking the status of voltage probes. Thanks to Ken McKinlay for a patch. - - Fix when identifying blades via SNMP with very old OMSA versions. Patch from Ken McKinlay. - - Better way of finding the ID of physical drives via SNMP - -* Wed Jan 13 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.4-1 -- update to version 3.5.4 - - Added support for storport driver version for controllers, only applicable on servers running Windows. A new blacklisting keyword for suppressing storport driver messages was added. - - The "all" keyword in blacklisting is now case insensitive. - - More fine-grained reporting in the rare case where a controller battery fails during learning and charging states. - - New improved way of reporting perl warnings during execution of the plugin. -