YunoHost 4.0 (Buster) release / Sortie de YunoHost 4.0 (Buster)

J’ai aussi eu des soucis de disque dur qui ne se montaient pas après la mise à jour, mais c’étaient des disques chiffrés.
Si c’est aussi ton cas, avec un peu de chance j’ai encore quelquepart la modif que j’ai faite pour que ça se relance.

Edit :
Dans /etc/fstab je suis passé de
UUID=42a5e02b-8ae0-4b23-a05c-29a3bdd04ec8 /mnt/disqueNoir auto noatime 0 2
à
/dev/mapper/disquenoir /mnt/disqueNoir auto noatime 0 2
(Pour les autres disques, qui eux ne sont pas chiffrés, j’ai toujours leur uuid qui est utilisé)

Il doit y avoir quelquepart le lien fait avec /dev/mapper mais je ne sais pas où :frowning:

Récemment j’ai eu un soucis au boot avec ce disque mais un reboot et c’est reparti.

Bonjour,

Dans mon cas, la migration 0017 postgresql 9p6-11 plantait du fait qu’il ne trouvait pas de version 11 installée.
J’ai suivi les commandes suivantes

apt install postgresql-11
apt update
apt dist-upgrade
pg_ctlcluster 11 main start
yunohost tools migrations migrate

et j’ai également du faire (préconisée par Aleks)

pg_dropcluster --stop 11 main

Merci !

1 Like

Another bunch of minor fixes released in Yunohost 4.0.7.1 and 4.0.8 :

Thanks to all contributors (ljf, Kayou) :heart: !

9 Likes

Thanks for this work :heart:

I upgraded my YunoHost machine, and here is my feedback.

PostgreSQL migration issue

I got some errors with postgresql migration, since German locale was used.
sudo yunohost tools migrations migrate --accept-disclaimer
Info: Running migration 0017_postgresql_9p6_to_11...
Error: Migration 0017_postgresql_9p6_to_11 did not complete, aborting. Error: Failed to run command 'LC_ALL=C pg_upgradecluster -m upgrade 9.6 main'.
returncode: 1
stdout:
Disabling connections to the old cluster during upgrade...
Restarting old cluster with restricted connections...
Stopping old cluster...

stderr:
perl: warning: Setting locale failed.
perl: warning: Please check that your locale settings:
	LANGUAGE = (unset),
	LC_ALL = (unset),
	LC_MONETARY = "de_DE.UTF-8",
	LC_PAPER = "de_DE.UTF-8",
	LC_MEASUREMENT = "de_DE.UTF-8",
	LC_CTYPE = "en_US.UTF-8",
	LC_TIME = "de_DE.UTF-8",
	LC_NUMERIC = "de_DE.UTF-8",
	LANG = "en_US.UTF-8"
    are supported and installed on your system.
perl: warning: Falling back to a fallback locale ("en_US.UTF-8").
Error: The locale requested by the environment is invalid:
  LANG: en_US.UTF-8
  LC_CTYPE: en_US.UTF-8
  LC_MEASUREMENT: de_DE.UTF-8
  LC_MONETARY: de_DE.UTF-8
  LC_NUMERIC: de_DE.UTF-8
  LC_PAPER: de_DE.UTF-8
  LC_TIME: de_DE.UTF-8
Error: Could not create target cluster

Info: The operation 'Run migrations' could not be completed. Please share the full log of this operation using the command 'yunohost log display 20200919-135559-tools_migrations_migrate_forward --share' to get help

I had to force all locale environment variables this way:

export LC_ALL=en_US.UTF-8; export LC_MEASUREMENT=en_US.UTF-8; export LC_MONETARY=en_US.UTF-8; export LC_NUMERIC=en_US.UTF-8; export LC_PAPER=en_US.UTF-8; export LC_TIME=en_US.UTF-8

then rerun the migration:

sudo yunohost tools migrations migrate --accept-disclaimer

PHP

