No sign of replication being broken, but we do get this reasonably regularly.
Would it be worth reporting anywhere or any other info the might be useful?
Thanks for the resonse,
Orion
On 2/3/25 13:27, Mark Reynolds wrote:
> Hi Orion,
>
> These two messages just mean that the replication session did not close/end
> correctly. It is harmless on its own - unless replication is broken. We have
> been seeing these errors recently when a replica is being released, but no way
> to reproduce it yet.
>
> Not sure about the content-sync-plugin warning as I'm not familiar with that
> plugin.
>
> Mark
>
>
> On 2/3/25 10:44 AM, Orion Poplawski via 389-users wrote:
>> [02/Feb/2025:20:57:56.553507369 -0700] - ERR - decode_repl_ext_response -
>> decoding failed: response_code (Ok) ruv_bervals (Ok) data_guid (Ok) data
>> (Ok) bvdata (No data)
>> [02/Feb/2025:20:57:56.555181048 -0700] - ERR - NSMMReplicationPlugin -
>> release_replica - agmt="cn=IPA2-IPA1" (IPA1:389): Unable to parse the
>> response to the endReplication extended operation.
>
--
Orion Poplawski
he/him/his - surely the least important thing about me
Manager of IT Systems 720-772-5637
NWRA, Boulder Office FAX: 303-415-9702
3380 Mitchell Lane orion@nwra.com
Boulder, CO 80301 https://www.nwra.com/
No comments:
Post a Comment