exxos's Atari, Amiga & retro forum

I've been seeing it quite regularly over the last few weeks but since a refresh in the browser sorted it, didn't bother worrying about it.

I'll let you know if I see it again from now on....

The phrase was only found in the nginx cache (other than logs and the SQL database) So let me know if anyone sees it again...

It also begs the question why Nginx has a outdated cache, and why its even using it in the first place!

Yes. Its been happening to me for the last 2 days or so.

Last time I saw it was earlier today after the page 'times out'.(?)

I just refresh the page and can return to the sites landing page, so its not been a big problem for me.

Yeah I just assumed you were buggering about with something again :D

Its now stopped happening, so all good I guess? :)

Had you customised some of the status pages or error handling on say 503 errors? Eg
usr/local/nginx/html/error503.html

Edit: or any resource limits set? Like max_conns

mrbombermillzy wrote: 13 Jun 2025 07:17 Its now stopped happening, so all good I guess? :)

I would give it a fe days as it random happens to me..

viking272 wrote: 13 Jun 2025 07:47 Had you customised some of the status pages or error handling on say 503 errors? Eg
usr/local/nginx/html/error503.html

Edit: or any resource limits set? Like max_conns

404 is custom...

There's likely limits but they are generally "high". Possible nginx could serve a cached page, but it shouldn't have stored outdated pages for weeks in the firstplace.. Maybe it's some bug...

.NGINX makes it possible to remove outdated cached files from the cache. This is necessary for removing outdated cached content to prevent serving old and new versions of web pages at the same time

https://docs.nginx.com/nginx/admin-guid ... t-caching/

So you have to do this manually?! :WTF:

exxos wrote: 13 Jun 2025 09:01

viking272 wrote: 13 Jun 2025 07:47 Had you customised some of the status pages or error handling on say 503 errors? Eg
usr/local/nginx/html/error503.html

Edit: or any resource limits set? Like max_conns

404 is custom...

There's likely limits but they are generally "high". Possible nginx could serve a cached page, but it shouldn't have stored outdated pages for weeks in the firstplace.. Maybe it's some bug...

Maybe use grep for the word broken?
grep -Hrn 'broken' /
This searches from top level for the word broken and recurses directories, printing the path of files and lines the word or phrase is found