Description Christian Völker 2019-12-19 10:17:11 CET

When dns/backend is set to ldap systemctl status bind9 reports no errors even when the background service univention-bind-ldap fails to start.

Errors in the second should be seen in the foreground service, too!

systemctl status univention-bind-ldap reports the failure:
=======================================
root@backup02:/var/log # systemctl status univention-bind-ldap.service 
● univention-bind-ldap.service - BIND Domain Name Server with LDAP backend
   Loaded: loaded (/lib/systemd/system/univention-bind-ldap.service; disabled; vendor preset: enabled)
   Active: deactivating (stop-sigterm) (Result: exit-code) since Thu 2019-12-19 10:04:11 CET; 8min ago
     Docs: man:named(8)
  Process: 8103 ExecStop=/usr/lib/univention-bind/ldap stop (code=exited, status=0/SUCCESS)
  Process: 9727 ExecStartPost=/usr/lib/univention-bind/ldap wait-for-startup (code=exited, status=124)
 Main PID: 9726 (named)
    Tasks: 11 (limit: 4915)
   Memory: 28.3M
      CPU: 1.477s
   CGroup: /system.slice/univention-bind-ldap.service
           └─9726 /usr/sbin/named -c /etc/bind/named.conf -p 7777 -u bind -f -d 0

Dez 19 10:12:03 -backup02 named[9726]: configuring command channel from '/etc/bind/rndc.key'
Dez 19 10:12:03 backup02 named[9726]: command channel listening on 127.0.0.1#55555
Dez 19 10:12:03 backup02 named[9726]: managed-keys-zone: loaded serial 0
Dez 19 10:12:13 backup02 ldap[9727]: rndc: recv failed: operation canceled
Dez 19 10:12:13 backup02 systemd[1]: univention-bind-ldap.service: Control process exited, code=exited status=124
Dez 19 10:12:13 backup02 named[9726]: zone 10.10.10.in-addr.arpa/IN: sending notifies (serial 31)
=======================================

While systemctl status bind9 claims everything is fine:
=======================================
root@backup02:/var/log # systemctl status bind9
● bind9.service - BIND Domain Name Server proxy for LDAP backend
   Loaded: loaded (/lib/systemd/system/bind9.service; enabled; vendor preset: enabled)
  Drop-In: /etc/systemd/system/bind9.service.d
           └─10-configure-backend.conf
   Active: active (running) since Thu 2019-12-19 10:04:12 CET; 8min ago
     Docs: man:named(8)
  Process: 8110 ExecStop=/usr/lib/univention-bind/proxy stop (code=exited, status=0/SUCCESS)
  Process: 8117 ExecStartPost=/usr/lib/univention-bind/proxy wait-for-startup (code=exited, status=0/SUCCESS)
 Main PID: 8116 (named)
    Tasks: 11 (limit: 4915)
   Memory: 29.3M
      CPU: 216ms
   CGroup: /system.slice/bind9.service
           └─8116 /usr/sbin/named -c /etc/bind/named.conf.proxy -u bind -f -d 0
=======================================


There should be some sort of hint about the state of the services bind9 depends on.