Bug 53582 – add better monitoring for u-d-n

Bug 53582 - add better monitoring for u-d-n


Summary:	add better monitoring for u-d-n

Status:	NEW

Product:	UCS
Classification:	Unclassified
Component:	Notifier (univention-directory-notifier)
Version:	UCS 4.4
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:	2021-07-15 14:15 CEST by Dirk Ahrnke
Modified:	2021-07-15 14:15 CEST (History)
CC List:	0 users

See Also:
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?:
School Customer affected?:	Yes
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 Dirk Ahrnke

2021-07-15 14:15:22 CEST

While examining a replication issue in a customer environment we discovered that u-d-n was not listening on port 6669. 
The usual tests (check for running service, /usr/lib/nagios/plugins/check_univention_replication) did not detect the issue which was most likely present for a couple of months. 

The only hint for a major problem was a bt in notifier.log, indicating that /var/lib/univention-ldap/notify/transaction was corrupted. This was confirmed by "/usr/share/univention-directory-notifier/univention-translog check"

It would be nice if some kind of monitoring or health check could detect that the service is not functional.