Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKfXY-0005hi-B8 for buildfarm-members@arkaria.postgresql.org; Thu, 08 Nov 2018 08:19:48 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1gKfXV-0002o0-0w for buildfarm-members@arkaria.postgresql.org; Thu, 08 Nov 2018 08:19:45 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1gKfXU-0002nt-Or for buildfarm-members@lists.postgresql.org; Thu, 08 Nov 2018 08:19:44 +0000 Received: from mail-lj1-x244.google.com ([2a00:1450:4864:20::244]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1gKfXM-00017f-E4 for buildfarm-members@lists.postgresql.org; Thu, 08 Nov 2018 08:19:43 +0000 Received: by mail-lj1-x244.google.com with SMTP id v15-v6so8546864ljh.13 for ; Thu, 08 Nov 2018 00:19:35 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hagander-net.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/HW77dUy/4rn4p8TtyH8wU3ozWX+pRVyXO0/VV+jlEw=; b=XOoqqHBhyIzymwsfC7RNjBGk3FuJN/IjrE45D86J4sjxHQIbzWPuf0ZkLhcq3bp6/+ liCrJO7gICwFcZlWnj0VMV5sUww2NZRWZIEMEJbcsoDSR4oEvldepq0S1rOjk0J+Jnhy jmN6eVqWzt4lwcmTIH3N0Ke38XMq9K3ov7lv8XlQOsGJASds12DVxq4JSnA3xDEAIW8+ ke1wccJUePJjsvCd36KjURbD1eNmdUyikH4Kxq+49sNvnuElbRB8pCbFrBQJcwP+KPUt mop71h7pBLKGbkatBuIaylnlP/RO+G/GTjDO2HtYakBZnj+ziJbELkuQScKD9Fz8cBGK 5pSg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=/HW77dUy/4rn4p8TtyH8wU3ozWX+pRVyXO0/VV+jlEw=; b=mnSJtnOW58ZrFHII0cmtcRqMB/LMS2NRXIsts5Rtjja0w7sgDJL8Jao8dTDuKLpD4a ixUCbyj14L99i89PlbSW3HSa2Xs6CH9Z7XPVPOaZOsGPZVKToPGYn7QCzPcX7x+GYvgL UuAcsIfSoy/lKcUCFnmlH6aBQzEPv+0Lnqo5XeyHmv2cx/jO5C22gPzafy8iOxWE2qYZ +uF9Qd7jnDlZGnjllKUTNGwUK4yeJFvVOYPRx211AmdX0h2UFcW/GUb/vCDy0IpUBpeF C7RyjDYscDWkXXgreW4c8OV4uIccqdioAg7rR++r8xMEWWeStKY5FT9cCstys6vUsVVc 9NYw== X-Gm-Message-State: AGRZ1gIeSsx1Xq7LP1BWrgM5BtV2MPx/R0ao51ignyIduUtqTqJakcjY +/q6lACIrPd4kK2BlKr+0EJUGuDMN2uicRNgWylY0g== X-Google-Smtp-Source: AJdET5ewlMHUNAPrFXKTT/XRL6topAFOjPlZsGwg9ElaSUs6Sfjxg6KVzrWAO6eCkSN9bL6hOh78MtJSk2xtuBDWBZQ= X-Received: by 2002:a2e:6503:: with SMTP id z3-v6mr2086691ljb.153.1541665173973; Thu, 08 Nov 2018 00:19:33 -0800 (PST) MIME-Version: 1.0 References: <428FDD47-5325-4904-9306-F2D6F9D8232D@mac.com> In-Reply-To: From: Magnus Hagander Date: Thu, 8 Nov 2018 09:19:22 +0100 Message-ID: Subject: Re: 503 Backend fetch failed errors To: Stefan Kaltenbrunner Cc: remi_zara@mac.com, buildfarm-members@lists.postgresql.org, sysadmins Content-Type: multipart/alternative; boundary="0000000000000ec279057a22e5b9" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --0000000000000ec279057a22e5b9 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Thu, Nov 8, 2018 at 9:01 AM Stefan Kaltenbrunner wrote: > On 11/7/18 6:40 PM, R=C3=A9mi Zara wrote: > > Hi, > > Hi R=C3=A9mi! > > > > > I=E2=80=99m getting a lot of these errors with coypu (several per day),= but not > systematically. > > Is this a problem on my end, or is this on the sever end ? > > > > Query for: stage=3DOK&animal=3Dcoypu&ts=3D1541573277 > > Target: > https://buildfarm.postgresql.org/cgi-bin/pgstatus.pl/53b137e7c765b781699b= be73e3aec7751a8c4ab7 > > Status Line: 503 Backend fetch failed > > Web txn failed with status: 1 > > Query for: stage=3DOK&animal=3Dcoypu&ts=3D1541575423 > > Target: > https://buildfarm.postgresql.org/cgi-bin/pgstatus.pl/5e8e0913dc9f9a580a41= 25264d74fff95f26c926 > > Status Line: 503 Backend fetch failed > > Web txn failed with status: 1 > > given the error this is something that is created by the varnish > instance that is in front of the buildfarm. On a quick look I could > immediately figure out what the problem is - but it looks like you (or > somebody else) tried at least to click one of the links above using hist > desktop browser and got an error about a missing branch specification ;) > > > AFAICT: A quick look in the logs indicates that the buildfarm is responding: - RespHeader Status: 492 bad branch parameter However, 492 is not a valid http status code, so Varnish can't handle it and thus returns 503 failure to the client. --=20 Magnus Hagander Me: https://www.hagander.net/ Work: https://www.redpill-linpro.com/ --0000000000000ec279057a22e5b9 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable


On Thu, Nov 8, 2018 at 9:01 AM Stefan Kaltenbrunner <stefan@k= altenbrunner.cc> wrote:
On 11/7/18 6:40 PM, R=C3=A9mi Zara wrote:
> Hi,

Hi R=C3=A9mi!

>
> I=E2=80=99m getting a lot of these errors with coypu (several per day)= , but not systematically.
> Is this a problem on my end, or is this on the sever end ?
>
> Query for: stage=3DOK&animal=3Dcoypu&ts=3D1541573277
> Target: https://buildfarm.postgresql.org/cgi-bin/pgstatus.pl/53b137e7c765b781= 699bbe73e3aec7751a8c4ab7
> Status Line: 503 Backend fetch failed
> Web txn failed with status: 1
> Query for: stage=3DOK&animal=3Dcoypu&ts=3D1541575423
> Target: https://buildfarm.postgresql.org/cgi-bin/pgstatus.pl/5e8e0913dc9f9a58= 0a4125264d74fff95f26c926
> Status Line: 503 Backend fetch failed
> Web txn failed with status: 1

given the error this is something that is created by the varnish
instance that is in front of the buildfarm. On a quick look I could
immediately figure out what the problem is - but it looks like you (or
somebody else) tried at least to click one of the links above using hist desktop browser and got an error about a missing branch specification ;)


AFAICT:

A= quick look in the logs indicates that the buildfarm is responding:
-=C2=A0 =C2=A0RespHeader=C2=A0 =C2=A0 =C2=A0Status: 492 bad branch param= eter

However, 492 is not a valid http status code,= so Varnish can't handle it and thus returns 503 failure to the client.=


--
=C2=A0Magnus Hagander
=C2=A0M= e: https://www.hagan= der.net/
=C2=A0Work: https://www.redpill-linpro.com/
--0000000000000ec279057a22e5b9--