Re: [389-users] Replication trouble when promoting dedicated Consumer to Multiple master

[Roland Schwingel <Roland.Schwingel@xxxxxxxxxxxxx>]

Hi Reinhard,

Thanks for your reply!!


389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx wrote on
14.07.2011 16:25:10:

> From: Reinhard Nappert <rnappert@xxxxxxxxxxx>
> To: "General discussion list for the 389
Directory server project." 
> <389-users@xxxxxxxxxxxxxxxxxxxxxxx>
> Date: 14.07.2011 16:28
> Subject: Re: [389-users] Replication trouble
when promoting 
> dedicated Consumer to Multiple master
> Sent by: 389-users-bounces@xxxxxxxxxxxxxxxxxxxxxxx
> 
> Do a   ldapsearch -b 'nsuniqueid=ffffffff-ffffffff-ffffffff-
> ffffffff,dc=mydomain,dc=com' -D <directory manager> -w <password>
-s
> base objectclass=nstombstone
>  
> This gives you all the configured (history) of
replication ids. The 
> following is the output in my setup.
>  
> dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,o=base
> objectClass: top
> objectClass: nsTombstone
> objectClass: extensibleobject
> nsds50ruv: {replicageneration} 4df7a107000000010000
> nsds50ruv: {replica 1 ldap://yale:389} 4df7a396000000010000 4e19ad950000000100
>  00
> nsds50ruv: {replica 3 ldap://norquay:389} 4df7a39d000000030000 4e1605650000000
>  30000
> nsds50ruv: {replica 4 ldap://mustrum:389} 4df7a3a0000000040000 4dfb93650000000
>  40000
> nsds50ruv: {replica 2 ldap://louise:389} 4df7a39a000000020000 4e171a0700000002
>  0000
> o: base
> nsruvReplicaLastModified: {replica 1 ldap://yale:389} 00000000
> nsruvReplicaLastModified: {replica 3 ldap://norquay:389} 00000000
> nsruvReplicaLastModified: {replica 4 ldap://mustrum:389} 00000000
> nsruvReplicaLastModified: {replica 2 ldap://louise:389} 00000000
>              
                     
              /\ 
>              
                     
               |
>              
                     
         replication-id
>  
I issued that command on my server Server
C. I get the following results:

# extended LDIF
#
# LDAPv3
# base <nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,dc=mydomain,dc=com>
with scope baseObject
# filter: objectclass=nstombstone
# requesting: ALL
#

# ffffffff-ffffffff-ffffffff-ffffffff,
mydomain.com
dn: nsuniqueid=ffffffff-ffffffff-ffffffff-ffffffff,
dc=mydomain,dc=com
objectClass: top
objectClass: nsTombstone
objectClass: extensibleobject
nsds50ruv: {replicageneration} 4bf162c6000000010000
nsds50ruv: {replica 2 ldap://server-c.mydomain.com:389}
4cd3fa1e00000002
 0000 4e1ef45b000000020000
nsds50ruv: {replica 3 ldap://server-d.mydomain.de:389}
nsds50ruv: {replica 1 ldap://server-b.mydomain.de:389}
4bf16732000000010
 000 4e1ffa3e000000010000
dc: mydomain
nsruvReplicaLastModified: {replica 2
ldap://server-c.mydomain.com:389} 4
 e1ef445
nsruvReplicaLastModified: {replica 3
ldap://server-d.mydomain.de:389} 00000000
nsruvReplicaLastModified: {replica 1
ldap://server-b.mydomain.de:389} 4e
 1ffa26

# search result
search: 2
result: 0 Success

# numResponses: 2
# numEntries: 1

When I look at it I see that replica id 3 is assigned
to my server-d
(which should get that replica id). I started over
deleted my server-d
assigned it replica id 4 but nothing changes.

I also cannot get rid of the informations for server-d
in that nsuniqueid
how can I do that?

Thanks,

Roland
--
389 users mailing list
389-users@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/389-users