1.2.8 Windows sync agreement initialization

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Carten,

Thanks for your answer. In my case there's not a testing plugin but the
one that governs the win synchronization. As I am a sort of deep newbie
can you tell me where should I made those modifications in an out-of-the
box configuration, so I can retry your guidelines?

Regards!

El mar, 08-02-2011 a las 12:17 +0100, Carsten Grzemba escribi?:

> 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: 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
> --
> 389 users mailing list
> 389-users at lists.fedoraproject.org
> https://admin.fedoraproject.org/mailman/listinfo/389-users


-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.fedoraproject.org/pipermail/389-users/attachments/20110208/59fbe9ec/attachment.html 


[Index of Archives]     [Fedora User Discussion]     [Older Fedora Users]     [Fedora Announce]     [Fedora Package Announce]     [EPEL Announce]     [Fedora News]     [Fedora Cloud]     [Fedora Advisory Board]     [Fedora Education]     [Fedora Security]     [Fedora Scitech]     [Fedora Robotics]     [Fedora Maintainers]     [Fedora Infrastructure]     [Fedora Websites]     [Anaconda Devel]     [Fedora Devel Java]     [Fedora Legacy]     [Fedora Desktop]     [Fedora Fonts]     [ATA RAID]     [Fedora Marketing]     [Fedora Management Tools]     [Fedora Mentors]     [Fedora Package Review]     [Fedora R Devel]     [Fedora PHP Devel]     [Kickstart]     [Fedora Music]     [Fedora Packaging]     [Centos]     [Fedora SELinux]     [Fedora Legal]     [Fedora Kernel]     [Fedora QA]     [Fedora Triage]     [Fedora OCaml]     [Coolkey]     [Virtualization Tools]     [ET Management Tools]     [Yum Users]     [Tux]     [Yosemite News]     [Yosemite Photos]     [Linux Apps]     [Maemo Users]     [Gnome Users]     [KDE Users]     [Fedora Tools]     [Fedora Art]     [Fedora Docs]     [Maemo Users]     [Asterisk PBX]     [Fedora Sparc]     [Fedora Universal Network Connector]     [Fedora ARM]

  Powered by Linux