Crash of Yunomdns since last upgrade

My YunoHost server

Hardware: VPS bought online
YunoHost version: 11.1.6.2
I have access to my server : Through SSH and through the webadmin
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

Since few days now i have a diagnosis error about the service called yunomdns that is not running

After few searches i found some posts suggesting to force a rebuild of the configuration of the service before restarting the service
So i had executed the following commands /

admin@myhost:~$ sudo yunohost tools regen-conf mdns
[sudo] password for admin:
admin@myhost:~$ sudo systemctl restart yunomdns
admin@myhost:~$ sudo systemctl status yunomdns
● yunomdns.service - YunoHost mDNS service
     Loaded: loaded (/etc/systemd/system/yunomdns.service; enabled; vendor preset: enabled)
     Active: active (running) since Sun 2023-02-12 14:50:45 CET; 7s ago
   Main PID: 1184961 (yunomdns)
      Tasks: 5 (limit: 289849)
     Memory: 12.5M
     CGroup: /system.slice/yunomdns.service
             └─1184961 /usr/bin/python3 /usr/bin/yunomdns

Feb 12 14:50:45 myhost.fr systemd[1]: Started YunoHost mDNS service.
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['127.0.0.1'] on interface venet0
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.20.0.1'] on interface br-ab73e065e15e
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.27.0.1'] on interface br-e86133241bee
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.17.0.1'] on interface docker0
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Registering...
Feb 12 14:50:49 myhost.fr yunomdns[1184961]: Registered. Press Ctrl+C or stop service to stop.
admin@myhost:~$ sudo systemctl status yunomdns
● yunomdns.service - YunoHost mDNS service
     Loaded: loaded (/etc/systemd/system/yunomdns.service; enabled; vendor preset: enabled)
     Active: failed (Result: signal) since Sun 2023-02-12 14:51:03 CET; 3s ago
    Process: 1184961 ExecStart=/usr/bin/yunomdns (code=killed, signal=KILL)
   Main PID: 1184961 (code=killed, signal=KILL)

Feb 12 14:50:45 myhost.fr systemd[1]: Started YunoHost mDNS service.
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['127.0.0.1'] on interface venet0
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.20.0.1'] on interface br-ab73e065e15e
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.27.0.1'] on interface br-e86133241bee
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Adding yunohost.local with addresses ['172.17.0.1'] on interface docker0
Feb 12 14:50:47 myhost.fr yunomdns[1184961]: Registering...
Feb 12 14:50:49 myhost.fr yunomdns[1184961]: Registered. Press Ctrl+C or stop service to stop.
Feb 12 14:51:03 myhost.fr systemd[1]: yunomdns.service: Main process exited, code=killed, status=9/KILL
Feb 12 14:51:03 myhost.fr systemd[1]: yunomdns.service: Failed with result 'signal'.
admin@myhost:~$

I don’t understand the error message and where the kill signal comes from. I could not find any revelant information in the system logs
File access rights are different than others in the configuration folder, should i change them to root:root ?

drwx------  2 root root     4096 Nov  5 23:15 domains
-rw-------  1 root root      416 Nov 14 15:01 firewall.yml
-rw-r--r--  1 root root      386 Nov 14 15:01 firewall.yml.old
drwx------  8 root root     4096 Feb 10 09:25 hooks.d
-rw-r--r--  1 root root        0 Oct 27 10:38 installed
-r--------  1 root root     2488 Oct 27 11:10 letsencrypt_account.pem
-rw-r--r--  1 mdns mdns       30 Feb 11 12:17 mdns.yml
-rw-------  1 mdns mdns       30 Oct 27 10:31 mdns.yml.old
-rw-------  1 root root      231 Feb  2 09:13 migrations.yaml
-rw-------  1 root root       24 Oct 28 12:07 psql
-rw-------  1 root root     7891 Feb 11 12:17 regenconf.yml
-rw-------  1 root root      565 Feb 10 09:24 services.yml

EDIT : trying to set root:root on the file does not solve the issue

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