Occasional 502 bad gateway from trac.osgeo.org

[strk]

It happens to get 502 bad gateway from trac.osgeo.org urls, including .css files (ie: ​https://trac.osgeo.org/postgis/chrome/common/css/trac.css)

It was confirmed by me, by Grayshade and by Markus ( ​https://lists.osgeo.org/pipermail/sac/2024-September/016637.html )

[neteler]

I think I saw "​https://trac.osgeo.org/osgeo/newticket" as URL when the 502 error occurred.

BTW: Firefox 129.0.2 (64-bit) on Fedora 39 used here.

[strk]

With static files served without python (#3272) it looks like 502 are harder to get. Can you still get any, Markus, Grayshade ?

[strk]

I'm assuming this is fixed. At least I cannot reproduce the 502 anymore. Feel free to reopen shall you see it again.

[strk]

Not fixed. Still happens, /var/log/apache2/error.log reports segfaults in apache2 worker processes, which would explain the 502 response from nginx.

I've upgraded to Bookworm in staging to see if the problem goes away and it looks like it does. Please test there. ​https://dev.trac.osgeo.org

[strk]

We've upgraded TracSVN to Debian Bookworm which fixed the segfault. I'm closing this again as I don't see 502 anymore after that.

[strk]

And I'm reopening again as I saw a new apache segfault happening :(

[robe]

Is it still an issue. Haven't been getting these since you upgraded to bookworm.

[strk]

For the record between [Sun Sep 22 14:15:42.942001 2024] and [Sun Sep 22 22:43:11.019063 2024] we got 5 Segmentation faults, according to error log