From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 99904 invoked by alias); 26 Feb 2020 16:25:39 -0000 Mailing-List: contact overseers-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: , Sender: overseers-owner@sourceware.org Received: (qmail 99890 invoked by uid 89); 26 Feb 2020 16:25:38 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-7.6 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=unavailable version=3.3.1 spammy=december, December, H*MI:sk:w_o4EaM, our X-HELO: mail-qt1-f193.google.com Received: from mail-qt1-f193.google.com (HELO mail-qt1-f193.google.com) (209.85.160.193) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Wed, 26 Feb 2020 16:25:37 +0000 Received: by mail-qt1-f193.google.com with SMTP id i23so2668756qtr.5 for ; Wed, 26 Feb 2020 08:25:37 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=7qrKV1h3OXExKG5Fm6DsDmXEm/1bUV4TTrZ3+vcWHIc=; b=XjErvmjooayN5h7YNRH5C4zf9j/9UKkd8BJzh6viyBSW9pgmnQKuvXN9jUuvcUI+6y 1rLGdMn8ycDJT/mS7ypXUQOSq/4dM9NSyFhBwGjaJUl4PyDjilh7rVsb4J+YglFTDplT XCo4h3l2UaabQI1f3zOzhoSDCPFL1ycvG+bAvOpOB/avlpcD10riDsKrE2C6vkSlkkio zUvELozR94fYh3cU+GLCQUZSydCOyxsWD8GWisUv2VLaQZMIlf1PkRP4UAT94BNji3lj O2DtJ3aC1pzUpdCic3AMT6v5/PLICbf3il86QabsA7G9WHK+MoDgINwz3vEWcaXzLZWW u/+Q== Return-Path: Received: from [192.168.0.41] (174-16-106-242.hlrn.qwest.net. [174.16.106.242]) by smtp.gmail.com with ESMTPSA id v7sm1362581qkg.103.2020.02.26.08.25.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 26 Feb 2020 08:25:35 -0800 (PST) Subject: Re: GCC Bugzilla (and other) timeouts To: Jonathan Wakely Cc: overseers@sourceware.org, gcc mailing list References: <038bc19b-afd9-de7a-ff26-54ffa4d92b86@gmail.com> From: Martin Sebor Message-ID: <9937a596-e419-0a6e-e765-36cb8e8c5611@gmail.com> Date: Wed, 26 Feb 2020 16:25:00 -0000 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-IsSubscribed: yes X-SW-Source: 2020-q1/txt/msg00089.txt On 2/26/20 1:32 AM, Jonathan Wakely wrote: > On Tue, 25 Feb 2020 at 18:25, Martin Sebor wrote: >> >> Bugzilla has been slow lately, and today to the point of timing out >> (I see the same problem with Git). This seems to be a recurring theme >> around the time of a GCC release. Is anyone else experiencing this >> problem and if so, does anyone know what the cause it and an ETA for >> a solution? Is the upcoming hardware upgrade expected to solve it? >> >> Thanks >> Martin >> >> $ git pull >> Connection closed by 209.132.180.131 port 22 >> fatal: Could not read from remote repository. >> >> Please make sure you have the correct access rights >> and the repository exists. > > What URL are you using to pull? (git remote get-url origin) > I use git+ssh (from our documentation): $ git remote get-url origin git+ssh://msebor@gcc.gnu.org/git/gcc.git > Bugzilla and httpd are very slow, but I haven't had any git timeouts. > If you're using anonymous access that gets throttled more aggressively > than authenticated access (using git+ssh:// for the protocol). Thanks for the confirmation. Sounds like it's a known problem and it's just a coincidence that it's happening again as we near a GCC release. I think I remember last year there was also a disk problem, and ditto the year before then: https://gcc.gnu.org/ml/gcc/2018-01/msg00125.html Maybe we should proactively replace the disks every December ;-) Martin