Bug 41142 - univention-ad-connector not restarted after logrotate
univention-ad-connector not restarted after logrotate
Status: CLOSED FIXED
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 3.2
Other Linux
: P5 normal (vote)
: UCS 3.2-8-errata
Assigned To: Felix Botner
Arvid Requate
:
Depends on: 32265
Blocks:
  Show dependency treegraph
 
Reported: 2016-04-26 16:12 CEST by Stefan Gohmann
Modified: 2016-05-04 16:57 CEST (History)
3 users (show)

See Also:
What kind of report is it?: ---
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 Stefan Gohmann univentionstaff 2016-04-26 16:12:49 CEST
Please backport it to UCS 3.2.

+++ This bug was initially created as a clone of Bug #32265 +++

The univention-ad-connector is not restarted after each logrotate run. From Ticket# 2011111721003386 I know that this usually leads to log messages getting lost (in UCS 2.4). I think we need to adjust the logrotate configuration template to be similar to the one of the univention-s4-connector which performs a restart in the postrun phase.
Comment 1 Felix Botner univentionstaff 2016-05-02 13:33:41 CEST
univention-ad-connector: r69051
univention-ad-connector.yaml
Comment 2 Arvid Requate univentionstaff 2016-05-04 16:23:58 CEST
Ok, works and advisory is ok.
Comment 3 Janek Walkenhorst univentionstaff 2016-05-04 16:57:33 CEST
<http://errata.software-univention.de/ucs/3.2/424.html>