Dnsmasq keep failing after updating to bullseye

  • READ ME AND USE THIS TEMPLATE IF YOU WANT TO GET HELP ! You may ask your question in english or french, whichever is easiest for you… But please use one of the templates provided below :wink:
  • LISEZ-MOI ET UTILISEZ CE MODÈLE DE TOPIC SI VOUS SOUHAITEZ OBTENIR DE L’AIDE ! Vous pouvez poser votre question en anglais ou français, selon ce qui est le plus simple pour vous… Mais de préférence en utilisant l’un des deux modèles fournis ci-dessous :wink:

:uk:/:us: Message template (english)

The “support” category is meant to ask for help or troubleshooting related to installing or using YunoHost or its applications. It is not to ask assistance on general system administration, network administration or special use cases that goes beyond the scope of the project. If you wish to discuss more advanced use case, please post in the “Advanced Use Case” category.

Before posting, please :

My YunoHost server

Hardware: X64 system, NUC server
YunoHost version: 11.0.9.14 (stable)
I have access to my server : Through SSH | through the webadmin | direct access via keyboard / screen | through all of them
Are you in a special context or did you perform some particular tweaking on your YunoHost instance ? : no

Description of my issue

I update my server from 4.8 to bullseye with a running nextcloud instance, synapse server and other applications. In using the server I can not find any misbehavior or any malfunction. I am only getting the messing the error message when trying to start or restart my dnsmasq service, that this is not successful because the port 53 is already in use.

When doing “netstat -tulpn | grep 53” I get the following list
tcp 0 0 192.168.178.60:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5350 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN 22926/connmand
tcp 0 0 192.168.178.60:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 192.168.178.60:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp 0 0 127.0.0.1:5349 0.0.0.0:* LISTEN 8624/turnserver
tcp6 0 0 ::1:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5350 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:53 :::* LISTEN 22926/connmand
tcp6 0 0 ::1:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 ::1:5349 :::* LISTEN 8624/turnserver
tcp6 0 0 2001:a62:1568:8a01:5349 :::* LISTEN 8624/turnserver
udp 0 0 192.168.178.60:5349 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5349 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5349 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5349 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5349 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5349 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5349 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5349 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5350 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5350 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5350 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5350 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5350 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5350 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5350 0.0.0.0:* 8624/turnserver
udp 0 0 127.0.0.1:5350 0.0.0.0:* 8624/turnserver
udp 0 0 192.168.178.60:5353 0.0.0.0:* 1466/python3
udp 0 0 0.0.0.0:5353 0.0.0.0:* 1466/python3
udp 0 0 0.0.0.0:5353 0.0.0.0:* 650/avahi-daemon: r
udp 0 0 127.0.0.1:53 0.0.0.0:* 22926/connmand
udp6 0 0 ::1:5349 :::* 8624/turnserver
udp6 0 0 ::1:5349 :::* 8624/turnserver
udp6 0 0 ::1:5349 :::* 8624/turnserver
udp6 0 0 ::1:5349 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5349 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5349 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5349 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5349 :::* 8624/turnserver
udp6 0 0 ::1:5350 :::* 8624/turnserver
udp6 0 0 ::1:5350 :::* 8624/turnserver
udp6 0 0 ::1:5350 :::* 8624/turnserver
udp6 0 0 ::1:5350 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5350 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5350 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5350 :::* 8624/turnserver
udp6 0 0 2001:a62:1568:8a01:5350 :::* 8624/turnserver
udp6 0 0 :::5353 :::* 650/avahi-daemon: r
udp6 0 0 ::1:53 :::* 22926/connmand

Stopping connmand with pkill -9 connmand
no change in the behavior.

I also tried “yunohost tools regen-conf dnsmasq” with the same result.

The error message in the log is always "status=2/INVALIDARGUMENT
Sep 20 22:35:35 dnsmasq[69642]: Konnte Empfangs-Socket für port 53 nicht erzeugen: Die Adresse wird bereits verwendet or in English I could not create receiving socket for port 53. The address is already in use.

This is not a big issue in general, because I do not experience any malfunction, but I would like to understand what is blocking dnsmasq to avoid potential future problems with the server.

Any advice would be very much appreciated.

Sorry to reopen the post. This is still bugging me and I have not yet found a solution.

Other posts with a similar issue were solved by stopping other services like AdGuard or bind9 which were using port 53.
In my case it is connmand, the interface service for the network. Killing or removing it will result int a non-functioning and not accessible server. So what to do?

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