this post was submitted on 05 Jul 2023
3297 points (99.4% liked)

Lemmy.World Announcements

28381 readers
4 users here now

This Community is intended for posts about the Lemmy.world server by the admins.

Follow us for server news ๐Ÿ˜

Outages ๐Ÿ”ฅ

https://status.lemmy.world

For support with issues at Lemmy.world, go to the Lemmy.world Support community.

Support e-mail

Any support requests are best sent to [email protected] e-mail.

Report contact

Donations ๐Ÿ’—

If you would like to make a donation to support the cost of running this platform, please do so at the following donation URLs.

If you can, please use / switch to Ko-Fi, it has the lowest fees for us

Ko-Fi (Donate)

Bunq (Donate)

Open Collective backers and sponsors

Patreon

Join the team

founded 2 years ago
MODERATORS
 

Another day, another update.

More troubleshooting was done today. What did we do:

  • Yesterday evening @phiresky@[email protected] did some SQL troubleshooting with some of the lemmy.world admins. After that, phiresky submitted some PRs to github.
  • @[email protected] created a docker image containing 3PR's: Disable retry queue, Get follower Inbox Fix, Admin Index Fix
  • We started using this image, and saw a big drop in CPU usage and disk load.
  • We saw thousands of errors per minute in the nginx log for old clients trying to access the websockets (which were removed in 0.18), so we added a return 404 in nginx conf for /api/v3/ws.
  • We updated lemmy-ui from RC7 to RC10 which fixed a lot, among which the issue with replying to DMs
  • We found that the many 502-errors were caused by an issue in Lemmy/markdown-it.actix or whatever, causing nginx to temporarily mark an upstream to be dead. As a workaround we can either 1.) Only use 1 container or 2.) set ~~proxy_next_upstream timeout;~~ max_fails=5 in nginx.

Currently we're running with 1 lemmy container, so the 502-errors are completely gone so far, and because of the fixes in the Lemmy code everything seems to be running smooth. If needed we could spin up a second lemmy container using the ~~proxy_next_upstream timeout;~~ max_fails=5 workaround but for now it seems to hold with 1.

Thanks to @[email protected] , @[email protected] , @[email protected], @[email protected] , @[email protected] , @[email protected] for their help!

And not to forget, thanks to @[email protected] and @[email protected] for their continuing hard work on Lemmy!

And thank you all for your patience, we'll keep working on it!

Oh, and as bonus, an image (thanks Phiresky!) of the change in bandwidth after implementing the new Lemmy docker image with the PRs.

Edit So as soon as the US folks wake up (hi!) we seem to need the second Lemmy container for performance. So that's now started, and I noticed the proxy_next_upstream timeout setting didn't work (or I didn't set it properly) so I used max_fails=5 for each upstream, that does actually work.

(page 7) 49 comments
sorted by: hot top controversial new old
[โ€“] [email protected] 2 points 1 year ago
[โ€“] [email protected] 1 points 1 year ago (1 children)

I love how open you guys are when it comes to running the server! Much nicer than lemmy.ml imo

load more comments (1 replies)
[โ€“] [email protected] 1 points 1 year ago

Thanks admins, things feel much smoother now. ๐Ÿ‘

[โ€“] [email protected] 1 points 1 year ago

Amazing results! Thank you for all of your hard work. The collaboration among the admins is inspiring.

[โ€“] [email protected] 1 points 1 year ago

Yay, I can finally log in on Chrome!

[โ€“] [email protected] 1 points 1 year ago

Glorious, Ruud!

[โ€“] [email protected] 1 points 1 year ago

I think some of the empty page issues are back now?

[โ€“] [email protected] 1 points 1 year ago

Sounds like we need to comment more to me. Great work all around!

[โ€“] [email protected] 1 points 1 year ago

Amazing guys. I did donate so you can keep up with things. I really want Lemmy to last.

[โ€“] [email protected] 1 points 1 year ago

Building history one update at a time ๐Ÿ˜Ž

[โ€“] [email protected] 1 points 1 year ago

Everything is feeling great so far. The only bug I'm encountering is that when opening a thread (in Firefox on desktop) it auto-scrolls down past the content to the replies.

[โ€“] [email protected] 1 points 1 year ago

Awesome. Great work all!

[โ€“] [email protected] 1 points 1 year ago (1 children)

Can you describe your setup? Single instance or multi-node setup behind load balancer?

[โ€“] [email protected] 1 points 1 year ago

1 big server with nginx load balancing to the docker containers running Lemmy

[โ€“] [email protected] 1 points 1 year ago

You guys are amazing!

[โ€“] [email protected] 1 points 1 year ago

Huge thank you for all your hard work^^

[โ€“] [email protected] 1 points 1 year ago (4 children)

Not that it really matters, but did anyone else notice their comment/post points get deleted after this update? Seems odd.

load more comments (4 replies)
[โ€“] [email protected] 1 points 1 year ago

Great work!

[โ€“] [email protected] 1 points 1 year ago

Loading is faster, thank you guys ๐Ÿ‘

[โ€“] [email protected] 1 points 1 year ago

huge improvement! respect ... massive difference to before - well done

didn't get an error so far

[โ€“] [email protected] 1 points 1 year ago

I tried to enable push notifications and the app crashed. Also, how do I create a community?

[โ€“] [email protected] 1 points 1 year ago

The 502 error still seems to be common by me. Vut they are less permanent. Before it stayed multiple refreshes now it is safe to say after 1 reload it is most of the time gone.

[โ€“] [email protected] 1 points 1 year ago

Thank god, wasn't able to use the site lol

[โ€“] [email protected] 1 points 1 year ago

You guys are doing god's work. Thank you thank you thank you...

load more comments
view more: โ€น prev next โ€บ