possibly broken mirror: *.mirrors.cicku.me #12195
Labels
No labels
announcement
authentication
automate
aws
backlog
blocked
bodhi
ci
Closed As
Duplicate
Closed As
Fixed
Closed As
Fixed with Explanation
Closed As
Initiative Worthy
Closed As
Insufficient data
Closed As
Invalid
Closed As
Spam
Closed As
Upstream
Closed As/Will Not
Can Not fix
cloud
communishift
copr
database
deprecated
dev
discourse
dns
downloads
easyfix
epel
factory2
firmitas
gitlab
greenwave
hardware
help wanted
high-gain
high-trouble
iad2
koji
koschei
lists
low-gain
low-trouble
mbs
medium-gain
medium-trouble
mini-initiative
mirrorlists
monitoring
Needs investigation
notifier
odcs
OpenShift
ops
OSBS
outage
packager_workflow_blocker
pagure
permissions
Priority
Needs Review
Priority
Next Meeting
Priority
🔥 URGENT 🔥
Priority
Waiting on Assignee
Priority
Waiting on External
Priority
Waiting on Reporter
rabbitmq
rdu-cc
release-monitoring
releng
repoSpanner
request-for-resources
s390x
security
SMTP
src.fp.o
staging
taiga
unfreeze
waiverdb
websites-general
wiki
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Infrastructure/fedora-infrastructure#12195
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
NOTE
If your issue is for security or deals with sensitive info please
mark it as private using the checkbox below.
Describe what you would like us to do:
It appears that nl.mirrors.cicku.me is throttling downloads to an unusable degree. It starts out using my full bandwith (150Mbit/s), but then throttles to 30~40 kBit/s! I suspect that this also effects other mirrors by this individual, as they all appear hosted on cloudflare.
Here's a trace of a random large-ish package I tried to update. notice the rightmost column, current speed, decreasing over just a few seconds. It happens with all packages beyond a certain size, though.
(EDIT: after downloading this specific file a bunch of times, it seems cloudflare has cached it better, and the throttling is gone. this is PER-FILE, though: trying the same package with aarch64 still exhibits this. so if you can't reproduce it, please pick another random large package)
This mirror was automatically picked by fastestmirror=True (as their ping, coming from cloudflare, is quite good), so this probably affects a number of people.
after adding
minrate
andtimeout
to my dnf.conf, it finally gave up on this mirror:When do you need this to be done by? (YYYY/MM/DD)
somewhat soon, but realistically, whenever there's time.
Metadata Update from @zlopez:
Metadata Update from @zlopez:
I only throttle malicious bots which pull the site millions of times per day, they pull large files harder than any legitimate users here.
What happened here could be (I'm only guessing because I do not troubleshoot publicly) files absent in the NL location, when you are the first one to download the speed will be slower since the file is not sourced from a server in NL (this is contrary to your understanding that the slowness affects a lot of people). Once the formerly absent file is fully fetched to the NL location, you will be able to download with less issues (these file stay in the country location for over a month). You also have the freedom to manually use another mirror on your machine, which is also covered by the dnf.conf manpage.
The mirror is not only serving Fedora users and I have not received too many issue reports from my mirror admin address. Some issues are from the ISP, some issues are from the censorship and some are just network jitters. However, I must admit that the NL mirror was enabled for Fedora just from a week ago and you may be encountering issues higher than usual.
I kinda wish dnf would drop the 'fastest mirror' option... ping latency isn't really a very good indicator of download speed. ;(
So, what do we do here?
I have no idea.😄Checking my logs and I only received ~100 requests of last 14 days in NL...Whereas other hostnames have received 14M requests and nobody said anything for them.
All I can say is good luck, if nobody uses the NL location, then it won't be fast, so feel free to use other mirrors.
Closing this for now. I'm not sure what we can do in this case aside from drop the mirror, but it's working well for many others...
Metadata Update from @kevin: