Bug 45341 - update of unjoined DC backup fails due to bind9
update of unjoined DC backup fails due to bind9
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: DNS
UCS 4.2
Other Linux
: P5 normal (vote)
: UCS 4.3
Assigned To: Stefan Gohmann
Philipp Hahn
: interim-1
Depends on: 46053
Blocks:
  Show dependency treegraph
 
Reported: 2017-09-07 12:43 CEST by Felix Botner
Modified: 2018-03-14 14:37 CET (History)
1 user (show)

See Also:
What kind of report is it?: Development Internal
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Felix Botner univentionstaff 2017-09-07 12:43:11 CEST
Update of my unjoined 4.1-2 backup (errata 4.1-2 package updates) failes with

bind9 (1:9.9.5.dfsg-9+deb8u13A~4.2.1.201708081700) wird eingerichtet ...
Job for bind9.service failed. See 'systemctl status bind9.service' and 'journalctl -xn' for details.
invoke-rc.d: initscript bind9, action "start" failed.
dpkg: Fehler beim Bearbeiten des Paketes bind9 (--configure):
 Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück
dpkg: Abhängigkeitsprobleme verhindern Konfiguration von univention-bind:
 univention-bind hängt ab von bind9 (>= 1:9.8.0.P4); aber:
  Paket bind9 ist noch nicht konfiguriert.

dpkg: Fehler beim Bearbeiten des Paketes univention-bind (--configure):
 Abhängigkeitsprobleme - verbleibt unkonfiguriert
Fehler traten auf beim Bearbeiten von:
 bind9
 univention-bind
E: Sub-process /usr/bin/dpkg returned an error code (1)


-> systemctl status bind9.service
● bind9.service - LSB: bind9 Domain Name Server (DNS)
   Loaded: loaded (/etc/init.d/bind9)
  Drop-In: /run/systemd/generator/bind9.service.d
           └─50-insserv.conf-$named.conf
   Active: failed (Result: exit-code) since Do 2017-09-07 12:39:53 CEST; 9s ago
  Process: 20855 ExecStart=/etc/init.d/bind9 start (code=exited, status=1/FAILURE)

Sep 07 12:39:53 backup bind9[20855]: Starting bind9 Domain Name Server (DNS): Unknown DNS backend  failed!
Sep 07 12:39:53 backup systemd[1]: bind9.service: control process exited, code=exited status=1
Sep 07 12:39:53 backup systemd[1]: Failed to start LSB: bind9 Domain Name Server (DNS).
Sep 07 12:39:53 backup systemd[1]: Unit bind9.service entered failed state.


Since 4.2-0 the our bind init script returns 1 if dns/backend is not ldap or samba (dns/backup is empty on an unjoined system).

Pre 4.2-0  just ignored that and returned 0.
Comment 1 Felix Botner univentionstaff 2017-09-07 17:13:21 CEST
slave also, every system with univention-bind
Comment 2 Stefan Gohmann univentionstaff 2018-01-14 19:36:39 CET
The bind9 init script restart the service only if dns/backend is set.

Fix: svn r17935

Changelog: https://git.knut.univention.de/univention/ucs/commit/9018270af66042a2f7bd049b0f728d8f122554eb
Comment 3 Philipp Hahn univentionstaff 2018-01-18 12:21:38 CET
OK: r17935
OK: 9018270af660

OK: univention-upgrade --ignoressh --ignoreterm --noninteractive </dev/null
OK: univention-join
OK: dig +short @localhost $(ucr get ldap/master)
Comment 4 Stefan Gohmann univentionstaff 2018-03-14 14:37:38 CET
UCS 4.3 has been released:
 https://docs.software-univention.de/release-notes-4.3-0-en.html
 https://docs.software-univention.de/release-notes-4.3-0-de.html

If this error occurs again, please use "Clone This Bug".