That’s the same error I was asking about below, and wondering if I had to do with the current status of collecting all the content. If so, it sounds like it could be another day or two before we can view our front pages again?
Comment on Version update and server upgrade!
lvxferre@mander.xyz 5 months ago
Sal, I got some error here: couldnt_get_posts. That appears every time that I try to visualise the instance through the “Subscribed” communities.
The error does not appear if I browse the instance through “Local” or “All”, nor if I check the list of communities that I’m subscribed to. The error happens across devices and front-ends (tested with Linux Firefox, Android Firefox, Jerboa).
Shdwdrgn@mander.xyz 5 months ago
lvxferre@mander.xyz 5 months ago
Sorry for the double reply.
Check if you’re subscribed to any of those communities: !technology@lemmy.world , !comicstrips@lemmy.world or !memes@lemmy.world. If you are, try to unsubscribe and see if your front page works again. For me it did the trick.
!fediverse@lemmy.world was also giving me problems, but apparently it’s fine now, so odds are that the problem will eventually go away on its own.
acockworkorange@mander.xyz 5 months ago
Unsubscribing from comic strips did the trick a couple days ago, thanks! And just now I’ve subscribed back and everything is normal. So feel free to subscribe again.
Shdwdrgn@mander.xyz 5 months ago
All of this sounds like the issue is related to the new server still loading up the communities. I’m subbed to a pretty good list so it’s probably best just to wait for the server to catch up. Thanks for the info though!
lvxferre@mander.xyz 5 months ago
For now, one option is to temp change your settings to browse by “Local” or “All”. Or alternatively temporarily unsubscribe off a few comms; if you’re subscribed to a small number of comms, some trial and error might help you to find which ones are causing the issue. (For me it was two LW comms).
RobotToaster@mander.xyz 5 months ago
Having the same issue here unfortunately.
Sal@mander.xyz 5 months ago
(@Shdwdrgn@mander.xyz ) I think it is related with the processing of so many activities per second while syncing with Lemmy.World.
I have tried changing some rate limits and the number of maximum database connections, but I get similar errors while moving around the site. The server is running well below 100% on all metrics, and the logs don’t produce an obvious error. I will wait until we catch up with Lemmy.World and see if that fixes the issue. If it doesn’t, then I will trouble shoot more in-depth.
acockworkorange@mander.xyz 5 months ago
Letting you know I no longer see the issue. Thanks, Sal!
Sal@mander.xyz 5 months ago
Great to hear! Thanks!
lvxferre@mander.xyz 5 months ago
Thank you!
RobotToaster@mander.xyz 5 months ago
There’s some potential solutions to this mentioned here github.com/LemmyNet/lemmy/issues/4277
Sal@mander.xyz 5 months ago
Thanks! The database is currently fetching lemmy world data as fast as possible, so this might be saturating the database. Once the syncronization is tested, I will try to tune postgres if it still happens.
lvxferre@mander.xyz 5 months ago
The issue seems to be gone for me. And the instance “feels” considerably faster than it did before :-D
Sal@mander.xyz 5 months ago
Hey @RobotToaster@mander.xyz , @lvxferre@lemmy.ml , and @Shdwdrgn@mander.xyz - we are now in sync with lemmy.world and the database under much less stress. This seems to have fixed the problems that I observed on my end. Are your problems also resolved?
RobotToaster@mander.xyz 5 months ago
I just resubbed to the communities that were causing issues and it looks like everything is working well now, thanks.
Shdwdrgn@mander.xyz 5 months ago
Ah! It looks like it JUST fixed it, I had checked about 15 minutes ago and still couldn’t get my subscribed list to load, but it does appears to be loading up now. I’ll reset my preferences and keep an eye on it through the day – hoping for the best!