[Date Prev][Date Next]
[Chronological]
[Thread]
[Top]
syncrepl mangles entryUUID
Hi...
there was a brief thread on this in april "Subject: syncrepl entryUUID
syncrepl strangeness." but with no explanation posted. I am seeing
exactly this behaviour. the replicated entryUUID is base64 encoded and
when it is decoded it looks like garbage. Here is a real example:
dn: cn=admin1,ou=admins,ou=itss,dc=my-domain,dc=com
structuralObjectClass: person
entryCSN: 20040726102738Z#000001#00#000000
entryUUID:: FZjcyHM5ECiT9N5IILZ7Lg==
subschemaSubentry: cn=Subschema
hasSubordinates: FALSE
the entryUUID decodes to:
ÜÈs9(ôÞH ¶{.
Is this the expected behaviour in a consumer replica? I'm running 2.2.14
on the consumer (2.2.13 on the provider). No extra config on the
provider, the consumer syncrepl section looks like:
syncrepl rid=1
provider=ldap://<provider host>
updatedn="cn=manager,dc=my-domain,dc=com"
binddn="cn=manager,dc=my-domain,dc=com"
bindmethod=simple
credentials=secret
searchbase="dc=my-domain,dc=com"
type=refreshonly
interval=00:00:01:00
Apart from this strange value of the entryUUID attribute the replication
works fine.
GREG
--
Greg Matthews
iTSS Wallingford 01491 692445