ls: error while loading shared libraries: libacl.so.1:
 

Hi,

We have RHEL 4 update 4 running on IBM Server.

Recently i upgraded Database from 9.2.0.6 to 9.2.0.8.

After the upgrade was over ( which was sucessfull ) ,i started getting errors for ls command thru out the server

[oratst@tatasons lib]$ ls
ls: error while loading shared libraries: libacl.so.1: cannot open shared object file: Input/output error

Can someone help ? This is Urgent !!

Regards

Reboot. Check for error lights on the disks. Boot from live CD and fsck the partitions.

Oracle patch
 

Thanks for reply, however since this problem has coincided with the Oracle patch application, perhaps Oracle patch removed this library file?
Can a Linux admin recover this lost file?

The library belongs to the acl package. You could try reinstalling acl with yum.

It looks like it is time to upgrade your system. RHEL 4 has been out of maintenance for quite a while- about 4 years out of date.

"Input/output error" means something is wrong with the filesystem/disk/hardware. The timing is probably coincidental.

Commands to reinstall all package
 

Thanks hazel
Can you give me the command to reinstall all package?
All is already installed.
It seems only that particular file is missing.

Did you pay attention to the I/O error? Not only your OS is outdated, your hard drive may be dying, too. I'd have a closer look at this issue before it is too late.

Finding replacement for libacl.so.1
 

We have planned for an upgrade of Rhel 4 to OEL 7.

However till that time , we have to live with Rhel.

Our h/w is 8 years old , so a h/w upgrade also is in pipeline.

We have asked for linux Admin to have a look.

However apart from ls command , many other commands are working properly.

If there was a Disk error , none of the commands would have worked.

This seems more like a case of a particular library getting erased , and affecting only those commands which are using that shared lib.

I have checked that the ACL shared lib is installed in this Linux.

However the physical file is missing for sure.

So can we rectify this ? We have a production server ( where things are fine ) , and this file is present over there.

Regards,

ldd command output
 

[oratst@tatasons ~]$ ldd /bin/ls
/lib/libcwait.so (0x0058f000)
librt.so.1 => /lib/tls/librt.so.1 (0x00a65000)
libacl.so.1 => not found ************************************> see here
libselinux.so.1 => /lib/libselinux.so.1 (0x003b7000)
libc.so.6 => /lib/tls/libc.so.6 (0x00123000)
libpthread.so.0 => /lib/tls/libpthread.so.0 (0x0036c000)
/lib/ld-linux.so.2 (0x00105000)

Become root, then type yum remove acl followed by yum install acl

You could have found that out by yourself by reading the yum man page.

Hazel ,

Thanks for the update.
Actually i am an Oracle Dba , i am not confident on Linux admin ( even if i read the manual).
It seems easy to fire those 2 commands.

however seems i can't find yum
[root@tatasons ~]# yum
-bash: yum: command not found

Regards,

You might have some trouble finding repositories for RHEL 4.

I'm not sure yum was installed by default on RHEL 4 either (but it might depend on which release). I find that it was not available for 4.0, but was ported to 4.9 so it depends on how uptodate the release is as to whether a historical repository will have it.

I found this discussion on installing yum on a 4.0 saying it wasn't available until it was backported to 4.7/4.8/4.9, but still recommended using "uptodate".

http://www.linuxquestions.org/questi...nually-928888/

I looked at http://www.pramberger.at/peter/servi...ository/rhel4/ as a historical repository for RHEL 4... and didn't find yum there either.

You may have to manually search for the rpm package you want to get the "missing" file - but it should be on your install disk, or in the above archived repository (or another one).

Oh dear.

Hi. ¿Do you erase link libacl.so.1? Sometimes libacl.so or libacl.so.0 (or so.1) is a link to the file libacl.so.1.x.x. When you update the system, may be erased the link and cant put a new one. Or the link continue and the system erase old library and dont change the link.
Another problem may be a diferent 'ls' which need so.1.x.x but the system have so.0.x.x or s.2.x.x
Take a look at the /lib and /usr/lib directories. Sometimes special libraries files were on special directories under /lib/i486 /lib/i686 or /lib/i486-linux-gnu , etc.

Have a nice day.