What type of hardware are you using: Raspberry Pi 3, 4+
What YunoHost version are you running: 12.0.7
How are you able to access your server: SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no
Nextcloud upgrade 29.0.8 to 29.0.9 failed
Any idea how to fix that?
Thanks!
Seems db error… Is the service mysql working ?
systemctl status mysql
If there is not enough space on the disk also on the / path, mysql could stop…
df -h
systemctl status mysql returns a “active (running)”
$ df -h
Filesystem Size Used Avail Use% Mounted on
/dev/root 917G 241G 639G 28% /
devtmpfs 331M 0 331M 0% /dev
tmpfs 461M 160K 461M 1% /dev/shm
tmpfs 185M 1.2M 184M 1% /run
tmpfs 5.0M 16K 5.0M 1% /run/lock
/dev/mmcblk0p1 253M 53M 200M 21% /boot
tmpfs 93M 0 93M 0% /run/user/16213
have you the good credentials db in this file ( hidden sensible informations) ?
grep db `/var/www/nextcloud/
I do not understand the question…
The files within /var/www/nextcloud are own by the users “nextcloud” & “www-data”
grep db /var/www/nextcloud/
grep: /var/www/nextcloud/: Permission denied
sudo grep db /var/www/nextcloud/
grep: /var/www/nextcloud/: Is a directory
Sorry, a mistake
sudo grep db /var/www/nextcloud/config/config.php
sorry !!
$ sudo grep db /var/www/nextcloud/config.php
grep: /var/www/nextcloud/config.php: No such file or directory
But:
$ sudo ls -l /var/www/nextcloud/config
total 84
-rw------- 1 nextcloud www-data 2077 Nov 15 10:01 config.php
-rw-r–r-- 1 nextcloud www-data 78547 Oct 10 11:13 config.sample.php
The fail upgrade exit without restoring a backup ?
Ok, got it:
$ sudo grep db /var/www/nextcloud/config/config.php
'dbtype' => 'mysql',
'dbname' => 'nextcloud',
'dbhost' => 'localhost',
'dbport' => '',
'dbtableprefix' => 'oc_',
'dbuser' => 'nextcloud',
'dbpassword' => 'XXXXXXXXXXXXXXXXXXXX',
No, previous version has been restored and is running fine
So nextcloud is just running fine but haven’t been upgraded ?
exact
Perhaps it comes from the ressources of the machine ?
or perhaps inspect nextcloud before if it is relevant ? have you warnings in the admin paramters of nextcloud ?
On peut continuer en français…
Est-ce que nextcloud est sur une URL avec un sous-path comme domaine.tld/nextcloud ?
oui, c’est : mondomaine.fr/owncloud
(pour des raisons historiques 
)
Pour résoudre beaucoup de ces erreurs, il faut créer un domaine dédié genre nextcloud.mondomaine.fr et déplacé l’app à la racine.
Sinon aussi tu peux faire cela
yunohost app shell nextcloud
php occ maintenance:repair --include-expensive
Fait !
$ php occ maintenance:repair --include-expensive
- Repair MySQL collation
- All tables already have the correct collation -> nothing to do
- Clean tags and favorites
- 0 tags of deleted users have been removed.
- 0 tags for delete files have been removed.
- 0 tag entries for deleted tags have been removed.
- 0 tags with no entries have been removed.
- Repair invalid shares
- Move .step file of updater to backup location
- Add move avatar background job
- Repair step already executed
- Add preview cleanup background jobs
- Migrate oauth2_clients table to nextcloud schema
- Update the oauth2_access_tokens table schema.
- Update the oauth2_clients table schema.
- Delete clients (and their related access tokens) with the redirect_uri starting with oc:// or ending with *
- Fix potential broken mount points
- No mounts updated
- Repair language codes
- Add log rotate job
- Clear frontend caches
- Image cache cleared
- JS cache cleared
- Clear every generated avatar
- Add preview background cleanup job
- Queue a one-time job to cleanup old backups of the updater
- Cleanup invalid photocache files for carddav
- Add background job to cleanup login flow v2 tokens
- Remove potentially over exposing share links
- No need to remove link shares.
- Clear access cache of projects
- Reset generated avatar flag
- Keep legacy encryption enabled
- Check encryption key format
- Remove old dashboard app config data
- Add job to cleanup the bruteforce entries
- Queue a one-time job to check for user uploaded certificates
- Repair DAV shares
- Add background job to set the lookup server share state for users
- Add token cleanup job
- Clean up abandoned apps
- Add possibly missing system config
- Add AI tasks cleanup job
- Queue a job to generate metadata
- migrate lazy config values
- Cache logo dimension to fix size in emails on Outlook
- Theming is not used to provide a logo
- Remove shares of old group memberships
- Repair mime types
- Validate the phone number and store it in a known format for search
- WARNING: Can not validate phone numbers without `default_phone_region` being set in the config file
- Handle outdated scheduling events
- Cleaning up old scheduling events
- Adding background job to delete old scheduling objects
- Upgrading Circles App
- Fix component of birthday calendars
- 5 birthday calendars updated.
- Regenerating birthday calendars to use new icons and fix old birthday events without year
- Repair step already executed
- Fix broken values of calendar objects
0 [->--------------------------]
- Registering building of calendar search index as background job
- Repair step already executed
- Register building of social profile search index as background job
- Registering background jobs to update cache for webcal calendars
- Added 0 background jobs to update webcal calendars
- Registering building of calendar reminder index as background job
- Repair step already executed
- Clean up orphan event and contact data
- 0 events without a calendar have been cleaned up
- 0 properties without an events have been cleaned up
- 0 changes without a calendar have been cleaned up
- 0 cached events without a calendar subscription have been cleaned up
- 0 changes without a calendar subscription have been cleaned up
- 0 contacts without an addressbook have been cleaned up
- 0 properties without a contact have been cleaned up
- 0 changes without an addressbook have been cleaned up
- Remove activity entries of private events
- Removed 0 activity entries
- Clean up old calendar subscriptions from deleted users that were not cleaned-up
1/1 [============================] 100%
- 0 calendar subscriptions without an user have been cleaned up
- Remove invalid object properties
- 0 invalid object properties removed.
- Fix the share type of guest shares when migrating from ownCloud
- Copy the share password into the dedicated column
- Set existing shares as accepted
- Update OAuth token expiration times
- init metadata
- Switches from default updater server to the customer one if a valid subscription is available
- Repair step already executed
- Force-reset all Text document sessions
- Initialize migration of background images from dashboard to theming app
- Add background job to check for backup codes
- Insert UUIDFix background job for user and group in batches
- Remove deprecated refresh time markers for LDAP user records
- Populating added database structures for workflows
Mais j’aimerais comprendre pourquoi cela marchait très bien jusqu’à présent et plus maintenant ?
Il y a pas mal de petits trucs à régler avec les mises à jour de nextcloud qui vont très vite…
Après je surveille systématiquement les messages pour régler les warnings dans Nextcloud… Ils sont plus verbeux que avant aussi.