Bug 460140 - sosreport doesn't capture "dmesg" output
sosreport doesn't capture "dmesg" output
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: sos (Show other bugs)
All Linux
medium Severity medium
: rc
: ---
Assigned To: Adam Stokes
Depends On:
  Show dependency treegraph
Reported: 2008-08-26 09:35 EDT by Anders
Modified: 2009-09-02 03:30 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-09-02 03:30:03 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Anders 2008-08-26 09:35:23 EDT
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):

How reproducible:

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 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 03:30:03 EDT
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.


Note You need to log in before you can comment on or make changes to this bug.