Bug 43096 – The S4-Connector doesn't log UDM module debug messages

Bug 43096 - The S4-Connector doesn't log UDM module debug messages


Summary:	The S4-Connector doesn't log UDM module debug messages

Status:	CLOSED FIXED

Product:	UCS
Classification:	Unclassified
Component:	S4 Connector
Version:	UCS 4.3
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	UCS 4.4-2-errata
Assigned To:	Arvid Requate
QA Contact:	Florian Best

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2016-12-01 20:42 CET by Arvid Requate
Modified:	2019-11-06 14:40 CET (History)
CC List:	2 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?:	2: A Pain – users won’t like this once they notice it
User Pain:	0.046
Enterprise Customer affected?:	Yes
School Customer affected?:	Yes
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:	2018071221000295, 2018110921000668, 2019010421000318
Bug group (optional):
Max CVSS v3 score:

Flags:	requate: Patch_Available+

Attachments
make_s4_connector_log_udm_debug_messages.diff (1.12 KB, patch) 2016-12-01 20:42 CET, 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 Arvid Requate

2016-12-01 20:42:47 CET

Created attachment 8275 [details]
make_s4_connector_log_udm_debug_messages.diff

The S4-Connector doesn't log UDM module debug messages. In some situations it would be useful to get the messages logged into connector-s4.log as well.

The issue is complicated by the fact that the s4-connector code uses univention.debug2 (the Python implementation) while UDM uses the C implementation. In my test I could simply initialize both modules and log to the same file (synchronously) with no problems.

The attached patch implements this and introduces a new UCR variable

ucr set connector/debug/udm/level

maybe there are more elegant solutions to this, but it does the job.

Comment 1 Stefan Gohmann

2019-01-03 07:19:18 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.

Comment 2 Christina Scheinig

2019-01-07 13:57:54 CET

This is very useful and necessary

Comment 3 Arvid Requate

2019-10-10 17:50:33 CEST

ba32730375: Add possibility to log UDM debug messages.

Controlled by two new UCR variables connector/debug/udm/level and connector/debug/udm/function.

Unfortunately UDM and S4-Connector have different default debug levels, so I could not simply use connector/debug/level directly, which would be much more convenient in support situations. Anyway, a small step...

ea4cb34bd1: Advisory

Comment 4 Florian Best

2019-10-10 20:22:50 CEST

OK: univention.debug is initialized for UDM
FAIL: ud.init() is not called for category ud.LDAP :-/
OK: ud.function can be used
~OK: YAML

Be aware, that you will get a lot of stupid log spam due to Bug #50346 and Bug #50347 when setting level=4.

Comment 5 Arvid Requate

2019-10-10 22:16:46 CEST

> ~OK: YAML

Yes, sorry, forgot to push, merged now in d5abb8df8a.

Comment 6 Arvid Requate

2019-11-06 14:40:52 CET

<http://errata.software-univention.de/ucs/4.4/330.html>