Fedia Discussions

2 readers

3 users here now

founded 1 year ago

MODERATORS

jerry@fedia.io

Final fedia update for June 19 (fedia.io)

submitted 1 year ago by jerry@fedia.io to c/fedia@fedia.io

7 comments fedilink hide all child comments

It turns out the way I set up file sharing between the front end web server and the app server created immense slowdowns on fedia. I consolidated some things (web server on app server now), which isn't a long term solution, but will work in the very short term.

I am having to copy media from the s3 storage bucket back to a local directory - that is going to take a long time and images on the site are going to be broken until that finishes - hopefulle overnight.

There are still a few lingering error 500s and I will tackle that tomorrow evening.

you are viewing a single comment's thread
view the rest of the comments

[–] all-knight-party@fedia.io 2 points 1 year ago (1 children)

Its doing that on and off for me. I think it's got to be linked to the magazines that throw 500 errors. For instance, if you try to look at your subs and that first page contains a post that would've federated from one of the magazines throwing a 500 error, it just throws a 500 for that whole sub page. Just my assumption.

[–] jerry@fedia.io 2 points 1 year ago

it appears to (mostly) be due to some database issues - I am trying to learn the schema and relationships and find/fixing the discontinuities