-
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
Upgrade fails, synapse no longer usable #22
Comments
Hello, Thank you for your report, postgresql is already as a dependence. I think the problem is more about the migration script. Have you any more log about this upgrade because with that it's difficult to know were is the bug. Normally you could find a more verbose report in : |
Hello, Here it is! You're right. Actually it looks like the issue is elsewhere, but I'm not sure. Would that interrupt the whole thing? |
I see that :
Really strange, a think that the install of dependance fail. could you try to lunch this command : |
Ok, here the output, but it may have been convoluted with my later actions. I don't think I had postgresql installed before, but I've tried multiple apps, and one of them may have installed it as a dep at some points. So it may have left behind some config files. So, with all this taken in account, here's what
For now, I won't proceed, in case that destroys clues or confuses further the picture. The good news is that I was using it for rooms only, and the other users on my server had not touched it yet. So not really anything was lost for me but a bit of time. |
Ok, It look like that the synapse dependance can't be installed. Could you try this command to see witch package is a problem : It's also possible that postgresql wasn't cleanly removed because when you remove or purge the package there are a lot of file witch stay at sometime it could be a problem on the next install. |
Here's the output: |
I see that :
It look like that some package have a problem about dependance, and not only postgresql. You could also try after |
Ok! I found the problem! Once that was done, I also had to rename the directory in /opt/yunohost. That case is closed for me (I re-install Synapse and it worked). But for others, it may be worth having a less damaging upgrade when some issues are encountered during packages installation? I can still dig through log files if there is anything else you need. Thanks for your help! |
Hello, Thank you really much for your answer. I know that this upgrade could break the install, so I'm happy to know the issue for you. I will search a way to do the upgrade more secure. If your have any idea to increase the upgrade I'm open. |
We're getting off topic, but I traced down what went wrong with the backup restore. After reviewing the log, here's the sequence: -Attempt to upgrade: FAIL (that was this very ticket) But in the app removal process, I have: I should have been more curious at that time, but I wasn't. So I can't tell which happened:
I would bet on the 1st, though. I assume the restoration and installation share as much code as possible, right? |
I think that it look like that the yunohost app settings has been removed but not the file. I think that the yunohost cli have removed the settings (on the restore script when it fail) but the config file has not been removed. I these thing like that could append when a lot of things fail. But this problem could be with every apps when a lot of command fail... Since the last yunohost version less code is shared between the restoration and install script because with the last version a lot of file are automatically reinstalled by the special yunohost helper. So the restore script is really lighter than the install script. I will see (when I have time) to improve the upgrade script (when we do the migration) with more security. |
Upgraded today, had the following error:
Warning: dh_install: Compatibility levels before 9 are deprecated (level 7 in use) Warning: dh_installdocs: Compatibility levels before 9 are deprecated (level 7 in use) Warning: dh_installdeb: Compatibility levels before 9 are deprecated (level 7 in use) Warning: E: Packages need to be removed but remove is disabled. Warning: /etc/init.d/matrix-synapse wasn't deleted because it doesn't exist. Warning: /lib/systemd/system/matrix-synapse.service wasn't deleted because it doesn't exist. Warning: /etc/systemd/system/matrix-synapse.service wasn't deleted because it doesn't exist. Warning: Created symlink from /etc/systemd/system/multi-user.target.wants/matrix-synapse.service to /etc/systemd/system/matrix-synapse.service. Warning: No passwd entry for user 'postgres' Warning: !! Warning: synapse's script has encountered an error. Its execution was cancelled. Warning: !! Warning: Error: Unable to upgrade synapse Error: No app to upgrade
Would I be correct to say that the install fails if postgre is not already installed?
Should it not be in the dependencies?
The text was updated successfully, but these errors were encountered: