Yes, our 5.0.5 testing channel release is not yet a Release Candidate phase and there are know broken bits and bobs - and we have changed (upgraded by years) a very great deal of our libraries. But we are getting there and a replication related issue is about to be fixed, but it is partnered with another I am about to move onto:
See the following GitHub issue:
However they concern our current testing and I did not think we had broken replication at 5.0.5-0 but it would not be surpirsing. The state of our current testing channel rpm release is covered in the following forum thread:
So you are rather on the edge here. However replication is my current focus again and I’m working through the related issues before we release 5.0.6-0 hopefully.
But the error relates to supervisorctl which we are planing to cut-out entirely in the current testing channel phase:
as part of our current Milestone here:
Never seen that: but again we are at our first open testers release here, having just moved on from Developers only. Hang in there and it would be great to have your feedback now you are already on 5.0.5-0 and keep an eye out for the next and following testing versions to see if this rather involved subsystem starts to behave better. We have just had a lot of ‘churn’ of late in order to modernise our setup, but bit by bit.
We have just released 5.0.6-0 into the current testing channel:
and I’m pretty sure we have returned all prior replication capability, though we likely still have some performance/robustness improvements etc to address. Just wanted to note here given your interest in this capability and your feedback in this area here on the forum.