[Nagiosplug-devel] [ nagiosplug-Bugs-3049988 ] check_linux_raid fails on RAID0 and linear volumes

[SourceForge.net]

Bugs item #3049988, was opened at 2010-08-20 22:11
Message generated for change (Tracker Item Submitted) made by 
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3049988&group_id=29880

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: General plugin execution
Group: Release (specify)
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: clint-fewbar ()
Assigned to: Nobody/Anonymous (nobody)
Summary: check_linux_raid fails on RAID0 and linear volumes

Initial Comment:
Forwarding this bug from an Ubuntu bug report, seen here:

https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/621380

When the plugin is run with no arguments and there are RAID0 or linear volumes, it displays errors like this:

ch at vmserver1:~$ cat /proc/mdstat
Personalities : [linear] [multipath] [raid0] [raid1] [raid6] [raid5]
[raid4] [raid10]
md2 : active raid0 sdf1[1] sde1[0]
      1952443392 blocks 64k chunks

md0 : active raid1 sda1[0] sdd1[3] sdc1[2] sdb1[1]
      995904 blocks [4/4] [UUUU]

md1 : active raid5 sdc2[2] sdd2[3] sda2[0] sdb2[1]
      1460549184 blocks level 5, 64k chunk, algorithm 2 [4/4] [UUUU]

ch at vmserver1:~$ sudo /usr/lib/nagios/plugins/check_linux_raid
Use of uninitialized value within %status in pattern match (m//) at
/usr/lib/nagios/plugins/check_linux_raid line 82, <MDSTAT> line 11.
Use of uninitialized value within %status in pattern match (m//) at
/usr/lib/nagios/plugins/check_linux_raid line 91, <MDSTAT> line 11.
OK md0 status=[UUUU]. md1 status=[UUUU]. md2 active with no status
information.

The patch located here solves the issue:

https://bugs.launchpad.net/ubuntu/+source/nagios-plugins/+bug/621380/+attachment/1505517/+files/patch

I have not evaluated whether it has any adverse effects, though it seems like it shouldn't.

Note that this was also reported in Debian, here:

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579049


----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=397597&aid=3049988&group_id=29880