Date: Tue, 1 Dec 2020 09:52:18 +0000 From: =?iso-8859-1?B?RGF27fA=?= Steinn Geirsson <david@isnic.is> To: Ulrich =?iso-8859-1?Q?Sp=F6rlein?= <uqs@freebsd.org> Cc: Li-Wen Hsu <lwhsu@freebsd.org>, freebsd-git@freebsd.org Subject: Re: 504 errors from cgit-beta Message-ID: <20201201095218.GC6221@mail> In-Reply-To: <X8VjIoVizIIrqCeE@acme.spoerlein.net> References: <20201112155659.GQ913@mail> <20201113.032709.2108746957258946268.yasu@utahime.org> <CAKBkRUxqVSccn_9KJAJZW0po-1C%2B5H5EqTPsz=rM-4=cUrOLUw@mail.gmail.com> <20201130150642.GB6221@mail> <X8VjIoVizIIrqCeE@acme.spoerlein.net>
next in thread | previous in thread | raw e-mail | index | archive | help
--sXc4Kmr5FA7axrvy Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 30, 2020 at 10:24:50PM +0100, Ulrich Sp=F6rlein wrote: > On Mon, 2020-11-30 at 15:06:42 +0000, Dav=ED=F0 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> wr= ote: > > > > > > > > From: Dav=ED=F0 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` again= st an > > > > > existing checkout of `ports.git` from https://cgit-beta.freebsd.o= rg/ports.git: > > > > > > > > > > ``` > > > > > $ git fetch cgit-beta > > > > > error: RPC failed; HTTP 504 curl 22 The requested URL returned er= ror: 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. > > >=20 > > > 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. > >=20 > > This problem disappeared after your changes, but as of this weekend see= ms > > to be happening again: > >=20 > > 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: 5= 04 Gateway Time-out > > fatal: the remote end hung up unexpectedly > >=20 > > Is it possible some web server config got overwritten during the last > > batch of changes? >=20 > This is most definitely fallout from the commit hashes changing. That mea= ns > your client will upload basically all the hashes or packs for the server = to > compare what it does and does not have. >=20 > What is your up/downstream bandwidth situation like? Could you try some m= ore > tracing as outlined here: https://stackoverflow.com/questions/27442134/gi= t-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. Up/downstream should be good. Speedtests show ~100-160Mbit/s in both directions. Cloning a repo from cgit-beta.freebsd.org I see 7.75 MiB/s. The checkout I was working from had two branches: `upstream` which is a 1:1 clone of the state of the `main` branch on cgit-beta, and `main` which is the same but also has a couple of local ports in commits that get rebased on top of `upstream` when it's updated. When this error occurred I was on the `upstream` branch. This was a manual test, but normally the same update-then-rebase process happens as part of a CI job which was also failing. It seems this is fixed now, as the last 4 runs of the CI job were successful (first successful run was at 18:42 UTC). If I see a similar error again I'll follow the linked steps and send a more detailed trace. Thanks for your assistance, -Dav=ED=F0 >=20 > Li-Wen, we need to further up the timeouts here, freebsd repos are big, > after all. >=20 > Cheers > Uli --sXc4Kmr5FA7axrvy Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iQEzBAABCgAdFiEEvylfYbt7o3c60Grm/+HlKLuPmJoFAl/GElIACgkQ/+HlKLuP mJoKvQf/XmzIXD2KQeqEmOuwpyWYvmzKzZGuGgcarqVWBbbvWgtbQ01nTDZ6d9PF 6Fzf737iyiXW01awpcC5BUdZtsJT7ItLYqHSnJ1O2lQFZZkUKwxhlA231yZIR3wn 2ZzRozkAAlBKyGqpV+QZ8U7296eUU9qZU1ugGcgiVqCZvFhiVbaFMxJZE3J5fqfN fSl22R/pb0lJmjb4Wzl5U9gYrDz/zeuuRifNq5xB4abpnS4TpWyHgQU1u/jMl0/p OjWkc9kYCTjwYaacsVXX8Z5adtYcag3ZxdIRmwXw77Vu5LO6jFBWkqUdWMJ6FnqQ M4m9yBClvxATx8GJNzbwV9knBm0tjw== =26C5 -----END PGP SIGNATURE----- --sXc4Kmr5FA7axrvy--
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20201201095218.GC6221>