From nobody Tue Mar 31 13:25:44 2026 X-Original-To: freebsd-current@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4flTQN2jQrz6XwF3; Tue, 31 Mar 2026 13:25:48 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from smtp.freebsd.org (smtp.freebsd.org [96.47.72.83]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256 client-signature RSA-PSS (4096 bits) client-digest SHA256) (Client CN "smtp.freebsd.org", Issuer "R13" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 4flTQN0MbFz3KsT; Tue, 31 Mar 2026 13:25:48 +0000 (UTC) (envelope-from philip@freebsd.org) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774963548; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LuMCSIToz6vs1JGrTt/YyM7ASRCsCf7TkbJ0oBm8rTE=; b=nyeL3j2VzqF7+0mS4DUB4ivJWRq7FXFUEbM2qy1/cetcyAAvsHDH2PFx1bYFUn7W/hMPv2 dcYx40iQG0lYlXCA3l+cVdWfuqu9svC3biIRHLvC+XzaOeMQ8VcQvCIz9Gd59bB/gMUhKg QzucVxXp/RnaX4gq0lYpVJjxdToVFREYlJKAFioR5OR5LYcnlJCdJ8pTzPnHm/23QlIS6L Lzl9Bc3v044EKTywS+08NDf/Qg0lUQOSM12B+8aZcylyc9rLQvBJsCGuSOqXVtazYj+OB/ PHpTQ78G8wjT/6VpLlNWShsA4dGjZ/p54rSvtpWCbOERQkKDJXdH8FaSEQjaJQ== ARC-Seal: i=1; s=dkim; d=freebsd.org; t=1774963548; a=rsa-sha256; cv=none; b=HgqVBH24wcOOWZHglZiQLjdf43pLpN0aXY/j7l5ZJ3+N6YBMwe6x4NUN2RQDJmbHRUdyhz o+13NO2wWk/2PxgTBjiirlclUkMpMdtL7o5CgMDxe0hYNGHMf5JjTlleKMsptPHFA5LpNZ rT0p6Z35LgCtG2snedlYbGBPIhOXat5Gg0s4zN1sYeUNgjwJWyAoAhP6VDSivXYcUE9xPs QE2QZMyJMzStHGuLSYjLYPrSq4ZpSUrEL6h8H9De7kLHvgQCIQ5V5wY5iKIhNkJj6fOKXM Wh6TP4lP5XUVYrZfrc5K2bUmbcP43cxc2+hRS9wzm8DEvMFSfAuGM8+0+Y2y8w== ARC-Authentication-Results: i=1; mx1.freebsd.org; none ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=freebsd.org; s=dkim; t=1774963548; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=LuMCSIToz6vs1JGrTt/YyM7ASRCsCf7TkbJ0oBm8rTE=; b=LUZGcB7F1c1UKMCaMXkXxpEcYx5m2kD4jAVy4qtdPqk/o6mTWhD27DtidwSfHwpsj3D65z sSyP20bl99vP3dB1x9pFLMGqW2wsYjPbeWMXUe46hvfZuyvGABHrYhItxAkXhyIBwiLIws o8UI+ElnWtxGW65hLCVWUQ+LwT7DWc88XlQA2hbuu7oGk9vPRHhwlcWQBCClXxz3CqMBYu GMv/EhO1nAw2MnGOanfR7sWqdTI2+Qn7ChGLkdVstkmMQizN8jK8+ThDKW6E9RE5SRwA96 GrCHF/s22+SIJWh9J+ykcAbIMvNDhBzepu+kQWT0YxOSBf/ZButs9Ti2KkwQjw== Received: from fauth-a1-smtp.messagingengine.com (fauth-a1-smtp.messagingengine.com [103.168.172.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) (Authenticated sender: philip/mail) by smtp.freebsd.org (Postfix) with ESMTPSA id 4flTQM6cSpz16xC; Tue, 31 Mar 2026 13:25:47 +0000 (UTC) (envelope-from philip@freebsd.org) Received: from phl-compute-02.internal (phl-compute-02.internal [10.202.2.42]) by mailfauth.phl.internal (Postfix) with ESMTP id 99E98F4007B; Tue, 31 Mar 2026 09:25:47 -0400 (EDT) Received: from phl-frontend-04 ([10.202.2.163]) by phl-compute-02.internal (MEProxy); Tue, 31 Mar 2026 09:25:47 -0400 X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeefhedrtddtgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpuffrtefokffrpgfnqfghnecuuegrihhl ohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjughrpe fhvfevufffoffkjghfgggtgfesthhqmhdtredttdenucfhrhhomheprfhhihhlihhpucfr rggvphhsuceophhhihhlihhpsehfrhgvvggsshgurdhorhhgqeenucggtffrrghtthgvrh hnpeejudekfffgffekjeffgfefgfeltdehhfffgeegveegveehvdehgedtuddvteekieen ucffohhmrghinhepfhhrvggvsghsugdrohhrghenucevlhhushhtvghrufhiiigvpedtne curfgrrhgrmhepmhgrihhlfhhrohhmpehphhhilhhiphdomhgvshhmthhprghuthhhphgv rhhsohhnrghlihhthidqudduieeivdeivdegkedqvdefhedukedttdekqdhphhhilhhiph eppehfrhgvvggsshgurdhorhhgsehtrhhouhgslhgvrdhishdpnhgspghrtghpthhtohep fedpmhhouggvpehsmhhtphhouhhtpdhrtghpthhtohepghhrrghhrghmphgvrhhrihhnse hgmhgrihhlrdgtohhmpdhrtghpthhtohepfhhrvggvsghsugdqtghurhhrvghnthesfhhr vggvsghsugdrohhrghdprhgtphhtthhopehfrhgvvggsshguqdhsthgrsghlvgesfhhrvg gvsghsugdrohhrgh X-ME-Proxy: Feedback-ID: ia691475d:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Tue, 31 Mar 2026 09:25:46 -0400 (EDT) From: Philip Paeps To: Graham Perrin Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago) Date: Tue, 31 Mar 2026 21:25:44 +0800 X-Mailer: MailMate (2.0r6290) Message-ID: <5739E595-8A9F-4968-BA58-8D32F9E7E1C1@freebsd.org> In-Reply-To: <1895ba62-b069-4e28-a910-6c666703ee8e@gmail.com> References: <1895ba62-b069-4e28-a910-6c666703ee8e@gmail.com> List-Id: Discussions about the use of FreeBSD-current List-Archive: https://lists.freebsd.org/archives/freebsd-current List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-current@FreeBSD.org MIME-Version: 1.0 Content-Type: text/plain; format=flowed Content-Transfer-Encoding: quoted-printable On 2026-02-28 19:32:35 (+0800), Graham Perrin wrote: > On 28/02/2026 10:32, Mark Millard wrote: >> The following got "504 Gateway Time-out" when I tried them: >> >> >> >> > > Both somewhat slow to load, however they do load for me. I only just noticed this thread, sorry for resurrecting it. I've noticed that beefy23 and beefy24 (2x EPYC 9254, 512G RAM) sometimes = get too busy building to schedule nginx (or sshd). They eventually = manage to plough through. Usually. That causes the 504 timeouts if you're going through pkg-status.f.o. If = you're going directly to beefyX.chi.freebsd.org you'll just get a = timeout. They're running exactly the same poudriere.conf as the other builders. = I wonder if our calc_builders() function that tries to assign about 12G = per builder isn't quite right for this particular configuration of cores = and RAM. I haven't had a chance to look closely. As far as I can tell the builds = do eventually succeed. If the only problem is "I can't obsessively poll = pkg-status in real time", it's not a very high priority. :) This is on my list. It's just a VERY long list. :) Philip