Re: 2.3.18 syncrepl problem

[Pierangelo Masarati <ando@sys-net.it>]

On Fri, 2006-01-20 at 09:27 +0400, Dmitry Melekhov wrote:

> Very strange...
> Do yuo have any suggestions?

Yes; going back to your previous posting,

syncrepl rid=1
    provider=ldap://backup.p98.belkam.com:389
    type=refreshOnly
    interval=00:00:10:00
    searchbase="o=Aspec,c=RU"
    filter="(objectClass=belkamAccount)"
                scope=sub
                attrs="dn,cn,sn,uid,email"
                schemachecking=off
                bindmethod=simple
                binddn="uid=admin,ou=People,o=Aspec,c=RU"
                credentials=eeadewewe

In general, I suggest sticking with existing examples, to see if things
work; then, starting from them, one can play with configuration to
change details.  attrs="*,+" is the default, which means that
operational attributes must be present.
In fact, you need to sync (at least some) operational attributes; "+"
would be fine in your case as well, but at least "entryUUID" and
"entryCSN" should be there.  I'm not sure, but I think "objectClass"
would help, and "structuralObjectClass" could be of interest, although
the consumer, with objectClass available, would be able to generate it
if required.  If needed, you might add "modifyTimestamp" and
"modifiersName", for friendly access to modification indicators.

p.




Ing. Pierangelo Masarati
Responsabile Open Solution
OpenLDAP Core Team

SysNet s.n.c.
Via Dossi, 8 - 27100 Pavia - ITALIA
http://www.sys-net.it
------------------------------------------
Office:   +39.02.23998309          
Mobile:   +39.333.4963172
Email:    pierangelo.masarati@sys-net.it
------------------------------------------