Abrtd: Unrecognized variables
 

I have a system thats been having problems with abrtd. The log file is flooded with the fallowing messages:

abrtd: Unrecognized variable 'BlackListedPaths' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'ActionsAndReporters' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'ProcessUnpackaged' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'Database' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'Python' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable '120' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'CCpp' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'BlackList' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'OpenGPGCheck' in '/etc/abrt/abrt.conf'
abrtd: Unrecognized variable 'Kerneloops' in '/etc/abrt/abrt.conf'

This is the contentnts of my abrt.conf file

[ Common ]
# With this option set to "yes",
# only crashes in signed packages will be analyzed.
# the list of public keys used to check the signature is
# in the file gpg_keys
#
OpenGPGCheck = yes

# Blacklisted packages
#
BlackList = nspluginwrapper,valgrind,strace,mono-core

# Process crashes in executables which do not belong to any package?
#
ProcessUnpackaged = no

# Blacklisted executable paths (shell patterns)
#
BlackListedPaths = /usr/share/doc/*,*/example*,/usr/bin/nspluginviewer

# Which database plugin to use
#
Database = SQLite3

# Enable this if you want abrtd to auto-unpack crashdump tarballs which appear
# in this directory (for example, uploaded via ftp, scp etc).
# Note: you must ensure that whatever directory you specify here exists
# and is writable for abrtd. abrtd will not create it automatically.
#
#WatchCrashdumpArchiveDir = /var/spool/abrt-upload

# Max size for crash storage [MiB] or 0 for unlimited
#
MaxCrashReportsSize = 1000

# Vector of actions and reporters which are activated immediately
# after a crash occurs, comma separated.
#
ActionsAndReporters = Mailx("[abrt] new crash was detected")
#ActionsAndReporters = FileTransfer("store")
ActionsAndReporters = SOSreport


# What actions or reporters to run on each crash type
#
[ AnalyzerActionsAndReporters ]
#Kerneloops = RHTSupport, Logger
#CCpp = RHTSupport, Logger
#Python = RHTSupport, Logger
Kerneloops = Logger
CCpp = Logger
Python = Logger

#CCpp:xorg-x11-apps = RunApp("date", "date.txt")


# Which Action plugins to run repeatedly
#
[ Cron ]
# h:m - at h:m
# s - every s seconds

120 = KerneloopsScanner

#02:00 = FileTransfer

I look at my config file and don't see anything wrong. Everything looks configured and formatted correctly. I looked up the variables and they all should be recognized. So why is abrtd complaining? A fresh pair of eyes would be appreciated. Thanks in advance.

Between versions 2.0.4.981-1 and 2.0.7-4 (F17 being around the corner) a lot of bugs have been fixed (see https://bugzilla.redhat.com/buglist....icksearch=abrt), so maybe first check if you're running the latest version available for your release? I've seen these messages as well but they don't seem to affect running Fedora.

abrt is such a crock of shit.

Period.

I didn't think you had it in you. Being a longtime member and all that. Should we expect more unfounded, disrespectful and worthless responses from you?

Nope - just more pithy assessments of poorly designed and implemented tools foisted on users without proper consultation.

Hi unSpawn

Thanks for the response. I should have been a bit more specific, the system is a RHEl 6 server. I've checked the rhel yum repo and all they have is the 2.0.4-14 package. Looking through bugzilla I have a feeling this is yet another bug. Epel had nothing to offer so I'm crossing my fingers google has an answer.

Like I said it doesn't noticeably hamper normal operation in any way as far as I have observed. Since a package for F17 is available you could --rebuild it for RHEL6 and test it on a non-production server?