-
Notifications
You must be signed in to change notification settings - Fork 262
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
Cannot update from v20.0.7.1 #5741
Comments
When updating via the web, the database is not backed up? |
What version of Nextcloud is that? |
This doesn't make sense. Your error said the exception was thrown on L127 but there is no such code there https://github.com/nextcloud/server/blob/68fecc1d9f6810e815c6a6ba80d4c13a0bde98b8/lib/private/Repair.php#L127 I would expect it to throw here instead https://github.com/nextcloud/server/blob/68fecc1d9f6810e815c6a6ba80d4c13a0bde98b8/lib/private/Repair.php#L143 |
@C-Magic can you compare your file to stable20 please? https://github.com/nextcloud/server/blob/stable20/lib/private/Repair.php#L129 |
How did you get your version? Did you pull it from Github? |
I do not remember. I remember trying to run it on docker, but there were a lot of problems in the finished solution, in particular, they were connected with ssl and Collabora, which were frozen, I launched it on LXC. Well, there were so many experiments that I can't even remember where I got the code from. But several times everything was updated normally through the console. This time I decided that once the product is a stable update via the web interface. And that's all. Everything is broken! Was it just lucky? |
If I just change this file, will it be correct? |
Replacing single files will likely cause more damage. Could you download an official package from https://download.nextcloud.com/server/releases/? E.g. the latest stable 20 and then replace your copy with that? As always: make backups before so you can restore the previous state. |
Found a snapshot of the previous update: Now I'll try to change it to latest-20.zip |
you need to provide the relevant section(s) of your nextcloud.log But may I ask you to put the upgrade issues to https://help.nextcloud.com/c/support/7? Github is not a support forum and so far we don't see a clear indication of a bug in Mail. Please use the forums to get your instance to a working version of nextcloud. Once that is done you can try to reproduce the Mail migration error when you enable the app. Leave the app disabled until then. |
I have a very similar problem docker container on unraid
|
I have the same error. Installed NC originally from official release tarball. CLI logs:
|
If you need an urgent workaround to get your NC install up and running again (as I did), then follow the instructions here to disable the mail app from CLI, then your NC should finish the upgrade and work correctly: https://help.nextcloud.com/t/how-to-remove-apps-from-the-terminal/63569 |
exact same issue here. enabling the app afterwards again is still not possible
|
@Rello you can still reproduce after the upgrade? This is great. You can help us 🤗 Do you remember the trick to track down a injected service that can't be loaded by the DI container? It must be something like that here. Could you comment out some of the constructor args of ProvisionAccounts or nested classes? |
nextcloud/server@40507ca was only added for 21. Therefore your installations also do 💥 when |
The fix can be found at #5783. https://patch-diff.githubusercontent.com/raw/nextcloud/mail/pull/5783.patch is the patch. https://docs.nextcloud.com/server/latest/admin_manual/issues/applying_patch.html will guide you through the patching process. I would appreciate if two of you could test and verify the patch. Once I got your confirmation I'll merge, backport and release. ✌️ |
Weird! |
Well welcome to Nextcloud 21. I need test results for 20. 21 won't be affected. You won't see the error. |
If necessary, I can roll back to 20.0.6 and update again |
Hi, |
20.0.6 (mail 1.4.2 to 1.11.0) - OK (post patch)! |
pseudoua is also me (from home) |
The text was updated successfully, but these errors were encountered: