Beta-testing for YunoHost 4.0 on Debian Buster (and migration shipped in Yunohost 3.8.5)

Hey there!

Following the alpha-testing opened two weeks ago, we are happy to announce that we are moving to the beta-testing stage for Buster :tada: !

The feedback from the alpha-testing was pretty positive and no major issue was found so far. Therefore we consider that it should be okay to upgrade to or install a fresh Yunohost 4.0+ running on Buster. However, you should still remain careful, especially when running the Stretch->Buster migration depending on the complexity of your setup (but doing so helps spotting issues !). Additionally, some apps are still known to not be Buster-ready yet though fixes are on the way for most of them.

:construction: Please keep in mind that this is a beta-testing and small issues or edge-cases are still expected, so be careful. :construction:

:space_invader: What to test ?

(N.B. : all these can be tested independently)

Pre-installed images

For Raspberry Pi 2, 3, 4

Image : https://build.yunohost.org/yunohost-buster-4.0.2-rpi-beta.zip
To be tested using these instructions.
(The image may partially work with RPi 0 and 1 but it’s pretty likely that you’ll encounter this issue)

We may or may not add other pre-installed images such as x86 ISO or other ARM-board images in the coming days

Installing a fresh YunoHost on top of a fresh Debian 10/Buster

This is done with :

$ wget https://install.yunohost.org/buster -O install_script
$ chmod +x install_script
$ ./install_script
# You will get a disclaimer intended to make sure what you're doing. 
# Read it and follow the instructions.

Apart from validating that the install does work, we encourage you to test every apps and features that you would typically use in a real-life server (so including the webadmin, the user portal, diagnosis, emails, 
).

Migrating an existing Debian 9/Stretch + YunoHost 3.8.x server

YunoHost 3.8.5 (currently testing) ships a migration that allows to upgrade to Debian 10/Buster + Yunohost 4.x.

Before going through this process, we reiterate that ideally, you should have a way to entirely rollback your server before proceeding with the upgrade. That way, if you spot issues, we’ll be able to provide a fix then validate that the fix works by re-running the upgrade from the same starting point.

  1. Switch to testing by running:

curl https://install.yunohost.org/switchToTesting | bash

  1. After upgrading, in the webadmin, under Tools > Migrations, you should now see an available migration to upgrade to Buster. Read the disclaimer and start the migration.

  2. 
 be patient, this will take a while. But try to stay attentive to what’s going on. Share the detailed log if anything that goes wrong.

  3. Ideally after the upgrade, test that everything (e.g. apps installed) still works as expected.

12 Likes

I am happy ! I have a fresh install of buster on a raspberry Pi4 ( Propulsé par YunoHost 4.0.2~beta+202006191317 (unstable)), I have installed VPN_client (now I am using vpn connexion), I have install Roundcube and backup my emails and I have backup Wordpress also on a subdomain www.my_domain.tld and it seems working fine.
anyway, first bug: the icon on the top of wordpress to come back at the SSO have a wrong url, he point to www.my_domain.tld/yunohost/sso and it should be my_domain.tld/yunohost/sso. But the Worpress not private, so I doesn’t matter if I watch it like public.

Another issue for wordpress loocking in health of the CMS:

Les modules PHP rĂ©alisent la plupart des tĂąches sur le serveur qui fait fonctionner votre site. Toute modification les concernant doit ĂȘtre rĂ©alisĂ©e par la personne chargĂ©e de l’administration de votre serveur.

L’équipe HĂ©bergement de WordPress maintient une liste des modules recommandĂ©s et obligatoires dans le manuel de l’équipe (en anglais) (ouvre un nouvel onglet).

  • Avertissement Le module facultatif, imagick, n’est pas installĂ©, ou a Ă©tĂ© dĂ©sactivĂ©.

php-imagick dependencies should be nice to add in the script install I am not sure that is the solution.
No, I don’t know how to do it, but to resolve this issue, it is php7.3-imagick dependencie to add, but if I try
apt-get install php7.3-imagick
it puts
Note, selecting 'php-imagick' instead of 'php7.3-imagick'
I don’t know how to get the ‘php7.3-imagick’

1 Like

Tried to update to buster yunohost 4 beta with wordpress and nextcloud on rp3b with no luck https://paste.yunohost.org/raw/rajipaworo

@walt : eeh can you confirm that you upgrade to the latest version (3.8.5.3 if i remember correctly) before running the migration ?