I had to start php to have the php apps working:

sudo systemctl start php7.3-fpm

H5ai

502 error, I changed this line to php7.3-fpm.sock
Fixed by h5ai_ynh!2.

Wallabag & PluXml

Nothing displayed when accessing the apps. I forced upgrades and things are back to normal. I didn’t investigate, but it might be some php configuration issue.

Salutations, j’ai tenté une migration depuis Stretch et elle a échouée.

Et je me retrouves bloqué avec cette erreur qui boucle sur elle-même :

~$ sudo apt --fix-broken install
Reading package lists… Done
Building dependency tree
Reading state information… Done
Correcting dependencies… failed.
The following packages have unmet dependencies:
coturn : Depends: libmariadb3 (>= 3.0.0) but it is not installed
libalgorithm-diff-xs-perl : Depends: perlapi-5.24.1 but it is not installable
libclass-c3-xs-perl : Depends: perlapi-5.24.1 but it is not installable
libclass-xsaccessor-perl : Depends: perlapi-5.24.1 but it is not installable
Depends: perl (< 5.24.2~) but 5.28.1-6+deb10u1 is installed
libcommon-sense-perl : Depends: perlapi-5.24.1 but it is not installable
Depends: perl (< 5.24.2~) but 5.28.1-6+deb10u1 is installed
libdbd-mysql-perl : Depends: perlapi-5.24.1 but it is not installable
libdbi-perl : Depends: perlapi-5.24.1 but it is not installable
libdevel-caller-perl : Depends: perlapi-5.24.1 but it is not installable
libdevel-lexalias-perl : Depends: perlapi-5.24.1 but it is not installable
libfcgi-perl : Depends: perlapi-5.24.1 but it is not installable
libfile-fcntllock-perl : Depends: perlapi-5.24.1 but it is not installable
libhtml-parser-perl : Depends: perlapi-5.24.1 but it is not installable
libimage-magick-q16-perl : Depends: perlapi-5.24.1 but it is not installable
libjson-xs-perl : Depends: perlapi-5.24.1 but it is not installable
liblocale-gettext-perl : PreDepends: perlapi-5.24.1 but it is not installable
libnet-ssleay-perl : Depends: perlapi-5.24.1 but it is not installable
libnetaddr-ip-perl : Depends: perlapi-5.24.1 but it is not installable
libpackage-stash-xs-perl : Depends: perlapi-5.24.1 but it is not installable
libpadwalker-perl : Depends: perlapi-5.24.1 but it is not installable
libpam-systemd : Depends: systemd (= 232-25+deb9u12) but 241-7~deb10u4 is installed
libparams-classify-perl : Depends: perlapi-5.24.1 but it is not installable
libparams-util-perl : Depends: perlapi-5.24.1 but it is not installable
libparams-validate-perl : Depends: perlapi-5.24.1 but it is not installable
libsocket6-perl : Depends: perlapi-5.24.1 but it is not installable
libssl-dev : Depends: libssl1.1 (= 1.1.1g-1+0~20200421.17+debian10~1.gbpf6902f) but 1.1.1g-1+0~20200421.17+debian9~1.gbpf6902f is installed
libsub-identify-perl : Depends: perlapi-5.24.1 but it is not installable
libsub-name-perl : Depends: perlapi-5.24.1 but it is not installable
libterm-readkey-perl : Depends: perlapi-5.24.1 but it is not installable
libtext-charwidth-perl : Depends: perlapi-5.24.1 but it is not installable
libtext-iconv-perl : Depends: perlapi-5.24.1 but it is not installable
libtype-tiny-xs-perl : Depends: perlapi-5.24.1 but it is not installable
libunicode-utf8-perl : Depends: perlapi-5.24.1 but it is not installable
libvariable-magic-perl : Depends: perlapi-5.24.1 but it is not installable
python3 : Depends: libpython3-stdlib (= 3.5.3-1) but 3.7.3-1 is installed
python3-dev : Depends: python3 (= 3.7.3-1) but 3.5.3-1 is installed
python3-distutils : Depends: python3 (>= 3.7.1-1~) but 3.5.3-1 is installed
python3-lib2to3 : Depends: python3 (>= 3.7.1-1~) but 3.5.3-1 is installed
python3-llfuse : Depends: python3 (>= 3.7~) but 3.5.3-1 is installed
python3-tk : Depends: python3 (>= 3.7.1-1~) but 3.5.3-1 is installed
python3-venv : Depends: python3 (= 3.7.3-1) but 3.5.3-1 is installed
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.
E: Unable to correct dependencies

