On Wed, 2017-11-22 at 13:30 +, Paul Whitney wrote:
> We have a few new servers deployed with 389-ds-base version 1.3.5.10-
> 21. These servers were deployed in an environment where auto-
> patching happens and we forgot to disable that feature.
>
> Overnight the servers were updated to 389-ds
On Wed, 2017-11-22 at 13:20 +, Paul Whitney wrote:
> We are seeing an issue with our replication agreements on 389DS.
> When we look at the Console, we used to be able to tell when was the
> last successful attempt to replicate and end of said replication.
> Same thing for Initialization stat
We have a few new servers deployed with 389-ds-base version 1.3.5.10-21. These
servers were deployed in an environment where auto-patching happens and we
forgot to disable that feature.
Overnight the servers were updated to 389-ds-base version 1.3.6.1-19. All of the
upgraded servers are now
We are seeing an issue with our replication agreements on 389DS. When we look
at the Console, we used to be able to tell when was the last successful attempt
to replicate and end of said replication. Same thing for Initialization state.
With the new 389DS (currently using version 1.3.5.10-21)
