🚀 YunoHost 12.0 (Bookworm) release / Sortie de YunoHost 12.0 (Bookworm)

[NathanU]

Fairly catastrophic failure here - the migration failed on my online VPS: grub-install failure for /dev/vda4 (full log). Now, when I go to try to fix the issue, none of my admin users have sudo permissions anymore, and I cannot log in with root (neither via SSH or directly using the VNC function from my VPS provider). I’m a bit concerned here as this is a large media hosting VPS for which I cannot afford a backup. Any help appreciated!

Note: the log is from my second attempt to migrate - the migration failed earlier initially with the same error.

---

Update:

• Fixed the sudo issue by resetting the root password and adding admin users to the sudo group.
• Ran sudo DEBIAN_FRONTEND=dialog dpkg --configure grub-pc per log: received a scary warning saying that GRUB had failed to install on /dev/vda4 and asked whether I would like to continue knowing that my machine may not boot. I selected yes as I was fairly certain that vda4 wasn’t my boot device, and the logs had indicated that GRUB had installed succesfully to /dev/vda2, which is my boot device according to the output of cat /etc/fstab/.
• …and it survived a reboot. Calibreweb is dead now with: ModuleNotFoundError: No module named 'flask'
• Calibreweb fixed with yunohost app upgrade --force calibreweb

[rungeard]

Merci beaucoup pour cette nouvelle version et tout le travail accompli !

La migration s’est bien passée sur mon VPS, j’ai simplement eu le même problème que mentionné ici : 🚀 YunoHost 12.0 (Bookworm) release / Sortie de YunoHost 12.0 (Bookworm) - #228 by utkarshsethi. La solution proposée par utkarshsethi a très bien fonctionnée pour moi !

Deux (petits) problèmes avec la nouvelle version :

• côté admin, impossible d’accéder à https://mydomain.tld/yunohost/admin/#/groups, la page charge indéfiniment
• côté portail utilisateur, l’application ifconfig n’a pas de logo ou celui-ci est cassé

[XPJ38]

Hey there, thanks for the release! I just noticed on the installation page this warning:

Support for Raspberry Pi 0, 1 and 2 was unfortunately dropped since Debian 12 Bookworm. We suggest you migrate to a more modern Raspberry Pi model, supported by Bookworm.

I don’t get it. Where is it written that Debian Bookworm does not support them? The newest Raspberry Pi OS on Bookworm still supports all Pi models after all. Besides, I just upgraded my Pi 2 from Yunohost 11 to 12 and everything works perfectly so why this warning?

[Aleks]

@XPJ38 : what is meant is that we don’t provide pre-installed images for those version because of technical specificities and probably a separate build process compared to RPi 3 and 4. It doesn’t mean that you can’t get to install YunoHost somehow using some other “more technical” process such as obtaining the image from the RPi website, just like you can install YunoHost on pretty much any arm board if you obtain the image from the Armbian website.

[XPJ38]

@Aleks Got it, thanks for the clarification.

[MokuJinJin]

I’ve got yunohost 12 online

My only problems are :

• Wireguard
• PostgreSQL migration (aeneria, paperless, immich)

Wireguard was simple : backup, unistall, migrate, restore.

PostgreSQL migration (29. Migrer les bases de données de PostgreSQL 13 vers 15 ) is still failing.

I’ve tried apt install postgresql-15-postgis-3 postgresql-15-postgis-3-scripts no change.

sudo pg_lsclusters
Ver Cluster Port Status Owner    Data directory              Log file
13  main    5432 down   postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log
16  main    5433 down   postgres /var/lib/postgresql/16/main /var/log/postgresql/postgresql-16-main.log

migration logs

server reboot, PostgreSQL service is still down.

What can i do next ?

[MokuJinJin]

Since i have 3 app (aeneria, immich, paperless) using postgresql, i’ve made backup of each.

I’ve already made a full backup before launching migration 11->12, but 400G to decompress for only 3 app was too long for me.

during backup, aeneria can’t made db backup

ERROR: invalid page in block 35217 of relation base/16421/3192429

DB is corrupted. Aeneria is not active anymore, i’ve decide to abandon it. RIP Aenaria

Removing aeneria was not difficult, but the migration doesn’t want to work.

Immich and Paperless are not in big use, backup them, uninstall them.

Launch migration, and it does it in a blink of an eye. Of course there is no postgresql app, so no postgresql installed.

Go to restore app, restoration OK for both app

and if launch the migration now ?

$ sudo yunohost tools migrations run 0029_postgresql_13_to_15 --force-rerun

and same error

ERREUR:  page invalide dans le bloc 0 de la relation base/16464/2605

error : full logs

relaunch postgresql/immich/paperless services, it works. i’ve postgresql 13 and 16 running.
i hope it would not cause any trouble.

[alexg]

Upgraded and it all went super fine ! Thank you so much for this awesome work !

[m_t]

Salut !

J’ai tenté de faire la migration il y a quelques semaines mais elle a échouée en partie.
J’ai lancé un post ici mais sans succès.

Mon serveur est pour l’instant coincé avec des versions mélangées:

