Univention Bugzilla – Bug 38735
UMC drops log messages univention.debug.LDAP
Last modified: 2023-06-20 20:57:50 CEST
uldap.py makes some nice log messages but UMC doesn't log them. There is no call to set_level for univention.debug.LDAP. Even if this is added the messages doesn't occur in the logfile. A quick python example showed me that this works in general but somehow not with UMC (I will further investigate this later). >>> ud.init('stderr', ud.FLUSH, ud.NO_FUNCTION) 19.06.15 16:23:58.397 DEBUG_INIT <open file 'stderr', mode 'a+' at 0x7fcf270978a0> >>> ud.set_level(ud.LDAP, 4) >>> ud.debug(ud.LDAP, ud.ERROR, 'tesT') 19.06.15 16:24:47.717 LDAP ( ERROR ) : tesT >>> ud.debug(ud.LDAP, ud.WARN, 'tesT') 19.06.15 16:25:03.197 LDAP ( WARN ) : tesT >>> ud.debug(ud.LDAP, ud.PROCESS, 'tesT') 19.06.15 16:25:13.725 LDAP ( PROCESS ) : tesT >>> ud.debug(ud.LDAP, ud.INFO, 'tesT') 19.06.15 16:25:20.045 LDAP ( INFO ) : tesT >>> ud.debug(ud.LDAP, ud.ALL, 'tesT') 19.06.15 16:25:24.438 LDAP ( ALL ) : tesT
Created attachment 6982 [details] patch Patch, adds the logging component to UMC. There are still other logging components which aren't initialized but they can be ignored afaik (which are USERS SLAPD SEARCH TRANSFILE LISTENER POLICY CONFIG KERBEROS LICENSE DHCP).
The content of attachment 6982 [details] has been deleted for the following reason: applied and does not work
This has magically been fixed via the UMC server unification (Bug #43633). I can't explain the reason and never understood why it didn't work. *** This bug has been marked as a duplicate of bug 43633 ***