Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 672232

Summary: Update ABRT chapter
Product: Red Hat Enterprise Linux 6 Reporter: Jiri Moskovcak <jmoskovc>
Component: doc-Deployment_GuideAssignee: Martin Prpič <mprpic>
Status: CLOSED CURRENTRELEASE QA Contact: ecs-bugs
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.1CC: dfediuck, eric, jskeoch
Target Milestone: rcKeywords: Documentation
Target Release: 6.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-25 11:49:26 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 Jiri Moskovcak 2011-01-24 14:22:19 UTC
Description of problem:
There is a missing information of how to configure ABRT to do automatic reporting, please see https://bugzilla.redhat.com/show_bug.cgi?id=671359
for more information

The text draft:

There is a list of reporters in the config file /etc/abrt/abrt.conf like this:

# What actions or reporters to run on each crash type
#
[ AnalyzerActionsAndReporters ]
Kerneloops = RHTSupport, Logger
CCpp = RHTSupport, Logger
RHTSupport and Logger reporters will be run.

so to use logger for autoreporting you need to change it to: 

[ AnalyzerActionsAndReporters ]
Kerneloops = Logger
CCpp = Logger
Python = Logger

and then in:

/etc/abrt/plugins/CCpp.conf
/etc/abrt/plugins/Kerneloops.conf
/etc/abrt/plugins/Python.conf

add line a line:

AutoReportUIDs = uids

-> uids are actually usernames (not UIDs) specifying the user for whom you
want to report crashes automatically -> e.g: if you're running httpd it runs
under user apache and you want to automatically report the crashes, then you
should add:

 AutoReportUIDs = apache

you can specify more the one user by comma separated list:

 AutoReportUIDs = apache, user1, user2