mt@server:~$ sudo dpkg --list | grep "yunohost\|moulinette"
ii  moulinette                            12.0.3                                         all          prototype interfaces with ease in Python
iF  yunohost                              12.0.7                                         all          manageable and configured self-hosting server
ii  yunohost-admin                        11.3.0    

Est-ce que quelqu’un aurait une idée de la meilleure marche à suivre pour tenter de réparer ça ?

Merci beaucoup!

[croulibri]

Hello,
I have made the migration of my first Yunohost server hosted on a Ionos VPS.
I started with full backup… in case.

At first, the migration failed

I faced :

• grub-install failure for /dev/vda4 (similar to 🚀 YunoHost 12.0 (Bookworm) release / Sortie de YunoHost 12.0 (Bookworm) - #266 by NathanU)
• admin user doesn’t have sudo permissions anymore

Solution :

Put again sudo permission to admin user : log on ssh with admin account, then

su
sudo usermod -aG sudo admin

Then with my admin account, I tried to solve the GRUB problem with

sudo DEBIAN_FRONTEND=dialog dpkg --configure grub-pc

and install GRUB again on /dev/vda4 even if an error arise in the process

I ran the migration again… successfully this time.

My only app on this server is Wireguard and is still functional after migration and reboot.

I have now to migrate another bigger Yunohost server (at home), with critical apps for my daily use, particularly:

• Synapse (+++)
• Nextcloud (+++)
• Dokuwiki (+++)
• My_Webapp (with Piwigo connected to a MySQL database) (+++)
• Vaultwarden (++)

I will clone system disk + full backup in case.

But do you know if I may encounter particular difficulties with these apps during migration?
I have currently php7.4-fpm, php8.1-fpm, php8.2-fpm and php.8.4-fpm running at the same time on my server. Is this normal? May I face problem with this during migration (I remember problems with php in my last migration 10=>11 so…).

Thanks in advance for your advices

[crustyourmind]

@croulibri

I have currently php7.4-fpm, php8.1-fpm, php8.2-fpm and php.8.4-fpm running at the same time on my server. Is this normal?

Yes

Pourquoi plusieurs versions de php-fpm sur mon serveur?

C’est clairement pas la seule chose à modifier … il faut aussi éditer et bouger le fichier de conf qui se trouve dans /etc/php/7.0/fpm/pool.d/my_webapp.conf (un truc du genre, pas sur du chemin exact) vers l’équivalent en 7.4 (et modifier le contenu, notamment pour le chemin du socket) Puis redémarrer les services php-fpm correspondants etc … Le truc c’est que c’est franchement pas conseillé de faire tout ce bricolage car ensuite l’app yunohost va être perdue lors des upgrade / backup … Par …

[navanchauhan]

I can’t directly reply to Erreur 504 via yunohost/sso portalapi (debian Bookworm)

For me this was because /etc/nginx/conf.d/yunohost_api.conf.inc did not have the location /yunohost/portalapi/ section in it

[croulibri]

Youuuuu
I am flying with Yunohost 12 !!!

Thanks again for the huge work of all volunteers of Yunohost project. Everything went fine during the migration.
My small home server running since January 2017 have successfully moved to a new version.

I am only wondering how can I check the PostgreSQL migration was done?

[Aleks]

@croulibri

I am only wondering how can I check the PostgreSQL migration was done?

It should be listed in Tools > Migrations (probably under ‘previous migration’ if it’s done, and that part which is wrapped by default if i remember correctly)

[croulibri]

Hello @Aleks
In October 2022, you helped me during the previous migration 10=>11 that failed on my server. But this time everything seems fine!
So I didn’t have to bother you repairing the Php dependencies

My current previous migration are:

Does it means everything is OK?

[Aleks]

Yup, sounds like it

(Don’t scream it too loud though, computers have a tendency to spontaneously break when we’re too happy about them)

[Christian]

Hi, I have the following problem when updating. When I start the update on the command line I get:

W: http://deb.debian.org/debian/dists/bookworm/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/php.gpg are ignored as the file has an unsupported filetype.
W: http://security.debian.org/debian-security/dists/bookworm-security/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/php.gpg are ignored as the file has an unsupported filetype.
W: http://deb.debian.org/debian/dists/bookworm-updates/InRelease: The key(s) in the keyring /etc/apt/trusted.gpg.d/php.gpg are ignored as the file has an unsupported filetype.

Any ideas how to set this straight? Thanks

[BrunoK]

migration went extremly well, all in all. Thanks for the great work !!
Only one thing:
Diagnosis says:

Die Konfigurationsdatei /etc/apt/sources.list.d/extra_php_version.list scheint manuell verändert worden zu sein.

I guess that translates ~ to:

configurationfile '/etc/apt/sources.list.d/extra_php_version.list seems to have been changed manually

I executed

yunohost tools regen-conf apt --dry-run --with-diff
yunohost tools regen-conf apt --force

and now everything looks fine!

[Morraycage]

English Version

It’s exactly what we call a Christmas Gift !

Thanks to all Yunohost team for the hard work and continuing to bring us

French Version

C’est ce qu’on appelle un cadeau de Noël !

Merci à toute l’équipe de Yunohost pour votre travail acharné et votre dévotion !

[rodinux]

Have you try like the next post these steps ?

yunohost tools regen-conf apt --dry-run --with-diff
yunohost tools regen-conf apt --force