Bug 460140

Summary: sosreport doesn't capture "dmesg" output
Product: Red Hat Enterprise Linux 5 Reporter: Sirius Rayner-Karlsson <akarlsso>
Component: sosAssignee: Adam Stokes <astokes>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 5.4CC: agk, azelinka, bmr
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-09-02 07:30:03 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sirius Rayner-Karlsson 2008-08-26 13:35:23 UTC 
Description of problem:
sosreport does not capture the output of "dmesg" at the time of running the sosreport command. Comparatively, the older commmand sysreport does capture this output.

Version-Release number of selected component (if applicable):
sos-1.7-9.2.el5-noarch

How reproducible:
100%

Steps to Reproduce:
1. run sosreport
2. unpack archive
3. look for the "dmesg" file
  
Actual results:
not found

Expected results:
found in the root folder

Additional info:
I ran a find in a recently received sosreport, and these are the files containing "dmesg" in the filename:
$ find . -name "*dmesg*"
./var/log/dmesg
./sos_commands/memory/dmesg_grep_-e_e820._-e_aperature
./sos_commands/hardware/dmesg_.bin.grep_-e_e820._-e_agp
./sos_commands/hardware/dmesg_.bin.egrep_8139cp_aacraid_acenic_ahci_aic79xx_aic7xxx_aic9
./sos_commands/x11/dmesg_grep_-e_agpgart

/var/log/dmesg is not the file I am looking for, as /var/log/dmesg is created at boot and once klogd starts, nothing more is added to this file.
Comment 8 errata-xmlrpc 2009-09-02 07:30:03 UTC 
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHBA-2009-1418.html