Nftables et yunohost-portal-api ne se lancent plus

What type of hardware are you using: Virtual machine
What YunoHost version are you running: 12.0.11+202501212200
How are you able to access your server: The webadmin
SSH
Are you in a special context or did you perform specific tweaking on your YunoHost instance ?: no

Describe your issue

Hello,
since the last update, the 2 services don’t start at all and I can’t restart anything via the webadmin.
I’ve restarted the server, tried to launch the services but it doesn’t start.

Are there any error logs that I can add for help?
Thanks a lot.

Share relevant logs or error messages

Jan 21 18:25:50 systemd[1]: Starting nftables.service - nftables…
Jan 21 18:25:51 systemd[1]: Finished nftables.service - nftables.
Jan 24 01:06:41 systemd[1]: Stopping nftables.service - nftables…
Jan 24 01:06:41 systemd[1]: nftables.service: Deactivated successfully.
Jan 24 01:06:41 systemd[1]: Stopped nftables.service - nftables.
Jan 24 01:06:41 systemd[1]: Starting nftables.service - nftables…
Jan 24 01:06:42 systemd[1]: Finished nftables.service - nftables.
Jan 24 09:21:54 systemd[1]: Stopping nftables.service - nftables…
Jan 24 09:21:54 systemd[1]: nftables.service: Deactivated successfully.
Jan 24 09:21:54 systemd[1]: Stopped nftables.service - nftables.

Hello!

Exactly the same problem here. With the version “12.0.11+202501291415 (unstable)”.

In addition, here is the YunoHost Portal API log:

  • Feb 08 22:02:27 systemd[1]: yunohost-portal-api.service: Scheduled restart job, restart counter is at 154516.
  • Feb 08 22:02:27 systemd[1]: Stopped yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:27 systemd[1]: Started yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:27 systemd[1]: yunohost-portal-api.service: Main process exited, code=killed, status=31/SYS
  • Feb 08 22:02:27 systemd[1]: yunohost-portal-api.service: Failed with result ‘signal’.
  • Feb 08 22:02:33 systemd[1]: yunohost-portal-api.service: Scheduled restart job, restart counter is at 154517.
  • Feb 08 22:02:33 systemd[1]: Stopped yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:33 systemd[1]: Started yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:33 systemd[1]: yunohost-portal-api.service: Main process exited, code=killed, status=31/SYS
  • Feb 08 22:02:33 systemd[1]: yunohost-portal-api.service: Failed with result ‘signal’.
  • Feb 08 22:02:38 systemd[1]: yunohost-portal-api.service: Scheduled restart job, restart counter is at 154518.
  • Feb 08 22:02:38 systemd[1]: Stopped yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:38 systemd[1]: Started yunohost-portal-api.service - YunoHost Portal API.
  • Feb 08 22:02:38 systemd[1]: yunohost-portal-api.service: Main process exited, code=killed, status=31/SYS
  • Feb 08 22:02:38 systemd[1]: yunohost-portal-api.service: Failed with result ‘signal’.

In addition…

I tried systemctl list-dependencies yunohost-portal-api.
And ‘─nftables.service’ appear well, in green. So, I suppose that it confirm the link between both and apparently, it start well… If i understand something…

Maybe, it is related to /etc/systemd/system/fail2ban.service.d/systemd-override-bind-nftables.conf?

# This override config restarts and reloads fail2ban when nftables is started/reloaded

[Unit]
PartOf=nftables.service
ReloadPropagatedFrom=nftables.service

As I’m a simple user… I guess that this is better to wait the next stable update instead of modify the .conf…

You folks are running the unstable version of YunoHost … The unstable version is, as the name indicates, unstable

The install script should have warned you during the initial install that the unstable will break and that you should only install if you know what you’re doing …

1 Like

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.