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

Announcements
, ,
328

It went well :smile: Thanks @YunoHost and team :tada:

329

Hi jarod5001,
Thanks for your reply. I had a glitch with spftoolbox using php7.3.
I deleted the file /etc/php/7.3/fpm/pool.d/spftoolbox.conf and everything went back to normal.

330

Hello. I seem to have had quite the error upgrading. Lots of PHP dying (8.1).
Please, @ericg, stop making apps require YNH 12 when they don’t need to. Pretty please. I simply can not upgrade to 12 yet, but you’re gatekeeping the newest version of these apps for no reason. I know you said the helpers2.1 was updated on 12, but unless that’s an actual change in functionality, I think it is fine as is.

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

331 
2025-01-30 14:57:51,414: WARNING - Job for php8.1-fpm.service failed because the control process exited with error code.
2025-01-30 14:57:51,416: WARNING - See "systemctl status php8.1-fpm.service" and "journalctl -xeu php8.1-fpm.service" for details.
2025-01-30 14:57:51,418: WARNING - invoke-rc.d: initscript php8.1-fpm, action "restart" failed.

Can you look into this error (check the logs of php8.1-fpm) and retry the upgrade?

you’re gatekeeping the newest version of these apps for no reason

We just want to use the newest features of ynh 12 in our packages. We aren’t gatekeeping anything.

332

Thank you for the prompt response! I’m not seeing a lot in these logs. Would uninstalling PHP8.1 be a solution, or is php8.1 a required package?
I did previously have this issue:
Edit: there was no mediawiki pool. Not sure why. I just copied the prestashop config and renamed a few sections. Thank you for your patience. I have now successful upgraded to 12.

systemctl:

