How to fix "ImportError: No module named argparse" exception in abrt-action-notify and abrt-action-generate-machine-id

Solution In Progress - Updated -

Issue

ABRT sends dozens of emails about the crash in abrt-action-generate-machine-id and fills the system logs with messages like these:

abrt: detected unhandled Python exception in '/usr/libexec/abrt-action-generate-machine-id'
abrt-server[18907]: Saved Python crash dump of pid 18906 to /var/spool/abrt/pyhook-2015-07-23-08:43:33-18906
abrtd: Directory 'pyhook-2015-07-23-08:43:33-18906' creation detected
abrtd: Duplicate: core backtrace
abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-08:43:33-18906
abrtd: Deleting problem directory pyhook-2015-07-23-08:43:22-18675 (dup of pyhook-2015-07-23-08:43:33-18906)
abrtd: Sending an email...
abrtd: Email was sent to: root@localhost
abrtd: Duplicate: core backtrace
abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2015-07-23-03:59:32-5493
abrtd: Deleting problem directory pyhook-2015-07-23-08:43:22-18687 (dup of pyhook-2015-07-23-03:59:32-5493)
abrt: detected unhandled Python exception in '/usr/bin/abrt-action-notify'
abrt-server[18918]: Saved Python crash dump of pid 18917 to /var/spool/abrt/pyhook-2015-07-23-08:43:34-18917
abrtd: Directory 'pyhook-2015-07-23-08:43:34-18917' creation detected
abrtd: Traceback (most recent call last):
abrtd:   File "/usr/bin/abrt-action-notify", line 18, in <module>
abrtd:     from argparse import ArgumentParser
abrtd: ImportError: No module named argparse

Environment

  • Red Hat Enterprise Linux 6
  • ABRT

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In