From owner-freebsd-doc@freebsd.org Sun Jan 28 01:13:53 2018 Return-Path: Delivered-To: freebsd-doc@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 63E2BECFF90 for ; Sun, 28 Jan 2018 01:13:53 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from freefall.freebsd.org (freefall.freebsd.org [IPv6:2610:1c1:1:6074::16:84]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "freefall.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 067CB83C05 for ; Sun, 28 Jan 2018 01:13:53 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: by freefall.freebsd.org (Postfix) id F281815506; Sun, 28 Jan 2018 01:13:52 +0000 (UTC) Delivered-To: www@localmail.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx1.freebsd.org", Issuer "Let's Encrypt Authority X3" (verified OK)) by freefall.freebsd.org (Postfix) with ESMTPS id EBD0A15504; Sun, 28 Jan 2018 01:13:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (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 A4D9B83C04; Sun, 28 Jan 2018 01:13:52 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.89 (FreeBSD)) (envelope-from ) id 1efbXZ-000AHY-PG; Sat, 27 Jan 2018 17:13:50 -0800 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id w0S1DmDZ039527; Sat, 27 Jan 2018 17:13:48 -0800 (PST) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Sat, 27 Jan 2018 17:13:48 -0800 From: Oleksandr Tymoshenko To: Mark Millard Cc: bugmeister@FreeBSD.org, clusteradm@freebsd.org, www@freebsd.org Subject: Re: Lots of "Backend status: Backend fetch failed" notices in recent days. . . Message-ID: <20180128011348.GA39489@bluezbox.com> References: <8AD619C2-470B-4A0D-89A3-AE4445BE2C45@yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8AD619C2-470B-4A0D-89A3-AE4445BE2C45@yahoo.com> X-Operating-System: FreeBSD/11.1-RELEASE-p4 (amd64) User-Agent: Mutt/1.9.1 (2017-09-22) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Mark Millard (marklmi26-fbsd@yahoo.com) wrote: > In recent daysI've been getting lots of: > > > Error 503 Backend fetch failed > > > > Backend status: Backend fetch failed > > for various https://list [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-BeenThere: freebsd-doc@freebsd.org X-Mailman-Version: 2.1.25 Precedence: list List-Id: Documentation project List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 Jan 2018 01:13:53 -0000 Mark Millard (marklmi26-fbsd@yahoo.com) wrote: > In recent daysI've been getting lots of: > > > Error 503 Backend fetch failed > > > > Backend status: Backend fetch failed > > for various https://lists.freebsd.org/pipermail/. . ./.html > attempts. The ones are (normally?) recent ones. The next > day I'll have no trouble looking at the same. But at the time it > seems completely repeatable over a fair amount of time. Hi Mark, Thanks for reporting this issue. bugmeister@ team doesn't handle mailing lists infrastructure we only have access to Bugzilla instance. I added clusteradm@ and www@ to Cc, hopefully someone from these teams can look into this problem Thanks -- gonzo