-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
upgrade: oc_migrations already exists #2227
Comments
Sorry to hear you ran into difficulties. You should be able to start with a clean set of volumes, return to your original image, and restore your database + config from a backup, I'm unclear what originally occurred. The moment the 29 image boots it checks and aborts (as you saw) if the major versions aren't reasonable for an upgrade to occur. So the 29 container start alone wouldn't touch your existing db. 27.1.1 is fairly old. Nextcloud suggests upgrading to then current latest maintenance release in a given major before upgrading to a new major release. Part of the reason for that is to make sure all previous db changes (migrations) have been applied before upgrading. It's possible you encountered something related to that. https://docs.nextcloud.com/server/latest/admin_manual/maintenance/upgrade.html You might find help at the community help forum: https://help.nextcloud.com |
I just tried to upgrade nextcloud trying to get a fix applied:
then I downgraded the container one version and tried again:
and now nextcloud is no longer accessible and I have no idea what to do, and I need it working as soon as possible :/
Edit: After trying several times to make it accept my backup, which all ended up booting into maintenance mode anyway, I don't think this is properly salvageable
The text was updated successfully, but these errors were encountered: