Exactement, merci
Merci pour le retour, jâai crĂ©Ă© une nouvelle PR, pour Ă©viter dâajouter ces dossiers Ă chaque mise Ă jour, mais plutĂŽt dĂ©clencher une action manuelle si besoin de les ajouter de nouveau.
Attention cependant, je ne lâai pas encore complĂštement testĂ©, et ça nâarrivera probablement pas avant la version 19 de nextcloud
Concernant les erreurs relatives Ă .well-known
jâai du mal Ă comprendre pourquoi il y a encore ce problĂšme. Si quelquâun a les logs de lâupgrade, ca peut mâaider. Sinon il faudrait aussi voir si il y a dans la configuration nginx du domaine oĂč se trouve nextcloud ce genre de lignes:
location = /.well-known {
[...]
}
New stable release :
-
16 Aug 2020 - #323
- Upgrade to 18.0.7
- Fix âspinning wheelâ when there is no README.md in the folder
Bonjour,
Mise à jour réalisée sans souci ce matin.
Seule demeure toujours cette petite alerte dans lâinterface admin :
Mais pour le reste, câest nickel ! Super travail, comme dâhabitude
Sangokuss
Bonjour,
Soucis pour la mise à jour de 18.0.5 à 18.0.7 de mon cÎté :
$ sudo yunohost log display 20200820-054942-app_upgrade-nextcloud
description: Upgrade the ânextcloudâ app
log_path: /var/log/yunohost/categories/operation/20200820-054942-app_upgrade-nextcloud.log
logs:
- 2020-08-20 07:37:41,479: DEBUG - 1303360 + local length
- 2020-08-20 07:37:41,481: DEBUG - 1303365 + local log_path
- 2020-08-20 07:37:41,484: DEBUG - 1303367 + local timeout
- 2020-08-20 07:37:41,485: DEBUG - 1303368 + ynh_handle_getopts_args --service_name=nginx --action=reload
- 2020-08-20 07:37:41,487: DEBUG - 1303370 + set +o xtrace
- 2020-08-20 07:37:41,488: DEBUG - 1303374 + service_name=nginx
- 2020-08-20 07:37:41,490: DEBUG - 1303376 + action=reload
- 2020-08-20 07:37:41,491: DEBUG - 1303378 + line_match=
- 2020-08-20 07:37:41,493: DEBUG - 1303380 + length=20
- 2020-08-20 07:37:41,494: DEBUG - 1303381 + log_path=/var/log/nginx/nginx.log
- 2020-08-20 07:37:41,495: DEBUG - 1303383 + timeout=300
- 2020-08-20 07:37:41,496: DEBUG - 1303384 + [[ -n ââ ]]
- 2020-08-20 07:37:41,497: DEBUG - 1303385 + â[â reload == reload â]â
- 2020-08-20 07:37:41,499: DEBUG - 1303387 [###################.] > Reloading nginx web serverâŠ
- 2020-08-20 07:37:41,500: DEBUG - 1303388 + action=reload-or-restart
- 2020-08-20 07:37:41,502: DEBUG - 1303389 + systemctl reload-or-restart nginx
- 2020-08-20 07:37:43,510: DEBUG - 1305397 + [[ -n ââ ]]
- 2020-08-20 07:37:43,511: DEBUG - 1305398 + ynh_script_progression ââmessage=Restoration completed for nextcloudâ --last
- 2020-08-20 07:37:43,512: DEBUG - 1305398 + set +o xtrace
- 2020-08-20 07:37:43,512: DEBUG - 1305399 + set +o xtrace
- 2020-08-20 07:37:43,513: DEBUG - 1305400 + echo â! Helper used in legacy mode !â
- 2020-08-20 07:37:43,514: DEBUG - 1305400 + set +x
- 2020-08-20 07:37:43,615: DEBUG - 1305502 + echo â[####################] > Restoration completed for nextcloudâ
- 2020-08-20 07:37:43,616: DEBUG - 1305504 + set -o xtrace
- 2020-08-20 07:37:43,617: DEBUG - 1305505 + ynh_exit_properly
- 2020-08-20 07:37:43,618: DEBUG - 1305506 + local exit_code=0
- 2020-08-20 07:37:43,618: DEBUG - 1305507 + â[â 0 -eq 0 â]â
- 2020-08-20 07:37:43,619: DEBUG - 1305508 + exit 0
- 2020-08-20 07:37:43,619: DEBUG - 1305509 [####################] > Restoration completed for nextcloud
- 2020-08-20 07:37:43,721: DEBUG - 1305577 To view the log of the operation âRestore ânextcloudâ from a backup archiveâ, use the command âyunohost log display 20200820-061817-backup_restore_app-nextcloudâ
- 2020-08-20 07:37:44,023: DEBUG - 1305849 The permission database has been resynchronized
- 2020-08-20 07:37:45,028: DEBUG - 1306893 SSOwat configuration generated
- 2020-08-20 07:37:45,330: DEBUG - 1307176 Restored
- 2020-08-20 07:37:45,331: DEBUG - 1307177 action [22815.1] executed in 1305.125s
- 2020-08-20 07:37:45,331: DEBUG - apps:
- 2020-08-20 07:37:45,332: DEBUG - nextcloud: Success
- 2020-08-20 07:37:45,332: DEBUG - system:
- 2020-08-20 07:37:45,434: DEBUG - + ynh_die ââmessage=The app was restored to the way it was before the failed upgrade.â
- 2020-08-20 07:37:45,435: WARNING - The app was restored to the way it was before the failed upgrade.
- 2020-08-20 07:37:45,436: DEBUG - + local legacy_args=mc
- 2020-08-20 07:37:45,437: DEBUG - + args_array=([m]=message= [c]=ret_code=)
- 2020-08-20 07:37:45,438: DEBUG - + local -A args_array
- 2020-08-20 07:37:45,439: DEBUG - + local message
- 2020-08-20 07:37:45,439: DEBUG - + local ret_code
- 2020-08-20 07:37:45,440: DEBUG - + ynh_handle_getopts_args ââmessage=The app was restored to the way it was before the failed upgrade.â
- 2020-08-20 07:37:45,441: DEBUG - + set +o xtrace
- 2020-08-20 07:37:45,442: DEBUG - + ret_code=1
- 2020-08-20 07:37:45,443: DEBUG - + echo âThe app was restored to the way it was before the failed upgrade.â
- 2020-08-20 07:37:45,444: DEBUG - + exit 1
- 2020-08-20 07:37:45,610: ERROR - Could not upgrade nextcloud: An error occurred inside the app upgrade script
metadata:
ended_at: 2020-08-20 07:37:45
env:
YNH_APP_ID: nextcloud
YNH_APP_INSTANCE_NAME: nextcloud
YNH_APP_INSTANCE_NUMBER: 1
YNH_CWD: /var/cache/yunohost/from_file/nextcloud_ynh-04dab1b77f4435260ea4217fdd2acb18a05da2ec/scripts
YNH_INTERFACE: cli
YNH_STDINFO: /tmp/tmpx58SsC/stdinfo
YNH_STDRETURN: /tmp/tmpX7sVPG/stdreturn
error: An error occurred inside the app upgrade script
operation: app_upgrade
related_to: - app
- nextcloud
started_at: 2020-08-20 06:49:42
success: False
yunohost_version: 3.8.5.7
metadata_path: /var/log/yunohost/categories/operation/20200820-054942-app_upgrade-nextcloud.yml
name: 20200820-054942-app_upgrade-nextcloud
Small question: is it safer to first upgrade Nextcloud from 18.0.5 to 18.0.7 and then Yunohost from 3 to 4 ? Or the opposite?
Pour ma part, jâavais fait la migration vers Buster avant de mettre Ă jour Nextcloud.
Bonjour/Hi,
@aoz ce nâest pas les logs complets, donc je ne peux pas voir lâerreur. De plus, est-il possible de mettre les logs lĂ https://paste.yunohost.org/ et de mâenvoyer le lien plutĂŽt
@gauthier67 for now itâs the same.
New testing release :
-
22 Aug 2020 - #326
Upgrade to 19.0.1Upgrade to 19.0.2- Upgrade to 19.0.3
- Add action add_multimedia_directories
- The multimedia directories are no longer added on each upgrade
sudo yunohost app install https://github.com/YunoHost-Apps/nextcloud_ynh/tree/testing --debug
or
sudo yunohost app upgrade nextcloud -u https://github.com/YunoHost-Apps/nextcloud_ynh/tree/testing --debug
I just did the upgrade. I just checked that my NC instance wasnât completely broken. It seems fine.
Iâll do some more checks later.
Thx !!
Hello,
Lâupdate totalement ratĂ© chez moi, je me retrouve sans Nextcloud (et sans savoir comment le restaurer car la restauration depuis lâappli sauvegarde plante
Pourriez-vous jeter un oeil Ă mes logs ? https://paste.yunohost.org/raw/tirohufijo
Merci !
Bonjour,
Je vois ça comme problÚmes:
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
W: Target Packages (main/binary-amd64/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
W: Target Packages (main/binary-all/Packages) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
W: Target Translations (main/i18n/Translation-en) is configured multiple times in /etc/apt/sources.list.d/extra_php_version.list:1 and /etc/apt/sources.list.d/php7.list:1
et:
You might want to run âapt --fix-broken installâ to correct these.
The following packages have unmet dependencies:
php7.3-bz2 : Depends: php7.3-common (= 7.3.19-1~deb10u1) but 7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2 is to be installed
php7.3-gmp : Depends: php7.3-common (= 7.3.19-1~deb10u1) but 7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2 is to be installed
php7.3-imap : Depends: php7.3-common (= 7.3.19-1~deb10u1) but 7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2 is to be installed
Depends: libc-client2007e but it is not going to be installed
php7.3-zip : Depends: php7.3-common (= 7.3.19-1~deb10u1) but 7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2 is to be installed
Je pense quâil faut supprimer le fichier /etc/apt/sources.list.d/php7.list
qui doit ĂȘtre les restes dâune app mal packagĂ©/packagĂ© il y a longtemps
On peut dĂ©jĂ essayer de le dĂ©placer pour voir si câest mieux:
sudo mv /etc/apt/sources.list.d/php7.list ~/
sudo apt update
Puis relancer la restauration dans un premier temps (le souci nâest visiblement pas la version testing de nextcloud)
Merci beaucoup pour ta réponse rapide !
Jâai fait ce que tu proposais mais malheureusement la restauration plante toujours
https://paste.yunohost.org/raw/kovehasuzo
Nâest-ce pas ça le problĂšme ?
716355 WARNING E: Packages need to be removed but remove is disabled.
@Limezy : mon feeling câest quâil faut ptete que tu fasses un apt install php7.3-common=7.3.19-1~deb10u1
(mais fait quand meme gaffe Ă ce que dit apt avant de valider)
Merci beaucoup pour vos conseils ! HĂ©las, ça rĂ©siste encoreâŠ
Le log du apt install
apt install php7.3-common=7.3.19-1~deb10u1
Reading package lists... Done
Building dependency tree
Reading state information... Done
The following packages will be REMOVED:
php7.3 php7.3-cli php7.3-curl php7.3-fpm php7.3-gd php7.3-intl php7.3-json php7.3-ldap php7.3-mbstring php7.3-mysql php7.3-opcache php7.3-readline php7.3-xml
The following packages will be DOWNGRADED:
php7.3-common
0 upgraded, 0 newly installed, 1 downgraded, 13 to remove and 0 not upgraded.
Need to get 956 kB of archives.
After this operation, 13.6 MB disk space will be freed.
Do you want to continue? [Y/n] Y
Get:1 http://debian.mirrors.ovh.net/debian buster/main amd64 php7.3-common amd64 7.3.19-1~deb10u1 [956 kB]
Fetched 956 kB in 0s (5,163 kB/s)
(Reading database ... 105918 files and directories currently installed.)
Removing php7.3 (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-fpm (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-cli (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-curl (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-gd (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-intl (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-json (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-ldap (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-mbstring (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-mysql (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-opcache (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-readline (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Removing php7.3-xml (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
**dpkg:** **warning:** downgrading php7.3-common from 7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2 to 7.3.19-1~deb10u1
(Reading database ... 105777 files and directories currently installed.)
Preparing to unpack .../php7.3-common_7.3.19-1~deb10u1_amd64.deb ...
Unpacking php7.3-common (7.3.19-1~deb10u1) over (7.3.21-1+0~20200807.66+debian10~1.gbp18a1c2) ...
Setting up php7.3-common (7.3.19-1~deb10u1) ...
Processing triggers for man-db (2.8.5-2) ...
Updating loolwsd systemplate
AprĂšs ça je nâarrive plus Ă dĂ©marrer le service php7.3-fpm
Est-ce une conséquence ? La restauration de Nextcloud plante toujours lamentablement :
https://paste.yunohost.org/ukamupazic.sql
Merci dâavance pour votre aide pour me retirer cette belle Ă©pine du pied !
php7.3-fpm.service is masked
Du coup faisons un
systemctl unmask php7.3-fpm
systemctl restart php7.3-fpm
systemctl status php7.3-fpm
(N.B. : pas la peine de tenter des trucs avec Nextcloud si PHP7.3-fpm tourne pasâŠ)
Just wanted to confirm that Iâve just updated Nextcloud without issue, thanks a lot !
Nextcloud 19.02, waouh
Merci encore pour ton aide ! LĂ je dois reconnaĂźtre que je suis complĂštement paumĂ©âŠ
Le service php ne tourne pas et rend un statut bizarre active (exited)
**â** php7.3-fpm.service - LSB: starts php7.3-fpm
Loaded: loaded (/etc/init.d/php7.3-fpm; generated)
Active: **active (exited)** since Sat 2020-08-29 01:25:38 UTC; 8min ago
Docs: man:systemd-sysv-generator(8)
Process: 768 ExecStart=/etc/init.d/php7.3-fpm start (code=exited, status=0/SUCCESS)
Aug 29 01:25:38 domaine.fr systemd[1]: Starting LSB: starts php7.3-fpm...
Aug 29 01:25:38 domaine.fr systemd[1]: Started LSB: starts php7.3-fpm.
Dans lâinterface dâadministration Yunohost, ça se prĂ©sente comme ça :
Chose assez bizarre, les logs ne donnent rien et les derniĂšres lignes datent dâhier
https://paste.yunohost.org/aqiditufuc.cs
Je ne sais pas quoi faire !
PS: Faut-il que je migre sur un autre fil pour Ă©viter de polluer celui-ci ?
Hmokay tu peux faire un php-fpm7.3 --test
?
Tested on my side Had a similar issue to @Limezy with some php package version conflicts etc due to sury and misconfigured apt preferences ⊠which I believe should be fixed by this PR on the core : Add apt conf regen hook by alexAubin · Pull Request #1041 · YunoHost/yunohost · GitHub
After manually fixing the preferences.d / pinning policy, the upgraded worked