From owner-freebsd-questions@FreeBSD.ORG Tue Apr 21 12:11:38 2009 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 422981065672 for ; Tue, 21 Apr 2009 12:11:38 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by mx1.freebsd.org (Postfix) with ESMTP id BFF498FC08 for ; Tue, 21 Apr 2009 12:11:37 +0000 (UTC) (envelope-from freebsd-questions@m.gmane.org) Received: from list by ciao.gmane.org with local (Exim 4.43) id 1LwEow-0003GY-UR for freebsd-questions@freebsd.org; Tue, 21 Apr 2009 12:11:26 +0000 Received: from frigga.summersault.com ([12.161.105.138]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Apr 2009 12:11:26 +0000 Received: from mark by frigga.summersault.com with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 21 Apr 2009 12:11:26 +0000 X-Injected-Via-Gmane: http://gmane.org/ To: freebsd-questions@freebsd.org From: Mark Stosberg Date: Tue, 21 Apr 2009 08:11:15 -0400 Lines: 70 Message-ID: <20090421081115.27dc7785@summersault.com> References: <20090420162045.6e09beb5@summersault.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: frigga.summersault.com X-Newsreader: Claws Mail 3.7.1 (GTK+ 2.12.9; i486-pc-linux-gnu) Sender: news Subject: Re: named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 21 Apr 2009 12:11:38 -0000 > > We had problem with "named" starting on boot on a FreeBSD 6.1 server, > > managed > > by /etc/rc.conf. > > > > The startup script failed with errors about shared library "libm.so.2" > > failing > > to load because of something related to libxml2.so.5. > > > > Later, when I then tried starting it via /etc/rc.d/named it worked fine. > > > > I include the following "ldd" output in case it's helpful. What could > > possibly > > be the issue here? > > > > Mark > > > > ### > > > > # ldd /usr/sbin/named > > /usr/sbin/named: > > libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) > > libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) > > libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x283ef000) > > libm.so.4 => /lib/libm.so.4 (0x284e3000) > > libc.so.6 => /lib/libc.so.6 (0x284f9000) > > libm.so.2 => /usr/local/lib/compat/libm.so.2 (0x285d1000) > > I also see to LOCAL libraries in it. named is part of base, unless you > compiled and installed the port version and maybe told it to overwrite the > base. > > None of this adds up. > > %ldd /usr/sbin/named > /usr/sbin/named: > libcrypto.so.5 => /lib/libcrypto.so.5 (0x281fe000) > libthr.so.3 => /lib/libthr.so.3 (0x28357000) > libc.so.7 => /lib/libc.so.7 (0x2836a000) > > There's a named on 7.1p4 Thanks for the response. I've now compared this named 'ldd' outfit to another 6.1 install we have that also runs named. It has the exact same file size and version, but slightly different ldd output: -- from the second machine with FreeBSD 6.1 # ldd /usr/sbin/named /usr/sbin/named: libcrypto.so.4 => /lib/libcrypto.so.4 (0x281ff000) libxml2.so.5 => /usr/local/lib/libxml2.so.5 (0x282f1000) libz.so.3 => /lib/libz.so.3 (0x283ff000) libiconv.so.3 => /usr/local/lib/libiconv.so.3 (0x2840f000) libm.so.4 => /lib/libm.so.4 (0x284fc000) libc.so.6 => /lib/libc.so.6 (0x28512000) #### XML is still there, but the mention of libm.so no longer points into /usr/local/lib/compat This other FreeBSD user also found the libxml link: https://lists.isc.org/pipermail/bind-users/2008-November/073929.html I also checked "/etc/make.conf" on both machines. They mentioned X11_BASE and Perl... nothing about XML. However, these machines have evolved some over time. Perhaps something with there in the past. It sounds like advisable paths forward include re-compiling or re-installing named. Mark