Bug 47446 – univention-maintenance fails to start during boot (dependency problem, DNS)

Bug 47446 - univention-maintenance fails to start during boot (dependency problem, DNS)


Summary:	univention-maintenance fails to start during boot (dependency problem, DNS)

Status:	RESOLVED DUPLICATE of bug 45119

Product:	UCS
Classification:	Unclassified
Component:	Update - univention-updater
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	UCS maintainers
QA Contact:	UCS maintainers

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-08-02 14:50 CEST by Hendrik Peter
Modified:	2019-01-04 14:12 CET (History)
CC List:	2 users (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
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Hendrik Peter

2018-08-02 14:50:06 CEST

The service 'univention-maintenance.service' fails to start during boot on UCS 4.3 systems, if UCS@school is installed.

syslog error during Boot:
 Aug  2 12:00:46 server univention-maintenance[1661]: Checking network for Univention maintenance...ldap[master.new-solutions.intranet]...repository[updates.software-univention.de]...failed.
 Aug  2 12:00:46 server systemd[1]: univention-maintenance.service: Control process exited, code=exited status=1
 Aug  2 12:00:46 server systemd[1]: Failed to start LSB: Univention Updater.
 Aug  2 12:00:46 server systemd[1]: univention-maintenance.service: Unit entered failed state.
 Aug  2 12:00:46 server systemd[1]: univention-maintenance.service: Failed with result 'exit-code'.

The service won't retry to start and will stay in it's failed state. 
This happens because the service tries to reach servers by FQDN domains BEFORE bind9 (DNS) is running. It fails to resolve them and exits. This can be fixed by (somehow) adding DNS to the 'Required-Start' parameter of the service.

Comment 1 Philipp Hahn

2019-01-04 14:12:21 CET


*** This bug has been marked as a duplicate of bug 45119 ***