I made the huge mistake of upgrading on the same day of the new release. I had copied my inventory folder to a new pull of lemmy-ansible, checked out 1.3.0, and ran it with no errors. But refreshing the took a very long time to load. The closest issue I found was at https://github.com/LemmyNet/lemmy/issues/4244 but that’s a deep dive that didn’t shine any light for me. Hours of extensive searching yielded little help.
I was expecting to see downtime like the readme meantioned, but the site was back up right after the playbook ran. Is the current slowdown actually the “downtime” the readme is referring to? I reran the playbook and re-examined every point in the documentation and the instructions for something I may have missed, but could not determine where I may have gone wrong.
I don’t know if this will help, but my Jerboa client gives the error when I try to refresh on my instance:
Illegal input: Field 'admin' is required for type with serial nam... and the rest is cut off.
I’ll leave with some questions that may relate to a solution, but will be good to know anyway. I appreciate any insight you may have.
-
Is it possible to downgrade to 1.2.1?
-
My database is backed up. Would deleting the /srv/lemmy/sitedirectory and starting from scratch restore things?
___
The lemmy frontend will come up fast, but you would see an error and a popup telling you that lemmy is still starting. If you can see content, then the DB migration is finished already. The 1.3.0 branch of ansible doesn’t have any changes which would cause performance impact. Currently it just adjusts the readme and adds pictrs 0.4.7.
There’s Lemmy 0.19.0’s persistent federation queue which brings a much higher database load, this could be why OP reports reduced performance.
Yes, but those changes are not unique to the ansible 1.3.0 deployment