Red Hat Bugzilla – Bug 458135
Sort control message should not be logged for internal operations
Last modified: 2015-01-04 18:33:38 EST
Created attachment 313597 [details]
The backend plug-in currently attempts to log a message whenever it is processing a sort control as part of a search operation. For an internal operation, this causes an error to be logged since the connection ID is not set for an internal operation, but the access log needs it for the log message. Here is the error log message:
[05/Aug/2008:13:12:34 -0700] - Connection is NULL and hence cannot access SLAPI_CONN_ID
When using the DNA plug-in, you will see lots of these messages since it does an internal sorted search. We should not attempt to log anything related to the sort control in the access log for internal operations.
Checked into ldapserver (HEAD). Thanks to Rich for his review!
Checking in back-ldbm/ldbm_search.c;
/cvs/dirsec/ldapserver/ldap/servers/slapd/back-ldbm/ldbm_search.c,v <-- ldbm_search.c
new revision: 1.14; previous revision: 1.13
Can I verify this by executing the DNA acceptance tests and verifying the errors log does not contain this message? I could add regression test to this suite also.
Yes, check(In reply to comment #2)
> Can I verify this by executing the DNA acceptance tests and verifying the
> errors log does not contain this message? I could add regression test to this
> suite also.
Yes, you can verify by checking for the following message in the errors log during the DNA test. It should not appear.
[05/Aug/2008:13:12:34 -0700] - Connection is NULL and hence cannot access
fix verified DS 8.1 RHEL 5 - adding regression test to DNA acceptance test that will parse both replica's access logs for the error message.
Test case added to acceptance tests is failing on RHEL 4 64bit and 32 bit with 2882 instances of the error in the access log.
More investigation - RHEL 4 is problem with test - no actual messages in access log.
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.