Description of problem: Error while loading liblwres.so.50 Version-Release number of selected component (if applicable): bind-libs-9.6.1-2.fc11.x86_64 How reproducible: Just run whatever bind util like "host" and "nslookup" Steps to Reproduce: 1. Run host www.cnn.com 2. 3. Actual results: host www.cnn.com host: error while loading shared libraries: liblwres.so.50: cannot open shared object file: No such file or directory Expected results: IP resolving of www.cnn.com Additional info: The link of shared library is broken: ls -al /usr/lib64/liblwres* lrwxrwxrwx 1 root root 18 2009-07-06 08:55 /usr/lib64/liblwres.so.50 -> liblwres.so.50.2.0 -rwxr-xr-x 1 root root 73336 2009-06-24 17:58 /usr/lib64/liblwres.so.50.0.2 It should have pointed to liblwres.so.50.0.2 and not to liblwres.so.50.2.0. A workaround would be possibly to manually fix the link.
Manually fixing the link does indeed correct the problem. There is a second one that needs fixing, libbind9.so.50 -> libbind9.so.50.2.0 should be libbind9.so.50 -> libbind9.so.50.0.3 This appears to have been changed on my system with the latest updates of the bind packages.
Also, appears (for me) to only be effecting the 64-bit libraries, as my i386 box has the correct file that the link is linking to.
running ldconfig -v fixed both problems.
Indeed, ldconfig can also help as an alternative workaround and only as that. The link was delivered by the bind-libs package: $ rpm -qf /usr/lib64/liblwres.so.50 bind-libs-9.6.1-2.fc11.x86_64 Either the package to include the correct link or to run ldconfig as post install procedure. In no case a user should be required to run additional programs or manually fix broken links.
[10:40:25][adam@turnip][SRPMS]+ host www.google.com host: error while loading shared libraries: liblwres.so.50: cannot open shared object file: No such file or directory [10:41:03][adam@turnip][SRPMS]+ rpm -qf /usr/lib/liblwres.so.50 bind-libs-9.6.1-2.fc11.i586 [10:41:17][adam@turnip][SRPMS]+ uname -a Linux fooBox 2.6.29.5-191.fc11.i686.PAE #1 SMP Tue Jun 16 23:19:53 EDT 2009 i686 i686 i386 GNU/Linux Happening on 32-bit here.
Potential duplicate of Bug #509618.
*** This bug has been marked as a duplicate of bug 509635 ***