-
-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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 page shown although upgrade already completed #10362
Comments
Here the output of updater.phar
The error happens too when I upgrade via web + occ upgrade command. |
I have seen this as well :/ Do you have the opcache enabled? cc @rullzer @nickvergessen Ideas why this happens? |
Yes. |
Uh. By the way. I had this effect upgrading from 13.0.1 to 13.0.2 and so on too. It happens on two of my 4 instances only. The main difference is ldap. Only the instances with ldap user management show this behaviour. Don't know if thats the reason or not. |
@MorrisJobke yes I have also experinced this (but only on my production instance). And no real idea why it happens. |
I thought it is related to the opcache (a few seconds of caching), but apparently it also happens after yesterdays upgrade and there it was in this mode for a longer period. My idea here was:
Sadly this also was the case after a few hours and didn't went away. :/ So it need to be something else. |
Could it be that this happens when an app is upgraded from the appstore? For me the first update run had following log message:
Could you check if there is also an upgrade of an app present in your first upgrade? |
I can do the next time but i don't think there was. Here the complete log of the update run: https://nopaste.fluffycloud.de/?012be90bfad34ece#8XJVeZiqs/k4+G+4FaWm3ZItyIT/BvLDQza7g6ZKevY= |
Doesn't seem to be :/ But it says it says both times:
... so there seems to be some caching hitting in :/ |
Apache vs Nginx? Both of my apache installations work without problem. The nginx ones show that problem. |
Same here - I'm on nginx as well. |
For me Nginx as well. But I think that is a coincidence. Since I run the updater from the cli. And then again an occ upgrade from the cli. (since I had it before). So nginx doesn't come into play here. |
I guess you're right. One of my supposed to be nginx installations is in fact apache. |
Just ran into this again and the |
|
I guess I know what happened: This one reads the cached config from the opcache and still holds the old version info. Thus causing the update page to reappear. |
Options: either clear opcache right before that or disable the maintenance mode before the updater.phar triggers occ upgrade. |
Why is that not using the config class? DI? |
Because it's not the server code ;) It's the updater.phar - goal of this to have it completely independent from the actual code it replaces ;) |
So what is the current workaround? Not using updater.phar? Is that enough? thanks and cheers |
@MorrisJobke may I ask what the suggested workoaround is for the time being? |
run updater.phar, but don't let it execute |
As there is no feedback since a while I will close this ticket. If this is still happening please make sure to upgrade to the latest version. After that, feel free to reopen. |
Steps to reproduce
Expected behaviour
regular login page
Actual behaviour
upgrade page is shown
Server configuration
Operating system: Ubuntu 16.04
Web server: Apache 2.4
Database: Mariadb
PHP version: 7.2
Nextcloud version: 13.0.5.2
Updated from an older Nextcloud/ownCloud or fresh install: Upgrade from 13.0.4
Where did you install Nextcloud from: tar
Signing status:
Signing status
List of activated apps:
Nothing specific in the log. When I hit the upgrade button, the upgrade succeeds but i would expect to already being done.
The text was updated successfully, but these errors were encountered: