Thanks Robert,

I've added the ability for MetaCPAN to have puppet secrets so have kept it
private and made the change to the new hostname.

We currently have up to 5 separate servers running rrr-watcher - but each
with an additional nightly full rsync

Thanks

Leo




On Sat, Oct 25, 2025 at 4:10 PM Robert Spier <[email protected]> wrote:

>
> I've sent you a special hostname to switch to.  If you could avoid making
> it public, that would be appreciated.  If there's no way to not make it
> public, we'll need to do some more complicated configuration.
>
> Are you doing more than 1 rsync at a time?
>
> -R
>
> On Sat, Oct 25, 2025 at 10:24 AM Leo Lapworth <[email protected]> wrote:
>
>> Hi Ask,
>>
>> MetaCPAN is getting quite a few of these:
>>
>> ```
>> @ERROR: max connections (10) reached -- try again later
>> rsync error: error starting client-server protocol (code 5) at
>> main.c(1666) [Receiver=3.1.2]
>> ```
>>
>> Anything you can do on that?
>>
>> Cheers
>>
>> Leo
>>
>>
>>
>> On Wed, Oct 22, 2025 at 8:26 PM Olaf Alders <[email protected]>
>> wrote:
>>
>>> I just restarted the rrr-client. Let's see if that helps. We already run
>>> a daily rsync to ensure nothing has been missed via rrr.
>>>
>>> Olaf
>>>
>>> On Wed, Oct 22, 2025, at 3:14 PM, Ask Bjørn Hansen wrote:
>>>
>>>
>>> We rebuilt the primary CPAN mirror source over the last weeks. (It’s now
>>> in Kubernetes and operated via git, including the current version of the
>>> various decades old tools maintaining metadata).
>>>
>>> I tried pretty hard to make sure the RRR recent data was accurate, but I
>>> had to relearn a bit about how it works in the process so the files had
>>> some erroneous epochs for a few days.
>>>
>>> Maybe metacpan needs a onetime full rsync (or the rrr client restarted?)
>>>
>>>
>>> Ask
>>>
>>>
>>> --
>>> Olaf Alders
>>>
>>> 📮 [email protected]
>>> 🚀 https://prettygoodping.com
>>>
>>>
>>>

Reply via email to