> On 1 Mar 2024, at 10:47, Marc Sauton wrote:
>
> there was an old RHEL-7.4 and RHEL-7.5 issue and fix in
> 1.3.5.10-20 replication halt - pending list first CSN not committed, pending
> list increasing
> https://bugzilla.redhat.com/1460070
> https://github.com/389ds/389-ds-base/issues/2346
there was an old RHEL-7.4 and RHEL-7.5 issue and fix in
1.3.5.10-20 replication halt - pending list first CSN not committed,
pending list increasing
https://bugzilla.redhat.com/1460070
https://github.com/389ds/389-ds-base/issues/2346
but you have a (somehow) more recent version,
> FYI: There is a list of pending operations to ensure that the RUV is not
> updated while an older operation is not yet completed. And I suspect that
> you hit a bug about this list. I remember that we fixed something in that
> area a few years ago ...
I think I found it, or something closely
Thanks, Pierre and Thierry.
After quite some time of poring over these debug logs, I've found some
anomalies and they seem like they're matching up with the idea that the
affected replica isn't updating its own RUV correctly.
The logs show a change being made, and it lists the CSN of the
On 2/29/24 06:08, Karlderletzte wrote:
On 2/28/24 08:54, karlderletzte wrote:
Am 27.02.24 um 22:41 schrieb Samuel Sieb:
On 2/27/24 07:58, karlderletzte wrote:
two days ago, i installed fedora jam 39 on an external drive. This
runs successfully.
BUT after restart and plug off the external
On 2/29/24 09:08, Karlderletzte wrote:
On 2/28/24 08:54, karlderletzte wrote:
Am 27.02.24 um 22:41 schrieb Samuel Sieb:
On 2/27/24 07:58, karlderletzte wrote:
two days ago, i installed fedora jam 39 on an external drive. This
runs successfully.
BUT after restart and plug off the external
On 2/28/24 08:54, karlderletzte wrote:
Am 27.02.24 um 22:41 schrieb Samuel Sieb:
On 2/27/24 07:58, karlderletzte wrote:
two days ago, i installed fedora jam 39 on an external drive. This
runs successfully.
BUT after restart and plug off the external drive Grub from my
internal drive does
Hi William,
>I don't think it's going backwards. What I'm trying to rule out is that
the replica is failing to advance its max CSN in the RUV being used to
compare.
Since you see CSN 4 months after the RUV, I think that your suspicion is
right:
The RUV is not updated any more.
FYI: There is a
On 2/29/24 05:12, William Faulk wrote:
Might be worth re-reading
Well, I still don't really know the details of the replication process.
I have deduced that changes originated on a replica seem to prompt that replica
to start a replication process with its peers, but I don't really know what
