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

On Sat, Feb 28, 2026 at 3:33 AM Graham Perrin <grahamperrin@gmail.com>
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.
>
> Thanks


beefy22 is showing hte same issues. Something is tying up the builders with
builds hanging in "build-depends" and "lib-depends" for very long periods
of time, as long as over 4 hours) with high load averages. This has been
going on for months and seems to be getting worse. Chromium builds which
used to take around 20 hours are now running around 40 and I really don't
think that this is just code bloat. At times, about half of the active
builds are in some state other than "build"; mostly one of the depends
states which should never take long as all dependencies are built before a
build is started.

After some time passes (often hours) things clear up. Dependencies are
suddenly loaded in a few minutes or less. Note that things do continue to
complete, but the 10 minute averages are in single digits and frequently go
to 0. During this time, my connection to beefy22 will timeout and sometimes
I can't establish a connection.

I don't have any special access to the machines... just via pkg-status, so
I'm fairly limited in any analysis.
-- 
Kevin Oberman, Part time kid herder and retired Network Engineer
E-mail: rkoberman@gmail.com
PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683