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).
EDIT/UPDATE: I unsubscribed manually to a few communities each time, checking if the front page loaded fine. Eventually, it did.
Re-subscribing to either !technology or !fediverse seems to trigger the error again.
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?
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).
Check if you're subscribed to any of those communities: !technology , !comicstrips or !memes. If you are, try to unsubscribe and see if your front page works again. For me it did the trick.
!fediverse was also giving me problems, but apparently it's fine now, so odds are that the problem will eventually go away on its own.
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!
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 ) 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.
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.
Great, thanks for letting me know!! I did a bit of research and I think that the next time I need to upgrade the instance I will move it to a dedicated server instead of a virtual private server. But hopefully it runs smoothly for some time! :)
Hey @RobotToaster , @lvxferre , and @Shdwdrgn - 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?
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!
It should have been fixed about 13 minutes ago! Thanks for checking! If problems persist I will try to fine-tune the database settings as suggested above.
There was a brief outage soon after I left that last reply, assume you were doing another round of maintenance at the time, but otherwise it's still looking good from here.
Ah, thanks. I think that was when I reboot the instance to change a setting that controls how post thumbnails are generated, as the new setting was failing to generate thumbnails for many posts.
Since the upgrade, I can see (here) that activities from lemmy.world are being fetched significantly faster. I will let it run for some time and hopefully this speed-up is enough to catch up.
The instance is catching up at a rate of ~15 activities/s, and we are 2.5M activities behind. So it should take about 2 days to catch up.
I have tried fiddling with some parameters to see if this could be improved, but I did not find the right knob to tune. Best is probably to just let it run 😄
Does this have anything to do with the front page giving an error message? I get a lemmy server error, however I was able to log out and log back in again, and I can get to the communities page which got me back to this discussion, but even forcing a browser refresh of the front page continues to give an error message for me. FYI, ctrl-shift-R also fails, I'm not sure what else to try.
We are working on resolving the issues
Over the next few days, there will be a change in server infrastructure. Temporary problems with the website's functionality may occur during this time.
Yeah indeed.. I too check the site from time to time. I had seen on their last posts that they were thinking of moving out of kbin.social due to the downtimes..
I will try to update you if/when they come back online.😅
Exactly! It is something that I wanted to do over a year ago, but I was not sure how... Pretty much all my knowledge about servers comes from setting up and trying not to break a lemmy instance, so this was another lesson that I was a bit scared to learn 😂 It turns out that it was very simple as the pict-rs (Lemmy's image backend) developer made a robust migration tool that automates this process. But since I don't know that beforehand, I need to triple check backups and read the instructions several times in preparation so even if it is easy and the hard work has been done by others it still requires some focus.
Mander
Hot