I didn't have long to look but I went ahead and raise the connection limit
on the one I bet you were hitting. Let me know if this solved it for you.
If not I can look closer later.
On Fri, Jul 12, 2024 at 5:56 PM Jonathan Wright
Ankesh,
There aren't capacity issues in terms of bandwidth but we may need to raise the connection limit (again). The limit is mostly arbitrary.
I'll do this ASAP but I can't look into this at the exact moment. We also currently have one of our rsync mirrors out of the mix right now for maintenance which has the others under increased load (but still nowhere near the bandwidth capacity on our pipes).
With the EOL of CentOS 7 it's very likely the unique number of connections hitting the rsync mirrors is up. I'll look into this ASAP and let you know when it is remedied.
On Fri, Jul 12, 2024 at 5:51 PM Ankesh Anand
wrote: Hi Peter
Maybe the rsync repo of Alma might be overwhelmed? Tried rsync from other places yet which have ok status?
We've actually used a conditional approach to this. Whenever the main rsync repo has capacity problems, we try it from one of the other mirrors supporting rsync.
Best Regards, Ankesh
On Sat, Jul 13, 2024 at 4:03 AM Petar Smilajkov < peconi@cloudpropeller.com> wrote:
Howdy,
I am seeing my mirror (and a lot of others https://mirrors.almalinux.org/) once again in Expired status ...
When trying to rsync, I get:
/usr/bin/rsync -avSH --exclude='.~tmp~' --delete-delay --delay-updates rsync://rsync.repo.almalinux.org/almalinux/ /var/www/html/almalinux/
*@ERROR: max connections (555) reached -- try again laterrsync error: error starting client-server protocol (code 5) at main.c(1680) [Receiver=3.1.3]*
I am wondering if there's an issue w/ rsync running on rsync.repo.almalinux.org/almalinux/
Please advise. Thank you.
Note, my TIME file has 1720766184 (16 hours ago), but it should be 1720821179 (40 minutes ago).
Thanks,
*Petar Smilajkov* CEO & Chief Architect Cloud Propeller, Inc. +1 (614) 639-1122 // cell +1 (614) 467-3596 // e-fax +1 (614) 505-9555 // support ☁ cloudpropeller.com // web
📅 *Book a Meeting* https://calendly.com/cloudpropeller/quick30 with me...
On Fri, May 3, 2024 at 1:35 PM Petar Smilajkov < peconi@cloudpropeller.com> wrote:
Awesome.
Thank you Jonathan!
Warmest regards and all the best with 9.4!
Cheers.
*Petar Smilajkov* CEO & Chief Architect Cloud Propeller, Inc.
On Fri, May 3, 2024 at 1:13 PM Jonathan Wright
wrote: The TIME and timestamp.txt file updater scripts weren't working on one of the 3 rsync sources. This is fixed now and the "expired" status should resolve itself within 15 minutes of your next sync that grabs the update files.
Thanks for bringing this to our attention.
On Fri, May 3, 2024 at 11:59 AM Petar Smilajkov < peconi@cloudpropeller.com> wrote:
Hi all,
Got Jonathan's announcement tabout 9.4 syncing soon (yay), however, when I checked Cloud Propeller's mirror status on the website - it shows as expired.
This is odd since we are syncing, or so I believe.
*[Cursory check]*
- https://rsync.repo.almalinux.org/almalinux/TIME and - https://mirror.cloudpropeller.com/almalinux/TIME
*... MATCH*
*[Bash/Dash script]*
*root@mirror:/home/mirror# cat sync-alma.sh*
#/bin/dash > > # Define where you want the mirror-data to be on your mirror > > *RSYNCSOURCE=rsync://rsync.repo.almalinux.org/almalinux/ > http://rsync.repo.almalinux.org/almalinux/* > BASEDIR=/var/www/html/almalinux/ >
# Ensure target dir exists > if [ ! -d ${BASEDIR} ]; then > warn "${BASEDIR} does not exist yet, trying to create it..." > mkdir -p ${BASEDIR} || fatal "Creation of ${BASEDIR} failed." > fi > > # Do some internal timestamping for CP purposes
rm ${BASEDIR}_cp_last_sync.txt > date -u > ${BASEDIR}_rsync_in_progress.txt > date >> ${BASEDIR}_rsync_in_progress.txt > > # Sync
/usr/bin/flock -n /tmp/almalinux_rsync.lock -c "/usr/bin/rsync -avSH > --no-owner -f 'R .~tmp~' --progress --stats --delete-delay --delay-updates > --delete-excluded ${*RSYNCSOURCE*} ${BASEDIR}" > > # Update internal timestamping for CP purposes
date -u > ${BASEDIR}_cp_last_sync.txt > date >> ${BASEDIR}_cp_last_sync.txt > cp ${BASEDIR}_cp_last_sync.txt > /var/www/html/almalinux-isos/_cp_last_sync.txt >
*[Script run]*
*mirror@mirror:~$ ./sync-alma.sh*
receiving file list ... > 193970 files to consider > ./ > 8.9/isos/x86_64/ > deleting _rsync_in_progress.txt > deleting 8.9/isos/x86_64/_cp_last_sync.txt
Number of files: 193,970 (reg: 193,086, dir: 812, link: 72) > Number of created files: 0 > Number of deleted files: 2 (reg: 2) > Number of regular files transferred: 0 > Total file size: 740,447,001,014 bytes > Total transferred file size: 0 bytes > Literal data: 0 bytes > Matched data: 0 bytes > File list size: 10,541,632 > File list generation time: 0.552 seconds > File list transfer time: 0.000 seconds > Total bytes sent: 52 > Total bytes received: 10,541,661
> sent 52 bytes received 10,541,661 bytes 1,109,654.00 bytes/sec > total size is 740,447,001,014 speedup is 70,239.72
*[Dir check]*
*root@mirror:/var/www/html/almalinux# du -sh* > > *612G *.
*root@mirror:/var/www/html/almalinux# ls -lhat*
total 152K > -rw-rw-r-- 1 mirror mirror 64 May 3 12:53 _cp_last_sync.txt > drwxrwxr-x 13 mirror mirror 4.0K May 3 12:53 . > > *-rw-r--r-- 1 mirror mirror 11 May 2 12:51 TIME*-rw-r--r-- 1 > mirror mirror 32 May 2 12:51 timestamp.txt > drwxrwxr-x 2 mirror mirror 4.0K Apr 12 07:37 8.8 > drwxrwxr-x 2 mirror mirror 4.0K Apr 12 07:37 9.2 > drwxr-xr-x 22 mirror mirror 4.0K Mar 6 07:57 .. > drwxr-xr-x 20 mirror mirror 4.0K Dec 21 05:43 9.3 > drwxr-xr-x 20 mirror mirror 4.0K Dec 21 04:58 8.9 > lrwxrwxrwx 1 mirror mirror 70 Nov 21 11:24 > almalinux-release-latest-8.ppc64le.rpm -> > 8.9/BaseOS/ppc64le/os/Packages/almalinux-release-8.9-1.el8.ppc64le.rpm > lrwxrwxrwx 1 mirror mirror 66 Nov 21 11:24 > almalinux-release-latest-8.s390x.rpm -> > 8.9/BaseOS/s390x/os/Packages/almalinux-release-8.9-1.el8.s390x.rpm > lrwxrwxrwx 1 mirror mirror 70 Nov 21 11:24 > almalinux-release-latest-8.aarch64.rpm -> > 8.9/BaseOS/aarch64/os/Packages/almalinux-release-8.9-1.el8.aarch64.rpm > lrwxrwxrwx 1 mirror mirror 68 Nov 21 11:24 > almalinux-release-latest-8.x86_64.rpm -> > 8.9/BaseOS/x86_64/os/Packages/almalinux-release-8.9-1.el8.x86_64.rpm > lrwxrwxrwx 1 mirror mirror 3 Nov 21 11:24 8 -> 8.9 > lrwxrwxrwx 1 mirror mirror 68 Nov 13 10:39 > almalinux-repos-latest-9.ppc64le.rpm -> > 9.3/BaseOS/ppc64le/os/Packages/almalinux-repos-9.3-1.el9.ppc64le.rpm > lrwxrwxrwx 1 mirror mirror 71 Nov 13 10:39 > almalinux-gpg-keys-latest-9.ppc64le.rpm -> > 9.3/BaseOS/ppc64le/os/Packages/almalinux-gpg-keys-9.3-1.el9.ppc64le.rpm > lrwxrwxrwx 1 mirror mirror 70 Nov 13 10:39 > almalinux-release-latest-9.ppc64le.rpm -> > 9.3/BaseOS/ppc64le/os/Packages/almalinux-release-9.3-1.el9.ppc64le.rpm > lrwxrwxrwx 1 mirror mirror 64 Nov 13 10:39 > almalinux-repos-latest-9.s390x.rpm -> > 9.3/BaseOS/s390x/os/Packages/almalinux-repos-9.3-1.el9.s390x.rpm > lrwxrwxrwx 1 mirror mirror 67 Nov 13 10:39 > almalinux-gpg-keys-latest-9.s390x.rpm -> > 9.3/BaseOS/s390x/os/Packages/almalinux-gpg-keys-9.3-1.el9.s390x.rpm > lrwxrwxrwx 1 mirror mirror 66 Nov 13 10:39 > almalinux-release-latest-9.s390x.rpm -> > 9.3/BaseOS/s390x/os/Packages/almalinux-release-9.3-1.el9.s390x.rpm > lrwxrwxrwx 1 mirror mirror 68 Nov 13 10:39 > almalinux-repos-latest-9.aarch64.rpm -> > 9.3/BaseOS/aarch64/os/Packages/almalinux-repos-9.3-1.el9.aarch64.rpm > lrwxrwxrwx 1 mirror mirror 71 Nov 13 10:39 > almalinux-gpg-keys-latest-9.aarch64.rpm -> > 9.3/BaseOS/aarch64/os/Packages/almalinux-gpg-keys-9.3-1.el9.aarch64.rpm > lrwxrwxrwx 1 mirror mirror 70 Nov 13 10:39 > almalinux-release-latest-9.aarch64.rpm -> > 9.3/BaseOS/aarch64/os/Packages/almalinux-release-9.3-1.el9.aarch64.rpm > lrwxrwxrwx 1 mirror mirror 66 Nov 13 10:39 > almalinux-repos-latest-9.x86_64.rpm -> > 9.3/BaseOS/x86_64/os/Packages/almalinux-repos-9.3-1.el9.x86_64.rpm > lrwxrwxrwx 1 mirror mirror 69 Nov 13 10:39 > almalinux-gpg-keys-latest-9.x86_64.rpm -> > 9.3/BaseOS/x86_64/os/Packages/almalinux-gpg-keys-9.3-1.el9.x86_64.rpm > lrwxrwxrwx 1 mirror mirror 68 Nov 13 10:39 > almalinux-release-latest-9.x86_64.rpm -> > 9.3/BaseOS/x86_64/os/Packages/almalinux-release-9.3-1.el9.x86_64.rpm > lrwxrwxrwx 1 mirror mirror 3 Nov 13 10:11 9 -> 9.3 > -rw-rw-r-- 1 mirror mirror 5.1K Oct 16 2023 RPM-GPG-KEY-AlmaLinux > -rw-rw-r-- 1 mirror mirror 3.5K Oct 12 2023 > RPM-GPG-KEY-AlmaLinux-legacy > lrwxrwxrwx 1 mirror mirror 72 Aug 24 2023 > almalinux-release-synergy-latest-9.noarch.rpm -> > 9/extras/x86_64/os/Packages/almalinux-release-synergy-9-2.el9.noarch.rpm > lrwxrwxrwx 1 mirror mirror 72 Aug 24 2023 > almalinux-release-synergy-latest-8.noarch.rpm -> > 8/extras/x86_64/os/Packages/almalinux-release-synergy-8-2.el8.noarch.rpm > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 8.7 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 9.0 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 9.1 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 8.3 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 8.4 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 8.5 > drwxrwxr-x 2 mirror mirror 4.0K Aug 3 2023 8.6 > lrwxrwxrwx 1 mirror mirror 21 May 16 2022 > RPM-GPG-KEY-AlmaLinux-8 -> RPM-GPG-KEY-AlmaLinux > -rw-rw-r-- 1 mirror mirror 3.1K Apr 19 2022 RPM-GPG-KEY-AlmaLinux-9 >
This should just work, as it has in the past.
*Can anyone spot an issue here?*
Thanks in advance.
*Petar Smilajkov* CEO & Chief Architect Cloud Propeller, Inc. +1 (614) 639-1122 // cell +1 (614) 467-3596 // e-fax +1 (614) 505-9555 // support ☁ cloudpropeller.com // web _______________________________________________ Mirror mailing list -- mirror@lists.almalinux.org To unsubscribe send an email to mirror-leave@lists.almalinux.org
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat https://chat.almalinux.org/almalinux/messages/@jonathan
_______________________________________________ Mirror mailing list -- mirror@lists.almalinux.org To unsubscribe send an email to mirror-leave@lists.almalinux.org
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat https://chat.almalinux.org/almalinux/messages/@jonathan
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat https://chat.almalinux.org/almalinux/messages/@jonathan