Bug 1267333
Summary: | SELinux is preventing /usr/lib/systemd/systemd-journald from read, write access on the file /var/log/journal/3f77855635d14fba9a3e387d445174fb/. | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | michal <bami95> |
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> |
Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 22 | CC: | bami95, dominick.grift, dwalsh, fedora, lvrabec, mgrepl, plautrba |
Target Milestone: | --- | Keywords: | Reopened |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | abrt_hash:b1b87bc02d146bb878fc8b3342a704f250c94978bd0cad5527fb090eca21f5c0;VARIANT_ID=workstation; | ||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2016-07-19 20:22:56 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: |
Description
michal
2015-09-29 16:43:03 UTC
setroubleshoot told you what you needed to do? restorecon -R -v /var/log/journal Is there a different mount point there? It seems something was causing this error to repeat. The last restorecon seemed to work though. It hasn't shown up since. I've observed similar errors (read, write, gettatr avc denied) on a freshly installed Fedora 23 system. It was installed via the netinstall image, a few days ago. Since I didn't mess with any files under /var/log/journal I am a little bit surprised that the SELinux contexts are incorrect. Restorecon fixed the context for now: # restorecon -v /var/log/journal/abc123etc/user-1000.journal restorecon reset /var/log/journal/abc123etc/user-1000.journal context system_u:object_r:unlabeled_t:s0->system_u:object_r:var_log_t:s0 Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. |