#48904 syncrepl search returning error 329; plugin sending a bad error code
Closed: wontfix None Opened 6 years ago by nhosoi.

Description of problem:
dns connection (see binddn) that does a search returning error 329; plugin
sending a bad error code to the server?

How reproducible:
This is something extremely strange:

dns connection (see binddn) that does a search returning error 329 which does
not seem to be standard ldap error. It repeats several times.

[..] conn=93893 op=2 RESULT err=0 tag=97 nentries=0
etime=0 dn="krbprincipalname=dns/user.test.example.com@example.com,cn=ser
[..] conn=93893 op=3 SRCH
base="cn=dns,dc=example,dc=com" scope=2 filter="(|(objectClass=idnsConfigObj
)" attrs=ALL
[..] conn=93893 op=3 RESULT err=329 tag=121 nentries=0 etime=1

I guess it's a plugin sending a bad error code to the server.

This shows up regularly on multiple machines.

Description: Implemented based upon the analysis by lkrispen@redhat.com.

the problem is in the new function send_ldap_intermediate() introduced for
sync_repl, it calls log_result (....,rc, ) where rc is the return code of
ber_put_seq(). It should call log_result( ...,1, ) if rc==LBER_ERROR and
(...,0,..) else.

Instead of using 1 and 0, use ldap code LDAP_OPERATIONS_ERROR and LDAP_SUCCESS,

See also: Ticket 47388 - RFE to implement RFC4533 -ver2

Reviewed by William (Thanks!!!)

Pushed to master:
2309c38..0157eb1 master -> master
commit 0157eb1

Metadata Update from @firstyear:
- Issue assigned to nhosoi
- Issue set to the milestone:

5 years ago

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/1963

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

2 years ago

Login to comment on this ticket.