Hi Harald,
What version of DS are you running ?
We have a reproducer (not systematic) for versions before
https://bugzilla.redhat.com/show_bug.cgi?id=1516309 but we have not
reproduced it since then, you may need to upgrade.
best regards
thierry
On 03/12/2018 05:10 PM, Ludwig Krispenz wrote:
Hi,
to get rid of this ruv entry with replicaid 7 you could try to run the
cleanallruv task directly. On any server (and onöy on one) run
ldapmodify ..... -D "cn=directory manager"
|dn: cn=clean 7, cn=cleanallruv, cn=tasks, cn=config changetype: add
objectclass: extensibleObject replica-base-dn: <your suffix >
replica-id: 7 replica-force-cleaning: yes |
|But I would like to understand how you did get in|to this state, we
have seen this occasionly, but have no reproducer. Unfortunately the
csn for replicaid 7 is from Jan, 19th 2017 11:01:16 - so you will
probably not remember
||
On 03/12/2018 03:55 PM, Harald Dunkel via FreeIPA-users wrote:
Hi folks,
somehow my ipa servers became out of sync. ipa4 has an
additional host entry, not known on the others. On
examining I stumbled over this:
[root@ipa0 ~]# ipa-replica-manage clean-dangling-ruv
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
These RUVs are dangling and will be removed:
Host: ipabak.ac.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Host: ipa1.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Host: ipa0.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Host: ipa3.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Host: ipa4.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Host: ipa2.example.de
RUVs:
id: 11, hostname: ipabak.ac.example.de
CS-RUVs:
Proceed with cleaning? [no]: yes
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
Clean the Replication Update Vector for ipabak.ac.example.de:389
Background task created to clean replication data. This may take a
while.
This may be safely interrupted with Ctrl+C
Cleanup task created
[root@ipa0 ~]# ipa-replica-manage clean-dangling-ruv
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
No dangling RUVs found
[root@ipa0 ~]# ipa-replica-manage list-ruv
unable to decode: {replica 7} 58809c7c000300070000 58809c7c000300070000
Replica Update Vectors:
ipa0.example.de:389: 12
ipa2.example.de:389: 5
ipa1.example.de:389: 4
ipa4.example.de:389: 8
ipa3.example.de:389: 6
ipabak.ac.example.de:389: 13
Certificate Server Replica Update Vectors:
ipa0.example.de:389: 1095
ipa2.example.de:389: 97
ipa1.example.de:389: 96
ipabak.ac.example.de:389: 1090
The ruvs are the same on all 6 hosts (AFAICS), so I wonder how I could
fix this?
Every helpful comment is highly appreciated.
Harri
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to
freeipa-users-le...@lists.fedorahosted.org
--
Red Hat GmbH,http://www.de.redhat.com/, Registered seat: Grasbrunn,
Commercial register: Amtsgericht Muenchen, HRB 153243,
Managing Directors: Charles Cachera, Michael Cunningham, Michael O'Neill, Eric
Shander
_______________________________________________
FreeIPA-users mailing list -- freeipa-users@lists.fedorahosted.org
To unsubscribe send an email to freeipa-users-le...@lists.fedorahosted.org
