Elisa Pellegrini wrote:
Hi!
to configure 2 suppliers to use multi master replication over SSL, I
configure both of them to use SSL. (I use the same CA that I import in
CAcert in Manage certificate for the 2 suppliers and I create a
certificate for both of them)
Then in the guide say :
-Config
Hi!
to configure 2 suppliers to use multi master replication over SSL, I
configure both of them to use SSL. (I use the same CA that I import in
CAcert in Manage certificate for the 2 suppliers and I create a
certificate for both of them)
Then in the guide say :
-Configure your consumer server
Elisa Pellegrini wrote:
Hi!
if i'm configruring multimaster replication is necessary to enable ssl
in both supplier than consumer.
Ok, but that is not a requirement for replication to work.
My question is: the CA that give certificate for supplier and consumer
in necessary to be the same CA?
N
Hi!
if i'm configruring multimaster replication is necessary to enable ssl
in both supplier than consumer. My question is: the CA that give
certificate for supplier and consumer in necessary to be the same CA?
thanks
--
Fedora-directory-users mailing list
Fedora-directory-users@redhat.com
http
I'd love to know how your RUV could be missing. I wonder if whatever
problem left you with mismatched generation ID still persists, it seemed
odd that happened after a network outage. If the RUV entry was missing
that would explain it, that's where the generation ID of the local data
is store
"Can you show us the RUV from the server that produces the csnplCommit
error?"
All I get is "ldap_search: No such object"
Replica Configuration -- in it's current state.
version: 1
dn: cn=replica,cn="dc=,dc=com",cn=mapping tree,cn=config
objectClass: nsDS5Replica
objectClass: top
nsDS5ReplicaRoot
Wendt, Trevor wrote:
##
"The generation ID errors sound like real errors, but those should be
resolvable with the correct replica re-initialization done."
I've tried re-initializing the consumer multiple times with no success.
The NSMMReplicationPlugin - replica_check_for_dat
"Are you thinking this is an 'error' ? It looks fine to me. 2300
entries/s processed. The hit ratio won't fill out until the load has
been going for a few cycles, which it may never get to with a small
number of entries."
It get's up to 100% then it backs down to 0% and holds at a processed
number
Wendt, Trevor wrote:
I'm having some significant issues getting my multi-master servers
synchronized after a network outage this past weekend. First I was
getting:
error--> NSMMReplicationPlugin - agmt="cn=srv1-to-srv2" (srv2:389):
Replica has a different generation ID than the local data.
> I'm having some significant issues getting my multi-master servers
> synchronized after a network outage this past weekend. First I was
> getting:
>
> error--> NSMMReplicationPlugin - agmt="cn=srv1-to-srv2" (srv2:389):
> Replica has a different generation ID than the local data.
>
> Then after
Eugene M Liberman wrote:
[EMAIL PROTECTED] wrote on 11/06/2006 03:56:20 PM:
> Eugene M Liberman wrote:
> >
> > I am testing a multi master replication. The replication agreements
> > between host a and b are setup. When I add an entry to a replicated
> > subtree from host a the new entry is al
[EMAIL PROTECTED] wrote on
11/06/2006 03:56:20 PM:
> Eugene M Liberman wrote:
> >
> > I am testing a multi master replication. The replication agreements
> > between host a and b are setup. When I add an entry to a replicated
> > subtree from host a the new entry is also visible on host b when
Eugene M Liberman wrote:
I am testing a multi master replication. The replication agreements
between host a and b are setup. When I add an entry to a replicated
subtree from host a the new entry is also visible on host b when I
browse host b. This works as I expect, however, when I delete thi
I am testing a multi master replication.
The replication agreements between host a and b are setup. When I add an
entry to a replicated subtree from host a the new entry is also visible
on host b when I browse host b. This works as I expect, however, when I
delete this entry from host b login, the
Susan wrote:
--- Richard Megginson <[EMAIL PROTECTED]> wrote:
If the consumer can verify and validate the suppliers cert, as in
certificate based auth, then it should work. Otherwise, you can just
use regular SSL replication with password auth.
OK, I understand. I don't care about
--- Richard Megginson <[EMAIL PROTECTED]> wrote:
> If the consumer can verify and validate the suppliers cert, as in
> certificate based auth, then it should work. Otherwise, you can just
> use regular SSL replication with password auth.
OK, I understand. I don't care about cert-based SSL, so
Susan wrote:
I got this from the manual:
Note
Replication configured over SSL with certificate-based authentication will fail in the following
cases:
* If the supplier's certificate is a self-signed certificate.
_
Is that still the case for FDS? Is there any way to get it workin
I got this from the manual:
Note
Replication configured over SSL with certificate-based authentication will fail
in the following
cases:
* If the supplier's certificate is a self-signed certificate.
_
Is that still the case for FDS? Is there any way to get it working using
self-
18 matches
Mail list logo
