Logoj0ke.net Open Build Service > Projects > server:monitoring > check_openmanage > Changes
Sign Up | Log In

Changes of Revision 24

[-] Changed check_openmanage.changes
x
 
1
@@ -1,4 +1,11 @@
2
 -------------------------------------------------------------------
3
+Fri Jun 24 20:56:18 UTC 2011 - cs@linux-administrator.com
4
+
5
+- Update to version 3.6.8:
6
+    * Added workaround for a rare condition in which blade detection fails because the chassis IDs for the blade
7
+      and interconnect board have switched places in the BaseBoardType SNMP table.
8
+
9
+-------------------------------------------------------------------
10
 Sun May 15 16:15:45 UTC 2011 - cs@linux-administrator.com
11
 
12
 - Update to version 3.6.7:
13
[-] Changed check_openmanage.spec ^
201
 
1
@@ -1,7 +1,7 @@
2
 Summary:   A Nagios plugin to check hardware health on Dell servers
3
 Name:      check_openmanage
4
 Version:   3.6.8
5
-Release:   1%{?dist}
6
+Release:   2%{?dist}
7
 License:   GPL
8
 Group:     Applications/System
9
 BuildRoot: %{_tmppath}/%{name}-%{version}-root
10
@@ -24,14 +24,14 @@
11
 
12
 %build
13
 gzip %{name}.8
14
-mkdir -p %{buildroot}/%{_libdir}/nagios/plugins/contrib
15
+mkdir -p %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib
16
 mkdir -p %{buildroot}/%{_mandir}/man8
17
 
18
 %install
19
-install -d -m 0755 %{buildroot}/%{_libdir}/nagios/plugins/contrib
20
-install -m 0755 %{name} %{buildroot}/%{_libdir}/nagios/plugins/contrib
21
+install -d -m 0755 %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib
22
+install -m 0755 %{name} %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib
23
 install -m 0755 %{name}.8.gz %{buildroot}/%{_mandir}/man8
24
-pushd %{buildroot}/%{_libdir}/nagios/plugins/contrib
25
+pushd %{buildroot}/%{_prefix}/lib/nagios/plugins/contrib
26
 ln -s %{name} %{name}_alertlog
27
 ln -s %{name} %{name}_batteries
28
 ln -s %{name} %{name}_cpu
29
@@ -51,254 +51,10 @@
30
 
31
 %files
32
 %defattr(-, root, root, -)
33
-%{_libdir}/nagios/plugins/contrib/%{name}*
34
-%dir %{_libdir}/nagios
35
-%dir %{_libdir}/nagios/plugins
36
-%dir %{_libdir}/nagios/plugins/contrib
37
+%{_prefix}/lib/nagios/plugins/contrib/%{name}*
38
+%dir %{_prefix}/lib/nagios
39
+%dir %{_prefix}/lib/nagios/plugins
40
+%dir %{_prefix}/lib/nagios/plugins/contrib
41
 %attr(0755, root, root) %{_mandir}/man8/%{name}.8*
42
 
43
 %changelog
