Univention Bugzilla – Bug 31757
Print reason for object class violation
Last modified: 2016-07-21 15:15:59 CEST
Even with debuglevel 4 the listener does not log the reason for an object class violation: 17.06.13 16:38:42.505 LISTENER ( ALL ) : replication: add: uid=Administrator,cn=users,dc=xyz,dc=de 17.06.13 16:38:42.505 LISTENER ( ERROR ) : replication: object class violation while adding uid=Administrator,cn=users,dc=xyz,dc=de 17.06.13 16:38:42.505 LISTENER ( INFO ) : handler: replication (successful The ldap.OBJECT_CLASS_VIOLATION exception should return a more detailed reason that should be logged (at least in higher debug level)
Created attachment 5874 [details] replication_exception_info.patch
r69831 | Bug #31757 repl: Improve log information Package: univention-directory-replication Version: 9.0.1-3.104.201606061133 Branch: ucs_4.1-0 Scope: errata4.1-2 r69841 | Bug #33594,Bug #41347,Bug #28232,Bug #30489,Bug #31757: univention-directory-logger YAML univention-directory-replication.yaml
Created attachment 7800 [details] the missing patch While the changes for streamlining the logging code are good, I cannot see the actual issue fixed, am I missing something? I rephrased the previous patch to use the new code.
r71063 | Bug #31757 repl: Log object class violation Package: univention-directory-replication Version: 9.0.1-4.108.201607181744 Branch: ucs_4.1-0 Scope: errata4.1-2 r71076 | Bug #31757,Bug #33594 repl: YAML univention-directory-replication.yaml
Code review: Ok Advisory: Ok
<http://errata.software-univention.de/ucs/4.1/216.html>