Bug 35686 – S4-Connector-Log schreibt Partition voll

Bug 35686 - S4-Connector-Log schreibt Partition voll


Summary:	S4-Connector-Log schreibt Partition voll

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.2
Hardware:	All other

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

URL:
Keywords:

Duplicates:	33927 (view as bug list)
Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2014-08-22 08:11 CEST by Dirk Siemer
Modified:	2020-07-03 20:55 CEST (History)
CC List:	4 users (show)

See Also:
What kind of report is it?:	Bug Report
What type of bug is this?:	2: Improvement: Would be a product improvement
Who will be affected by this bug?:	2: Will only affect a few installed domains
How will those affected feel about the bug?:	3: A User would likely not purchase the product
User Pain:	0.069
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):	External feedback
Max CVSS v3 score:

Flags:	best: Patch_Available+

Attachments
maxsize.patch (972 bytes, patch) 2017-06-19 20:04 CEST, Arvid Requate	Details \| Diff
View All 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 Dirk Siemer 2014-08-22 08:11:30 CEST

Release 3.2-2 errata178
ucs@school 3.2 R2 v1
Samba4

Ich betreue mehrere Schulen in einer Master-Slave-Umgebung. In einer Schule werden auf Wunsch des dortigen Ansprechpartners (Lehrer) zu jedem Schuljahreswechsel sämtliche Schüleraccounts (ca. 800) und Klassen gelöscht und anschließend neu angelegt.

Im Zuge der diesjährigen Aktion ist mir folgendes aufgefallen:
Die Datei /var/log/univention/connector-s4.log auf dem DC-Slave bläht sich größenmäßig (21 GB) soweit auf, dass sie letztendlich sämtlichen freien Platz auf der Root-Partition (diese ist 27 GB groß) belegt und damit auch den Squid3-Prozeß abschießt.

Letztlich hilft nur manuelles Löschen des Logfiles und Neustart des S4-Connectors.

Gibt es vielleicht eine ucr-Variable, die die Größe von Logfiles beschränkt? Oder bestände die Möglichkeit, im Zuge eines Updates dieses Verhalten zu unterbinden?

Comment 1 Stefan Gohmann

2016-10-11 07:08:37 CEST

*** Bug 33927 has been marked as a duplicate of this bug. ***

Comment 2 Stefan Gohmann

2017-06-16 20:40:38 CEST

This issue has been filed against UCS 3. UCS 3 is out of the normal maintenance and many UCS components have vastly changed in UCS 4.

If this issue is still valid, please change the version to a newer UCS version otherwise this issue will be automatically closed in the next weeks.

Comment 3 Arvid Requate

2017-06-19 20:04:43 CEST

Created attachment 8933 [details]
maxsize.patch

Support rotating s4-connector.log depending on maximal size:

ucr set lorotate/s4/maxsize=100M

I guess we would also want:

* set a reasonable default for this
* support a general lorotate/maxsize
* run logrotate hourly (currently only /etc/cron.daily/logrotate)

Comment 4 Ingo Steuwer

2020-07-03 20:55:23 CEST

This issue has been filed against UCS 4.2.

UCS 4.2 is out of maintenance and many UCS components have changed in later releases. Thus, this issue is now being closed.

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