Opened 3 years ago

Closed 20 months ago

#9359 closed defect (fixed)

FFmpeg trac server frequently 503'ing

Reported by: varenc Owned by:
Priority: normal Component: trac
Version: Keywords: wiki trac
Cc: Blocked By:
Blocking: Reproduced by developer: no
Analyzed by developer: no

Description

Right now this trac server is returning 503 errors half the time for me.

Screenshot: https://dl.dropboxusercontent.com/s/wgszvysgpcuyx68/Screen%20Shot%202021-08-03%20at%202.15.48%20PM.png

You can also check this by running this a few times:

curl -o /dev/null -s -w "%{http_code}\n" https://trac.ffmpeg.org/

Seems like the server needs a capacity upgrade? Or database rebuild?

Alternatively, I imagine the majority of traffic is to the ffmpeg wiki documentation pages from logged out users, meaning they're just accessing static content that's identical between viewers. Some more aggressive caching might relieve the load from these views. It would require setting the right caching headers, but something like Cloudflare could even be used to cache that static content for logged out user and relieve the load from the trac server. ¯\_(ツ)_/¯

Change History (11)

comment:1 by Balling, 3 years ago

Status: newopen

Same here. Really irritating. It is actually more often 503 than not.

Also why it says "Apache/2.4.41 (Ubuntu) Server at trac.ffmpeg.org Port 80" even for https??

Last edited 3 years ago by Balling (previous) (diff)

comment:2 by Balling, 3 years ago

Resolution: fixed
Status: openclosed

No longer happens, nice.

comment:3 by Balling, 3 years ago

Resolution: fixed
Status: closedreopened

Started happening again.

comment:4 by varenc, 3 years ago

I can also report it's still happening. Got 503'd when trying to login.

comment:5 by hydra3333, 3 years ago

Yes almost all of the time yields a 503

comment:6 by hydra3333, 3 years ago

503 still occurring, took 4 tries to get up the list of tickets :(

comment:7 by Balling, 3 years ago

Resolution: fixed
Status: reopenedclosed

Did not happen for a couple of days, hope this is over.

comment:8 by Balling, 2 years ago

Resolution: fixed
Status: closedreopened

Started happening again.

comment:9 by Elon Musk, 2 years ago

Resolution: invalid
Status: reopenedclosed

comment:10 by Balling, 20 months ago

Resolution: invalid
Status: closedreopened

Started happening again.

comment:11 by Balling, 20 months ago

Resolution: fixed
Status: reopenedclosed

Fixed again.

Note: See TracTickets for help on using tickets.