Fedora directory users - Nov 2006 - Re: Problems Setting up 1.0.3

"Chris St. Pierre" <stpierre@NebrWesleyan.edu> kirjoitti:
> 
> I guess you did say, though, that the problem _only_ happens to
> SSL-enabled machines, not that it _always_ happens to SSL-enabled
> machines.  Still, hope this helps you root out the problem.
>
> On Thu, 2 Nov 2006, Richard Megginson wrote:
> 
> > It appears that the permission problem only happens with servers that
were
> > configured to use SSL in fds102 and upgraded to fds103.  Can anyone
confirm the
> > problem occurred in a system not using SSL?

My server (laptop) had not ever been configured to use SSL.


--
mike

After the update from 1.0.2 to 1.0.3, I had some replication problems,
and it appears that one of my four servers was no longer properly
replicating to the others.  I recreated the replication agreements and
reinitialized the replications, but now I''m getting some strange
errors in the error logs of the borked server:

[03/Nov/2006:08:54:23 -0600] NSMMReplicationPlugin - Total update
aborted: Replication agreement for "agmt="cn="Replication to
zeppo.nebrwesleyan.edu"" (zeppo:389)" can not be updated while
the
replica is disabled
[03/Nov/2006:08:54:23 -0600] NSMMReplicationPlugin - (If the suffix is
disabledyou must enable it then restart the server for replication to
take place).

This happens right after I try to re-init the replication agreements.

I''m hoping that the fix is as simple as enabling the replication
agreements; how do I do that (w/o console)?

Also, it says I have to restart "the server"; which server?  Consumer
or producer?

Thanks!

Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University

Chris St. Pierre wrote:
> After the update from 1.0.2 to 1.0.3, I had some replication problems,
> and it appears that one of my four servers was no longer properly
> replicating to the others.  I recreated the replication agreements and
> reinitialized the replications, but now I''m getting some strange
> errors in the error logs of the borked server:
>
> [03/Nov/2006:08:54:23 -0600] NSMMReplicationPlugin - Total update
> aborted: Replication agreement for "agmt="cn="Replication to
> zeppo.nebrwesleyan.edu"" (zeppo:389)" can not be updated
while the
> replica is disabled
> [03/Nov/2006:08:54:23 -0600] NSMMReplicationPlugin - (If the suffix is
> disabledyou must enable it then restart the server for replication to
> take place).
>
> This happens right after I try to re-init the replication agreements.
>
> I''m hoping that the fix is as simple as enabling the replication
> agreements; how do I do that (w/o console)?
>
> Also, it says I have to restart "the server"; which server? 
Consumer
> or producer?
>   
The consumer.  The supplier thinks the consumer suffix is disabled.  It 
might be as simple a fix as restarting the consumer.
> Thanks!
>
> Chris St. Pierre
> Unix Systems Administrator
> Nebraska Wesleyan University
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

On Fri, 3 Nov 2006, Richard Megginson wrote:
> The consumer.  The supplier thinks the consumer suffix is disabled.  It
might
> be as simple a fix as restarting the consumer.
That changed the error message.

[03/Nov/2006:11:21:24 -0600] NSMMReplicationPlugin -
agmt="cn="Replication to chico.nebrwesleyan.edu""
(chico:389): Replica
has a different generation ID than the local data.

I get that every 3-5 seconds WRT replication to the same host.  When I
restarted the problematic host, it reinitialized all of its
replication agreements; do I need to reinitialize the agreement the
other way, too?

Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University

I went ahead and re-inited pretty much all of my replication
agreements, and now I''m getting the error below on the other three
servers, but not on the one that originally had the problem.  Do I
just need to keep re-initing agreements until I hit the magic
combination?  Is there a better solution?  (Please say yes!)

Chris St. Pierre
Unix Systems Administrator
Nebraska Wesleyan University

On Fri, 3 Nov 2006, Chris St. Pierre wrote:
>On Fri, 3 Nov 2006, Richard Megginson wrote:
>
>> The consumer.  The supplier thinks the consumer suffix is disabled.  It
might
>> be as simple a fix as restarting the consumer.
>
>That changed the error message.
>
>[03/Nov/2006:11:21:24 -0600] NSMMReplicationPlugin -
>agmt="cn="Replication to chico.nebrwesleyan.edu""
(chico:389): Replica
>has a different generation ID than the local data.
>
>I get that every 3-5 seconds WRT replication to the same host.  When I
>restarted the problematic host, it reinitialized all of its
>replication agreements; do I need to reinitialize the agreement the
>other way, too?
>
>Chris St. Pierre
>Unix Systems Administrator
>Nebraska Wesleyan University
>
>
>--
>Fedora-directory-users mailing list
>Fedora-directory-users@redhat.com
>https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

Chris St. Pierre wrote:
> On Fri, 3 Nov 2006, Richard Megginson wrote:
>
>   
>> The consumer.  The supplier thinks the consumer suffix is disabled.  It
might
>> be as simple a fix as restarting the consumer.
>>     
>
> That changed the error message.
>
> [03/Nov/2006:11:21:24 -0600] NSMMReplicationPlugin -
> agmt="cn="Replication to chico.nebrwesleyan.edu""
(chico:389): Replica
> has a different generation ID than the local data.
>
> I get that every 3-5 seconds WRT replication to the same host.  When I
> restarted the problematic host, it reinitialized all of its
> replication agreements; do I need to reinitialize the agreement the
> other way, too?
>   
You should not need to, but that is what the error message is telling 
you.  Different generation ID means that the replica needs to be 
reinitialized.
> Chris St. Pierre
> Unix Systems Administrator
> Nebraska Wesleyan University
>
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>

Chris St. Pierre wrote:
> I went ahead and re-inited pretty much all of my replication
> agreements, and now I''m getting the error below on the other three
> servers, but not on the one that originally had the problem.  Do I
> just need to keep re-initing agreements until I hit the magic
> combination?  Is there a better solution?  (Please say yes!)
>   
Once you reinitialize one, you have to reinitialize the others.

I''m afraid I can''t offer a better solution because I
don''t understand
why this happened in the first place.
> Chris St. Pierre
> Unix Systems Administrator
> Nebraska Wesleyan University
>
> On Fri, 3 Nov 2006, Chris St. Pierre wrote:
>
>   
>> On Fri, 3 Nov 2006, Richard Megginson wrote:
>>
>>     
>>> The consumer.  The supplier thinks the consumer suffix is disabled.
It might
>>> be as simple a fix as restarting the consumer.
>>>       
>> That changed the error message.
>>
>> [03/Nov/2006:11:21:24 -0600] NSMMReplicationPlugin -
>> agmt="cn="Replication to chico.nebrwesleyan.edu""
(chico:389): Replica
>> has a different generation ID than the local data.
>>
>> I get that every 3-5 seconds WRT replication to the same host.  When I
>> restarted the problematic host, it reinitialized all of its
>> replication agreements; do I need to reinitialize the agreement the
>> other way, too?
>>
>> Chris St. Pierre
>> Unix Systems Administrator
>> Nebraska Wesleyan University
>>
>>
>> --
>> Fedora-directory-users mailing list
>> Fedora-directory-users@redhat.com
>> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>>
>>     
>
> --
> Fedora-directory-users mailing list
> Fedora-directory-users@redhat.com
> https://www.redhat.com/mailman/listinfo/fedora-directory-users
>