My team is running a sync job of Rawhide and ELN composes into Red Hat Beaker instance for testing.
It's essentially running a rsync rsync://dl0[123].fedoraproject.org/... /mnt/... to pull in a new compose.
rsync rsync://dl0[123].fedoraproject.org/... /mnt/...
This has been working well from hosts in BOS datacenter, but now we need to migrate to IAD2 and the same code is no longer working.
This is the error:
$ rsync --list-only rsync://dl01.fedoraproject.org/fedora-eln rsync: [Receiver] failed to connect to dl01.fedoraproject.org (38.145.60.22): Connection refused (111) rsync error: error in socket IO (code 10) at clientserver.c(138) [Receiver=3.2.3]
$ nmap dl01.fedoraproject.org -p 873 -AA Starting Nmap 7.92 ( https://nmap.org ) at 2024-04-23 10:19 EDT Nmap scan report for dl01.fedoraproject.org (38.145.60.22) Host is up (0.0071s latency). rDNS record for 38.145.60.22: dl-iad01.fedoraproject.org PORT STATE SERVICE VERSION 873/tcp closed rsync Service detection performed. Please report any incorrect results at https://nmap.org/submit/ . Nmap done: 1 IP address (1 host up) scanned in 0.40 seconds
The external IP is 209.132.179.5
Is this blocked somehow on Fedora side? Should it be done in some different way? Can you advise on what we should check to find out where the connection is blocked?
Metadata Update from @phsmoura: - Issue priority set to: Waiting on Assignee (was: Needs Review) - Issue tagged with: medium-gain, medium-trouble, ops
So, our servers are also in IAD2, so perhaps there is a hairpin issue going on.
Can you reach dl01.iad2.fedoraproject.org from there? ( 10.3.163.49 )
We may need to talk to networking folks to see whats going on.
Using the internal IPs have worked. Thanks for the pointer!
Metadata Update from @lsedlar: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Log in to comment on this ticket.