Red Hat Bugzilla – Bug 164600
Shared Objects cannot be accessed: Permission Denied
Last modified: 2013-01-09 20:19:14 EST
From Bugzilla Helper:
User-Agent: Opera/8.02 (Windows NT 5.1; U; en)
Description of problem:
Just downloaded Fedora Core 4 and attempted an install. All four disks checked
out with sha1 checksums, and prior to install all four disks passed the media
check as good to install. Installation completed without incident. Now cannot
boot system. During boot up sequence numerous instances of error messages
appear along the lines of "Cannot open shared object file xxxxx: permission
denied." Where xxxxx denotes various files -- it scrolls too rapidly to read.
Had this problem (a little bit) with FC 3, particularly with file libc.so.6; all
permissions were checked out but even though were set to 777 (or 755) the boot
up sequence is denied permission to access.
Right now, inability to open libc.so.6 knocks out, among other things, the
network connection eth0, so I cannot get online. But, there are several files
which cannot be opened, so I'm hoping there is a common cause (and solution).
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Boot up Fedora Core 4.
2. Watch text messages for errors as boot sequence progresses.
Actual Results: See above. Numerous (two dozen? three dozen?) error messages scroll rapidly
across the screen.
Expected Results: Typical text messages of successful system boot up, free of error messages and
red-font FAILED reports.
Problem narrowed to SELinux. Set mode of SELinux to "permissive" to generate
warnings rather than deny access to files. Now, boot up provides about three
dozen (?) -- they scroll by so fast -- warnings but almost all services start.
This is something we've been working on upstream. Systems now boot fine if
selinux is in enforcing. Closing nextrelease.