Problem starting named in FreeBSD 10.2

[Olivier Nicole]

Hi,

I am having problems starting named in FreeBSD 10.2. I have been using
the exact same rc.d/named script for years, it is still working in FreeBSD 10.1

The rc.d/named script contains a REQUIRE line that is not honnorred:

# REQUIRE: NETWORKING ldconfig syslogd

on the consle I have the following messages:

[...]
Starting syslogd.
Sep 15 16:02:38  syslogd: hostname nor servname provided, or not known: Bad file
descriptor
Shared object "libxml2.so.2" not found, required by "named-checkconf"
/etc/rc; WARNING; named-checkconf failed for /usr/local/sbin/named-checkconf -t
/var/chroot/named /etc/namedb/named.conf
Starting named.
Shared object "libxml2.so.2" not found, required by "named"
/etc/rc; WARNING; failed to start named
/etc/rc: WARNING: Ignoring scratch file /etc/rc.d/named~
/etc/rc: WARNING: Ignoring scratch file /usr/local/etc/rc.d/named~
ELF ldconfig path: /lib /usr/lib /usr/lib/compat /usr/local/lib /usr/local/lib/c
ompat/pkg /usr/local/lib/compat/pkg /usr/local/lib/gcc48 /usr/local/lib/nss
a.out ldconfig path: /usr/lib/aout /usr/lib/compat/aout
Loading vmmemctl kernel module: VMware memory control driver initialized
done.
Loading vmxnet kernel module: done.
Loading vmblock kernel module: done.
Loading vmhgfs kernel module: done.
Clearing /tmp (X related).
[...]

Clearly, named cannot start because it cannot find libxml2.so.2 and it
cannot find the library because ldconfig has not been started yet.

When the system has finished booting, rc.d/named will start without any
problem.

What could cause the fact tha ldconfig directive is being ignored (on
the dump above, ldcnfig starts *after* named).

This is bugging me quite a bit and ideas are welcome.

best regards,

Olivier


--