× php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager
     Loaded: loaded (/lib/systemd/system/php8.1-fpm.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2025-01-30 14:57:53 CST; 1h 6min ago
       Docs: man:php-fpm8.1(8)
   Main PID: 1238397 (code=exited, status=78)
        CPU: 235ms

Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Scheduled restart job, restart counter is at 5.
Jan 30 14:57:53 host.domain.com systemd[1]: Stopped php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Start request repeated too quickly.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Failed with result 'exit-code'.
Jan 30 14:57:53 host.domain.com systemd[1]: Failed to start php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager.

journalctl:

░░ A start job for unit php8.1-fpm.service has begun execution.
░░
░░ The job identifier is 118506.
Jan 30 14:57:53 host.domain.com php-fpm8.1[1238397]: [30-Jan-2025 14:57:53] ALERT: [pool mediawiki] user has not been defined
Jan 30 14:57:53 host.domain.com php-fpm8.1[1238397]: [30-Jan-2025 14:57:53] ERROR: failed to post process the configuration
Jan 30 14:57:53 host.domain.com php-fpm8.1[1238397]: [30-Jan-2025 14:57:53] ERROR: FPM initialization failed
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Main process exited, code=exited, status=78/CONFIG
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ An ExecStart= process belonging to unit php8.1-fpm.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 78.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit php8.1-fpm.service has entered the 'failed' state with result 'exit-code'.
Jan 30 14:57:53 host.domain.com systemd[1]: Failed to start php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager.
░░ Subject: A start job for unit php8.1-fpm.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit php8.1-fpm.service has finished with a failure.
░░
░░ The job identifier is 118506 and the job result is failed.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Scheduled restart job, restart counter is at 5.
░░ Subject: Automatic restarting of a unit has been scheduled
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ Automatic restarting of the unit php8.1-fpm.service has been scheduled, as the result for
░░ the configured Restart= setting for the unit.
Jan 30 14:57:53 host.domain.com systemd[1]: Stopped php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager.
░░ Subject: A stop job for unit php8.1-fpm.service has finished
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A stop job for unit php8.1-fpm.service has finished.
░░
░░ The job identifier is 118583 and the job result is done.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Start request repeated too quickly.
Jan 30 14:57:53 host.domain.com systemd[1]: php8.1-fpm.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ The unit php8.1-fpm.service has entered the 'failed' state with result 'exit-code'.
Jan 30 14:57:53 host.domain.com systemd[1]: Failed to start php8.1-fpm.service - The PHP 8.1 FastCGI Process Manager.
░░ Subject: A start job for unit php8.1-fpm.service has failed
░░ Defined-By: systemd
░░ Support: https://www.debian.org/support
░░
░░ A start job for unit php8.1-fpm.service has finished with a failure.
░░
░░ The job identifier is 118583 and the job result is failed.

Regarding gatekeeping claim:
I am aware that there are several applications that utilize features that are only available in 12. Immich, vaultwarden, Nextcloud are examples of apps that rely on features only available in 12.
Perhaps I am making this issue larger than life. I only have 3 real examples currently:
Peertube - ericg made peertube require 12, yalh reverted to 11.2.30
LSTU - why is this 12? I see no reason. Because helpers 2.1?
Filebrowser: requires 12 entirely arbitrarily.

The above mentality is what I was referring to with the last sentence in my previous post. I thought apps were requiring 12 just because of helpers 2.1.
I know that ericG is a pillar of YuNoHost given his countless contributions to the project. I appreciate the work that he, and you all do.
I apologize for my outburst.

333

Mailman3 fails to upgrade and seems to require a manual editing of a config file, at the present time: mailman daemon does not start after yunohost 12 upgrade · Issue #48 · YunoHost-Apps/mailman3_ynh · GitHub .

See my proposed PR for the FAQ : Add pointer for failed mailman3 by olberger · Pull Request #2552 · YunoHost/doc · GitHub

Hth,

334

I confirm that this is the problem in YunoHost 12.0. The default admin page used to be https://apps.xxxxx.yyy and after the update became https://xxxx.yyy/yunohost/sso . This bug needs to be fixed as the domain xxxx.yyy needs to be used by another website (blog).

Edit: I checked, and even other root domains that are added to the YunoHost have the “Portal Customization” option available (although these root domains do not redirect to the Yunohost portal page).

image
image1470×865 43.9 KB

335

J’ai pu faire ma migration vers YunoHost v12 aujourd’hui : un grand coup de chapeau Ă  l’équipe, celle-ci s’est vraiment bien passĂ©e, du premier coup et sans nouvelle alerte dans la partie diagnostic. Bravo !

Seul souci que je rencontre : certaines de mes applis n’affichent plus leur icĂŽne dans le portail, alors que c’était le cas en v11. Voici les Ă©lĂ©ments de troubleshoot que j’ai pu collecter :

  • le problĂšme apparaĂźt dans tous les comptes sans distinction ;
  • les applis restent accessibles par leur URL et entiĂšrement fonctionnelles ;
  • l’option “visible en tuile” est bien active pour les applis impactĂ©es, et j’ai Ă©galement essayĂ© de la dĂ©sactiver/rĂ©activer, sans rĂ©sultat ;
  • les droits d’accĂšs aux applis sont corrects ;
  • les applis sont toutes Ă  jour, et celles qui ne l’étaient pas ont Ă©tĂ© mises Ă  jour dans leur derniĂšre version, lĂ  aussi sans effet.

Quelqu’un a-t-il eu ce problĂšme ? Je vais continuer Ă  chercher une explication, mais en attendant, si quelqu’un a une idĂ©e, je suis preneur


Merci encore aux admins pour cette upgrade !

[EDIT] Nevermind, je viens de voir la solution dans une rĂ©ponse un peu plus haut, avec l’option “Afficher les applications d’autres domaines”
 J’avais fait une recherche, mais je pense que je l’ai faite alors que tous les commentaires n’étaient pas chargĂ©s. Donc tout va bien, ouf ! :+1:

343

Bonsoir,
pour la rĂ©cupĂ©ration de mot de passe, ne sachant pas si l’option Ă  Ă©tĂ© prĂ©vue pour plus tard

Il pourrait ĂȘtre judicieux d’ajouter un champ “@Mail de rĂ©cupĂ©ration”,
en effet, si le mot de passe est perdu pour l’accùs au serveur,
il l’est de fait Ă©galement pour le mail associĂ© ( sur le serveur )

344

Le prĂ©cĂ©dent post Ă©tait en anglais, mais lĂ  c’est plus simple pour moi de le faire en français :

Post migration vers yunohost 12, le serveur tournait bien. Plusieurs upgrades ainsi que l’installation de nouvelles applications semblaient s’ĂȘtre dĂ©roulĂ©es sans erreurs.

Ensuite il a fallu effectuer plusieurs cycles arrĂȘt-dĂ©marrage au serveur. C’est aprĂšs ces cycles que j’ai constatĂ© plusieurs problĂšmes :

Mastodon tourne, mais les versions de l’appli renseignĂ©es entre masto et yunohost sont diffĂ©rentes ce qui fait que j’ai constamment la proposition de mise Ă  jour. Sauf que lancer la mise Ă  jour me remonte une erreur indiquant qu’une sauvegarde avec ce nom existe dĂ©jĂ .
:white_check_mark: Aprùs suppression du fichier backup bloquant et un sudo yunohost app upgrade mastodon --force, l’appli est à jour et fonctionnelle.

L’instance de Sharkey refuse de se lancer suite au dernier reboot.
:white_check_mark: Une upgrade forcée semble aussi avoir été la solution. (oui je ne fais pas dans la finesse, je sais)

Supervisor est en status “unknown”. Quand je tente de le lancer à la main, j’obtiens
Failed to enable unit: Unit file supervisor.service does not exist.. Dans les log il s’avĂšre qu’il a Ă©tĂ© redĂ©marrĂ© trop souvent et a fini par ĂȘtre dĂ©sactivĂ©.
Toujours dans les logs on trouve des erreurs liés à pixelfed-horizon :
PHP Fatal error: Composer detected issues in your platform: Your Composer dependencies require a PHP version ">= 8.3.0". You are running 8.2.27. in /var/www/pixelfed/vendor/composer/platform_check.php on line 26
:white_check_mark: AprĂšs une nouvelle upgrade forcĂ©e, supervisor tourne et ne remonte plus d’erreurs de version de php pour pixelfed-horizon.

Nextcloud a un soucis similaire Ă  masto, une diffĂ©rence de version entre l’interface admin yuno et l’instance nextcloud. Une tentative d’install forcĂ©e donne : https://paste.yunohost.org/raw/detolatuka
:x: Échec, il semble impossible d’effectuer une nouvelle sauvegarde de l’appli. Ce qui est trĂšs gĂȘnant car je pensais avoir transfĂ©rĂ© les prĂ©cĂ©dentes sauvegardes (incluant celle de l’upgrade post migration) sur un HDD externe et Ă  priori ce n’est pas le cas. Mais elles ne sont plus sur le stockage du serveur non plus.

345

Est-ce qu’il y a plus de dĂ©tail sur ces fameux moyens de permettre ça : une API qui permettrait de coder des choses dans l’UI ? Est-ce que ça permettrait d’avancer sur : Force password reset upon new user account creation? ?

EDIT: J’ai l’impression qu’il n’y a pas de doc nulle-part sur yunohost-portal-api
 ou alors, Google n’est pas mon ami :-/

346

Bonsoir Ă  tous,

Pour ma part, la montĂ©e de version s’est dĂ©roulĂ©e sans encombre. :partying_face:
Un trÚs grand merci à tous ceux qui ont contribué et surtout aux dev ! :clap:

Longue vie au projet.
Bien sincĂšrement.

347

Another (minor ?) issue with Mailman3 after upgrade : Strange list nonmembers seem to have appeared after upgrade to YNH 12 · Issue #53 · YunoHost-Apps/mailman3_ynh · GitHub

There seem to be strange mails present in the nonmember lists in Postorius for every legit members of the lists
 but that seems quite harmless to me so far.

Hope this helps.

348

il y a eu une erreur similaire ici Upgrade Nextcloud de 29 Ă  30 - #7 by rodinux

est-ce que ce ne serait une erreur dans le script backup au sujet du changement de variable phpversion et php_version ? Dans le post, la cause Ă©tait un module quicknotes qui cassait l’upgrade


349

Salut,
La migration de mon serveur vers yunohost 12 a échoué.
Voici les derniùres lignes avant l’interruption :

Info: [###################.] > 98.8% Installing python3-ldb
Info: [####################] > 100.0% Done 
Info: Downloading...
Warning: E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/setuptools/python3-pkg-resources_66.1.1-1%2bdeb12u1_all.deb: Undetermined Error [IP: 2a01:e0c:1:1598::2 80]
Warning: E: Unable to fetch some packages; try '-o APT::Get::Fix-Missing=true' to continue with missing packages
Error: Migration 0027_migrate_to_bookworm did not complete, aborting. Error: Failed to run command 'aptitude full-upgrade --show-why -o Dpkg::Options::='--force-confold''
Info: The operation 'Run migrations' could not be completed. Please share the full log of this operation using the command 'yunohost log share 20250225-064929-tools_migrations_migrate_forward' to get help

Suite Ă  cette Ă©chec j’ai une erreur python qd j’utilise la commande yunohost (donc je ne peux pas rĂ©cupĂ©rer les logs proposĂ©s) :

sudo yunohost log share 20250225-064929-tools_migrations_migrate_forward
Traceback (most recent call last):
  File "/usr/lib/python3.11/logging/config.py", line 389, in resolve
    found = getattr(found, frag)
            ^^^^^^^^^^^^^^^^^^^^
AttributeError: module 'moulinette.interfaces' has no attribute 'api'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.11/logging/config.py", line 391, in resolve
    self.importer(used)
  File "/usr/lib/python3/dist-packages/moulinette/interfaces/api.py", line 16, in <module>
    from bottle import request, response, Bottle, HTTPResponse, FileUpload
  File "/usr/lib/python3/dist-packages/bottle.py", line 44, in <module>
    from inspect import getargspec
ImportError: cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/lib/python3.11/logging/config.py", line 562, in configure
    handler = self.configure_handler(handlers[name])
              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/logging/config.py", line 724, in configure_handler
    klass = self.resolve(cname)
            ^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/logging/config.py", line 396, in resolve
    raise v from e
ValueError: Cannot resolve 'moulinette.interfaces.api.APIQueueHandler': cannot import name 'getargspec' from 'inspect' (/usr/lib/python3.11/inspect.py)

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/usr/bin/yunohost", line 77, in <module>
    yunohost.cli(
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 35, in cli
    init_logging(interface="cli", debug=debug, quiet=quiet)
  File "/usr/lib/python3/dist-packages/yunohost/__init__.py", line 168, in init_logging
    configure_logging(logging_configuration)
  File "/usr/lib/python3/dist-packages/moulinette/utils/log.py", line 67, in configure_logging
    dictConfig(logging_config)
  File "/usr/lib/python3.11/logging/config.py", line 812, in dictConfig
    dictConfigClass(config).configure()
  File "/usr/lib/python3.11/logging/config.py", line 569, in configure
    raise ValueError('Unable to configure handler '
ValueError: Unable to configure handler 'api'

J’ai tentĂ© 2 fois la migration (en revenant dans un Ă©tat prĂ©cĂ©dent grĂące Ă  un snapshot lors du premiĂšre Ă©chec) et j’ai eu 2 fois la mĂȘme erreur.
Comment résoudre ce problÚme de migration ?

350

Genre tu as vraiment eu dans deux tentative différente cette erreur précise 
? :

E: Failed to fetch http://ftp.fr.debian.org/debian/pool/main/s/setuptools/python3-pkg-resources_66.1.1-1%2bdeb12u1_all.deb: Undetermined Error [IP: 2a01:e0c:1:1598::2 80]
351

Oui j’ai eu 2 fois l’erreur " Failed to fetch 
"
J’ai pas pris note du paquet concernĂ© Ă  la deuxiĂšme tentative mais il me semble bien que c’était aussi
python3-pkg-resources_66.1.1-1%2bdeb12u1_all.deb
J’ai trouvĂ© ça bizarre car en me rendant Ă  l’adresse via mon navigateur, le paquet Ă©tait bien accessible


Je pense rĂ©essayer ce soir, peut-ĂȘtre en modifiant le sources.list de http://ftp.fr.debian.org vers http://ftp.debian.org
Quelles infos je peux vous donner pour identifier le problĂšme si il persiste ?

352

Donc aprĂšs avoir changĂ© le sources.list, la migration s’est bien passĂ©e !

353

Hello, big thanks to the @YunoHost team for this 12.0 release :sparkler: !
I have done the migration this WE and most of the things went well.
Issues I encounter :

  • Metronome app replacement doesn’t have multi-domain support out of the box
  • Metronome data aren’t migrated from the old installation, clients reacts weirdly and don’t reconnect into rooms/channels, I had to click on “Join channel” then it seems to work.
  • Metronome have to restart but wait indefinitely during installation, I had to manually do systemctl restart metronome to make it finish the installation
  • It seems there is no check for free space in /var for the PG migration from 13 to 15, so the first time it crash and auto relaunch in the background but I had to manually add to space to the partition so it can finish with success
  • PG migration doesn’t report any progress and logs are empty /var/log/postgresql/pg_upgradecluster-13-15-main.XXXX

List of apps I have : AgenDAV, Ampache, Baikal, Gitea, Kresus, Lufi, Mastodon, Metronome, Web App ( my blog ), Piwigo, some Redirect, riot, Roundcube, Rspamd, Seafile, Synapse, Tiny Tiny RSS, VPN Client, Wallabag