-
Notifications
You must be signed in to change notification settings - Fork 33
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
Updater doesn't do anything / All checkmarks already set (or green) #378
Comments
Now that its moved here it seems the same problem mentioned here: |
@Rilgamon The update button on the web client worked for me today. I was able to successfully update. |
The update button on mine just does nothing. No feedback, no errors, nothing. |
I had similar issue from |
Did it actually work for you? |
It shows version 21.0.0 in the |
For me, using the updater is an invariant action:
So, executing the updater a second (or however many times) directly in sequence produces the same output everytime, but no change. |
I solve this issue with a delete of the data/updater-xyz/ folder, and after that updater.phar --no-interaction. |
This worked, thanks! |
@blizzard4591 , did u succeed to go to 22 ? In my case not yet. I am was stuck as u @21.0.X and now i am on 21.0.4, but i cant go to 22... |
Don't know if this is still relevant to you @Benouare , but I could upgrade from 21.0.5.1 to 22.2.0.2 with the following steps
|
Hi, --- EDIT --- Benoît |
Maybe, but be aware that the updates are usually rolled out gradually to the userbase, the schedule for 22.1.1 is given at
If you want to upgrade earlier you can always download the archive and upgrade manually. |
I have removed that folder now its upgrading, thanks @dirks |
The bug came back! I am now (this time around) stuck on 22.1.1 and can not upgrade to 22.2.0. |
yeah, even after an update to 22.2.0 some apps didn't updated and I did the update processes manually, enabled them again. |
It sounds like the You can remove them manually (as noted above in some of the comments), but the safest is to run Of course always have backups before doing updates/upgrades. To get to the bottom of what's going on, it would be helpful to see your |
Closing since this issue hasn't had new traffic or info on it needed to determine root cause. If you encounter this situation, please check your EDIT: Additional more recent coverage in #243 |
When using web-updater or commandline-updater a new update (21.0.3) is found. But the process ends with "Nextcloud is already latest version" and stays at current 21.0.2.
System:
Updater-Output
www-data@home:~/home/updater$ php updater.phar
Nextcloud Updater - version: v20.0.0beta4-11-g68fa0d4
Current version is 21.0.2.
Update to Nextcloud 21.0.3 available. (channel: "stable")
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-21.0.3.zip
Open changelog ↗
Steps that will be executed:
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
Continue update? [y/N] y
Info: Pressing Ctrl-C will finish the currently running step and then stops the updater.
[✔] Check for expected files
[✔] Check for write permissions
[✔] Create backup
[✔] Downloading
[✔] Verify integrity
[✔] Extracting
[✔] Enable maintenance mode
[✔] Replace entry points
[✔] Delete old files
[✔] Move new files in place
[✔] Done
Update of code successful.
Should the "occ upgrade" command be executed? [Y/n]
Nextcloud is already latest version
Keep maintenance mode active? [y/N]
Maintenance mode already disabled
Maintenance mode is disabled
The text was updated successfully, but these errors were encountered: