On 2/25/25 12:38 PM, Orion Poplawski wrote:
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?
Hi Orion,
There have already been several cases opened on the issue. So I see no
need in opening yet another ticket on it. Unless you have a systematic
reproducer :-) We have debated removing the error message (or moving it
to repl logging) since it's been harmless in all the cases we've seen so
far.
Mark
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.
--
Identity Management Development Team
--
_______________________________________________
389-users mailing list -- 389-users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to 389-users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/389-users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
