named fails to start on boot on FreeBSD 6.1, complains about libxml2.so.5

Tim Judd tajudd at gmail.com
Tue Apr 21 03:09:51 UTC 2009


On Mon, Apr 20, 2009 at 2:20 PM, Mark Stosberg <mark at summersault.com> wrote:

>
> 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

I find yours really confusing.


More information about the freebsd-questions mailing list