44
-* Tue Jun 07 2011 Carsten Schoene <cs@linux-administrator.com> - 3.6.8-1
45
-- update to version 3.6.8
46
- - Added workaround for a rare condition in which blade detection fails because the chassis IDs for the blade
47
-   and interconnect board have switched places in the BaseBoardType SNMP table.
48
-
49
-- changes in version 3.6.7
50
- - A regression wrt. non-certified drives were fixed.
51
-   The plugin failed to identify non-certified physical drives via SNMP.
52
- - Added the ability to blacklist non-certified drives with the 'pdisk_cert' blacklisting keyword.
53
-
54
-- changes in version 3.6.6
55
- - Fixed typo in help output
56
- - SD card check is now included if the parameter '--only chassis' is specified
57
- - The plugin will issue a proper warning if a physical drive is uncertified,
58
-   instead of an unspecified warning. One or more uncertified drives will make
59
-   the controller go into a non-critical (warning) state.
60
- - Slightly improved reporting of fan status
61
- - Exit with value 3 (unknown) if printing debug, help or version info.
62
-   This is considered best practice for Nagios plugins.
63
- - Workaround added for logical SAS connectors to external storage enclosures,
64
-   when using check_openmanage in local mode with OMSA 6.4.0 or later versions.
65
-   The output from omreport could contain lines that the plugin was unable to parse,
66
-   which would lead to internal errors.
67
-
68
-* Wed Feb 09 2011 Carsten Schoene <cs@linux-administrator.com> - 3.6.5-1
69
-- update to version 3.6.5
70
- - Fix counting of components when blacklisting is used. Components should be counted even if blacklisted
71
- - Added some unsupported vdisk types to the list. The OMSA MIB identifies these, but lists them as unsupported
72
- - Added option '-B' or '--show-blacklist' to show any blacklistings in the OK output
73
- - Fixed a bug for checking voltage probes, if the reading is missing via SNMP
74
- - Fixed a regression bug for a power monitoring corner case
75
-
76
-* Mon Dec 13 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.3-1
77
-- update to version 3.6.3
78
- - A few compatibility fixes for OMSA 6.4.0 were added
79
-
80
-* Thu Nov 25 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.2-1
81
-- update to version 3.6.2
82
- - Added support for IPv6 when checking via SNMP. IPv6 can be turned on with the option -6 or --ipv6.
83
-   The default is IPv4 if the option is not present.
84
- - Added support for TCP when checking vis SNMP. The option --tcp can be used to turn on TCP.
85
-   The default transport protocol is UDP if the option is not present.
86
- - The mode of operation (local or SNMP) is shown in the debug output. If SNMP is used,
87
-   the debug output will also show the SNMP protocol version, IP version and transport protocol (UDP or TCP).
88
- - Amperage probe status via SNMP is of type "probe status", not regular status. This has been fixed.
89
- - Massive overall robustness improvements to handle OMSA bugs where some information from OMSA is missing.
90
- - Memory module enumeration via SNMP changed somewhat to reflect enumeration provided by omreport.
91
-   This ensures that the plugin's output is identical in SNMP or local mode wrt. dimms IDs.
92
- - Fan enumeration via SNMP changed somewhat to reflect enumeration provided by omreport.
93
-   This ensures that the plugin's output is identical in SNMP or local mode wrt. fan IDs.
94
-
95
-* Tue Nov 02 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.1-1
96
-- update to version 3.6.1
97
- - Minor feature enhancements, Minor bugfixes
98
- - Included new check for SD cards. Newer servers such as the R710 can have SD cards installed, these should be monitored.
99
-   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".
100
- - Handle special cases where power monitoring capability is disabled due to non-redundant and/or non-instrumented power supplies.
101
- - For physical disks probed via SNMP, check that values for vendor, product ID and capacity is available before attempting to display those values.
102
- - If a physical disk is in sufficiently bad condition, the vendor field reported by OMSA may be empty.
103
-   The plugin now handles this situation without throwing an internal error.
104
-
105
-* Tue Aug 31 2010 Carsten Schoene <cs@linux-administrator.com> - 3.6.0-1
106
-- update to version 3.6.0
107
- - Major feature enhancements, Minor bugfixes
108
- - Storage is no longer allowed to be absent. If the plugin doesn't find a storage controller, it will give an alert.
109
-   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.
110
- - Added an option "--no-storage", which is equivalent to the general option "--check storage=0".
111
- - Report the system revision (if applicable) wherever the model name is printed. E.g. "PowerEdge 2950 III" instead of "PowerEdge 2950".
112
- - Small change in search path for omreport: The new location for OMSA 6.2.0 and later on Linux will be attempted first.
113
- - Small bugfix for the "--check" parameter, if the argument is a filename. The file could not contain a linebreak, this has been fixed.
114
-
115
-* Sat Jul 17 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.10-1
116
-- update to version 3.5.10
117
- - Minor feature enhancements, Minor bugfixes
118
- - If a physical disk is a hot spare, display this information in the debug output
119
- - Report the bus protocol (e.g. SAS, SATA) and media type (e.g. HDD, SDD) for physical disks in the debug output, if applicable
120
- - Minor fix for 100GB physical disks, write "100GB" instead of "99GB"
121
- - SNMP: Use new features of OMSA 6.3.0 to display occupied and total slots in storage enclosures,
122
-   if applicable. This information is not available with omreport and check_openmanage will not display this info in local mode.
123
- - SNMP: Added new processor IDs from the OMSA 6.3.0 MIBs
124
- - SNMP: Use connection tables in a proper way to determine controller and enclosure IDs,
125
-   for use with physical disks and enclosure components (fan, temp sensors etc.).
126
-   This fixes a long standing bug for servers with more than one controller, if checked via SNMP.
127
- - SNMP: Use the nexus ID as last resort to find the controller for physical disks. Workaround for older, broken OMSA versions.
128
- - SNMP: Identify enclosures (e.g. '2:0:0') properly so that the reporting with SNMP corresponds to the same report with omreport.
129
- - SNMP: added a couple of workarounds for pre-historic OMSA versions
130
-
131
-* Wed Jun 30 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.9-1
132
-- update to version 3.5.9
133
- - Minor feature enhancements, Minor bugfixes
134
- - More fine-grained reporting of temperature warnings for enclosure temperature probes.
135
- - Max/min temperature limits for enclosure temp probes are reported in the debug output
136
- - Report enclosure temperature probes that are "Inactive" as ok
137
- - Don't try to print out the reading of enclosure temperature probes if the reading doesn't exist or is not an integer
138
- - Report enclosure EMMs that are "Not Installed" as ok, instead of critical
139
- - Corrected typo in the PNP4Nagios template
140
-
141
-- changes in 3.5.8
142
- - Minor feature enhancements
143
- - Remove reporting of which controller a logical drive is "attached" to, since this information can't be reliably extracted via SNMP.
144
- - avoid collecting Lun ID via SNMP for virtual disks, we don't use it
145
- - report total memory and number of dimms in the ok output
146
- - difference in reporting if amperage probes have discrete readings
147
- - workaround for broken amperage probes
148
- - added workaround for bad temperature probes that yields no reading in SNMP mode
149
- - get OMSA version via SNMP slightly more efficiently
150
-
151
-* Sat Mar 20 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.7-1
152
-- update to version 3.5.7
153
- - Minor feature enhancements, Minor bugfixes
154
- - Added robustness for received SNMP values that are not defined in the MIB.
155
-   Instead of throwing a perl warning when this happens, the plugin will not report the undefined value.
156
- - Defined "Replacing" as a defined state for physical disks in SNMP mode,
157
-   even though this state is not defined in the MIB. It is reported as such by omreport.
158
- - Physical disk brand/model is now reported when the state of the disk is "Rebuilding" or "Replacing".
159
- - The state of a physical disk is reported in parentheses when predictive failure is detected.
160
-   It is useful to know if a disk is online, offline, spare or even failed when predictive failure is reported.
161
- - Handling of physical disk predictive failure has been improved overall.
162
- - Refactoring of the perfdata code. In conformance with the plugin development guidelines,
163
-   the UOM (unit of measure) previously reported in the perfdata output has been removed.
164
- - The -p or --perfdata option now takes an optional agrument "minimal",
165
-   which triggers shorter names for the perfomance data labels.
166
-   This shortens the output and is a workaround for systems where the amount of output exceeds the 1024 char limit of NRPE.
167
- - The PNP4Nagios template has been updated.
168
-   Users of check_openmanage and PNP4Nagios are advised to upgrade.
169
-   This version of check_openmanage needs the new template.
170
- - Lots of other small improvements and updates.
171
-
172
-* Tue Feb 23 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.6-1
173
-- update to version 3.5.6
174
- - New option --use-get_table  is added as a workaround for SNMPv3 on Windows using net-snmp.
175
-   This option will make check_openmanage use the Net::SNMP function get_table() instead of get_entries() to collect information via SNMP.
176
- - Include a blacklisting option ctrl_pdisk which takes the controller number as argument.
177
-   This blacklisting option only works with omreport and is a workaround for broken disk firmwares that contain illegal XML characters.
178
-   These characters makes openmanage barf and exit with an error. Thanks to Bas Couwenberg for a patch.
179
- - 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.
180
-   This will make check_openmanage execute faster if blacklisting is heavily used.
181
- - Option --htmlinfo now has a shorter equivalent -I
182
- - The option --short-state now has a shorter equivalent -S
183
-
184
-* Sat Jan 23 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.5-1
185
-- update to version 3.5.5
186
- - Fixed an SNMP bug where the plugin didn't handle OID indexes that were not sequential. Thanks to Gianluca Varenni for reporting.
187
- - Fixed an SNMP bug when checking old hardware such as the PE 2650 and PE 750. The controller id for physical drives were 
188
-   collected and displayed incorrectly. This release uses an additional OID to fetch this info, which would otherwise be unavailable.
189
-   Thanks to Gianluca Varenni for reporting this bug.
190
- - Should use %snmp_probestatus, not %snmp_status when checking the status of voltage probes. Thanks to Ken McKinlay for a patch.
191
- - Fix when identifying blades via SNMP with very old OMSA versions. Patch from Ken McKinlay.
192
- - Better way of finding the ID of physical drives via SNMP
193
-
194
-* Wed Jan 13 2010 Carsten Schoene <cs@linux-administrator.com> - 3.5.4-1
195
-- update to version 3.5.4
196
- - 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.
197
- - The "all" keyword in blacklisting is now case insensitive.
198
- - More fine-grained reporting in the rare case where a controller battery fails during learning and charging states.
199
- - New improved way of reporting perl warnings during execution of the plugin.
200
-
201