(Debian 10 mais yunohost 3.8

Je peux faire une fresh install si ce n’est pas réparable)

À mon avis c’est réparable mais pour mieux comprendre il faudrait idéalement fournir le log de la migration échouée…

Le log de migration (0015_migrate_to_buster) renvoie au log de mise-à-jour (tools_upgrade) qui dit ceci :

  • 2020-09-25 01:15:39,114: INFO - + Preparing to unpack …/nginx-extras_1.14.2-2+deb10u3_amd64.deb …
  • 2020-09-25 01:15:39,315: INFO - + Unpacking nginx-extras (1.14.2-2+deb10u3) over (1.10.3-1+deb9u5) …
  • 2020-09-25 01:15:40,118: INFO - + Setting up nginx-extras (1.14.2-2+deb10u3) …
  • 2020-09-25 01:15:50,549: INFO - + Upgrading binary: nginx failed!
  • 2020-09-25 01:15:50,550: WARNING - invoke-rc.d: initscript nginx, action “upgrade” failed.
  • 2020-09-25 01:15:50,951: INFO - + ● nginx.service - A high performance web server and a reverse proxy server
  • 2020-09-25 01:15:50,952: WARNING - Job for nginx.service failed because the control process exited with error code.
  • 2020-09-25 01:15:50,952: INFO - + Loaded: loaded (/lib/systemd/system/nginx.service; enabled; vendor preset: enabled)
  • 2020-09-25 01:15:50,953: WARNING - See “systemctl status nginx.service” and “journalctl -xe” for details.
  • 2020-09-25 01:15:50,953: INFO - + Active: failed (Result: exit-code) since Fri 2020-09-25 01:15:50 CEST; 4ms ago
  • 2020-09-25 01:15:50,954: WARNING - invoke-rc.d: initscript nginx, action “restart” failed.
  • 2020-09-25 01:15:50,954: INFO - + Docs: man:nginx(8)
  • 2020-09-25 01:15:50,955: WARNING - dpkg: error processing package nginx-extras (–configure):
  • 2020-09-25 01:15:50,955: INFO - + Process: 13920 ExecStartPre=/usr/sbin/nginx -t -q -g daemon on; master_process on; (code=exited, status=1/FAILURE)
  • 2020-09-25 01:15:50,956: WARNING - installed nginx-extras package post-installation script subprocess returned error exit status 1
  • 2020-09-25 01:15:50,956: INFO - +
  • 2020-09-25 01:15:50,957: INFO - + Sep 25 01:15:50 domaine.tld systemd[1]: Starting A high performance web server and a reverse proxy server…
  • 2020-09-25 01:15:50,957: INFO - + Sep 25 01:15:50 domaine.tld nginx[13920]: nginx: [emerg] open() “/etc/nginx/conf.d/onlyoffice-documentserver.conf” failed (2: No such file or directory) in /etc/nginx/nginx.conf:61
  • 2020-09-25 01:15:50,958: INFO - + Sep 25 01:15:50 domaine.tld nginx[13920]: nginx: configuration file /etc/nginx/nginx.conf test failed
  • 2020-09-25 01:15:50,958: INFO - + Sep 25 01:15:50 domaine.tld systemd[1]: nginx.service: Control process exited, code=exited, status=1/FAILURE
  • 2020-09-25 01:15:50,959: INFO - + Sep 25 01:15:50 domaine.tld systemd[1]: nginx.service: Failed with result ‘exit-code’.
  • 2020-09-25 01:15:50,960: INFO - + Sep 25 01:15:50 domaine.tld systemd[1]: Failed to start A high performance web server and a reverse proxy server.
  • 2020-09-25 01:15:51,060: WARNING - Errors were encountered while processing:
  • 2020-09-25 01:15:51,061: WARNING - nginx-extras
  • 2020-09-25 01:15:51,864: WARNING - E: Sub-process /usr/bin/dpkg returned an error code (1)
  • 2020-09-25 01:15:53,054: WARNING - Could not upgrade packages: [beaucoup de paquets]

