Sysreport is a diagnostic utility. It collects information about the running system, which is used for Red Hat Support to analyze current problems with the system. While sysreport is generally considered non-invasive, diagnostic utilities should always be run with caution.

In Red Hat Enterprise Linux 3 Update 7, and Red Hat Enterprise Linux 5.0, a change was introduced to sysreport. In the new version, sysreport will issue a “sysrq t” to the kernel by default. This collects a backtrace on every running process. As such, it can cause unexpected problems such as application freezes, scsi reset errors, and bonding failovers. Sysrq is especially invasive and should never be collected in production. It should only be run when specific debugging information is needed to troubleshoot certain types of problems during scheduled outage windows.

While sysreport should always be run with caution, Red Hat is correcting this default behavior in sysreport on Red Hat Enterprise Linux 3 and 5.0. An errata release will make sysrq non-default with sysreport. For version 5.0, the errata has already been released and is available on RHN. For version 3, an older version of sysreport (from Update 6 or earlier) can be used in the place of the current version. More details can be found in the following Bugzilla links:

# Version 3: https://bugzilla.redhat.com/show_bug.cgi?id=348981
# Version 5: https://rhn.redhat.com/rhn/errata/details/Details.do?eid=5836

Sysreport in Red Hat Enterprise Linux 4 and 5.1 do not run Syrq by default, but as with all diagnostic utilities, caution should be employed appropriately.

Red Hat’s customer service and support teams receive technical support questions from users all over the world. Red Hat technicians add the questions and answers to Red Hat Knowledgebase on a daily basis. Access to Red Hat Knowledgebase is free. Every month, Red Hat Magazine offers a preview into the Red Hat Knowledgebase by highlighting some of the most recent entries. The information provided in this article is for your information only. The origin of this information may be internal or external to Red Hat. While Red Hat attempts to verify the validity of this information before it is posted, Red Hat makes no express or implied claims to its validity.

原文链接: http://www.redhatmagazine.com/2007/12/10/tips-and-tricks-is-it-safe-to-run-sysreport-in-production/