From owner-freebsd-questions@freebsd.org Sat Sep 2 20:07:30 2017 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 395C9E01EC5 for ; Sat, 2 Sep 2017 20:07:30 +0000 (UTC) (envelope-from raf@rafal.net) Received: from mxout-08.mxes.net (mxout-08.mxes.net [216.86.168.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 967D06EFFC for ; Sat, 2 Sep 2017 20:07:29 +0000 (UTC) (envelope-from raf@rafal.net) Received: from [192.168.40.37] (unknown [86.40.118.125]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.mxes.net (Postfix) with ESMTPSA id A9F42509B6 for ; Sat, 2 Sep 2017 16:07:27 -0400 (EDT) From: Rafal Lukawiecki Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 10.3 \(3273\)) Subject: pkg.freebsd.org mirror having issues? Message-Id: <8A70F0B7-7B7A-4BA7-ACCC-A7DFBE754768@rafal.net> Date: Sat, 2 Sep 2017 21:07:25 +0100 To: Ralf Mardorf via freebsd-questions X-Mailer: Apple Mail (2.3273) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Sep 2017 20:07:30 -0000 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 = (151.101.60.204) 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. -- Rafal Lukawiecki Data Scientist=20 Project Botticelli Ltd