that means that all apps with āno compatible versionā might not work any more if you update. They might become less as you postpone the update a bit
for a smooth an successful update experience:
- be sure to be on the āstableā Update channel
- do the upgrades from the command line rather than via the frontend (you need ssh access to your server). See below
assumes that your nextcloud data root is in /var/www/nextcloud/
you might need to replace the apache by the user your files belong to
[root@XXX ~]# ls -l /var/www/nextcloud/
total 164
drwxr-xr-x. 43 apache apache 4096 22. Okt 19:34 3rdparty
drwxr-xr-x. 55 apache apache 4096 22. Okt 19:34 apps
-rw-rārā. 1 apache apache 19327 6. Okt 09:15 AUTHORS
drwxr-xr-x. 2 apache apache 4096 22. Okt 19:34 config
-rw-rārā. 1 apache apache 4095 6. Okt 09:15 console.php
-rw-rārā. 1 apache apache 34520 6. Okt 09:15 COPYING
drwxr-xr-x. 22 apache apache 4096 22. Okt 19:34 core
advantage of command line:
-
you can see what hppens
-
if s.th. goes wrong, you have proper error reports that you can directly ask google or the nextcloud forum for
sample update:
[root@XXX ~]# sudo -u apache php /var/www/nextcloud/updater/updater.phar
Nextcloud Updater - version: v24.0.0beta3-1-g67bf13b dirty
Current version is 24.0.4.
Update to Nextcloud 24.0.6 available. (channel: āstableā)
Following file will be downloaded automatically: https://download.nextcloud.com/server/releases/nextcloud-24.0.6.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
Start 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] y
Nextcloud or one of the apps require upgrade - only a limited number of commands are available
You may use your browser or the occ upgrade command to do the upgrade
Setting log level to debug
Repair step: Repair MySQL collation
Repair info: Not a mysql database ā nothing to do
Repair step: Repair SQLite autoincrement
Repair step: Copy data from accounts table when migrating from ownCloud
Repair step: Drop account terms table when migrating from ownCloud
Updating database schema
Updated database
Disabled incompatible app: ocsms
Updating ā¦
Updated to 2.12.1
Update app calendar from App Store
Repair step: Update name of the stored view
Update app contacts from App Store
Update app mail from App Store
Repair step: Restore default tags that are missing
Repair info: Looking up default tags
Repair info: 2 accounts to check found
Restore default tags that are missing
Starting ā¦
0/2 [>---------------------------] 0%
Starting ā¦
2/2 [============================] 100%
Repair step: Add a generated message-id to all Mail messages that have none
Repair info: Looking up messages without a message-id
Repair step: Purify and migrate collected mail addresses
Purify and migrate collected mail addresses
Starting ā¦
0/65 [>---------------------------] 0%
Starting ā¦
65/65 [============================] 100%
Repair step: Insert background jobs for all accounts
Insert background jobs for all accounts
Starting ā¦
0/2 [>---------------------------] 0%
Starting ā¦
2/2 [============================] 100%
Repair step: Make Mail itinerary extractor executable
Repair step: Create or update provisioned Mail accounts
Repair info: 0 accounts provisioned
Repair step: Repair Broken Threads for all mail accounts
Repair info: Repaired threads, 0 messages updated
Update app tasks from App Store
Repair step: Migrate legacy conversation reading states
Migrate legacy conversation reading states
Starting ā¦
0/0 [----------->----------------] 0%
Repair step: Repair MySQL collation
Repair info: Not a mysql database ā nothing to do
Repair step: Repair mime types
Repair step: Clean tags and favorites
Repair info: 0 tags of deleted users have been removed.
Repair info: 0 tags for delete files have been removed.
Repair info: 0 tag entries for deleted tags have been removed.
Repair info: 0 tags with no entries have been removed.
Repair step: Repair invalid shares
Repair step: Move .step file of updater to backup location
Repair info: .step file exists
Repair info: .step-previous-update removed
Repair info: .step file moved to .step-previous-update
Repair step: Add move avatar background job
Repair info: Repair step already executed
Repair step: Add preview cleanup background jobs
Repair step: Migrate oauth2_clients table to nextcloud schema
Repair info: Update the oauth2_access_tokens table schema.
Repair info: Update the oauth2_clients table schema.
Repair step: Fix potential broken mount points
Repair info: No mounts updated
Repair step: Repair language codes
Repair step: Install new core bundle components
Repair step: Add log rotate job
Repair step: Clear frontend caches
Repair info: Image cache cleared
Repair info: SCSS cache cleared
Repair info: JS cache cleared
Repair step: Clear every generated avatar on major updates
Repair step: Add preview background cleanup job
Repair step: Queue a one-time job to cleanup old backups of the updater
Repair step: Cleanup invalid photocache files for carddav
Repair step: Add background job to cleanup login flow v2 tokens
Repair step: Remove potentially over exposing share links
Repair info: No need to remove link shares.
Repair step: Clear access cache of projects
Repair step: Reset generated avatar flag
Repair step: Keep legacy encryption enabled
Repair step: Check encryption key format
Repair step: Remove old dashboard app config data
Repair step: Add job to cleanup the bruteforce entries
Repair step: Queue a one-time job to check for user uploaded certificates
Repair step: Repair DAV shares
Repair step: Add background job to set the lookup server share state for users
Repair step: Add token cleanup job
Starting code integrity checkā¦
Finished code integrity check
Update successful
Maintenance mode is kept active
Resetting log level
Keep maintenance mode active? [y/N] n
Maintenance mode disabled
Maintenance mode is disabled