Description of problem: When abrt is configured some plugin, but the plugin is not installed, it starts anyway silently Version-Release number of selected component (if applicable): 0.0.7.1-1 How reproducible: always Steps to Reproduce: 1.configure abrt to use logger plugin 2.make sure abrt-plugin-logger is not installed 3.service abrt restart Actual results: Starting abrt daemon: [ OK ] Expected results: abrt should fail to start, some error messages are also expected Additional info:
the problem here is two-fold: 1. abrt fails to report some of initialization problems * abrt may fail (exit/crash) but user sees "Starting abrt daemon: [ OK ]" * abrt may start but be not fully functional (some/all plugins not installed) 2. We have too many .rpms: * users are easily confused what rpms they need * it's easy to install wrong set of rpms: so that abrt config says "load plugins foo, bar and baz", but only foo is installed with reduced number of rpms we may be able to eliminate most of these scenarios
*** Bug 518245 has been marked as a duplicate of this bug. ***
This bug is fixed now, right?
(In reply to comment #3) > This bug is fixed now, right? no, there is only (intentional?) ugly workaround with metapackage "install everything": yum remove abrt-plugin-logger ... Removing: abrt-plugin-logger Removing for dependencies: abrt-desktop abrt-gui ------------------------- If I try: rpm -e abrt-plugin-logger --nodeps service abrtd restart > Stopping abrt daemon: [ OK ] > Starting abrt daemon: [ OK ] but logger is still configured: # grep -i logger /etc/abrt/abrt.conf EnabledPlugins = SQLite3, CCpp, Logger, Kerneloops, KerneloopsScanner, KerneloopsReporter, Bugzilla, Python CCpp = Bugzilla, Logger Python = Bugzilla, Logger so I think it's not fixed
This is not a bug as the wrong plugin in config file is not a reason for abrt to not run, if the plugin is not essential. Adn as for the abrt-desktop - I agree it's not a Fedora way and should be turned into a group. Jirka
This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle. Changing version to '12'. More information and reason for this action is here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
(In reply to comment #5) > This is not a bug as the wrong plugin in config file is not a reason Why this is not a bug? If configuration is wrong (typo) or plugin is configured but not installed, user should be informed when starting abrt, not just hit by runtime error
As I said "it's not a reason for daemon to not run", but you're right, user should be informed about this, but how would you do that during boot? ABRT can write it into syslog, but user still probably wouldn't notice, maybe we can add a notice into gui, that some plugin is misconfigured. Jirka
(In reply to comment #8) > As I said "it's not a reason for daemon to not run", but you're right, user > should be informed about this, but how would you do that during boot? ABRT can > write it into syslog, but user still probably wouldn't notice, maybe we can add > a notice into gui, that some plugin is misconfigured. 1) default installation should "just work". If user has changed something in the configuration, it's his responsibility to check if it still works. He usually changes configuration file and do service xyz restart afterwards. This command should a)fail OR b)(at least) produce error message to both syslog and console 2) some notification in gui would be great, but not required for case the daemon does not start with wrong configuration, because notification for this (daemon is not running) already exists
> 1) default installation should "just work". If user has changed something in > the configuration, it's his responsibility to check if it still works. He > usually changes configuration file and do service xyz restart afterwards. This > command should a)fail OR b)(at least) produce error message to both syslog and > console > The default install works now (all plugins mentioned in config file are installed by default) > 2) some notification in gui would be great, but not required for case the > daemon does not start with wrong configuration, because notification for this > (daemon is not running) already exists This warning is removed on request of users. Jirka
Committed a fix to git. Now abrtd will refuse to start if a required plugin is missing, with these messages in syslog: Dec 2 16:23:09 abrtd: Can't initialize plugin RunApp: no such plugin installed Dec 2 16:23:09 abrtd: Error while initializing daemon Fix will be in the next update after abrt-1.0.0
abrt-1.0.1-1.fc12 has been submitted as an update for Fedora 12. http://admin.fedoraproject.org/updates/abrt-1.0.1-1.fc12
abrt-1.0.1-1.fc12 has been pushed to the Fedora 12 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update abrt'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F12/FEDORA-2009-12994
we have abrt-1.0.6 right now.