Bug 54050 – univention-directory-listener-ctrl resync fails for nagios-client

Bug 54050 - univention-directory-listener-ctrl resync fails for nagios-client


Summary:	univention-directory-listener-ctrl resync fails for nagios-client

Status:	CLOSED INVALID

Product:	UCS
Classification:	Unclassified
Component:	Monitoring (Prometheus or Nagios)
Version:	UCS 5.0
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-11-10 15:56 CET by riess82
Modified:	2021-11-11 09:53 CET (History)
CC List:	2 users (show)

See Also:	53681
What kind of report is it?:	Bug Report
What type of bug is this?:	4: Minor Usability: Impairs usability in secondary scenarios
Who will be affected by this bug?:	1: Will affect a very few installed domains
How will those affected feel about the bug?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
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
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 riess82 2021-11-10 15:56:17 CET

continuing to work on setting up a 4.4 nagios member server in a 5.0 environment.
After fixing a decoding problem, the nagios client works fine on the primary 5.0 system.

I have added a 5.0 backup node now, and the command "univention-directory-listener-ctrl resync nagios-client" does not work but shows a line with red "0       nagios-client   /usr/lib/univention-directory-listener/system/nagios-client.py"

I could not find any related log so far, so I dont know where to start looking.

Comment 1 Philipp Hahn

2021-11-10 16:52:35 CET

`univention-directory-listener-ctrl` works for us every day - so not a major bug (as it is more an internal tool than an exported API) and neither affecting average domains (we use it in all our test runs).

"status" just checks and displays the content of the file "/var/lib/univention-directory-listener/handlers/nagios-client". It might take some time for UDL to re-run the handler for all existing objects.

See log file "/var/log/univention/listener.log" for any hints.
Maybe also `journalctl -b 0 -u univention-directory-listener.service` and `systemctl status univention-directory-listener.service`.

Comment 2 Florian Best

2021-11-10 17:28:00 CET

I sent you the required hints via email.
Please use https://help.univention.com/ next time for such problems.

Comment 3 riess82 2021-11-10 18:36:57 CET

Checking back after some hours now, the error has disappeared, without changing anything except what has been discussed before. I'll keep an eye on it though.

Maybe the comment of Philipp Hahn about just giving it some time is right.