Univention Bugzilla – Bug 50519
Increasing the debug level for s4connector make the connector-s4.log nearly unreadable
Last modified: 2021-03-02 22:16:03 CET
ucr set connector/debug/level=3 systemctl restart univention-s4-connector.service One reject lists now the LockingDB 19.11.2019 16:41:46.261 LDAP (INFO ): LockingDB: Return SQL result: '[(1292451,), (1292467,), (1292483,), (1292499,), (1292515,), (1292531,), (1292547,)..... If there are some entrys in the tables, the output is one line. So the logfile is now not searchable, scrollable, readable anymore. Debugging is not possible. And these lines are useless. Maybe this is remnant of Bug 49459? I had this issue now in 2 customer environments.
> Maybe this is remnant of Bug 49459? Yes.
The log format is still not easily readable - even with default debug level. I suggest to rework this completely and also use ud.ALL (4) instead of ud.INFO (3) more for unrelevant details. ud.PROCESS (2) should also log more relevant things and drop the unrelevant things. Logging should be done in a more structured way, proposal: > sync to ucs: [ user] [ modify] 'uid=test,l=school,l=dev' > ucs_operation=modify ad_operation=modify > ucs_type=users/user ad_type=user > mapped dn: 'uid=test,l=school,l=dev' is 'CN=test,DC=school,DC=dev'|not found > ignore_object? No|Yes:(Subtree|Filter|...) > changed attributes: firstname, lastname, displayName, password > diff: firstname: old=[b'foo'], new=[b'bar'] > diff: displayName: old=[b'foo bar'] new=[b'bar foo'] > diff: lastname: old=[b'bar'], new=[b'foo'] > diff: password: old=**** new=*** > object modified: new dn='CN=test,DC=school,DC=dev' (changed|unchanged) > Call post_ucs_modify_function: <function password_sync_s4_to_ucs()> > Call post_ucs_modify_function: <function lockout_sync_s4_to_ucs()> > Successfully synced 'uid=test,l=school,l=dev' to AD.