Bug 678724

Summary: without GUI, abrt doesn't notify users by default
Product: Red Hat Enterprise Linux 6 Reporter: Andrew Hecox <ahecox>
Component: abrtAssignee: Jiri Moskovcak <jmoskovc>
Status: CLOSED ERRATA QA Contact: BaseOS QE - Apps <qe-baseos-apps>
Severity: medium Docs Contact:
Priority: urgent    
Version: 6.1CC: ahecox, dfediuck, dvlasenk, gavin, kklic, mnowak, npajkovs, rvokal, sdodson
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: abrt-1.1.16-2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-05-19 13:41:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 684209    
Bug Blocks:    

Description Andrew Hecox 2011-02-19 02:46:21 UTC
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...

Comment 2 Jiri Moskovcak 2011-02-21 09:37:10 UTC
(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?

Comment 3 Andrew Hecox 2011-02-21 12:01:19 UTC
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.

Comment 4 Jiri Moskovcak 2011-03-11 13:21:10 UTC
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")

Comment 5 Jiri Moskovcak 2011-03-11 13:22:20 UTC
How to test:

$ sleep 100&
$ kill -s SEGV $!

- there should be email about the crash in root@localhost

Comment 7 Andrew Hecox 2011-03-14 11:35:50 UTC
will this send to syslog as well or should I spin out a new (6.2) request?

Comment 8 Jiri Moskovcak 2011-03-14 11:49:51 UTC
> 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?

Comment 9 Andrew Hecox 2011-03-14 15:39:39 UTC
looks great, thanks Jiri

Comment 13 errata-xmlrpc 2011-05-19 13:41:44 UTC
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