Package: bind9-dyndb-ldap Version: 11.6-3 Platform: amd64
Dear Maintainer, after upgrading my system (Debian Bullseye), I cannot start the naming service. With 'systemctl status named.service' I have got the following output: ● named.service - BIND Domain Name Server Loaded: loaded (/lib/systemd/system/named.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Sat 2022-03-12 11:33:01 CET; 19min ago Docs: man:named(8) Process: 1062 ExecStart=/usr/sbin/named -f $OPTIONS (code=exited, status=1/FAILURE) Main PID: 1062 (code=exited, status=1/FAILURE) CPU: 62ms Mär 12 11:33:00 neptun named[1062]: loading DynDB instance 'local_db' driver '/usr/lib/bind/ldap.so' *Mär 12 11:33:00 neptun named[1062]: failed to dynamically load instance 'local_db' driver '/usr/lib/bind/ldap.so': libdns-9.16.15-Debian.so: cannot open shared object file: No such file or directory (failure)** *Mär 12 11:33:00 neptun named[1062]: dynamic database 'local_db' configuration failed: failure Mär 12 11:33:00 neptun named[1062]: loading configuration: failure Mär 12 11:33:00 neptun named[1062]: exiting (due to fatal error) Mär 12 11:33:01 neptun systemd[1]: named.service: Scheduled restart job, restart counter is at 5. Mär 12 11:33:01 neptun systemd[1]: Stopped BIND Domain Name Server. Mär 12 11:33:01 neptun systemd[1]: named.service: Start request repeated too quickly. Mär 12 11:33:01 neptun systemd[1]: named.service: Failed with result 'exit-code'. Mär 12 11:33:01 neptun systemd[1]: Failed to start BIND Domain Name Server. The command 'ldd /usr/lib/bind/ldap.so' says: linux-vdso.so.1 (0x00007ffda3ab4000) libuuid.so.1 => /lib/x86_64-linux-gnu/libuuid.so.1 (0x00007fd4f1ce0000) libkrb5.so.3 => /lib/x86_64-linux-gnu/libkrb5.so.3 (0x00007fd4f1c00000) libldap_r-2.4.so.2 => /lib/x86_64-linux-gnu/libldap_r-2.4.so.2 (0x00007fd4f1ba8000) * libdns-9.16.15-Debian.so => not found** ** libisc-9.16.15-Debian.so => not found** * libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd4f19e0000) /lib64/ld-linux-x86-64.so.2 (0x00007fd4f1d60000) libk5crypto.so.3 => /lib/x86_64-linux-gnu/libk5crypto.so.3 (0x00007fd4f19b0000) libcom_err.so.2 => /lib/x86_64-linux-gnu/libcom_err.so.2 (0x00007fd4f19a8000) libkrb5support.so.0 => /lib/x86_64-linux-gnu/libkrb5support.so.0 (0x00007fd4f1998000) libkeyutils.so.1 => /lib/x86_64-linux-gnu/libkeyutils.so.1 (0x00007fd4f1990000) libresolv.so.2 => /lib/x86_64-linux-gnu/libresolv.so.2 (0x00007fd4f1970000) liblber-2.4.so.2 => /lib/x86_64-linux-gnu/liblber-2.4.so.2 (0x00007fd4f1958000) libsasl2.so.2 => /lib/x86_64-linux-gnu/libsasl2.so.2 (0x00007fd4f1938000) libgnutls.so.30 => /lib/x86_64-linux-gnu/libgnutls.so.30 (0x00007fd4f1738000) libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fd4f1710000) libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fd4f1708000) libp11-kit.so.0 => /lib/x86_64-linux-gnu/libp11-kit.so.0 (0x00007fd4f15d0000) libidn2.so.0 => /lib/x86_64-linux-gnu/libidn2.so.0 (0x00007fd4f15a8000) libunistring.so.2 => /lib/x86_64-linux-gnu/libunistring.so.2 (0x00007fd4f1420000) libtasn1.so.6 => /lib/x86_64-linux-gnu/libtasn1.so.6 (0x00007fd4f1408000) libnettle.so.8 => /lib/x86_64-linux-gnu/libnettle.so.8 (0x00007fd4f13c0000) libhogweed.so.6 => /lib/x86_64-linux-gnu/libhogweed.so.6 (0x00007fd4f1370000) libgmp.so.10 => /lib/x86_64-linux-gnu/libgmp.so.10 (0x00007fd4f12e8000) libffi.so.7 => /lib/x86_64-linux-gnu/libffi.so.7 (0x00007fd4f12d8000) The output of the command 'apt-cache show bind9-dyndb-ldap | grep Depends' is: Depends: bind9-libs (>= 1:9.16.15), libc6 (>= 2.14), libkrb5-3 (>= 1.6.dfsg.2), libldap-2.4-2 (>= 2.4.7), libuuid1 (>= 2.16), bind9 (>= 9.11) The libraries libdns-9.16.15-Debian.so and libisc-9.16.15-Debian.so are not installed on my system, instead I have found the files /lib/x86_64-linux-gnu/libdns-9.16.22-Debian.so /lib/x86_64-linux-gnu/libisc-9.16.22-Debian.so So I assume, that there could be a dependency problem. Best regards, Christian
