If there is a search request with an invalid base dn, the access log will look like this:
[01/Jan/2014:23:23:23 -0800] conn=1 op=1 SRCH dn="uid=,ou=people,dc=example,dc=com" authzid="(null)", invalid dn [01/Jan/2014:23:23:23 -0800] conn=1 op=1 RESULT err=34 tag=101 nentries=0 etime=0
This causes logconv.pl to report uninitialized variable use. It doesn't know how to parse the authzid and invalid dn parts.
0001-Ticket-47675-logconv-errors-when-search-has-invalid-.patch 0001-Ticket-47675-logconv-errors-when-search-has-invalid-.patch
To ssh://git.fedorahosted.org/git/389/ds.git 3b049f6..f83f7fe master -> master commit f83f7fe Author: Rich Megginson rmeggins@redhat.com Date: Wed Jan 15 09:54:32 2014 -0700
Ticket has been cloned to Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1057803
Metadata Update from @nhosoi: - Issue assigned to rmeggins - Issue set to the milestone: 1.3.3 - 1/14 (January)
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/1012
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: Fixed)
Login to comment on this ticket.