27.3. Configuring ABRT

ABRT's main configuration file is /etc/abrt/abrt.conf. ABRT plugins can be configured through their config files, located in the /etc/abrt/plugins/ directory.

After changing and saving the abrt.conf configuration file, you must restart the abrtd daemon—as root—for the new settings to take effect:

~]# service abrtd restart

The following configuration directives are currently supported in /etc/abrt/abrt.conf.

[ Common ] Section Directives

OpenGPGCheck = <yes/no>: Setting the OpenGPGCheck directive to yes (the default setting) tells ABRT to only analyze and handle crashes in applications provided by packages which are signed by the GPG keys whose locations are listed in the /etc/abrt/gpg_keys file. Setting OpenGPGCheck to no tells ABRT to catch crashes in all programs.
BlackList = nspluginwrapper, valgrind, strace, avant-window-navigator, [<additional_packages> ]: Crashes in packages listed after the BlackList option will not be handled by ABRT. If you want ABRT to ignore other packages, list them here separated by commas.
Database = SQLite3: This option instructs ABRT to store its crash data in the SQLite3 database. Other databases are not currently supported. However, ABRT's plugin architecture allows for future support for alternative databases.
MaxCrashReportsSize = <size_in_megabytes>: This option sets the amount of storage space, in megabytes, used by ABRT to store all crash information from all users. The default setting is 1000 MB. Once the quota specified here has been met, ABRT will no longer catch and save program crash information.
ActionsAndReporters = SOSreport: This option tells ABRT to run the sosreport command immediately after an application crash. You can turn this behavior off by commenting out this line. For further fine-tuning, you can add SOSreport to either the CCpp or Python options to make ABRT run sosreport after C and C++ or Python application crashes, respectively.

[ AnalyzerActionsAndReporters ] Section Directives

This section allows you to associate certain analyzer actions and reporter actions to run when ABRT catches kernel oopses or crashes in C, C++ or Python programs. The order of actions and reporters is important.

Kerneloops = TicketUploader, Bugzilla: This directive specifies that, for kernel oopses, the TicketUploader and Bugzilla reporters should run.
CCpp = TicketUploader, Bugzilla: This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.
Python = TicketUploader, Bugzilla: This directive specifies that, when C or C++program crashes occur, both the TicketUploader and Bugzilla reporters should run.

[ Cron ] Section Directives

<time> = <action_to_run>

The [ Cron ] section of abrt.conf allows you to specify the exact time, or elapsed amount of time between, when ABRT should run a certain action, such as scanning for kernel oopses or performing file transfers. You can list further actions to run by appending them to the end of this section.

# Which Action plugins to run repeatedly
[ Cron ]
# h:m - at h:m
# s - every s seconds
120 = KerneloopsScanner
#02:00 = FileTransfer

Example 27.1. [ Cron ] section of /etc/abrt/abrt.conf

The format for an entry is either <time_in_seconds> = <action_to_run> or <hh:mm> = <action_to_run> , where hh (hour) is in the range 00-23 (all hours less than 10 should be zero-filled, i.e. preceded by a 0), and mm (minute) is 00-59, zero-filled likewise.