From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-return-195021-listarch-gcc=gcc.gnu.org@gcc.gnu.org>
Received: (qmail 46322 invoked by alias); 21 Jan 2018 06:20:35 -0000
Mailing-List: contact gcc-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <gcc.gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <http://gcc.gnu.org/ml/>
Sender: gcc-owner@gcc.gnu.org
Received: (qmail 39693 invoked by uid 89); 21 Jan 2018 06:18:43 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,SPF_PASS autolearn=ham version=3.3.2 spammy=reoccur, eigler, services, Frank
X-HELO: mail-ot0-f175.google.com
Received: from mail-ot0-f175.google.com (HELO mail-ot0-f175.google.com) (74.125.82.175) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Sun, 21 Jan 2018 06:18:41 +0000
Received: by mail-ot0-f175.google.com with SMTP id p36so4867611otd.10        for <gcc@gcc.gnu.org>; Sat, 20 Jan 2018 22:18:37 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;        d=1e100.net; s=20161025;        h=x-gm-message-state:mime-version:in-reply-to:references:from:date         :message-id:subject:to:cc;        bh=pKlZ2g5xQD1DMSKUqKsBZnPYTwhngNB+waFqBJ7J66A=;        b=tx4e8Zcd7cFG+25fHsJvqeJTFjjjRmoiA6VkIbH0yDktzYn52zMJ/MY1e+MpWEuRBs         F9oMTUTB/qeuZTAJueuVCiHSEC6tcHL/IdIZtKxzV/lfZ/C/A6oBGAblXAAYSDyAR0nV         ioas1pGlh8Ir37PgegecLDzEqob54EIiPvWkBQfk/tm5IJ1/cmTDpGcTs8972WfUO/ym         W1FQw8+VvLorbQdUZZ7iQWrxRU3u/y6wWS8ULAy5KHFCWpO+zt6CGS0HA62jSt4071DO         XHg4l1l7YHfTnd1CjUe3p4yBPsO8eflOEs9/zdW8CdlWXGb1zy/eDZ+WG7TXesN9Ozx2         f/2Q==
X-Gm-Message-State: AKwxytfwHJDxTTR246cbd6sC9ufz58TN91Rl7Hx2iSARfKPQODOt7c8W	DOb+oW8oMxh3hP5QoAVWwI7Lppeoguo+1JEkxmA0EA==
X-Google-Smtp-Source: AH8x224pkhjM2hgLmbNep4PACcaQJf/d02Cm6ZeqZ9NhDHuNVepetijZfUR84RQbMOxSdV3horyoUIru+GZXYLUeWdk=
X-Received: by 10.157.63.132 with SMTP id r4mr2117274otc.400.1516515516410; Sat, 20 Jan 2018 22:18:36 -0800 (PST)
MIME-Version: 1.0
Received: by 10.157.82.159 with HTTP; Sat, 20 Jan 2018 22:18:35 -0800 (PST)
In-Reply-To: <87mv1b2d8m.fsf@redhat.com>
References: <cf68f346-914e-2826-608f-ed9fe461f790@gmail.com> <87mv1b2d8m.fsf@redhat.com>
From: Eric Gallager <egall@gwmail.gwu.edu>
Date: Sun, 21 Jan 2018 06:20:00 -0000
Message-ID: <CAMfHzOsH-E68rRK-9krMU5wkBSCwcLF43zLTRtCZZTcLbcg3DA@mail.gmail.com>
Subject: Re: Bugzilla timing out
To: "Frank Ch. Eigler" <fche@redhat.com>
Cc: Martin Sebor <msebor@gmail.com>, GCC Mailing List <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-IsSubscribed: yes
X-SW-Source: 2018-01/txt/msg00143.txt.bz2

On 1/18/18, Frank Ch. Eigler <fche@redhat.com> wrote:
>
> msebor wrote:
>
>> I'm having trouble bringing up bugs or updating them.  Has anyone else
>> noticed Bugzilla (and/or other services running on gcc.gnu.org) being
>> very slow or timing out?
>
> One failed disk in the server has been replaced yesterday.  Please let
> us know if problems persist or reoccur.
>
> - FChE
>

Problems are still occurring for me; Bugzilla gives me 504 Gateway
Time-outs when I try to access it tonight...