[abrt] a crash has been detected again

 

If you've received 1000's of emails in a short space of time that look like the one below, then this KB will help you to resolve this.

Email received will look something like:

=================================================================
[abrt] a crash has been detected again
ABRT Daemon <[email protected]>


Received: by example.com (Postfix)
 id 698D7F4267E; Mon, 14 Sep 2015 06:05:20 +0100 (BST)
Delivered-To: [email protected]
Received: by example.com (Postfix, from userid 0)
 id 5DEC4F42900; Mon, 14 Sep 2015 06:05:20 +0100 (BST)
Date: Mon, 14 Sep 2015 06:05:20 +0100
From: ABRT Daemon <[email protected]>
To: [email protected]
Subject: [abrt] a crash has been detected again
User-Agent: Heirloom mailx 12.4 7/29/08
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Message-Id: <[email protected]>

=================================================================

 

Upon checking the /var/log/syslog OR /var/log/messages logs you will see something similar to the below logging being printed over and over again:

 

=================================================================

Aug 20 08:14:06 server abrtd: Error Message:
Aug 20 08:14:06 server abrtd: Invalid crash name: pyhook-2015-08-20-07:21:57-13802
Aug 20 08:14:06 server abrtd: Error Class Code: 5005
Aug 20 08:14:06 server abrtd: Error Class Info: Invalid crash name
Aug 20 08:14:06 server abrtd: Explanation:
Aug 20 08:14:06 server abrtd: An error has occurred while processing your request. If this problem
Aug 20 08:14:06 server abrtd: persists please enter a bug report at bugzilla.redhat.com.
Aug 20 08:14:06 server abrtd: If you choose to submit the bug report, please be sure to include
Aug 20 08:14:06 server abrtd: details of what you were trying to do when this error occurred and
Aug 20 08:14:06 server abrtd: details on how to reproduce this problem.
Aug 20 08:14:06 server abrtd:
Aug 20 08:14:06 server abrtd: See /var/log/up2date for more information

=================================================================

This relates to the following bug: https://bugs.php.net/bug.php?id=69605

 

To fix this problem you can simply install arg-parse.

1. Log into your server via SSH

2.  Type 'yum install python-argparse -y' without quotes and press enter

3. Once complete, type 'python /usr/libexec/abrt-action-generate-machine-id' and press enter.

 

If you see the following error, please contact us:

=================================================================

This will throw a traceback error:

        Traceback (most recent call last):

File "/usr/bin/abrt-action-notify", line 18, in <module>

from argparse import ArgumentParser

=================================================================

 

Otherwise, you have resolved the issue.