On 02/06/2017 05:14 PM, Giorgio Biacchi wrote:
On 02/06/2017 04:54 PM, Rob Crittenden wrote:
Giorgio Biacchi wrote:
Hi list,
I have this message in the logs:
Feb 6 16:43:10 dc01 ns-slapd: [06/Feb/2017:16:43:10.157801305 +0100]
NSMMReplicationPlugin -
On 02/06/2017 04:54 PM, Rob Crittenden wrote:
Giorgio Biacchi wrote:
Hi list,
I have this message in the logs:
Feb 6 16:43:10 dc01 ns-slapd: [06/Feb/2017:16:43:10.157801305 +0100]
NSMMReplicationPlugin -
agmt="cn=masterAgreement1-dc02.myorg.local-pki-tomcat" (dc02:389): Data
required to
Giorgio Biacchi wrote:
> Hi list,
> I have this message in the logs:
>
> Feb 6 16:43:10 dc01 ns-slapd: [06/Feb/2017:16:43:10.157801305 +0100]
> NSMMReplicationPlugin -
> agmt="cn=masterAgreement1-dc02.myorg.local-pki-tomcat" (dc02:389): Data
> required to update replica has been purged from the
I have been having replication issues since the update to RHEL6.4 and
389-ds-base-1.2.11.15-12.
It is entirely possible that we have more than just 1 problem.
Frequently we seeing errors in our replication monitoring indicating: -1
Incremental update has failed and requires administrator
On Jun 5, 2013, at 5:26 PM, Rich Megginson wrote:
On 06/05/2013 05:49 PM, JR Aquino wrote:
I have been having replication issues since the update to RHEL6.4 and
389-ds-base-1.2.11.15-12.
It is entirely possible that we have more than just 1 problem.
Frequently we seeing errors in our
On 06/05/2013 07:20 PM, JR Aquino wrote:
On Jun 5, 2013, at 5:26 PM, Rich Megginson wrote:
On 06/05/2013 05:49 PM, JR Aquino wrote:
I have been having replication issues since the update to RHEL6.4 and
389-ds-base-1.2.11.15-12.
It is entirely possible that we have more than just 1 problem.
