On Mon, Aug 24, 2009 at 01:33, John D. Rowell<j...@eyb.com.br> wrote: > Hi Ondřej, > > 2009/8/23 Ondřej Surý <ond...@sury.org> >> >> John, >> >> could you please add libdns50 version and dependencies to the bug >> report, please? Again you can just add reportbug > > The original bug report _is_ from reportbug. Here's the libdns50 line: > > ii libdns50 1:9.6.1.dfsg.P1-1 DNS Shared Library used by BIND > > Do you mean you'd like to get a "reportbug libdns50" instead of a "reportbug > bind9"?
Yep, I meant that. Sorry for not being clear. reportbug doesn't do recursive dependencies, and the link failure is between libdns.so.50 and libGeoIP.so.1. So it would be better to know what version of libgeoip1 have you installed. >> Also maybe objdump -T on libGeoIP.so.1 could be helpful, mine does >> include needed symbol, does yours? >> >> # objdump -T libGeoIP.so.1.4.6 | grep GeoIP_country_name_by_ipnum_v6 >> 000051d0 g DF .text 00000050 Base >> GeoIP_country_name_by_ipnum_v6 > > My lib also contains the symbol, I have no idea why it is not found by the > other libs: > > yoda:~# objdump -T /usr/lib/libGeoIP.so.1.4.6 | grep > GeoIP_country_name_by_ipnum_v6 > 00005190 g DF .text 00000050 Base GeoIP_country_name_by_ipnum_v6 > > I haven't rebooted the machine (for obvious reasons), maybe there's some > other process that's keeping and older version of the lib in shared memory > with the same version/signature as the "new" lib? Any tools to check that? lsof /usr/lib/libGeoIP.so.1 or lsof /usr/lib/libGeoIP.so.1.4.6 Also you can try: lsof +L1 (which lists unlinked, but still used files) > The problem does indeed seem to persist as more ppl are reporting it, and > for each person who reports it there's usually at least 10 or 100 that don't > bother. Maybe it only happens on 32bit systems. Nope, my 32-bit as well as 64-bit chroot runs named just fine. But I am using unstable pbuilder chroots. so something maybe rotten in testing. Are you able to test again on your box? Could you do: # ldd /usr/lib/libdns.so.50 and # ldd /usr/sbin/named when it's not working? Also maybe running strace named -g could give us some hints. And finally does manually updating libgeoip1 to latest version from unstable help? Ondrej -- Ondřej Surý <ond...@sury.org> http://blog.rfc1925.org/ -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
