Mikael Kermorgant wrote:
That's really odd. Do you get that at startup? That indicates some sort of configuration problem. You could try starting the server with /usr/lib/dirsrv/slapd-instance/start-slapd -d 8192 to see if there is more detailed information.Hello,On Fri, Oct 2, 2009 at 10:40 PM, Rich Megginson <[email protected]> wrote:First ones were the day after a schema modification on the master which had not been weel propagated on the slaves.How did you modify the schema on the master?Via the console, by adding an attribute. Had to copy the schema files to the slaves later.Were there any messages in the errors logs on the supplier or consumers about not being able to replicate the schema?Yep, there were some : [23/Sep/2009:10:59:58 +0200] NSMMReplicationPlugin - agmtlist_add_callback: Can't start agreement "cn=supann0& - bsupann01,cn=replica,cn="dc=dede, dc=deded, dc=fr",cn=mapping tree,cn=config"
And many of these : [23/Sep/2009:14:37:13 +0200] NSMMReplicationPlugin - agmt="cn=bsupann01" (192:389): Replica has a different generation ID than the local data. [23/Sep/2009:14:37:17 +0200] NSMMReplicationPlugin - agmt="cn=bsupann01" (192:389): Replica has a different generation ID than the local data.
This usually means the consumer has not been initialized.
However, I now really want to migrate to some safer virtualisation environment. Maybe a bit over pessimistic but I'm affraid of the FC11 domU on centos dom0... Regards, Mikael -- 389 users mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-directory-users
smime.p7s
Description: S/MIME Cryptographic Signature
-- 389 users mailing list [email protected] https://www.redhat.com/mailman/listinfo/fedora-directory-users