Hmokay let’s check what this tells then :

ls -l /etc/nginx/conf.d/onlyoffice-documentserver.conf

Ce qui donne

lrwxrwxrwx 1 root root 67 Mar 5 2020 /etc/nginx/conf.d/onlyoffice-documentserver.conf → /etc/onlyoffice/documentserver/nginx/onlyoffice-documentserver.conf

Et j’imagine que

ls  /etc/onlyoffice/documentserver/nginx/onlyoffice-documentserver.conf

dit que le fichier n’existe pas ?

Si c’est le cas alors on va commencer par faire un

mv /etc/nginx/conf.d/onlyoffice-documentserver.conf /root/onlyoffice-documentserver.conf.bkp

pour backuper le fichier, puis nginx -t pour confirmer que nginx est content, puis on relance la migration / mise à jour (j’ai comme l’impression que c’est pas le seul soucis)

1 Like

Nginx est content
Et en effet, j’ai une autre erreur, il me marques tout mes paquets yunohost (les paquets des apps yunohost) comme “was already set on hold” puis :

ERROR Migration 0015_migrate_to_buster did not complete, aborting. Error: You cannot do this right now because dpkg/APT (the system package managers) seems to be in a broken state… You can try to solve this issue by connecting through SSH and running sudo apt install --fix-broken and/or sudo dpkg --configure -a.
Traceback (most recent call last):
File “/usr/lib/moulinette/yunohost/tools.py”, line 895, in tools_migrations_migrate
migration.run()
File “/usr/lib/moulinette/yunohost/data_migrations/0015_migrate_to_buster.py”, line 79, in run
tools_upgrade(system=True, allow_yunohost_upgrade=False)
File “/usr/lib/moulinette/yunohost/log.py”, line 313, in func_wrapper
result = func(*args, **kwargs)
File “/usr/lib/moulinette/yunohost/tools.py”, line 509, in tools_upgrade
raise YunohostError(“dpkg_is_broken”)
YunohostError: You cannot do this right now because dpkg/APT (the system package managers) seems to be in a broken state… You can try to solve this issue by connecting through SSH and running sudo apt install --fix-broken and/or sudo dpkg --configure -a.

Un sudo apt-mark unhold sur tout les paquets -ynh-deps listés a permis de sortir de la boucle de ‘sudo apt --fix-broken install’. J’ai lancé un ‘sudo apt --fix-broken install’ qui s’est bien passé puis j’ai relancé la migration, pas d’erreur. J’ai quelques apps cassées mais je vais vérifier tout ça mais ça a l’air bon !

In my case, I had nginx 502 errors related to incorrectly configured sockets for several apps. I manually changed sockets to listen to the php7.3-fpm.

@zero1Dre Can you specify which app caused issues

Sure.
It was Wallabag, Wordpress, Baikal and Roundcube.
My context was a bit specific however. I also used this as an opportunity to physically migrate my server. So I upgraded both servers, then did a backup/restore. Everything worked perferctly, except for the 502 errors which I realised were related to the wrong sockets being listened to.

1 Like

Hello,

