Product SiteDocumentation Site

Chapter 20. Automatic Bug Reporting Tool (ABRT)

20.1. Overview
20.2. Installing ABRT and Starting its Services
20.3. Running ABRT
20.3.1. Using the Graphical User Interface
20.3.2. Using the Command Line Interface
20.4. Configuring ABRT
20.4.1. ABRT Events
20.4.2. Standard ABRT Installation Supported Events
20.4.3. Event Configuration in ABRT GUI
20.4.4. ABRT Specific Configuration
20.4.5. Configuring Automatic Reporting
20.4.6. Uploading and reporting using a proxy server
20.5. Configuring Centralized Crash Collection
20.5.1. Configuration Steps Required on a Dedicated System
20.5.2. Configuration Steps Required on a Client System
20.5.3. Saving Package Information
20.5.4. Testing ABRT's Crash Detection

20.1. Overview

Migration to ABRT version 2.0

For Red Hat Enterprise Linux 6.2, the Automatic Bug Reporting Tool has been upgraded to version 2.0. The ABRT 2-series brings major improvements to automatic bug detection and reporting.
ABRT is the Automatic Bug Reporting Tool. ABRT consists of a daemon, abrtd, which runs silently in the background most of the time. It springs into action when an application crashes, or a kernel oops is detected. The daemon then collects the relevant problem data such as a core file if there is one, the crashing application's command line parameters, and other data of forensic utility.
ABRT currently supports detection of crashes in applications written in the C/C++ and Python languages, as well as kernel oopses.
ABRT is capable of reporting problems to a remote issue tracker. Reporting can be configured to happen automatically whenever an issue is detected, or problem data can be stored locally, reviewed, reported, and deleted manually by a user. The reporting tools can send problem data to a Bugzilla database, a Red Hat Technical Support (RHTSupport) site, upload it using FTP/SCP, email it, or write it to a file.
The part of ABRT which handles already-existing problem data (as opposed to, for example, creation of new problem data) has been factored out into a separate project, libreport. The libreport library provides a generic mechanism for analyzing and reporting problems, and it is used by applications other than ABRT. However, ABRT and libreport operation and configuration is closely integrated. They are therefore discussed as one in this document.
The ABRT packages provide the following crucial components, among others:
  • abrtd — The ABRT daemon which runs under root as a background service.
  • abrt-applet — The program that receives messages from abrtd and informs you whenever a new problem occurs.
  • abrt-gui — The GUI application that shows collected problem data and allows you to further process it.
  • abrt-cli — The command line interface, which provides similar functionality to the GUI.
  • abrt-ccpp — The ABRT service that provides the C/C++ problems analyzer
  • abrt-oops — The ABRT service that provides the kernel oopses analyzer.