Bug 37594

Summary:	logrotate does not trigger heimdal-kdc to reopen logfiles
Product:	UCS	Reporter:	Florian Best <best>
Component:	Kerberos	Assignee:	UCS maintainers <ucs-maintainers>
Status:	RESOLVED WONTFIX	QA Contact:
Severity:	normal
Priority:	P5	CC:	gohmann
Version:	UCS 4.0
Target Milestone:	UCS 4.x
Hardware:	Other
OS:	Linux
See Also:	https://forge.univention.org/bugzilla/show_bug.cgi?id=36473
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:

Description Florian Best

2015-01-22 16:52:40 CET

The config files /var/log/heimdal-kdc.log and /var/log/heimdal-database.log are referenced in /etc/heimdal-kdc/kdc.conf and etc/krb5.conf.
If these logfiles are removed by logrotate the heimdal/kdc service logs into nowhere. This should be fixed by a postrotate section in the logrotate script which restarts the heimdal service (maybe also possible to send SIGHUP).
(Bug #36473 comment 2)

Comment 1 Stefan Gohmann

2019-01-03 07:18:27 CET

This issue has been filled against UCS 4.0. The maintenance with bug and security fixes for UCS 4.0 has ended on 31st of May 2016.

Customers still on UCS 4.0 are encouraged to update to UCS 4.3. Please contact
your partner or Univention for any questions.

If this issue still occurs in newer UCS versions, please use "Clone this bug" or simply reopen the issue. In this case please provide detailed information on how this issue is affecting you.