Final fedia update for June 19

3 years ago by jerry to c/fedia

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.

load all comments

chris 6 points 3 years ago

I'm getting 500s on the homepage and on my /sub page. Federation seems to have stopped again too.

save

path: 0 377368, hotness: undefined, score: 6, children: 4

jerry 6 points 3 years ago

I intend to spend some time debugging the reason that federation periodically just stops and has to be manually restarted, as well as the cause of the error 500's. Sorry for the problems.

save

path: 0 377368 377447, hotness: undefined, score: 6, children: 1

chris 1 point 3 years ago

No worries! This is new and I appreciate the time and effort you are spending on it.

save

path: 0 377368 377447 378996, hotness: undefined, score: 1, children: 0

all-knight-party 2 points 3 years ago

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.

save

path: 0 377368 387379, hotness: undefined, score: 2, children: 1

jerry 2 points 3 years 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

save

path: 0 377368 387379 391292, hotness: undefined, score: 2, children: 0