Description of problem: Bind failed to start because of wrong linked libs. Version-Release number of selected component (if applicable): bind-libs-9.6.1-2.fc11.x86_64 bind-9.6.1-2.fc11.x86_64 bind-chroot-9.6.1-2.fc11.x86_64 bind-utils-9.6.1-2.fc11.x86_64 How reproducible: Always Steps to Reproduce: 1. install latest bind 2. service named start Actual results: /usr/sbin/named: error while loading shared libraries: libbind.so.50: cannot open shared object file: No such file or directory Expected results: Bind start and working. Additional info: It seems, that the latest update is linked to the wrong libs, that are not in the repo: /usr/lib64/libbind9.so.50 -> libbind9.so.50.2.0 /usr/lib64/libbind9.so.50.0.3 /usr/lib64/liblwres.so.50 -> liblwres.so.50.2.0 /usr/lib64/liblwres.so.50.0.2 I corrected the links to: libbind9.so.50 -> libbind9.so.50.0.3 liblwres.so.50 -> liblwres.so.50.0.2 and bind semms to work ok. best regards
*** Bug 509649 has been marked as a duplicate of this bug. ***
Created attachment 350497 [details] rpm transaction log Easily reprocible as attached. The reason this happened is - bind-libs-9.6.1-0.4.rc1.fc11 had libbind9.so.50.2.0, bind-libs-9.6.1-2.fc11 has libbind9.so.50.0.3, which is the less version than libbind9.so.50.2.0 - rpm usually skips "%postun ldconfig" on upgrade like this case. So when bind is upgrade from 9.6.1-0.4.rc1.fc11 to : - First libbind9.so.50 pointed to libbind9.so.50.2.0 - 9.6.1-2.fc11 binary rpm is unpacked, at this stage libbind9.so.50 pointed to libbind9.so.50.0.3 - ldconfig is called in %post 9.6.1-2.fc11. Now libbind9.so.50 points to libbind9.so.50.2.0 because this one has higher version. - Then 9.6.1-0.4.rc1.fc11 is removed, now libbind9.so.50 symlink is broken because libbind9.so.50.2.0 does not exist any longer. - And ldconfig in %postun 9.6.1-0.4.rc1.fc11 is skipped (as the attached log shows). Broken symlink is not touched.
The broken symlinks also break nslookup: $ nslookup nslookup: error while loading shared libraries: liblwres.so.50: cannot open shared object file: No such file or directory /usr/lib64/liblwres.so.50 is a broken symlink to liblwres.so.50.2.0, while the version that actually exists is liblwres.so.50.0.2
This looks like a duplicate of bug 509618. Running ldconfig manually resolved the issue for me.
*** Bug 509964 has been marked as a duplicate of this bug. ***
*** Bug 509618 has been marked as a duplicate of this bug. ***
Thanks for report, fixed in bind-9.6.1-3.fc11.
bind-9.6.1-3.fc11 has been submitted as an update for Fedora 11. http://admin.fedoraproject.org/updates/bind-9.6.1-3.fc11
Created attachment 351484 [details] rpm transaction log Seems to work, thanks.
Seems as if it may be necessary for bind-utils as well. On a workstation, without bind installed, updated today, bind-utils is still showing as bind-9.6.1-2.fc11 and giving the same error, with, for example host <ipaddress>. The fix of running ldconfig works.
Indeed, I don't have the bind package installed either: $ rpm -qa | grep "^bind" bind-utils-9.6.1-2.fc11.x86_64 bind-libs-9.6.1-2.fc11.x86_64 However, the problem was resolved from a recently update that issued possibly ldconfig.
Every call of "ldconfig" should solve this problem, nevertheless, the bind package should execute ldconfig in %post etc.
reply to comment #10 and comment #11: Fixed package (bind-9.6.1-3.fc11) is still in "pending" state so it is not available in the official repositories. When fixed package hits stable or testing repo you will be notified. Please be patient.
bind-9.6.1-3.fc11 has been pushed to the Fedora 11 testing repository. If problems still persist, please make note of it in this bug report. If you want to test the update, you can install it with su -c 'yum --enablerepo=updates-testing update bind'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F11/FEDORA-2009-7708
Adam, I apologise for the inconvenience. It seems that we haven't made our point clear. # yum --enablerepo=updates-testing update bind <snip> Setting up Update Process Package(s) bind available, but not installed. No Packages marked for Update This is what we were trying to say on comment 10 and comment 11. I don't know how a package that it is not installed on my system will resolve my issue through the update process. It may resolve the current problem reported on this bug when bind package is installed, but not for the duplicate bugs where a simple usage of bind-utils is concerned.
http://cvs.fedoraproject.org/viewvc/rpms/bind/F-11/bind.spec?r1=1.317&r2=1.318 Panos, the fix was applied to bind-libs, so: yum --enablerepo=updates-testing update bind-libs IIRC neither bind nor bind-utils contain libraries so must not contain ldconfig calls, but bind-libs.
bind-9.6.1-3.fc11 has been pushed to the Fedora 11 stable repository. If problems still persist, please make note of it in this bug report.