Re: 2.3.18 syncrepl problem

[Dmitry Melekhov <dm@belkam.com>]

Pierangelo Masarati wrote:

> Well, if "sync" doesn't yield any useful info, it appears the problem is
> not with syncrepl itself; you should look somewhere else.  What I usually
> do is: have a run with "stats" only, to get some overview of what
> operations are being performed and what's the outcome.  Then, based on
> that, I refine the log level, to avid digging into -1 from the beginning. 
> Since sync replication involves (at least) two servers, I'd keep an eye on
> both; the issue can be in both, or it may be the result of incorrect
> interaction.
>
>  

Thank you!

On master server I see that slave issued search, but no results returned.

Jan 19 14:34:18 backup slapd[6094]: conn=11 op=1 SRCH 
base="o=aspec,c=ru" scope=2 deref=0 filter="(objectClass=belkamAccount)"
Jan 19 14:34:18 backup slapd[6094]: conn=11 op=1 SRCH attr=* +
Jan 19 14:34:18 backup slapd[6094]: slap_global_control: unavailable 
control: 1.3.6.1.4.1.4203.1.9.1.1
Jan 19 14:34:18 backup slapd[6094]: send_ldap_result: conn=11 op=1 p=3
Jan 19 14:34:18 backup slapd[6094]: send_ldap_result: err=0 matched="" 
text=""
Jan 19 14:34:18 backup slapd[6094]: send_ldap_response: msgid=2 tag=101 
err=0
Jan 19 14:34:18 backup slapd[6094]: conn=11 op=1 SEARCH RESULT tag=101 
err=0 nentries=0 text=
Jan 19 14:34:18 backup slapd[6094]: daemon: activity on 1 descriptor
Jan 19 14:34:18 backup slapd[6094]: daemon: activity on:
Jan 19 14:34:18 backup slapd[6094]:  18r


Colud you tell what this unavailable control messages mean?