cannot open shared object file: Permission denied
 

My syslog and httpd daemon on FC3 do not seem to e working

The both give me the same problem

Error while loading shared libraries: «library name» cannot open shared object file: Permission denied

the libraries that are giving me problems are

httpd: libprec.so.0
syslog: libc.so.6

they can both be found in /lib or /usr/lib. I did an ldd and alltheir dependencies can be found in /lib or /usr/lib. All the libraries and thei dependancies have either 777 or 755 permisions. I noticed I have libc.so.6 a few times in the system and one of the ldd specificall referenced /lib/tls/lib.so.6 so I added that to my /etc/ld.so.conf file (I also added /lib and /usr/lib out of paranoia). No avail.

All the symlinks seem to be valid though when I do file searches for them using the gnome search built into the taskbar all symlinks are labeled symbolic link (broken). I don't see whats broken about them (and it seems all symlinks are labeled broken so I'm ignoring this detail)

I have nod idea where to look next. Does anybody have any ideas?

Help would be appreciated.

Thx,
-Christian

I did I a tiny bit more investigating.
I have one more daemon which won't start because of this particular problem (mysqld). Ldd on the culprit dll for all of these always brings up only /lib/tls/libc.so.6.

I also have this file elsewhere in my library search path (/lib for for example). I renamed the copy in /lib/tls to see what would happen and I got what looked like a linking error to me instead. It seems it can open the other copies of the libraries but it can't find what it is looking for.

Very frustrating

Can't Open Shared Libraries
 

I, too, have multiple problems stemming from an error message "Can't open shared object files: Permission denied." File libc.so.6 seems a common culprit, but there are others.

I've checked the file permissions and all look good (777 or 755).

With Fedora Core 3 this was a nuisance; certain features didn't work well such as ntpd time synching daemon. Now I'm trying to upgrade to Fedora Core 4 and this is a major problem. For instance, now I can't even open my network connection eth0 due to this problem.

At present I'm unable to regress to FC 3 so trying to push on to complete FC 4 installation. Anyone have any help to offer?

- Bill

Work around
 

I found a workaround for this problem which I thought I posted. Since it appears I in fact didn't post it I'll go ahead and do it now.

This appears to be caused by the wierd permissions system imposed by selinux. I tried fixing my selinux permissions and could make no sense of the whole scheme.

I was able to resolve the problem by simply disabling selinux. I did that by adding the kernel argument selinux=0.

Hope this helps,
-Christian

Re: Work around
 

Sounds like something I'd like to try ... any help on how to do that? I'm not sure how to go about modifying kernel arguments.

- Bill

Okay. Following some guidance from Red Hat, I've found out that SELinux can be set to various modes. Running system-config-securitylevel from the terminal (logged in as root) allows the graphical management of SELinux. The manual method is to Edit /etc/selinux/config .

I see that SELinux has a mode, which can either be SELINUX=permissive or SELINUX=enforcing. In the graphical interface there is a checkblock for Enforcing? which I cleared, thus (I think) changing the mode to permissive. According to Red Hat, "This way SELinux will be running under the correct policy, but will let you login if there is a problem such as incorrect file context labeling."

Now, a reboot gives only two or three error messages, and the related services say they are starting. Most everything works. A few things don't, for instance from the graphical interface "Start Here" gives me a window at start-here:/// with three icons, namely "Applications" , "Preferences" , and "System Settings" . Each of these should navigate the window to applications:/// (and so on), but all three report ' "applications:///" is not a valid location. '

I will have to experiment and see what works and what doesn't ; also, whether even lower levels SELinux are preferred for now. Finally, I think I submit a couple of bugzilla reports at Fedora on this whole topic.

If you learn anything further in this area, please continue to post in this thread. Thanks.

- Bill