Red Hat ENTERPRISE LINUX 5.5 - S 2010, Руководство пользователя

Страница: 257 / 470

RHBA-2010:0201: bug fix and enhancement update
247
• the rh-upload-core script included with sos has been improved. Most significantly, the script can now
upload any file, and not just vmcores. (
BZ#523750
1986
)
• SOS reports include the name service cache daemon (nscd) configuration file found at /etc/
nscd.conf. With this update, SOS reports now also include the debug logs if nscd is running with
debugging enabled. Note: similarly to syslog, SOS limits the debug log files to 50 MiB. If nscd runs
in debug mode for extended periods (eg a week), the debug log files can be 100s of MiBs and
larger. (
BZ#536960
1987
)
• SOS now checks for the presence of Apache QPID (specifically, it checkes for qpidd, the QPID
daemon) and, if detected, collects QPID configuration, state and log information and saves it to
sos_command/broker/ in the sosreport. (
BZ#557851
1988
)
• SOS did not gather the SELinux audit log files (/var/log/audit/*). It has now been amended to gather
the last fifty entries of this log, meaning that SELinux problems can be investigated more easily.
(
BZ#443984
1989
)
• SOS did not gather sound card information, leading to prolonged support calls whilst this information
was manually collected and sent in by users. A new Python-based plug-in has been written that
collects information about soundcards via ALSA. As a result, users will not have to hunt for this
information themselves during a support call. (
BZ#478009
1990
)
• SOS was not reporting the output of the lsb_release command. If /etc/redhat-release was corrupted
or missing, it was impossible for support to confirm which version of Red Hat Enterprise Linux was
in use. lsb)release provides a useful fallback. A plug-in has been added to SOS to gather a large
amount of data provided by the lsb_release command and in associated /etc files. It also outputs
a message, informing the user if /etc/redhat-release is missing. By reporting this information, the
system version can be identified quickly and accurately, assisting in the troubleshooting process.
(
BZ#479111
1991
)
• SOS was not able to collect data relating to the Quagga routing suite if this was installed on a user's
systems. As a result, troubleshooting these systems was more difficult. To remedy this problem, a
plug-in has been added to SOS that collects Quagga-related configuration files, thereby providing
the requisite information to quckly and easily identify and remedy problems with these systems.
(
BZ#485191
1992
)
• SOS was not able to collect Cron data. As a result, troubleshooting was sometimes difficult. To
resolve this issue, SOS has been patched so that it now includes data from /var/spool/cron allowing
support engineers to know about the scheduling of tasks on a given system. (
BZ#485559
1993
)
• SOS was not able to report information about the Cobbler Linux installation suite, limiting engineers'
attempts to troubleshoot systems. To rectify this, SOS now has a plug-in that gathers the following
files if they are present:
/etc/cobbler
/var/log/cobbler
/var/lib/rhn/kickstarts
/var/lib/cobbler/snippits
/var/lib/cobbler/config
/var/lib/cobbler/kickstarts
/var/lib/cobbler/triggers
As a result, troubleshooting Cobbler is now much easier. (
BZ#495934
1994
).