Date: Sun, 1 Mar 2026 11:59:10 -0800 From: Mark Millard <marklmi@yahoo.com> To: Kevin Oberman <rkoberman@gmail.com>, Graham Perrin <grahamperrin@gmail.com> Cc: freebsd-current@freebsd.org, freebsd-stable@freebsd.org Subject: Re: 504 gateway time-outs Message-ID: <e6c5dead-a7a5-47bd-b030-e957990e6897@yahoo.com> In-Reply-To: <CAN6yY1uzkQTtEaaL0BpB9kvh7FZSbi-jT3jYDxy%2BB_O9=2COmw@mail.gmail.com> References: <d5fd8b56-35cd-4700-8e9b-7767cbb088a6@yahoo.com> <1895ba62-b069-4e28-a910-6c666703ee8e@gmail.com> <CAN6yY1vN8T=6SsNNtr%2B-NO7n5yCJGTPYz=HjVnwPOjM9827x8Q@mail.gmail.com> <CAN6yY1uzkQTtEaaL0BpB9kvh7FZSbi-jT3jYDxy%2BB_O9=2COmw@mail.gmail.com>
index | next in thread | previous in thread | raw e-mail
On 2/28/26 17:57, Kevin Oberman wrote: > On Sat, Feb 28, 2026 at 5:48 PM Kevin Oberman <rkoberman@gmail.com > <mailto:rkoberman@gmail.com>> wrote: > > On Sat, Feb 28, 2026 at 3:33 AM Graham Perrin > <grahamperrin@gmail.com <mailto: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/beefy24/build.html? > mastername=main-amd64-default&build=pdf4f957ea181_s178d0b5b8d>> > > > > <https://pkg-status.freebsd.org/beefy23/build.html? > mastername=150amd64-default&build=df4f957ea181 <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. > > > Just before I started my last message, all was well, but I last saw > were a dozen builds in one of the "depends" states and "impulse" at 74 > when I lost my connection. I can reconnect to the beefy22 status page, > but it has not updated for several minutes. > -- > Kevin Oberman, Part time kid herder and retired Network Engineer > E-mail: rkoberman@gmail.com <mailto:rkoberman@gmail.com> > PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683 FYI: beefy22 got an extract/timeout failure for attempting to build qt6-webengine-6.10.2: . . . ===> Extracting for qt6-webengine-6.10.2 => SHA256 Checksum OK for KDE/Qt/6.10.2/qtwebengine-everywhere-src-6.10.2.tar.xz. =>> Killing timed out build after 7200 seconds =>> Cleaning up wrkdir ===> Cleaning for qt6-webengine-6.10.2 . . . qt6-pdf-6.10.2 also got an extract/timeout failure. So it seems that it is not just the pkg-status.freebsd.org presentation pages that end up messed up. -- === Mark Millard marklmi at yahoo.comhome | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?e6c5dead-a7a5-47bd-b030-e957990e6897>