Mister Anonyme wrote:
> Date: Thu, 3 Sep 2009 13:30:30 -0600 > From: rmeggins@xxxxxxxxxx > To: fedora-directory-users@xxxxxxxxxx > Subject: Re: How to restore replica admin in the master> If those docs need to be corrected, please send us the links. Also note > that in 8.0: > If you want to add new schema to an existing instance, you must add the > files to /etc/dirsrv/slapd-instancename/schema, then restart the server > for the schema changes to take effect > /etc/dirsrv/schema is only for new instances only - existing servers > don't use these files > schema files are not replicated - the only way to replicate schema is to > add the new schema over LDAPI read docs from here: http://www.redhat.com/docs/manuals/dir-server/ <%20%20http://www.redhat.com/docs/manuals/dir-server/>About schemas, I read here:http://www.redhat.com/docs/manuals/dir-server/cli/8.0/Configuration_Command_File_Reference-Core_Server_Configuration_Reference.html#Configuration_Command_File_Reference-Server_Configuration___Overview-LDIF_Configuration_Files___Location <%20http://www.redhat.com/docs/manuals/dir-server/cli/8.0/Configuration_Command_File_Reference-Core_Server_Configuration_Reference.html#Configuration_Command_File_Reference-Server_Configuration___Overview-LDIF_Configuration_Files___Location>And here:http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Extending_the_Directory_Schema.html <%20http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Extending_the_Directory_Schema.html>I just can't find the description you just put here ? It must be hidden in some obscure area... or I need eyeglasses.> With 8.1 you have the ability to add schema files, then have the server > reload them without having to restart the server, but the schema files> added by copying them to the server instance schema directory will still> not be replicated. Yep exactly. > > > > Later, when I added a new bunch of users, I noticed that the > > replication was stopped between two masters, but not between master > > and slaves. I tried to understand why it doesn't work anymore > Anything in the errors or access logs?Yep, it happens each time I add a new schema on a replicated system. Here are the logs:Master A:[02/Sep/2009:10:15:17 -0400] NSMMReplicationPlugin - agmt="cn=INSTANCE_prod" (SERVER:389): Unable to acquire replica: there is no replicated area "dc=name,dc=domain,dc=net" on the consumer server. Replication is aborting. [02/Sep/2009:10:15:17 -0400] NSMMReplicationPlugin - agmt="cn=INSTANCE_prod" (SERVER:389): Incremental update failed and requires administrator action [02/Sep/2009:11:44:09 -0400] NSMMReplicationPlugin - agmt="cn=INSTANCE_netscaperoot" (SERVER:389): Unable to acquire replica: there is no replicated area "o=netscaperoot" on the consumer server. Replication is aborting. [02/Sep/2009:11:44:09 -0400] NSMMReplicationPlugin - agmt="cn=INSTANCE_netscaperoot" (SERVER:389): Incremental update failed and requires administrator actionMaster B:[02/Sep/2009:11:15:18 -0400] NSMMReplicationPlugin - conn=73 op=3 replica="unknown": Unable to acquire replica: error: no such replica [02/Sep/2009:11:44:10 -0400] NSMMReplicationPlugin - conn=3572 op=3 replica="unknown": Unable to acquire replica: error: no such replicaTake note that it happens only when I add a new schema and I restart the server. When I restart without adding a new schema, I don't have that kind of error, it just works. What I did is I copy the schema in /etc/dirsrv/slapd-XXXX/schema and then I restart the server. However, in the lab, at the installation, I initially copied the schema (before the the start of the replication) and started both servers and it works flawlessly.> > and I found out by reading in 8.1 (the next version that we don't use > > it yet) documentation that it says that we need to stop all > > replication before adding a new schema file. > Can you provide a link to the documentation? There you go:http://www.redhat.com/docs/manuals/dir-server/8.1/admin/dynamically-reloading-schema.html#reloading-schema-with-replication <%20http://www.redhat.com/docs/manuals/dir-server/8.1/admin/dynamically-reloading-schema.html#reloading-schema-with-replication>
How did you stop and restart replication?
> I'm not really sure what's going on here. I seriously doubt there is > any data corruption happening (unless there is some disk/hardware > failure). I would first suggest you check your errors log in > /var/log/dirsrv/slapd-instancename/errorsMaybe ? I find it very weird too but the fact is: I'm able to reproduce the issue in the lab. More than one. I already verified the logs and I also enabled the verbose mode by doing this:dn: cn=config changetype: modify replace: nsslapd-errorlog-level nsslapd-errorlog-level: 8192Thanks!------------------------------------------------------------------------New! Open Hotmail faster on the new MSN homepage! <http://go.microsoft.com/?linkid=9677400>------------------------------------------------------------------------ -- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
<<attachment: smime.p7s>>
-- 389 users mailing list 389-users@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/fedora-directory-users
