Good day to all! Over the last 30 minutes or so, I’ve been having issues loading beehaw.org. Sometimes CSS is missing and the page layout is broken, and others there is a server side NGINX error.

Just wanted to make the admins aware this is happening. There are some NGINX settings that can be adjusted to make more threads available to NGINX if it is hitting a worker limit.

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

[–] ffmike 4 points 1 year ago (15 children)

I'm not an official spokescritter, but I can assure you the Beehaw admins aren't ignoring the issues. But ultimately it's going to come down to someone getting PRs in to the code. I hope someone gets some performance-focused PRs in soon.

[–] BitOneZero 1 points 1 year ago* (last edited 1 year ago) (14 children)

I’m not an official spokescritter, but I can assure you the Beehaw admins aren’t ignoring the issues.

They are not informing the end-users (and flocking new server installers) of the problem, they are leaving people like me wasting their time calling out the problem. Denial isn't just a river in Egypt. Lemmy isn't scaling, it's falling flat on it's face, and the federation protocols of doing one single like per https transaction are causing servers to overload peer servers. There isn't even anything built into lemmy_server to detect that posts&comment are misisng, nor any tools to 'heal' missing data.

Where are the server logs? Why are the crashes not being shared to developers? Do i really have to build up an instance with 5000 users to get access to the data that Beehaw's servers are logging each hour?

[–] Penguincoder 1 points 1 year ago (3 children)

Why are the crashes not being shared to developers?

Because not every issue we're experiencing even the 500's , are a result of Lemmy or their code. There is no reason to share that with them.

[–] BitOneZero 1 points 1 year ago* (last edited 1 year ago) (1 children)

Because not every issue we’re experiencing even the 500’s , are a result of Lemmy or their code.

Then what are they, when Nginx is failing to talk to the NodeJS app? I also consider this more than code, as they are also giving recommendations for performance tuning various components, etc.

I have a lot of suspicion so far that federation activity is causing 500 and other errors due to how it queues (swarms) other peers. It isn't just the lemmy-ui webapp, smartphone users, and other end-users.

[–] Penguincoder 3 points 1 year ago (1 children)

[–] BitOneZero 1 points 1 year ago

If you aren't aware, Lemmy.ml has been down for the past 45 minutes, and could likely be causing your lemmy_server code to back up with all kinds of problems.

I'm actually working on these issues 10+ hours a day, for the past two weeks.

load more comments (1 replies)

load more comments (11 replies)