I'm involved with a fairly new mirror hosted by the BYU Computer Science
Department. This is a private mirror for the 22.214.171.124/255.255.254.0
subnet. I would like to subscribe to the mirrors mailing list.
PGP Fingerprint: 8A17 B57C 6879 1863 DE55 8012 AB4D 6098 8826 6868
Greetings. I have been reviewing the rsync logs for Fedora's master
mirror servers (download*.fedora.redhat.com), and am seeing some unusual
behavior from your mirror alviss. In the 5d8h between April 12 and
April 17, alviss synced (successfully) 3380 times. I believe this is
just a bit excessive. I understand wishing to keep up-to-date, but as
the content on the master mirrors changes at most 4 times a day, syncing
something every 2 minutes simply adds extra load to our servers and to
Instead of syncing each of the content directories separately as you do:
# Syncs # rsync module
Could you instead sync the top-level fedora-linux-development, or
fedora-linux-updates modules, and not their subdirectories, and sync
less frequently (say, once an hour at most)? Fedora-linux-development
is updated at most once a day (typically around 5am Eastern Standard
Time US). Syncing it more often is pointless.
For comparison, you sync 3x more often than even Red Hat's internal
mirrors and kernel.org, which themselves sync 3x more often than nearly
any other mirror. (yes, your 3380 syncs vs most mirrors under 300 in
the same time period).
I also see you sync using download.fedora.redhat.com. Because this is
name is a DNS round-robin, could you instead chose one to sync from
(such as download3.fedora.redhat.com), such that you consistently sync
from the same server?
Furthermore, we have instituted a "tiering" policy, whereby we're asking
mirrors to help reduce load on our masters by syncing to a "Tier 1"
mirror, as listed here:
Please consider syncing from a Tier 1 mirror instead of
Thanks for your longstanding support of Fedora. It is greatly
Fedora Mirror Wrangler
Linux Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
Our organization would be come a mirror site for Fedora OS.
So we want to register on the mirror list.
At this time, we have registered
<https://admin.fedoraproject.org/mirrormanager> site using by following
1. Site name: National University of Mongolia
2. Site password: sodbileg
Our IP address: 126.96.36.199
Location: Mongolia, Ulaanbaatar city.
Please inform email as soon as possible.
Please guide to become a public mirror site.
Sodbileg SH., PhD.,
Head of Academic Affairs,
School of Information technology,
National University of Mongolia
IP address: ftp://188.8.131.52/so/fedora/
Location (country): Mexico
Outbound bandwidth available for the mirror: 80 MBPS
Departamento de Computación
Servidor de Correo DIE/FI/UNAM (http://mail.fi-b.unam.mx)
Going to be running a private mirror for now. If'n folks could approve
me onto the mailing list at the appropriate moment, that'd be good.
Ph: 373-7599 x84679; Room 301-231, Chemistry Building (or shout loudly)
＃Please give the report to me it is write mail in English.
石川 大樹（Hiroki Ishikawa）
mail : ishikawa(a)tsukuba.wide.ad.jp
I was looking for the Fedora Core 3 distribution for PPC and I was not
able to find it anywhere.
Can you tell me any site where I can download it?
Thank you in advance
Satellite Navigation and Positioning
Looks like you were hitting our mirror on April 11. I don't show anything before or after that.
./access_log-20090412.gz:184.108.40.206 - - [11/Apr/2009:11:37:44 -0400] "GET /pub/rpmfusion/nonfree/fedora/updates/10/i386/repodata/repomd.xml HTTP/1.1" 200 2520 "-" "urlgrabber/3.0.0 yum/3.2.21"
./access_log-20090412.gz:220.127.116.11 - - [11/Apr/2009:11:37:46 -0400] "GET /pub/rpmfusion/free/fedora/updates/10/i386/repodata/repomd.xml HTTP/1.1" 200 2520 "-" "urlgrabber/3.0.0 yum/3.2.21"
Your IP wasn't in the range that we were blocking so that wasn't it. The return path to your IP does go a different route but that shouldn't matter.
Type escape sequence to abort.
Tracing the route to c-76-109-153-227.hsd1.fl.comcast.net (18.104.22.168)
1 ge-6-13.r04.asbnva01.us.bb.gin.ntt.net (22.214.171.124) [AS 2914] 36 msec 232 msec 20 msec
2 xe-1.level3.asbnva01.us.bb.gin.ntt.net (126.96.36.199) [AS 2914] 8 msec
188.8.131.52 [AS 3356] 8 msec 8 msec
3 vlan79.csw2.washington1.level3.net (184.108.40.206) [AS 3356] 8 msec
vlan69.csw1.washington1.level3.net (220.127.116.11) [AS 3356] 20 msec
vlan79.csw2.washington1.level3.net (18.104.22.168) [AS 3356] 12 msec
4 ae-91-91.ebr1.washington1.level3.net (22.214.171.124) [AS 3356] 12 msec 12 msec 20 msec
5 ae-2.ebr3.atlanta2.level3.net (126.96.36.199) [AS 3356] 36 msec 24 msec 36 msec
6 ae-72-70.ebr2.atlanta2.level3.net (188.8.131.52) [AS 3356] 24 msec
ae-62-60.ebr2.atlanta2.level3.net (184.108.40.206) [AS 3356] 24 msec 36 msec
7 ae-2.ebr2.miami1.level3.net (220.127.116.11) [AS 3356] 36 msec 40 msec 36 msec
8 ae-2-52.edge2.miami1.level3.net (18.104.22.168) [AS 3356] 36 msec 36 msec 36 msec
9 comcast-ip.edge2.miami1.level3.net (22.214.171.124) [AS 3356] 36 msec 36 msec 40 msec
10 te-8-2-ur01.staterd7.fl.pompano.comcast.net (126.96.36.199) [AS 20214] 40 msec 200 msec 64 msec
11 te-8-1-ur01.westboca.fl.pompano.comcast.net (188.8.131.52) [AS 20214] 36 msec 44 msec 40 msec
12 te-9-1-ur01.bocaraton.fl.pompano.comcast.net (184.108.40.206) [AS 20214] 40 msec 44 msec 40 msec
13 te-9-4-ur02.delrayeast.fl.pompano.comcast.net (220.127.116.11) [AS 20214] 40 msec 40 msec 44 msec
14 ge-1-46-ur01.delrayeast.fl.pompano.comcast.net (18.104.22.168) [AS 20214] 40 msec 40 msec 40 msec
I'm crunching through firewall logs over the last month to see what I get there.
Network Security Engineer
From: Tom Horsley [mailto:email@example.com]
Sent: Wednesday, April 15, 2009 2:33 PM
To: Anderson, Christopher M. (Network Security)
Subject: Re: mirrors.liberty.edu problem report
On Wed, 15 Apr 2009 14:17:22 -0400
Anderson, Christopher M. (Network Security) wrote:
> If you don't mind could you give us your IP address or IP range and I can check my firewalls and apache logs.
My system should look like xxx.xxx.xxx.xxx to the outside world (at least that is what
my router claims it got from comcast's dhcp server). I don't think it has changed
for several months (which always amazes me :-).
> I apologize for the problem and appreciate you reporting it to us as we had no idea there was an issue.
It wasn't that big a deal since there are plenty of other mirrors, I just
got tired of waiting for the timeouts if I happened to get one when running
yum interactively - I usually run it in cron at night so I don't
notice timeouts then.
Maybe I'll let the fastestmirror plugin use liberty again and see if the
timeouts come back :-).