Bug 757127
Summary: | abrt-dump-oops: Can't open '/etc/abrt/abrt.conf' ... but it exists | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Mads Kiilerich <mads> |
Component: | abrt | Assignee: | Jiri Moskovcak <jmoskovc> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | unspecified | Docs Contact: | |
Priority: | unspecified | ||
Version: | 16 | CC: | dfediuck, dvlasenk, iprikryl, jmoskovc, kklic, mmilata, mtoman, npajkovs |
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-08-13 08:04:04 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: | 756771 |
Description
Mads Kiilerich
2011-11-25 14:31:06 UTC
(In reply to comment #0) > On boot (with kernel oops) I get /var/log/messages: > > Nov 25 15:22:37 fladmast abrt-dump-oops[924]: abrt-dump-oops: Found oopses: 1 > Nov 25 15:22:37 fladmast abrt-dump-oops[924]: abrt-dump-oops: Can't open > '/etc/abrt/abrt.conf' - this part is weird > Nov 25 15:22:37 fladmast abrt-dump-oops[924]: abrt-dump-oops: Creating dump > directories > Nov 25 15:22:37 fladmast abrtd: Directory 'oops-2011-11-25-15:22:37-924-0' > creation detected > Nov 25 15:22:37 fladmast abrt-dump-oops: Reported 1 kernel oopses to Abrt > Nov 25 15:22:37 fladmast abrtd: Can't open file > '/var/spool/abrt/oops-2011-11-25-15:22:37-924-0/uid': No such file or directory > - this part is dupe of #752450 Do you still experience this problem? If yes, is there any AVC realated to abrt-dump-oops in /var/log/audit/audit.log? No, I haven't noticed it recently ... but I have also not seen so many crashes recently ;-) Thanks for the info. I believe it was caused by a wrong selinux policy which should be already fixed. |