Bug 558163
| Summary: | SELinux is preventing /usr/libexec/mysqld "unlink" access on /var/lib/squeezeboxserver/cache/squeezebox-mysql.sock. | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Dmitry Burstein <dmitryburstein> |
| Component: | selinux-policy | Assignee: | Daniel Walsh <dwalsh> |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | low | ||
| Version: | 12 | CC: | bugzilla+redhat, dwalsh, mailings, mgrepl, redhatbugzilla |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | setroubleshoot_trace_hash:baef7aae4b1d46fb837bc6fe6c64f5367c3a87a8c9e53a45c794e6bcceb9a23f | ||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2010-01-27 12:26:49 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
Dmitry Burstein
2010-01-24 02:07:34 UTC
Did you set the label on this directory to mysqld_db_t? If you set it to mysqld_var_run_t this would work. Ok, the problem is squeezeboxserver sets up the following context:
sh-4.0# rpm -q --scripts squeezeboxserver | grep "semanage fcontext -a"
[ -x /usr/sbin/semanage ] && /usr/sbin/semanage fcontext -a -t mysqld_db_t "${CACHEDIR}(/.*)?"
[ -x /usr/sbin/semanage ] && /usr/sbin/semanage fcontext -a -t mysqld_var_run_t "${CACHEDIR}/squeezeboxserver-mysql.sock"
They did not change "squeezeboxserver-mysql.sock" to squeezebox-mysql.sock"
You can add the proper label using:
semanage fcontext -a -t mysqld_var_run_t "/var/lib/squeezeboxserver/cache/squeezebox-mysql.sock"
*** Bug 557395 has been marked as a duplicate of this bug. *** Please open a bug with squeezeboxserver. *** Bug 571099 has been marked as a duplicate of this bug. *** |