Re: 504 gateway time-outs (was: FYI: The elapsed time shown for beefy24 [main-amd64] and beefy23 [150amd64-default] stopped over 2hrs ago)

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:
>>
>> <https://pkg-status.freebsd.org/beefy24/build.html?mastername=main-amd64-default&build=pdf4f957ea181_s178d0b5b8d>
>>
>> <https://pkg-status.freebsd.org/beefy23/build.html?mastername=150amd64-default&build=df4f957ea181>
>
> 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