Bug 42292 – univention-system-stats runs at the same time as ldap-group-to-file.py

Bug 42292 - univention-system-stats runs at the same time as ldap-group-to-file.py


Summary:	univention-system-stats runs at the same time as ldap-group-to-file.py

Status:	RESOLVED WONTFIX

Product:	UCS
Classification:	Unclassified
Component:	Maintenance/MRTG (univention-maintenance)
Version:	UCS 4.1
Hardware:	Other Linux

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

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-09-06 16:11 CEST by Daniel Tröder
Modified:	2021-04-14 14:06 CEST (History)
CC List:	2 users (show)

See Also:	44475
What kind of report is it?:	Feature Request
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?:	Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2016091221000321
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 Daniel Tröder

2016-09-06 16:11:40 CEST

univention-system-stats runs at the same time as ldap-group-to-file.py resulting in /var/log/univention/system-stats.log showing a heavily loaded slapd.
This can lead to a wrong interpretation of e.g. USIs.

Comment 1 Michael Grandjean

2016-09-12 12:25:49 CEST

2016091221000321

I just came across this, too.
'mrtg' is also shown in every output of 'top'.

Comment 2 Stefan Gohmann

2019-01-03 07:23:54 CET

This issue has been filled against UCS 4.1. The maintenance with bug and security fixes for UCS 4.1 has ended on 5st of April 2018.

Customers still on UCS 4.1 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.