An Ticket #2012022221001026 ist aufgefallen, dass in den Standard Debugleveln in UCS 3.0 sehr viele unnötige Informationen aus dem UDM-Modul gelogged werden. Kurzer Auszug aus der /var/log/univention/management-console-module-udm.log: UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = dnsEntryZoneReverse UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = name UNIVENTION_DEBUG_BEGIN : admin.handlers.base.__getitem__ key = dnsEntryZoneAlias UNIVENTION_DEBUG_END : admin.handlers.base.__getitem__ key = dnsEntryZoneAlias Man könnte hier evt. einmal prüfen, inwieweit diese Meldungen notwendig sind, oder durch ein alternatives Debuglevel unterdrückt werden können.
Beim Lesen der logfiles sind diese Meldungen extrem störend. In das listener.log werden die gleichen Meldungen geschrieben: # grep -c admin.handlers.base.__getitem__ /var/log/univention/*.log | egrep -v ':0$' /var/log/univention/directory-manager-cmd.log:3030 /var/log/univention/listener.log:24874 Sie stammen von management/univention-directory-manager-modules/modules/univention/admin/handlers/__init__.py:267 Das Gleiche gilt für die Ausgabe ------------------------------------------ UNIVENTION_DEBUG_BEGIN : uldap.searchDn filter=(&(cn=*)(|(objectClass=univentionGroup)(objectClass=sambaGroupMapping))(uniqueMember=uid=user50,cn=users,dc=uni,dc=dtr)) base= scope=sub unique=0 required=0 UNIVENTION_DEBUG_END : uldap.searchDn filter=(&(cn=*)(|(objectClass=univentionGroup)(objectClass=sambaGroupMapping))(uniqueMember=uid=user50,cn=users,dc=uni,dc=dtr)) base= scope=sub unique=0 required=0 ------------------------------------------ die bei jedem Zugriff auf eine groups/group geloggt wird. # grep -c 'UNIVENTION_DEBUG_BEGIN : uldap.searchDn' /var/log/univention/*.log | egrep -v '0$' /var/log/univention/listener.log:4066 Die Meldungen stammen von base/univention-python/modules/uldap.py:300 Das Problem: univention.debug.function loggt via /base/univention-debug/lib/debug.c univention_debug_begin()/end(), was keine loglevel unterstützt. Mögliche Lösung: In univention_debug_begin() univention_debug() statt fprintf() verwenden.
Are they printed even if debug-function level is disabled?
It is printed even with listener/debug/level=0 (and directory/manager/cmd/debug/level=0). univention_debug_begin()/end() do not support debug levels.
Isn't there a equivalent like: connector/debug/function: <empty> If the variable is set to '1' function calls are logged as additional debug information. If the variable is set to '0' or unset no calls are logged.
diff --git a/management/univention-directory-listener/src/main.c b/management/univention-directory-listener/src/main.c index 8d2f11d..9e19108 100644 --- a/management/univention-directory-listener/src/main.c +++ b/management/univention-directory-listener/src/main.c @@ -470,6 +470,7 @@ int main(int argc, char* argv[]) » univention_debug_set_level(UV_DEBUG_LISTENER, debugging); » univention_debug_set_level(UV_DEBUG_LDAP, debugging); +» univention_debug_set_function(0); » { » » char filename[PATH_MAX];
(In reply to Florian Best from comment #5) univention_debug_set_function(univention_config_get_int("listener/debug/function/level"));
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.