Am Tuesday, 18. February 2014 schrieb Jan Kowalsky: > Am Monday, 17. February 2014 schrieb Jan Kowalsky: > > Am Saturday, 15. February 2014 schrieb Rich Megginson: > > > On 02/14/2014 05:20 PM, Jeroen van Meeuwen (Kolab Systems) wrote: > > > > On 2014-02-14 23:03, Jan Kowalsky wrote: > > > >> On 2014-02-14 22:15, Rich Megginson wrote: > > > >>> On 02/14/2014 01:57 PM, Jan Kowalsky wrote: > > > Jan, please file a 389 ticket - I doubt we are going to figure this out > > > until someone with some familiarity with the 389 code and gdb can > > > reproduce this issue. > > I'm still not shure that I don't do something completely wrong ;-) ... But now I know that I did. I Used different domains in the "dn" and in the replicaroot. This is obviously not possible. dn: cn=replica,cn=dc\=example\,dc\=com,cn=mapping tree,cn=config nsds5replicaroot: dc=domain,dc=com I got confused because replication worked before restart. So the problem was - besides the one BCAC an unsufficiant error message ;-) > For excluding that's a kolab-specific problem I reproduced it again on a > fresh 389-ds installation. All ldif commands used for setting up database, > suffix and replication I added as a attachment to the ticket: > > https://fedorahosted.org/389/ticket/47705 > i close the bug. Thanks and Regards Jan -- 389 users mailing list 389-users@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/389-users
