What type of hardware are you using: Virtual machine
What YunoHost version are you running: 12.0.17 <= for the two yunohost
How are you able to access your server: The webadmin
SSH
Direct access via physical keyboard/screen
ftp
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: Update to 12.1.15.1
Describe your issue
Hello,
I’am using 2 yunohost installations on proxmox, the two in 12.0.17 version :
yuno 1 : an old installation (7 years old, maybe more), only used for emails.
Currently the only apply installed is roundcube.
yuno 2 : a recent installations (august 2024), with nextcloud and collabora.
For yuno 2, the last update have been done without any problem
But for yuno 1, unfortunatelly, no . . .
Since the last update, yunohost 1 take 6 minutes for shutdown; I have not this problem with my other yunohost installation.
The only way to quicky shutdown is with the following command :
sudo poweroff --force
Here is the list update for yuno 1 :
libhashkit2 (de 1.1.4-1+0~20250310.4+debian12~1.gbp476b80 à 1.1.4-1+0~20250818.5+debian12~1.gbp476b80)
libmemcached11 (de 1.1.4-1+0~20250310.4+debian12~1.gbp476b80 à 1.1.4-1+0~20250818.5+debian12~1.gbp476b80)
libssl3 (de 3.0.17-1~deb12u1 à 3.0.17-1~deb12u2)
libunbound8 (de 1.17.1-2+deb12u2 à 1.17.1-2+deb12u3)
libxml2 (de 2.9.14+dfsg-1.3~deb12u2 à 2.9.14+dfsg-1.3~deb12u4)
libxslt1.1 (de 1.1.35-1+deb12u1 à 1.1.35-1+deb12u2)
linux-image-amd64 (de 6.1.140-1 à 6.1.147-1)
linux-libc-dev (de 6.1.140-1 à 6.1.147-1)
moulinette (de 12.0.4 à 12.1.3)
openssl (de 3.0.17-1~deb12u1 à 3.0.17-1~deb12u2)
ssowat (de 12.0.3 à 12.1.1)
yunohost-admin (de 12.0.7.1 à 12.1.10)
yunohost-portal (de 12.0.10 à 12.1.1)
yunohost (de 12.0.17 à 12.1.15.1)
I was unable to found any information in any journal about which programm has a problem.
In order to have informations at startup and shutdown, I update grub :
sudo vim /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT=“quiet”
GRUB_CMDLINE_LINUX=“”
become :
GRUB_CMDLINE_LINUX_DEFAULT=“”
GRUB_CMDLINE_LINUX=“”
update-grub
And reboot
I didn’t see any problme at startup, but for the shutdown, in red :
job yunohost-firewall.service/stop running (5min / 5min
“sudo service yunohost-firewall status” give me this :
● yunohost-firewall.service - YunoHost Firewall
Loaded: loaded (/etc/systemd/system/yunohost-firewall.service; enabled; preset: enabled)
Active: active (exited) since Sat 2025-08-30 01:00:31 CEST; 9h ago
Process: 628 ExecStart=/usr/bin/yunohost firewall reload (code=exited, status=0/SUCCESS)
Main PID: 628 (code=exited, status=0/SUCCESS)
CPU: 207ms
août 30 01:00:31 mydomain.fr yunohost[628]: - 80
août 30 01:00:31 mydomain.fr yunohost[628]: - 443
août 30 01:00:31 mydomain.fr yunohost[628]: - 587
août 30 01:00:31 mydomain.fr yunohost[628]: - 993
août 30 01:00:31 mydomain.fr yunohost[628]: - 5222
août 30 01:00:31 mydomain.fr yunohost[628]: - 5269
août 30 01:00:31 mydomain.fr yunohost[628]: - 5353
août 30 01:00:31 mydomain.fr yunohost[628]: - 9000
août 30 01:00:31 mydomain.fr yunohost[628]: - 9090
août 30 01:00:31 mydomain.fr systemd[1]: Finished yunohost-firewall.service - YunoHost Firewall.
And in yuno 2 (he most recent installation)
Unit yunohost-firewall.service could not be found.
Very strange : with the same updates, yuno 1 (the older) still have yunohost-firewall.service, but not yuno 2 (the newer); and yuno 2 can shutdown without any problem
On yuno 1, with :
sudo service yunohost-firewall stop
and
shutdown now
Yuno 1 was able to shutdown correctly : the problem seems to be with yunohost-firewall.
On this announcement :
I saw this :
“A full rework of our firewall code which was pretty outdated and confusing. The new code is based on nftables which is the modern way of managing network rules.”
If now the firewall is nftables, why did I still have yunohost-firewall on yuno 1 (and not on the other) ?
With the help of this links :
https://www.malekal.com/supprimer-service-linux-systemctl/
I tried to remove yunohost-firewall like this :
sudo su
systemctl stop yunohost-firewall
systemctl disable yunohost-firewall
rm /etc/init.d/yunohost-firewall <= it seems to not be the same directory as in the links above
systemctl daemon-reload
systemctl reset-failed
And finaly :
shutdown now
And now this yunohost installation is able to shutdown correctly.
Even if I was able to found a solution (with difficulty and the great help of gaston) I’like to know why I stil have yunohost-firewall on one yunohost instance (the older), and not on the newer ?
Maybe a patch or/and verification about this for the next update can be usefull ?