Bug 752450
| Summary: | abrtd error on kernel dump. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | jurek.bajor | ||||
| Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | high | ||||||
| Version: | 16 | CC: | dfediuck, don-redhat-z6y, dvlasenk, iprikryl, jmoskovc, kklic, mmilata, mtoman, npajkovs, reaves735 | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2012-03-19 14:56:03 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 744774 | ||||||
| Attachments: |
|
||||||
A subsequent example of errors. /var/log/messages: ... Nov 12 13:49:36 localhost kernel: [ 31.811075] ---[ end trace bc7c1df64aaeb445 ]--- Nov 12 13:49:38 localhost abrt-dump-oops[700]: abrt-dump-oops: Found oopses: 1 Nov 12 13:49:38 localhost abrt-dump-oops[700]: abrt-dump-oops: Creating dump directories Nov 12 13:49:38 localhost abrtd: Directory 'oops-2011-11-12-13:49:38-700-0' creation detected Nov 12 13:49:38 localhost abrt-dump-oops: Reported 1 kernel oopses to Abrt Nov 12 13:49:38 localhost abrtd: Can't open file '/var/spool/abrt/oops-2011-11-12-13:49:38-700-0/uid': No such file or directory Nov 12 13:49:39 localhost abrtd: DUP_OF_DIR: /var/spool/abrt/oops-2011-11-09-09:52:29-759-0 Nov 12 13:49:39 localhost abrtd: Dump directory is a duplicate of /var/spool/abrt/oops-2011-11-09-09:52:29-759-0 Nov 12 13:49:39 localhost abrtd: Deleting dump directory oops-2011-11-12-13:49:38-700-0 (dup of oops-2011-11-09-09:52:29-759-0), sending dbus signal Nov 12 13:49:48 localhost systemd-logind[704]: New user jb logged in. ... - these messages are mostly useful only for debugging so, we should silence it by addind DD_FAIL_QUIETLY flag in the respective function calls Does this bug have anything to do with what I find in my messages below? (Or should I open a new bug?) Dec 31 14:54:21 number11 abrt: detected unhandled Python exception in '/usr/share/PackageKit/helpers/yum/yumBackend.py' Dec 31 14:54:21 number11 abrtd: New client connected Dec 31 14:54:21 number11 abrtd: Directory 'pyhook-2011-12-31-14:54:21-3471' creation detected Dec 31 14:54:21 number11 abrt-server[3472]: Saved Python crash dump of pid 3471 to /var/spool/abrt/pyhook-2011-12-31-14:54:21-3471 Dec 31 14:54:21 number11 abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 14:54:21 number11 abrtd: Problem directory is a duplicate of /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 14:54:21 number11 abrtd: Deleting problem directory pyhook-2011-12-31-14:54:21-3471 (dup of pyhook-2011-12-09-10:00:32-9935) Dec 31 14:54:21 number11 abrt: detected unhandled Python exception in '/usr/share/PackageKit/helpers/yum/yumBackend.py' Dec 31 14:54:21 number11 abrtd: New client connected Dec 31 14:54:21 number11 abrtd: Directory 'pyhook-2011-12-31-14:54:21-3483' creation detected Dec 31 14:54:21 number11 abrt-server[3488]: Saved Python crash dump of pid 3483 to /var/spool/abrt/pyhook-2011-12-31-14:54:21-3483 Dec 31 14:54:21 number11 abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 14:54:21 number11 abrtd: Problem directory is a duplicate of /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 14:54:21 number11 abrtd: Deleting problem directory pyhook-2011-12-31-14:54:21-3483 (dup of pyhook-2011-12-09-10:00:32-9935) Dec 31 14:59:55 number11 dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 31 14:59:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Dec 31 14:59:55 number11 dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 31 14:59:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' Dec 31 15:00:20 number11 dbus[1630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Dec 31 15:00:20 number11 dbus-daemon[1630]: dbus[1630]: [system] Activating service name='org.kde.powerdevil.backlighthelper' (using servicehelper) Dec 31 15:00:20 number11 org.kde.powerdevil.backlighthelper: QDBusConnection: system D-Bus connection created before QCoreApplication. Application may misbehave. Dec 31 15:00:20 number11 dbus[1630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Dec 31 15:00:20 number11 dbus-daemon[1630]: dbus[1630]: [system] Successfully activated service 'org.kde.powerdevil.backlighthelper' Dec 31 15:00:21 number11 abrt: detected unhandled Python exception in '/usr/share/PackageKit/helpers/yum/yumBackend.py' Dec 31 15:00:21 number11 abrtd: New client connected Dec 31 15:00:21 number11 abrtd: Directory 'pyhook-2011-12-31-15:00:21-3515' creation detected Dec 31 15:00:21 number11 abrt-server[3516]: Saved Python crash dump of pid 3515 to /var/spool/abrt/pyhook-2011-12-31-15:00:21-3515 Dec 31 15:00:21 number11 abrtd: DUP_OF_DIR: /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 15:00:21 number11 abrtd: Problem directory is a duplicate of /var/spool/abrt/pyhook-2011-12-09-10:00:32-9935 Dec 31 15:00:21 number11 abrtd: Deleting problem directory pyhook-2011-12-31-15:00:21-3515 (dup of pyhook-2011-12-09-10:00:32-9935) Dec 31 15:00:21 number11 abrt: detected unhandled Python exception in '/usr/share/PackageKit/helpers/yum/yumBackend.py' Dec 31 15:00:21 number11 abrtd: New client connected For the moment I've just killed abrtd to turn off this junk. (Now I see messages complaining about inability to connect...) Recent updates seem to have solved the problem above. Now I see this in /var/log/messages: Jan 2 09:29:55 number11 dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 2 09:29:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 2 09:29:55 number11 dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 2 09:29:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 2 09:35:55 number11 dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 2 09:35:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Activating service name='org.freedesktop.PackageKit' (using servicehelper) Jan 2 09:35:55 number11 dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' Jan 2 09:35:55 number11 dbus-daemon[1630]: dbus[1630]: [system] Successfully activated service 'org.freedesktop.PackageKit' (4 lines every 6 min.) Perhaps not related to abrt? What then? PackageKit ? or dbus? (In reply to comment #3) > Does this bug have anything to do with what I find in my messages below? > (Or should I open a new bug?) > > Dec 31 14:54:21 number11 abrt: detected unhandled Python exception in > '/usr/share/PackageKit/helpers/yum/yumBackend.py' > Dec 31 14:54:21 number11 abrtd: New client connected > Dec 31 14:54:21 number11 abrtd: Directory 'pyhook-2011-12-31-14:54:21-3471' > creation detected > Dec 31 14:54:21 number11 abrt-server[3472]: Saved Python crash dump of pid - this lines are saying that there is a problem in packagekit, if you don't see it in abrt-gui try running abrt-gui as root |
Created attachment 532581 [details] messages Description of problem: Abrtd error. Version-Release number of selected component (if applicable): abrt.i686 2.0.4.981-3.fc16 @koji-override-0/$releasever How reproducible: This is a special case: there is a kernel crash (BZ filed) that in turn activates abrt, which in turn issues an error. Steps to Reproduce: 1. as above 2. 3. Actual results: See attached /var/log/messages. ... Nov 9 09:52:29 localhost abrt-dump-oops: Reported 1 kernel oopses to Abrt Nov 9 09:52:29 localhost abrtd: Directory 'oops-2011-11-09-09:52:29-759-0' creation detected Nov 9 09:52:29 localhost abrtd: Can't open file '/var/spool/abrt/oops-2011-11-09-09:52:29-759-0/uid': No such file or directory Nov 9 09:52:30 localhost abrtd: New dump directory /var/spool/abrt/oops-2011-11-09-09:52:29-759-0, processing ... Expected results: no error Additional info: