Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 87999

Summary: lsraid produces no output
Product: [Retired] Red Hat Linux Reporter: kitchen_506
Component: raidtoolsAssignee: Doug Ledford <dledford>
Status: CLOSED WONTFIX QA Contact: David Lawrence <dkl>
Severity: medium Docs Contact:
Priority: medium    
Version: 7.3   
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2004-11-27 23:27:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Description kitchen_506 2003-04-04 14:47:58 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows 98; You trust this)

Description of problem:
I've got nagios installed and a cron job that regularly checks on the status of
the raiding on our systems.  On one system, lsraid occasionally produces no
output.  It's got multiple raid partitions and they all "go empty" from time to
time on this one system.  Then they mystically come back.

System usage is as normal, and I've never caught lsraid misbehaving by hand.

The other four boxes using this exact same procedure have never faulted. 

Note there is a hardware difference between failing box and the other four. 

The procedure was working for a long time on the box in question.  It *may* be
that an update to the system triggered it,but only after sufficient time had
passed for me not to see a direct correlation.

Version-Release number of selected component (if applicable):


How reproducible:
Sometimes

Steps to Reproduce:
Heh... cyclical running of lsraid -A -s /dev/mdX trips nagios.  output logging
during the test shows no output.  It's not everytime.
    

Actual Results:  sometimes good, sometimes no output.

Expected Results:  output

Additional info: