This updated sos package provides fixes for the following bugs:
• sosreport became unresponsive in a virtualized environment if the xend daemon had not been
started.
(BZ#497506
1.208.2. RHBA-2009:1418: bugfix and enhancement update
Sos is a set of tools that gathers information about system hardware and configuration. The
information can then be used for diagnostic purposes and debugging. Sos is commonly used to help
support technicians and developers.
This updated package provides the following bug fixes and enhancements.
* The French translation of sos would prompt the user Voulez vous continuer (y/n)? but
would ignore y as an answer and would only accept o or n. The prompt has now been corrected to
reflect the actual options.
* Previously, sos could handle only default, conventional python paths. When run on systems with
unconventional python paths, sos would crash. Sosreport is now tolerant of unconventional python
paths and will not crash when it encounters them.
* For security reasons, sos sanitizes passwords that would otherwise appear in its report, including
the shared secret (bindpw) from /etc/ldap.conf. Previously, if /etc/openldap/ldap.conf
were symbolically linked to /etc/ldap.conf, sos would sanitize the bindpw in ldap.conf itself.
Now, sos only sanitises the bindpw that is included in its report.
* Although sos is designed to run unattended if required to do so, recent versions still prompted users
for input during diagnose method tests if the test found any problem. This prompt meant that sos was
unable to run unattended. Furthermore, when it did not receive a reply to the prompt, sos would crash.
Sosreport now automatically chooses the option to continue instead of prompting the user whether to
continue or not, and can therefore run unattended.
* Previously, faulty logic in rh-upload-core prevented it from uploading a core if the quiet flag were not
set. Additionally, the destination directory was incorrectly specified as dropbox.redhat.com. Now,
rh-upload-core can upload a core regardless of the status of the quiet flag, and correctly sends the
core to dropbox.redhat.com/incoming.
* When used with the Xen plugin, sos would stop responding due to flaws in the code of the plugin. In
particular, a misnamed function would result in the plugin attempting to collect data from a Xen kernel
when xend was not running. With these flaws corrected, the Xen plugin now works correctly and does
not cause sos to stop responding.
* Sos archives its findings in a tar.bz2 file. However, neither tar nor bzip2 were listed as requirements
in the sos package. Therefore, on minimal installations that included neither of these tools, sos would
produce an empty tar.bz2 file. Sos now requires both these tools, which enable it to create its report.
1618
(BZ#503536
)
* The Xen plugin for sos was looking for the presence of fully virtualized guests by searching for int-
xen in /proc/acpi/dsdt. Due to changes in how the Xen hypervisor is implemented in Red Hat
1612
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=469365
1613
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=480302
1614
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=475190
1615
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=475991
1616
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=477042
1617
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=490186
1618
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=503536
1611
)
1612
(BZ#469365
)
(BZ#490186
RHBA-2009:1418: bugfix and enhancement update
1613
(BZ#480302
)
(BZ#475190
1615
(BZ#475991
)
1616
(BZ#477042
)
1617
)
1614
)
231
Need help?
Do you have a question about the ENTERPRISE LINUX 5.4 - TECHNICAL NOTES and is the answer not in the manual?
Questions and answers