Hi,

We have recovered one of our system.Its RedHat Linux 4.0 EL update 5. Everything looks fine. Just one error we keep getting for few commands like w , df , top etc.


[root@y ~]# w
w: error while loading shared libraries: libproc-3.2.3.so: cannot open shared object file: No such file or directory

[root@y ~]# top
top: error while loading shared libraries: libproc-3.2.3.so: cannot open shared object file: No such file or directory

The library libproc-3.2.3.so exists in /lib64.

Probably the system is looking for this library under /lib instead of /lib64.

Any words of suggestions??

Thanks in advance.

As a suggestion try re-installing the rpm package which contains libproc-3.2.3.so library;

rpm -Uvh procps-3.2.3-8.6.x86_64.rpm

Warning: You may have still undiscovered issues about 'missing libraries' with other tools.

i wish to share something here,

[root@y ~]# ldd `which w`
linux-gate.so.1 => (0xffffe000)
libproc-3.2.3.so => not found
libc.so.6 => /lib/i686/libc.so.6 (0xf7eb2000)
/lib/ld-linux.so.2 (0x0056b000)

[root@y ~]# ldd `which top`
linux-gate.so.1 => (0xffffe000)
libproc-3.2.3.so => not found
libncurses.so.5 => /usr/lib/libncurses.so.5 (0x04fc9000)
libc.so.6 => /lib/i686/libc.so.6 (0xf7eb2000)
/lib/ld-linux.so.2 (0x0056b000)

[root@y ~]# ldd `which uptime`
linux-gate.so.1 => (0xffffe000)
libproc-3.2.3.so => not found
libc.so.6 => /lib/i686/libc.so.6 (0xf7eb2000)
/lib/ld-linux.so.2 (0x0056b000)

Did you notice error with libproc.....thats the problem. Its in /lib64 and maybe system is looking it into /lib. ....How do I make the system look for those libraries in /lib64 and not in /lib?

The problem is not with where the library is located, the libproc-3.2.3.so is in the correct location and if the procps libraries is properly registered with the system then it would be found and used. I'm running CentOS5 64-bit which is newer and since the procps package is properly installed and registered I see for example;

So the problem is with your restore effort, it looks like you choose/did something incorrectly, perhaps you restored from a 32-bit image/system on a 64-bit system?? Or used a 64-bit restore image/system on a 32-bit system??

You should check;

rpm -qa --qf="%{n}-%{v}-%{r}.%{arch}\n" procps
uname -a

Perhaps you really need to [re]install the 32-bit version of procps judging from you posted output.

You are dead right!!

See here,

[root@y ~]# rpm -qa --qf="%{n}-%{v}-%{r}.%{arch}\n" procps
procps-3.2.3-7EL.i386

[root@y ~]# uname -a
Linux caregistry 2.6.9-55.ELlargesmp #1 SMP Fri Apr 20 16:46:56 EDT 2007 x86_64 x86_64 x86_64 GNU/Linux


So will it solve the prurpose if we simply install procps for 64-bit or 32-bit ??

Yes one should install the 64-bit version, you may have to remove the 32-bit version first or use the --force switch to install; rpm -Uvh procps-3.2.3-8.6.x86_64.rpm --force

You should also check which other 32-bit libraries are installed instead of the 64-bit version or if your missing the 64-bit version altogether. This will create a list of the installed packages for review, it is OK to have both the 32-bit and 64-bit library rpm packages installed in most cases. The list will be long but it will give you a reference to use and is easier then reading the screen;

rpm -qa --qf="%{n}-%{v}-%{r}.%{arch}.rpm\n" | sort > Installed.txt

Also verify that you have the proper 64-bit version of the glibc rpm package installed. And it may be a good idea to re-install the kernel.

.

#rpm -ivh procps-3.1.2.3-7EL.x86_64.rpm

warning: procps-3.1.2.3-7EL.x86_64.rpm: V3 DSA signature: NOKEY, key ID db42a60e
error: Failed dependencies:
libc.so.6()(64bit) is needed by procps-3.2.3-7EL.x86_64
libc.so.6(GLIBC_2.2.5)(64bit) is needed by procps-3.2.3-7EL.x86_64
libc.so.6(GLIBC_2.3)(64bit) is needed by procps-3.2.3-7EL.x86_64
libc.so.6(GLIBC_2.3.4)(64bit) is needed by procps-3.2.3-7EL.x86_64
libncurses.so.5()(64bit) is needed by procps-3.2.3-7EL.x86_64
Suggested resolutions:
glibc-2.3.4-2.36.x86_64.rpm
ncurses-5.4-13.x86_64.rpm


Shall I use -f option to forcibly install?

Nope, install all three packages at the same time try the following command;

rpm -Uvh procps-3.1.2.3-7EL.x86_64.rpm ncurses-5.4-13.x86_64.rpm glibc-2.3.4-2.36.x86_64.rpm --aid

This should take care of any additional dependencies for glibc and ncurses.