Date: Mon, 30 Nov 2020 22:24:50 +0100 From: Ulrich =?utf-8?B?U3DDtnJsZWlu?= <uqs@freebsd.org> To: =?utf-8?B?RGF2w63DsA==?= Steinn Geirsson <david@isnic.is> Cc: Li-Wen Hsu <lwhsu@freebsd.org>, freebsd-git@freebsd.org Subject: Re: 504 errors from cgit-beta Message-ID: <X8VjIoVizIIrqCeE@acme.spoerlein.net> In-Reply-To: <20201130150642.GB6221@mail> References: <20201112155659.GQ913@mail> <20201113.032709.2108746957258946268.yasu@utahime.org> <CAKBkRUxqVSccn_9KJAJZW0po-1C%2B5H5EqTPsz=rM-4=cUrOLUw@mail.gmail.com> <20201130150642.GB6221@mail>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, 2020-11-30 at 15:06:42 +0000, Davíð Steinn Geirsson wrote: >On Fri, Nov 13, 2020 at 05:33:12PM +0800, Li-Wen Hsu wrote: >> On Fri, Nov 13, 2020 at 2:28 AM Yasuhiro KIMURA <yasu@utahime.org> wrote: >> > >> > From: Davíð Steinn Geirsson <david@isnic.is> >> > Subject: 504 errors from cgit-beta >> > Date: Thu, 12 Nov 2020 15:56:59 +0000 >> > >> > > We are getting frequent 504 errors when running `git fetch` against an >> > > existing checkout of `ports.git` from https://cgit-beta.freebsd.org/ports.git: >> > > >> > > ``` >> > > $ git fetch cgit-beta >> > > error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 >> > > fatal: the remote end hung up unexpectedly >> > > ``` >> > >> > I experienced same error when accessing Emacs git remository with >> > HTTPS. Following is bug report that I submitted to report the issue. >> > >> > https://savannah.nongnu.org/support/?110322 >> > >> > As you can see, site administrator fixed the issue by icreasing >> > `fastcgi_read_timeout` and `proxy_read_timeout` parameters of >> > nginx. Since cgit-beta also uses nginx this may also fix your >> > error. In my case, however, access always failed and never >> > succeeded. So cause may be different from the one of my case. >> >> Thanks, I have checked this, indeed some requests' handlers don't have >> a long enough timeout setting and I've relaxed them. Hope this solves >> some people's issues. Please check it again, and if it still fails for >> you, we might need to have more information to debug. > >This problem disappeared after your changes, but as of this weekend seems >to be happening again: > >user@ssh:~/foo/ports$ git fetch -v cgit-beta >POST git-upload-pack (gzip 3272 to 1703 bytes) >POST git-upload-pack (gzip 2577 to 1354 bytes) >error: RPC failed; HTTP 504 curl 22 The requested URL returned error: 504 Gateway Time-out >fatal: the remote end hung up unexpectedly > >Is it possible some web server config got overwritten during the last >batch of changes? This is most definitely fallout from the commit hashes changing. That means your client will upload basically all the hashes or packs for the server to compare what it does and does not have. What is your up/downstream bandwidth situation like? Could you try some more tracing as outlined here: https://stackoverflow.com/questions/27442134/git-fetch-hangs-on-git-upload-pack What sort of custom work do you have in there (branches, etc)? I'm curious to find out a way to reset this non-destructively ... and I have an idea. Li-Wen, we need to further up the timeouts here, freebsd repos are big, after all. Cheers Uli
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?X8VjIoVizIIrqCeE>