Thanks everyone for the migration, it worked well on my server (Proxmox VM, ~10 users).
I had to manually remove a file used by a previous OnlyOffice installation :
rm /etc/nginx/conf.d/ds.conf
Then run :
sudo apt install --fix-broken
Anf then the migration again.

Congratulations ! Big up for you @Aleks

Have a nice day (or night :crescent_moon:)

1 Like

Lancé la migration hier soir, en 2h c’était plié : pas une erreur, tout fonctionne au poil.
Bravo à toute l’équipe YNH c’est du beau boulot !

Erratum :smiley: : en local tout va pour le mieux mais à distance l’interface admin est très instable et me répète “Une instance est déjà en cours d’exécution, merci d’attendre sa fin avant d’en lancer une autre.” quand je veux accéder à la liste des services ou au diagnostic par exemple. De plus, la version n’apparaît pas dans le coin inférieur droit, la commande yunohost --version me renvoie :
yunohost: repo: stable version: 4.0.8 yunohost-admin: repo: stable version: 4.0.4 moulinette: repo: stable version: 4.0.3 ssowat: repo: stable version: 4.0.4.1

Edit 2 : en SSH je lui demande yunohost service status pour essayer de voir ce qui coince et ça mouline et ne renvoie rien…

Same issue for me after restoring backup from serverA (with lasted yunohost version) to serverB

After forcing an upgrade with YNH_FORCE_UPGRADE=1 yunohost app upgrade agendav -u https://github.com/YunoHost-apps/agendav_ynh
All the apps are now running


Before the upgrade

# ls /var/run/php/ -l
total 4
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.0-fpm-agendav.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.0-fpm-dokuwiki__2.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.0-fpm-freshrss.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.0-fpm-kanboard.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.0-fpm-wallabag2.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm-ampache.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm-baikal.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm-dokuwiki.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm-nextcloud.sock
-rw-r--r-- 1 root     root     3 Oct 20 19:42 php7.3-fpm.pid
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm-roundcube.sock
srw-rw---- 1 www-data www-data 0 Oct 20 19:42 php7.3-fpm.sock
#

After

# ls /var/run/php/ -1
php7.3-fpm-agendav.sock
php7.3-fpm-ampache.sock
php7.3-fpm-baikal.sock
php7.3-fpm-dokuwiki__2.sock
php7.3-fpm-dokuwiki.sock
php7.3-fpm-freshrss.sock
php7.3-fpm-kanboard.sock
php7.3-fpm-nextcloud.sock
php7.3-fpm.pid
php7.3-fpm-roundcube.sock
php7.3-fpm.sock
php7.3-fpm-wallabag2.sock

PS: transmission is not listed as restore failed (I took the log but didn’t dig into it. I can reinstall it quickly)

ping @ericg who could be interested too

Hello !
For information, this release is available for docker, with delay :confused: and with an hard work :laughing: ! Don’t hesitate to give me feedbacks

I also remind : “Warning, all links ars changed ! Like domainelibre/yunohost3 became domainelibre/yunohost

Edit: fix links

4 Likes

I have a VPS running YunoHost 3.7.1.3 on Debian 9. It has Nextcloud 18.02, Rainloop and Borg. I need to move it to another VPS. What would be the recommended order of operations to migrate it?

  • Backup existing YH
  • Upgrade existing YH to 3.8.3.5
  • Upgrade apps on existing YH
  • Backup existing YH
  • Install Debian 9 to new VPS
  • copy over backup to new VPS
  • Shutdown existing YH
  • Update DNS IP at registrar
  • Wait an hour for DNS to propagate
  • Install YH 3.8.3.5?
  • Restore backup?
  • Migrate from 3.8.5+Debian9 to 4.0+Debian 10 using the upgrade tools?

Or is there a better or smoother process if I installed Debian 10 and Yunohost 4.0 and then tried to restore the backup from 3.8.5/Debian 9?

Or, should I just upgrade the existing YH to 4.0/Debian 10, then migrate to the new VPS on parity with YH 4.0/Debian 10?

Thanks