Bug 859646
Summary: | SELinux is preventing /usr/bin/mongod from 'open' accesses on the file /var/log/mongo/mongod.log. | ||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Lukas Sembera <semberal> | ||||||||
Component: | selinux-policy | Assignee: | Miroslav Grepl <mgrepl> | ||||||||
Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
Severity: | unspecified | Docs Contact: | |||||||||
Priority: | unspecified | ||||||||||
Version: | 17 | CC: | dominick.grift, dwalsh, k.03chandra, mgrepl, nobody | ||||||||
Target Milestone: | --- | ||||||||||
Target Release: | --- | ||||||||||
Hardware: | x86_64 | ||||||||||
OS: | Unspecified | ||||||||||
Whiteboard: | abrt_hash:84a794fd8d21aed96cac7cfe36b564eb1fd6d38e6501e4f1fbf673d025b37f52 | ||||||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||||||
Doc Text: | Story Points: | --- | |||||||||
Clone Of: | Environment: | ||||||||||
Last Closed: | 2013-08-01 17:48:59 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: | |||||||||||
Attachments: |
|
Description
Lukas Sembera
2012-09-22 18:27:11 UTC
Created attachment 615894 [details]
File: type
Created attachment 615895 [details]
File: hashmarkername
It does not look like Fedora ships mongo-10gen-server-2.2.0-mongodb_1. What does # rpm -qf /var/log/mongo Fedora doesn't ship with this version of MongoDB, it was installed from official 10gen MongoDB repository as described at http://docs.mongodb.org/manual/tutorial/install-mongodb-on-redhat-centos-or-fedora-linux/ Ok, and what is your output of # rpm -qf /var/log/mongo # rpm -qf /var/log/mongo error: file /var/log/mongo: No such file or directory Execute # chcon -t mongod_log_t /var/log/mongo/mongod.log which will fix it for now. selinux-policy-3.10.0-150.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-150.fc17 Package selinux-policy-3.10.0-150.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-150.fc17' as soon as you are able to, then reboot. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-14725/selinux-policy-3.10.0-150.fc17 then log in and leave karma (feedback). I tested the update, but it unfortunately didn't help. The service is still not starting and I receive SELinux security alert with the possibility to report it as a bug. Do you need any more information? And if you execute # restorecon -R -v /var/log/mongo/mongod.log Still the same... but now it seems it has a problem with /var/lib/mongo, not /var/log/mongo/mongod.log anymore. Ok, restorecon -R -v /var/log/mongo I tried that, too. Still not working. What does # matchpathcon /var/log/mongo # ls -dZ matchpathcon /var/log/mongo # matchpathcon /var/log/mongo > /var/log/mongo system_u:object_r:mongod_log_t:s0 # ls -dZ matchpathcon /var/log/mongo > ls: cannot access matchpathcon: No such file or directory > drwxr-xr-x. mongod mongod system_u:object_r:mongod_log_t:s0 /var/log/mongo But as I've already written earlier... the problem now seems to be with /var/lib/mongo, not /var/log/mongo. Ah, you are right, I missed it. selinux-policy-3.10.0-153.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/selinux-policy-3.10.0-153.fc17 Package selinux-policy-3.10.0-153.fc17: * should fix your issue, * was pushed to the Fedora 17 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing selinux-policy-3.10.0-153.fc17' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-15652/selinux-policy-3.10.0-153.fc17 then log in and leave karma (feedback). I've applied the update and now I'm getting:
> SELinux is preventing /usr/bin/mongod from getattr access on the filesystem /.
Lukas, could you switch to permissive and collect all AVC msgs? service mongod start Package: (null) Architecture: i686 OS Release: Fedora release 17 (Beefy Miracle) How do I collect all the AVC msgs? ausearch -m avc Created attachment 643535 [details]
ausearch -m avc output
This message is a reminder that Fedora 17 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 17. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '17'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 17's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 17 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 17's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 17 changed to end-of-life (EOL) status on 2013-07-30. Fedora 17 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. Thank you for reporting this bug and we are sorry it could not be fixed. |