[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
RE: delta sync repl out of sync
Hi,
When I run that query, I got content of acess log, including those can't be updated to the consumer. The entry contains:
# 20091212000001.000002Z, accesslog
dn: reqStart=20091212000001.000002Z,cn=accesslog
objectClass: auditModify
reqStart: 20091212000001.000002Z
reqEnd: 20091212000001.000003Z
reqType: modify
reqSession: 165
reqAuthzID: cn=Manager,dc=my,dc=domain
reqDN: uid=1234567,dc=my,dc=domain
reqResult: 0
reqMod: visible:= yes
reqMod: modifiersName:= cn=root,dc=my,dc=domain
reqMod: modifyTimestamp:= 20091212000000Z
reqMod: entryCSN:= 20091212000001.260843Z#000000#001#000000
Is there anything wrong with the entry?
Thanks a lot.
/ST Wong
________________________________
--On Wednesday, December 09, 2009 11:58 PM +0800 "ST Wong (ITSC)"
<ST@itsc.cuhk.edu.hk> wrote:
> Oops, the space/line feed as caused by the "<-----" I typed in the
> posting. Original configuration file looks like this:
>
> [snipped]
> logbase="cn=accesslog"
> logfilter="(&(objectClass=auditWriteObject)(reqResult=0))"
> syncdata=accesslog
> [snipped]
>
> BTW, just note that all 'pending' changes can be synchronized to
> consumer by restarting slapd.
And what happens if you run that query against the master as the syncrepl
DN?
I.e.,
ldapsearch -x -D "<syncrepl dn>" -W <syncrepl passwd> -b "cn=accesslog -H
ldap://<master> "(&(objectClass=auditWriteObject)(reqResult=0))"
--Quanah
--
Quanah Gibson-Mount
Principal Software Engineer
Zimbra, Inc
--------------------
Zimbra :: the leader in open source messaging and collaboration