Install fraiche de Debian 10 (en local dans une VM / Proxmox).
Install Yunohost via le script : nickel.

Aucun souci dans la procédure de création de yunohost 4.
CrĂ©ation d’utilisateur, installation d’appli (zerobin, roundcube, Diagram
). Et ça tourne super vite !
Mise Ă  jour en 4.0.2-beta : ok
Infos de diagnostics cohérentes / config perso.
Lancement de Backup : ok
Changement mot de passe admin : ok

Tout ça a l’air super bien fait.

Je vais la garder et me pencher sur une migration 3.8 -> 4.

En tout cas, c’est du super boulot. :sparkling_heart:

3 Likes

Yes - I ran system upgrade before running the migration. Same thing trying to upgrade to yunohost 4.01-alpha couple of days ago. Resored system from backup both times, which worked flawlessly.

Hmmmokay, can you maybe show the output of apt policy unscd then ?

After restoring system from backup and running system upgrade, I see offer to upgrade yunohost from 3.8.5.1 -> 4.0.2-beta (and yunohost-admin from 3.8.3.4 -> 4.0.2-beta. Is there some way to upgrade yunohost from 3.8.5.1 -> 3.8.5.3 before attempting migration?

Well that’s probably because you already attempted the upgrade before and now your sources.list points to buster instead of stretch 
 I think you can tweak by editing manually /etc/apt/sources.list.d/yunohost.list (replacing buster by stretch)

Mise à niveau effectuée depuis une 3.8.4.9 (VM locale sur promox)

  • Lancement du script
  • Lancement de la migration via l’interface
  • Aucun message d’erreur sur la migration, par contre l’interface web est “cassĂ©e” certaines fonctions ne rĂ©pondent plus et aucun message ne signale qu’il faut redĂ©marrer. Le bouton redĂ©marrer ne peut ĂȘtre activĂ©.
    Il faudrait le signaler ou le forcer Ă  la fin de la migration pour finir. Sinon, c’est tout cassĂ© et on ne peut rien faire en ssh.
    Au reboot, l’interface d’admin refonctionne j’ai bien une version “4.0.2~beta (testing)” fonctionnelle globalement. Pas tout testĂ©.
  • Les backups sont encore prĂ©sents mais leur restauration fonctionnerait-elle ? Sinon, autant les indiquer “obsolĂštes” et risquĂ©s Ă  restaurer.

Thank you, Alex. Your solution worked and my installation updated flawlessly. Wordpress website works better than before. You’ve put together an amazing collection of software, here.

1 Like

Nextcloud works, too.

PrĂ©paration d’une v 3.8.4.9 avec toutes les apps de haute qualitĂ© fonctionnelles (testĂ©es , validĂ©es) :

  • etherpad, gitlab, dokuwiki, Hextris, Leed, Wordpress
    et d’autres :
  • lstu, 20euros, zerobin, custom webapp, roundcube

Mise à niveau effectuée depuis le terminal (script + upgrade)
Cette fois ci, le retour sur l’interface web fonctionne sans redĂ©marrage (4.0.2-beta testing)
RĂ©actualisation de la page et c’est bon.

  • Services inactifs : dovecot, mysql, postegreslq, redis-server. Aucun ne redĂ©marre via l’interface web.
  • Une Ă©tape de Migration n’est pas passĂ©e :

Migrations en attente
17. Migrate databases from PostgreSQL 9.6 to 11

Les entrées de menu webadmin fonctionnent.
3 erreurs systÚme signalées :

  • Le fichier de configuration /etc/nslcd.conf semble avoir Ă©tĂ© modifiĂ© manuellement.
  • Le fichier de configuration /etc/nsswitch.conf semble avoir Ă©tĂ© modifiĂ© manuellement.
  • Le fichier de configuration /etc/ssh/sshd_config semble avoir Ă©tĂ© modifiĂ© manuellement.

Reboot pour tenter de finir la mise Ă  jour.
Les 4 services sont toujours down, malgré le reboot.
La migration de postgresql n’aboutit pas non plus :
https://paste.yunohost.org/raw/yurofurohe

Etat des applis

  • Dokuwiki : ok. OpĂ©rationnel et a conservĂ© le contenu prĂ©cĂ©dent (page accueil)

  • Etherpad : down erreur 502 nginx (du sans doute Ă  base postegresql qui est down)

  • Gitlab : ok. OpĂ©rationnel et a conservĂ© le contenu prĂ©cĂ©dent (langue)

  • Hextris : ok. OpĂ©rationnel et a conservĂ© le contenu prĂ©cĂ©dent (highscore)

  • Leed : HS. Page blanche (car mysql down ?)

  • Wordpress : HS (mysql)

  • 20 euros : OK

  • LSTU : HS (postegresql)

  • Custom Webapp : ok

  • Roundcube : HS (mysql ? postegresql ?)

Quelques infos débug sur les services HS :

systemctl status mariadb.service
● mariadb.service - MariaDB 10.3.22 database server
   Loaded: loaded (/lib/systemd/system/mariadb.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-06-21 09:40:36 UTC; 5s ago
     Docs: man:mysqld(8)
           https://mariadb.com/kb/en/library/systemd/
  Process: 6443 ExecStartPre=/usr/bin/install -m 755 -o mysql -g root -d /var/run/mysqld (code=exited, status=226/NAMESPACE)

Jun 21 09:40:36 myunoaf systemd[1]: Starting MariaDB 10.3.22 database server...
Jun 21 09:40:36 myunoaf systemd[6443]: mariadb.service: Failed to set up mount namespacing: Permission denied
Jun 21 09:40:36 myunoaf systemd[6443]: mariadb.service: Failed at step NAMESPACE spawning /usr/bin/install: Permission denied
Jun 21 09:40:36 myunoaf systemd[1]: mariadb.service: Control process exited, code=exited, status=226/NAMESPACE
Jun 21 09:40:36 myunoaf systemd[1]: mariadb.service: Failed with result 'exit-code'.
Jun 21 09:40:36 myunoaf systemd[1]: Failed to start MariaDB 10.3.22 database server.

Postgresql est reparti tout seul Ă  la main, mais affiche arrĂȘtĂ©e dans la webadmin


systemctl start postgresql.service
systemctl status postgresql.service
● postgresql.service - PostgreSQL RDBMS
   Loaded: loaded (/lib/systemd/system/postgresql.service; enabled; vendor preset: enabled)
   Active: active (exited) since Sun 2020-06-21 09:42:52 UTC; 16s ago
  Process: 7357 ExecStart=/bin/true (code=exited, status=0/SUCCESS)
 Main PID: 7357 (code=exited, status=0/SUCCESS)

Jun 21 09:42:52 myunoaf systemd[1]: Starting PostgreSQL RDBMS...
Jun 21 09:42:52 myunoaf systemd[1]: Started PostgreSQL RDBMS.

Dovecot n’est pas reparti.

systemctl start dovecot.service
systemctl status dovecot.service
● dovecot.service - Dovecot IMAP/POP3 email server
   Loaded: loaded (/lib/systemd/system/dovecot.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-06-21 09:44:06 UTC; 3s ago
     Docs: man:dovecot(1)
           http://wiki2.dovecot.org/
  Process: 7844 ExecStart=/usr/sbin/dovecot -F (code=exited, status=226/NAMESPACE)
 Main PID: 7844 (code=exited, status=226/NAMESPACE)

Jun 21 09:44:06 myunoaf systemd[1]: Started Dovecot IMAP/POP3 email server.
Jun 21 09:44:06 myunoaf systemd[7844]: dovecot.service: Failed to set up mount namespacing: Permission denied
Jun 21 09:44:06 myunoaf systemd[7844]: dovecot.service: Failed at step NAMESPACE spawning /usr/sbin/dovecot: Permission denied
Jun 21 09:44:06 myunoaf systemd[1]: dovecot.service: Main process exited, code=exited, status=226/NAMESPACE
Jun 21 09:44:06 myunoaf systemd[1]: dovecot.service: Failed with result 'exit-code'.

Redis-server n’est pas reparti

start redis-server.service
Job for redis-server.service failed because the control process exited with error code.
See "systemctl status redis-server.service" and "journalctl -xe" for details.
root@myunoaf:/home/admin# systemctl status redis-server.service
● redis-server.service - Advanced key-value store
   Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
   Active: failed (Result: exit-code) since Sun 2020-06-21 09:47:03 UTC; 6s ago
     Docs: http://redis.io/documentation,
           man:redis-server(1)
  Process: 9028 ExecStart=/usr/bin/redis-server /etc/redis/redis.conf (code=exited, status=226/NAMESPACE)

Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Control process exited, code=exited, status=226/NAMESPACE
Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 21 09:47:03 myunoaf systemd[1]: Failed to start Advanced key-value store.
Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Service RestartSec=100ms expired, scheduling restart.
Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Scheduled restart job, restart counter is at 5.
Jun 21 09:47:03 myunoaf systemd[1]: Stopped Advanced key-value store.
Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Start request repeated too quickly.
Jun 21 09:47:03 myunoaf systemd[1]: redis-server.service: Failed with result 'exit-code'.
Jun 21 09:47:03 myunoaf systemd[1]: Failed to start Advanced key-value store.

Au passage, aucune appli HS n’est repartie manullement (pad, leed, wordpress, lstu, roundcube.

Voilà pour les premiers retours, si ça peut aider.

1 Like

@francoisa : est-ce que tu as fait ces tests dans un LXC ?

Oui,dans un container dans un proxmox V6 (Buster). Mais j’ai compris aprĂšs que ce n’est pas l’idĂ©al. J’ai relancĂ© une install sur une VM propre Ă  part. J’ai eu des soucis avec. Donc je recommence dans une VM propre. Et je vous retourne le rĂ©sultat.

Alrighty, ce soucis dans LXC avec les namespace est “connu”, il faut mettre l’option nesting à true pour que ça marche bien : https://github.com/YunoHost/ynh-dev/blob/master/ynh-dev#L147

De mon cote, install propre pi 4 sous raspbian 64bit via script d’install.
Le seul “defaut” que je trouve jusqu’a present est que je ne recoit aucun mail du system sur le compte de mon utilisateur principal (retours de diagnostique, retour de cronjob, etc
) Feature de la version 4.0.2 ou issue?
Sinon les apps on fonctionne correctement, diagnostic est plutot dans le vert, rien de plus a signaler! Beau boulot tout le monde!

Edit:
1_Pour ceux qui voudraient jouer avec leur Pi 4 et Raspian/RaspberryOS Buster 64Bit /etc/*release retourne Debian Buster et non pas Raspbian Buster donc pas de suppression de l’utilisateur “pi” lors de l’install via le script. Vous devez donc modifier /etc/*release de la sorte avant de lancer le script:

RETTY_NAME="Raspbian GNU/Linux 10 (buster)"
NAME="Raspbian GNU/Linux"
VERSION_ID="10"
VERSION="10 (buster)"
VERSION_CODENAME=buster
ID=raspbian
ID_LIKE=debian
HOME_URL="http://www.raspbian.org/"
SUPPORT_URL="http://www.raspbian.org/RaspbianForums"
BUG_REPORT_URL="http://www.raspbian.org/RaspbianBugs"

2_ Pas de mail que ce soit avec le script d’install sur un raspbian 64bit ni avec l’image yunohost-buster-4.0.2-rpi-beta.zip mais les mail “normaux” sortants et entrants fonctionnent bien oui

RĂ©-Installation d’une V 3.8.4.9 dans une VM (kvm sous proxmox.
Installation d’un paquet d’applications dont Nextcloud :

  • Dokuwiki Dokuwiki
  • Etherpad Mypads Etherpad Mypads
  • Hextris Hextris
  • Leed Leed
  • Lstu Lstu
  • Monitorix Monitorix
  • Nextcloud Nextcloud
  • OpenSondage OpenSondage
  • phpMyAdmin phpMyAdmin
  • Roundcube Roundcube
  • WordPress WordPress
  • Zerobin Zerobin

Mise Ă  jour du systĂšme et des applications

yunohost tools update
yunohost tools upgrade --system
yunohost tools upgrade --app

Lancement du script :

curl https://install.yunohost.org/switchToTesting | bash

Puis mise Ă  niveau du paquet en Yunohost 3.8.5.3 (testing).

yunohost tools upgrade --system

Sauf qu’aprĂšs la migration Ă©choue sur des paquets qui ne passent pas la mise Ă  niveau et la migration Ă©choue :

yunohost tools migrations migrate migrate_to_buster --accept-disclaimer

https://paste.yunohost.org/raw/jubufetasu

J’ai retirĂ© Nextcloud sur l’installation de base et relancĂ© la migration mais souci similaire sur des paquets avec dĂ©pendances non satisfaites que je n’identifie pas.
https://paste.yunohost.org/raw/obifulepol

Je sĂšche.