Always max connections (30) reached in rsync rocky main mirror

It is 3 days after release of Rocky 9.

However, I did not see any mirror has finished to rsync from the rocky mirror.

# all CN mirrors is empty      # only folders, all folders is empty
# Many US mirrors is not finished, such as          # lack of folders: isos, live, plus   # 403 err

I can see the main rsync mirror of rockylinux is reached max connections.

@ERROR: max connections (30) reached -- try again later

Is there any suggestion to avoid this again while next release?


Yes the team will have it working differently for the future from what I’ve seen. Basically they will restrict syncing with the main Rocky mirror to tier-1 mirrors only. All other mirrors below tier-1 will then have to sync with their local mirrors. More or less, there will be a kind of sync hierachy.

Yes, sync hierachy is a good solution.

By the way, we may put the other folders except ‘isos’ into pub/rocky in several days before release. It will be helpful avoid having too much data to sync after release. That is, If pre-relaesed other folders, then, only the isos and the changed files of pre-relaesed folders are need to sync. The data size will be much less.

we are also experiencing this issue.
We’ve become a public mirror recently.
@iwalker how could I know if I’m “tier-1” mirror, and if not, how could I become one?


@z.linha I expect the Rocky team will decide based on the mirror specs on whether it will be able to be tier-1 or not. For example, 10gbps instead of 1gbps network speed for example, or the amount of bandwidth. It hasn’t been decided yet, but these types of parameters are likely to be taken into account. Obviously larger operators who can sync faster are most likely to be tier-1. Smaller will rather be lower tiers.

1 Like