[389-users] 1.2.8 Windows sync agreement initialization
Carsten Grzemba
grzemba at contac-dt.de
Tue Feb 8 11:17:47 UTC 2011
No, it is not a normaly behaviour.
I had a similar problem because my winsync plugin was not registered after a restart. I have fixed the problem that I have changed the plugin dependencies. But I do not know if it is the right way.
see thread "[389-devel] Problem using winsync API" in December 2010:
...
I have removed from win sync plugin:
nsslapd-plugin-depends-on-named: Multimaster Replication Plugin
from the plugin configuration, and instead added on the Multimaster Plugin config
nsslapd-plugin-depends-on-named: test Winsync API
...
Regards
Carsten
----- Ursprüngliche Nachricht -----
Von: Juan Carlos Camargo Carrillo <juancar at eprinsa.es>
Datum: Dienstag, 8. Februar 2011, 11:49
Betreff: [389-users] 1.2.8 Windows sync agreement initialization
An: 389-users at lists.fedoraproject.org
> Hi,
>
> I'm running 389-ds version 1.2.8 on CentOS 5x and configured a windows sync agreement against a 2003 active directory server. Everything works as expected. However, everytime I restart the directory server (service dirsrv restart) I need to reinitialize the windows agreement. Messages such as "Replica has no update vector. It has never been initialized" continously filling the error log until I proceed with the init. But the replica was initialized and conversations between 389 and AD were working nicely. And what I would not want at all is to lose any changes made on either side as a result of the initialization process. My question then, is this the normal behaviour ?
>
> Thanks!
> > --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users
-------------- next part --------------
A non-text attachment was scrubbed...
Name: grzemba.vcf
Type: text/x-vcard
Size: 233 bytes
Desc: Card for Carsten Grzemba <grzemba at contac-dt.de>
URL: <http://lists.fedoraproject.org/pipermail/389-users/attachments/20110208/6f027377/attachment.vcf>
More information about the 389-users
mailing list