Bug 146892
Summary: | Syslogd refuses to start, claiming that libc has a permission denied error | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | David Chipman <dchipman> |
Component: | glibc | Assignee: | Jakub Jelinek <jakub> |
Status: | CLOSED NOTABUG | QA Contact: | Brian Brock <bbrock> |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | menthos |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | i386 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-07-06 21:37:47 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
David Chipman
2005-02-02 16:22:30 UTC
That sounds like you have incorrect security context on /lib/tls/libc-2.3.4.so (and probably other libraries). ls -lZ should show *:shlib_t for /lib/tls/lib-[0-9]*.so restorecon /lib/tls/lib*.so ought to fix this. I have the exact same problem, only with a RHEL 4 system upgraded from RHEL 3. SELinux is enabled with the default policy. # ls -lZ /lib/tls/lib*.so -rwxr-xr-x root root system_u:object_r:shlib_t /lib/tls/libc-2.3.4.so -rwxr-xr-x root root system_u:object_r:shlib_t /lib/tls/libm-2.3.4.so -rwxr-xr-x root root system_u:object_r:shlib_t /lib/tls/libpthread-2.3.4.so -rwxr-xr-x root root system_u:object_r:shlib_t /lib/tls/librt-2.3.4.so -rwxr-xr-x root root system_u:object_r:shlib_t /lib/tls/libthread_db-1.0.so ...but still... # /sbin/service syslog restart Shutting down kernel logger: [ OK ] Shutting down system logger: [FAILED] Starting system logger: syslogd: error while loading shared libraries: libc.so.6: cannot open shared object file: Permission denied [FAILED] Starting kernel logger: [ OK ] I've added a bug report about the same problem in RHEL4 (as described in comment #2) as bug 156696. Does the command in 156696's #4 fix this one too? No response, I'm assuming it does. |