search

ubergeek77 / Lemmy-Easy-Deploy

Deploy Lemmy the easy way!
MIT License
133 stars 14 forks source link

0.18.3-rc.2 #51

Closed airjer closed 1 year ago

airjer commented 1 year ago

Using this to upgrade to 0.18.3-rc.2 creates nothing but an error page causing you to revert back to the latest stable release. After this is done, when you create a post it's just an endless loop visibly, but the post gets created.

ubergeek77 commented 1 year ago

Unfortunately, I cannot provide assistance with unofficial release candidate versions. It's possible they may break, and while reports of breakage are helpful for me to prepare for new versions, I can't do much other than ensure the latest stable version works once it is released officially.

However, it would help if you had not skipped the issue template, as this provides me with helpful info to understand what's going on :)

airjer commented 1 year ago

Yeah I understand, just thought I'd report. Sorry the issue template wasn't even there for me when I created the post this time for some reason. Will it help at all with me being back on the stable release? Or is there anywhere else you'd like me to copy from that would help you?

airjer commented 1 year ago

Actually, it seems that quite possibly this has completely ruined my instance again keeping posting from syncing elsewhere. 🤦‍♂️. Any tips? I did nothing but upgrade and then downgrade....

ubergeek77 commented 1 year ago

Ah, that is unfortunate. That is why Lemmy Easy Deploy has a very hard-to-miss warning about upgrades, as the Lemmy team has a habit of changing the schema pretty much every release. It's possible something got changed, breaking your instance. In that warning, I recommend taking a backup, which is especially advised for untested RC versions. If you didn't see that warning, let me know, because that actually is a bug. I want to make sure users of this script are properly warned. Here is what it looks like:

image

As for 0.18.3-rc.2, unfortunately I was not able to reproduce any deployment issues, everything is perfectly fine:

image

This particular screenshot was taken by upgrading my testing instance from 0.18.2-rc.2 to 0.18.3-rc.2. Haven't touched this one in a while so it was quite a few versions behind, but the upgrade still worked fine.

With RC's, this could be caused by really anything, and unfortunately I don't have much capacity to support Lemmy issues that aren't related to a misconfiguration in the deployment files. Everything looks good to go on my end, and I am also monitoring their reference deployment files. No significant changes were made.

If you upgrade back to 0.18.3-rc.2 and then post some logs, I may be able to point you in the right direction, but ultimately this may need to be filed as an issue on one of the Lemmy issue trackers, depending on if this is a UI or a Backend issue (I should be able to help you deduce at least that much)

ubergeek77 commented 1 year ago

I should mention, during the database migration, the UI will seem like it's throwing errors, but in reality, it's not ready to serve content yet, appearing as an error. Is it possible you shut it down too fast before the migration was complete?

If that's the case, maybe you could try re-upgrading to the RC version and waiting a little while.

airjer commented 1 year ago

Well good news, I just noticed rc3 released so I gave that a go and everything seems to be working fine! Wish I had more input for you as to what happened, but maybe your last explanation possibly is what happened? I'm not entirely sure.

airjer commented 1 year ago

Solved by going to rc3