<html>
<head>
<style>
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
</style>
</head>
<body class='hmmessage'>
<br><br>> Date: Thu, 3 Sep 2009 13:30:30 -0600<br>> From: rmeggins@redhat.com<br>> To: fedora-directory-users@redhat.com<br>> Subject: Re: [389-users] How to restore replica admin in the master<br><br><br><pre>> If those docs need to be corrected, please send us the links. Also note <br>> that in 8.0:<br>> If you want to add new schema to an existing instance, you must add the <br>> files to /etc/dirsrv/slapd-instancename/schema, then restart the server <br>> for the schema changes to take effect<br>> /etc/dirsrv/schema is only for new instances only - existing servers <br>> don't use these files<br>> schema files are not replicated - the only way to replicate schema is to <br>> add the new schema over LDAP<br><br>I read docs from here:<br><br><a href="%20%20http://www.redhat.com/docs/manuals/dir-server/">http://www.redhat.com/docs/manuals/dir-server/</a><br></pre><br>About schemas, I read here:<br><a href="%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"> 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</a><br><br>And here:<br><a href="%20http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Extending_the_Directory_Schema.html">http://www.redhat.com/docs/manuals/dir-server/ag/8.0/Extending_the_Directory_Schema.html</a><br><br><br><br>I just can't find the description you just put here ? It must be hidden in some obscure area... or I need eyeglasses.<br><br><br><br>> With 8.1 you have the ability to add schema files, then have the server <br>> reload them without having to restart the server, but the schema files <br>> added by copying them to the server instance schema directory will still <br>> not be replicated.<br><br><br>Yep exactly.<br><br><br>> ><br>> > Later, when I added a new bunch of users, I noticed that the <br>> > replication was stopped between two masters, but not between master <br>> > and slaves. I tried to understand why it doesn't work anymore<br>> Anything in the errors or access logs?<br><br>Yep, it happens each time I add a new schema on a replicated system. Here are the logs:<br><br><br>Master A:<br><br>[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. <br>[02/Sep/2009:10:15:17 -0400]
NSMMReplicationPlugin - agmt="cn=INSTANCE_prod" (SERVER:389):
Incremental update failed and requires administrator action<br>[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. <br>[02/Sep/2009:11:44:09 -0400]
NSMMReplicationPlugin - agmt="cn=INSTANCE_netscaperoot" (SERVER:389):
Incremental update failed and requires administrator action<br><br><br>Master B:<br><br>[02/Sep/2009:11:15:18 -0400] NSMMReplicationPlugin - conn=73 op=3
replica="unknown": Unable to acquire replica: error: no such replica<br>[02/Sep/2009:11:44:10 -0400] NSMMReplicationPlugin - conn=3572 op=3
replica="unknown": Unable to acquire replica: error: no such replica<br><br>Take 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. <br><br>What I did is I copy the schema in /etc/dirsrv/slapd-XXXX/schema and then I restart the server. <br><br>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.<br><br><br>> > and I found out by reading in 8.1 (the next version that we don't use <br>> > it yet) documentation that it says that we need to stop all <br>> > replication before adding a new schema file. <br>> Can you provide a link to the documentation?<br><br>There you go:<br><a href="%20http://www.redhat.com/docs/manuals/dir-server/8.1/admin/dynamically-reloading-schema.html#reloading-schema-with-replication"> http://www.redhat.com/docs/manuals/dir-server/8.1/admin/dynamically-reloading-schema.html#reloading-schema-with-replication</a><br><br><br>> I'm not really sure what's going on here. I seriously doubt there is <br>> any data corruption happening (unless there is some disk/hardware <br>> failure). I would first suggest you check your errors log in <br>> /var/log/dirsrv/slapd-instancename/errors<br><br><br>Maybe ? 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:<br><br><pre>dn: cn=config<br>changetype: modify<br>replace: nsslapd-errorlog-level<br>nsslapd-errorlog-level: 8192<br><br></pre>Thanks!<br><br><br><br /><hr />New! Open Hotmail faster on the new <a href='http://go.microsoft.com/?linkid=9677400' target='_new'>MSN homepage!</a></body>
</html>