Occasional error 503 when accessing library list

[Lastique]

https://www.boost.org/libraries/latest/list/

Sometimes, when I open the library list, I get a delay of several seconds and then error 503 "first byte timeout".

This doesn't happen every time, but it reproduces from time to time.

This is on Firefox 138 and 139 on Kubuntu 24.04.

[sdarwin]

I have increased the 'first byte timeout' from 15 seconds to 60 seconds.
Please report if the problem continues.

[sdarwin]

Also, for the next occurrence, it could help to send the exact time it happened. (and timezone. or UTC).

[Lastique]

Thanks. Right now it doesn't happen, but the page also opens quickly. I'm guessing, when it happens, something is running slow, and I'm not sure an increased timeout would be a proper solution in that case.

Last time it happened was when I reported this bug, a few minutes earlier.

[rbbeeston]

Something similar to this was also reported when the site was launched, and a fix was put in. @GregKaleka can you also keep an eye on this if it keeps happening?

[GregKaleka]

I think Rob is referring to #1798. The fix for that was related to parsing html from a documentation file, which the libraries list definitely does not do, so the fix would not be the same.

I'll definitely keep an eye on this.

[sdarwin]

In the screenshot "cache-fra" is Frankfurt. And then, even a further network trip to Andrey. Could be packet loss. Although not certain.

[Lastique]

Now the website seems to be completely down. I get "stream timeout" or "upstream request timeout" with no further details.

[sdarwin]

@Lastique , yesterday I enabled "Shielding" on the CDN, which routes all requests through one datacenter to increase the HIT ratio. Overall, statistics improved. And, there was not a drop-off of traffic. But you are reporting a problem.
I have now just switched the shield location from Chicago to Ashburn. If you enabled Developer Tools on the browser, the relevant fields are X-Cache, X-Served-By,

[Lastique]

Right now the website is accessible again. The response e.g. for styles.css is:

HTTP/2 200 OK
server: nginx/1.21.6
content-type: text/css
last-modified: Fri, 13 Jun 2025 00:14:44 GMT
etag: "684b6d74-c9e0"
via: 1.1 google, 1.1 varnish, 1.1 varnish
accept-ranges: bytes
date: Fri, 13 Jun 2025 14:29:02 GMT
age: 3221
x-served-by: cache-chi-klot8100152-CHI, cache-fra-eddf8230082-FRA
x-cache: HIT, HIT
x-cache-hits: 11, 1
x-timer: S1749824943.557052,VS0,VE2
strict-transport-security: max-age=300
content-length: 51680
X-Firefox-Spdy: h2

[sdarwin]

That's good. There is a real lag in their configuration, cache-chi is still Chicago, cache-iad is Ashburn. I'm getting

x-served-by cache-iad-kcgs7200030-IAD, cache-den-kden1300080-DEN

Or maybe FRA (Frankfurt) is serving a cache hit and it still remembers that is from CHI (Chicago). yes.