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.
by default in RHEL 6, ABRT doesn't enable any reporters, which means that data center users (who aren't running X) won't be notified when ABRT catches a problem.
I'd suggest we at least enable the mailx reporter by default...
(In reply to comment #0)
>
> I'd suggest we at least enable the mailx reporter by default...
You mean enable automatic reporting using mailx by default?
yeah, I'd suggest both mailing and logging by default, although are you guys using syslog?
I've noticed we're not getting ABRT reports from CLI environments, and I think it's because we're not notifying sysadmins through any of their normal communication channels.
We need to move abrt-plugin-mailx into @base in comps, the rest is just change in config file
-#ActionsAndReporters = Mailx("[abrt] new crash was detected")
+ActionsAndReporters = Mailx("[abrt] new crash was detected")
> will this send to syslog as well or should I spin out a new (6.2) request?
ABRT already sends a message to syslog when it detects a crash:
Mar 14 12:44:50 dhcp-25-200 abrt[28009]: saved core dump of pid 27973 (/bin/sleep) to /var/spool/abrt/ccpp-2011-03-14-12:44:50-27973.new/coredump (372736 bytes)
Mar 14 12:44:50 dhcp-25-200 abrtd: New crash /var/spool/abrt/ccpp-2011-03-14-12:44:50-27973, processing
is this enough or would you like to see something else in syslog?
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.
http://rhn.redhat.com/errata/RHBA-2011-0619.html