-
Notifications
You must be signed in to change notification settings - Fork 42
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
Failed to upgrade to 1.92.3~ynh1 #414
Comments
same here and AGAIN it removes everything after a failed upgrade and is unable to restore. I really don't understand why it deletes everything. |
Temporary fix, based on https://forum.yunohost.org/t/solved-synapse-update-failed-restore-not-possible/22888/5
Not sure why this rust python became mandatory, as I understood things, this is not really necessary for Synapse to run. I was able to successfully restore the backup after this. |
Upgrade to testing (1.93) worked fine |
Ok thank you very much for the info. So the testing works then? I cannot try it these days but as soon as I will I can close this issue. |
To be clear, did a restore as shown above and then upgraded to testing |
Thanks a lot @hieronymousch, I had the same issue, your fix worked. I just added |
Why do you have to also add |
Oh, it's not needed, it's just because yunohost backups can contain multiple apps, and the Restoring the database took about 4 hours and 15 minutes for my 40 GiB backup, I think a lot of that time was spent on index creation. As I don't want to wait such a long time again in case of failure, I'll also upgrade to testing. Edit: BTW, you can keep an eye on the restore process by running |
Thats a huge DB. I hope it's not for a familiy server because some cleaning might then be in order ;) (I'm at 3.8 GB for small familiy server but 5+ years of use) |
My database was 260GB after 2 years of use and 500 users. I managed to optimize it and bring it down to 100GB. Read more here as to why this is so big and how I managed to make it much smaller #354 So yeah for me the restore process even backup, is not feasible. I usually do a server snapshot before updating Synapse without backing it up, then if it fails I restore a snapshot for the entire server....else it is not manageable. |
I got pretty paranoid after the upgrade to bullseye and now I have a remote backup running with borg (iterative backup) and at the same time pgbackrest for incremental DB commits as well... but luckily not the volume you talk about... interesting stuff ;) |
Ok so now I finally tested it. My database is actually 60GB and files around 15GB. Restoring the backup worked thanks to the #414 (comment) comment. Backing up now takes around 25-30 minutes. Restoring takes around 40-50 minutes. Upgrading to testing also works with It is not terrible but it is something you have to do via the terminal. In case Matrix fails, then you will have to spend around 1h restoring it, if your instance is of a similar size. I hope they will push the testing into the master soon to fix this terrible issue. |
Full log here https://paste.yunohost.org/raw/satajenofu
The text was updated successfully, but these errors were encountered: