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
# Ensure target dir exists
if [ ! -d ${BASEDIR} ]; then
rm ${BASEDIR}_cp_last_sync.txt
/usr/bin/flock -n /tmp/almalinux_rsync.lock -c "/usr/bin/rsync -avSH
date -u > ${BASEDIR}_cp_last_sync.txt
*[Script run]* *mirror@mirror:~$ ./sync-alma.sh* receiving file list ...
Number of files: 193,970 (reg: 193,086, dir: 812, link: 72)
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
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
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:
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
Hi Jonathan, Additionally the cert for rsync.repo.almalinux.org its expired: % nmap -p 443 --script ssl-cert rsync.repo.almalinux.org Starting Nmap 7.95 ( https://nmap.org ) at 2024-05-03 13:17 -04 Nmap scan report for rsync.repo.almalinux.org (23.111.153.218) Host is up (0.12s latency). rDNS record for 23.111.153.218: repo-us-01.almalinux.org PORT STATE SERVICE 443/tcp open https | ssl-cert: Subject: commonName=rsync.repo.almalinux.org | Subject Alternative Name: DNS:atl.rsync.repo.almalinux.org, DNS: rsync.repo.almalinux.org | Issuer: commonName=R3/organizationName=Let's Encrypt/countryName=US | Public Key type: rsa | Public Key bits: 4096 | Signature Algorithm: sha256WithRSAEncryption | Not valid before: 2024-01-26T14:37:36 | Not valid after: 2024-04-25T14:37:35 | MD5: c6de:f0d8:7ea8:facb:c4aa:f3a6:3e46:c2c0 |_SHA-1: ff0d:a7b9:7572:07fe:39c2:5145:6221:d84a:14c8:8dbf Nmap done: 1 IP address (1 host up) scanned in 2.11 seconds Regards El 03-05-2024, 13:13:23, Jonathan Wright <jonathan@almalinux.org> escribió:
Yes we're going to be removing the certs from all hosts behind rsync.repo.almalinux.org - there's no need for them there. The web side of them is really just to make browsing and checking on them easier. On Fri, May 3, 2024 at 12:20 PM Roberto Alvarado <mirrors@hnd.cl> wrote:
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
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... <https://cloudpropeller.com/> On Fri, May 3, 2024 at 1:35 PM Petar Smilajkov <peconi@cloudpropeller.com> 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:
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 <anand.ankesh67@gmail.com> wrote:
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
Thank you both for the heads up... For the moment so I am not out of sync, I switched to https://mirror.facebook.net/almalinux/ - if anyone has bandwidth or higher limits on things, it should be them :) Also I get to hit them via IPv6 at over 100 Gbit so that should be fun :) Jonathan, FYI - I added another Cloud Propeller mirror via pull request <https://github.com/AlmaLinux/mirrors/pull/1070>. Once that one is approved - we will be contributing 2 total :) This one is also behind an Ohio IX <https://ohioix.net/> internet exchange w/ *dual* *100 G's *to local peers - so it should be quite useful in Ohio. Warmest regards, *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... <https://cloudpropeller.com/> On Fri, Jul 12, 2024 at 6:56 PM Jonathan Wright <jonathan@almalinux.org> wrote:
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 <jonathan@almalinux.org> wrote:
-- Jonathan Wright AlmaLinux Foundation Mattermost: chat <https://chat.almalinux.org/almalinux/messages/@jonathan>
Limit up worked, I can sync again from the official one as well. 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... <https://cloudpropeller.com/> On Fri, Jul 12, 2024 at 7:00 PM Jonathan Wright <jonathan@almalinux.org> wrote:
It seems that the status of the Cloud Propeller mirror might be outdated, as the sync times match, meaning the sync is actually happening. I would recommend checking the sync logs for any errors. It’s likely just a delay in updating the status on the website. We discussed a similar situation during a meeting about https://wellpin.io/ with colleagues — the system showed outdated information, but everything was actually working fine.
participants (5)
-
andrew＠wellpin.io -
Ankesh Anand -
Jonathan Wright -
Petar Smilajkov -
Roberto Alvarado