[Freeipa-users] Replica cannot be reinitialized after upgrade

2017-05-11 Thread Goran Marik
Hi, After an upgrade to Centos 7.3.1611 with “yum update", we started seeing the following messages in the logs: “”” May 9 21:58:28 inf01 ns-slapd[4323]: [09/May/2017:21:58:28.519724479 +] NSMMReplicationPlugin - changelog program - agmt="cn=cloneAgreement1-inf02.dev.ecobee.com-pki-tomcat"

Re: [Freeipa-users] Replica cannot be reinitialized after upgrade

2017-05-15 Thread Maciej Drobniuch
Hi Goran Exact same issue here with the same troubleshooting steps taken(I've tried to reinitialize the replicas with success msg) - no luck so far. I've additionally have run ipa_check_consistency script: FreeIPA servers:ipa1 ipa2 ipa3STATE =

Re: [Freeipa-users] Replica cannot be reinitialized after upgrade

2017-05-15 Thread Ludwig Krispenz
The messages you see could be transient messages, and if replication is working than this seems to be the case. If not we would need more data to investigate: deployment info, relicaIDs of all servers, ruvs, logs,. Here is some background info: there are some scenarios where a csn could no

Re: [Freeipa-users] Replica cannot be reinitialized after upgrade

2017-05-18 Thread Goran Marik
Thanks Ludwig for the suggestion and thanks to Maciej for the confirmation from his end. This issue is happening for us for several weeks, so I don’t think this is a transient problem. What is the best way to sanitize the logs without removing useful info before sending them your way? Will the

Re: [Freeipa-users] Replica cannot be reinitialized after upgrade

2017-05-19 Thread Ludwig Krispenz
On 05/18/2017 10:13 PM, Goran Marik wrote: Thanks Ludwig for the suggestion and thanks to Maciej for the confirmation from his end. This issue is happening for us for several weeks, so I don’t think this is a transient problem. What is the best way to sanitize the logs without removing useful