pkg.freebsd.org mirror having issues?
zi at FreeBSD.org
Sat Sep 2 22:36:17 UTC 2017
On (09/02/17 22:22), Rafal Lukawiecki wrote:
>I am glad to hear there is a reason for it. I am still awaiting a server to finish building, it has been some 25 minutes, looks like 2 min timeouts between files. :)
Looks like I misspoke. This actually didn't have anything to do with my
testing, but rather another mirror that was having issues.
The 2 minute delay you were experiencing was caused by pkg waiting for a
timeout on another mirror before trying one that is responding.
I've removing the offending mirror for now and will investigate a more
automatic solution in the near future.
>I will terminate this server instance and start over. I will report back here as soon as I can see it is faster.
>BTW, are you/others on an IRC/Freenode to let you know of such issues more directly?
>Thank you and regards from Ireland,
>> On 2 Sep 2017, at 22:20, Ryan Steinmetz <zi at FreeBSD.org> wrote:
>>> As a new FreeBSD user I wonder if it is a frequent problem. I am suddenly experiencing very slow access to the local mirrors of pkg.freebsd.org. Even a small file takes almost a minute. Updating FreeBSD repository catalogue (when using pkg) takes about 5-6 minutes. I have tried using several different machines from different IPs, all within AWS eu-west (Ireland). It was working well all week.
>>> The local mirror seems to resolve to dualstack.nonssl.global.fastly.net (18.104.22.168) at the moment. Pingtime is not bad, 9ms, but their server takes almost a minute before it starts serving files. Once the file starts, it comes fast. I assume it is some sort of a server issue at their end at Fastly, perhaps they have a dead machine in the pool which makes it intermittent.
>>> As I am building an automated server init, this means that instead of having a server provisioned in <5 min, it can take 20-35 mins, by which time it is not even considered to exist by the load balancer.
>>> Is this common? Should I start (somehow) specifying individual mirrors directly? Thank you very much for your wisdom.
>> This is not common and was caused by a configuration issue during some testing that I've been doing to (ironically) try to improve response time.
>> Would you be able to try this once more? I've made an edit which should drastically change the experience for you.
>>> Rafal Lukawiecki
>>> Data Scientist Project Botticelli Ltd
>> Ryan Steinmetz
>> PGP: 9079 51A3 34EF 0CD4 F228 EDC6 1EF8 BA6B D028 46D7
PGP: 9079 51A3 34EF 0CD4 F228 EDC6 1EF8 BA6B D028 46D7
More information about the freebsd-questions