Auto Discovery doesn't work | SSPD: Failed to setup listener for 0.0.0.0: [Errno 98] Address in use | GitHub Issue #61694

Configuration
1

Hi all :raised_hand: :grinning_face_with_smiling_eyes: ,

I updated my HA-instance a week ago, and hereafter, it’s complaining about the port for SSPD (Auto Discovery) are already in use.

The logger are simply throwing the following error:

Logger: homeassistant.components.ssdp
Source: components/ssdp/__init__.py:354
Integration: Simple Service Discovery Protocol (SSDP) (documentation, issues)
First occurred: 12:29:55 PM (1 occurrences)
Last logged: 12:29:55 PM

Failed to setup listener for 0.0.0.0: [Errno 98] Address in use

Home Assistant are already using the :5353 port

The wierd thing is, that Home Assistant are already the container, which are using the :5959 port, if I’m correct.

Here’s an output, while the HA-instance are running:

> sudo lsof -i :5353
COMMAND   PID USER   FD   TYPE DEVICE SIZE/OFF NODE NAME
python3 21432 root   13u  IPv4 116981      0t0  UDP *:mdns 
python3 21432 root   22u  IPv4 117012      0t0  UDP localhost:mdns 
python3 21432 root   24u  IPv4 117013      0t0  UDP 10.0.0.5:mdns 
python3 21432 root   25u  IPv4 117014      0t0  UDP 10.0.0.109:mdns 
python3 21432 root   26u  IPv4 117015      0t0  UDP 172.17.0.1:mdns 
python3 21432 root   27u  IPv4 117016      0t0  UDP 172.19.0.1:mdns

And here’s the result, if I kill the HA-instance:

> sudo lsof -i :5353
... nothing ...

The HA- instance is in “host” network-mode, and has been working like this for yeas.
The instance had not been updated for half a year (due to a stupid mistake, in my script), so I’m unsure if something related configuration-changes, has something to do with it.

By looking at the PID, it’s clear that the python-script for Home Assistant are the one using :5353:

> top -c | grep 21432
21432 root      20   0  457784 351572  31196 S   0.7   6.9   0:23.10 python3 -m homeassistant --config /config

Am I looking at the wrong things, while trying to spot the actual issue?

I’m running: Home Assistant 2021.11.5
With Frontend version: 20211109.0 - latest
In a docker-container on Debian

The outputs are from the host-system, not within the instance/container.

Could it be something related to another module?

I hope someone are able to point me in the right direction. It must be a minor thing, that I’ve overlooked :grinning_face_with_smiling_eyes: …

It’s now submitted on GitHub.

2

Anyone? I’m not sure what’s causing the problem.

3

I have the same issue. No solution found yet …

4

Are your setup simular to mine? Else, please share your setup so the devs have more information to work with.

5

Yes.

Docker container with network in host mode

6

Okay.

I’m still facing the same issue - also after the latest Update. I’m a bit unsure what to do next.

Did you manage to fix it?

7

I’ve had this issue for about 2-3 months now so it’s nothing specific to the latest version. @exetico have you logged an issue on github? You are more likely to find a solution via the devs on github than on here

8

No, not before now. I was wondering if other persons was facing the same issue. With the high volume of issues submitted on GitHub, I would like to check here on the forum, before submitting the issue :slight_smile:

It’s now created here:

9

I started having this problem after adding a service listening to port 1900 (Plex docker needs this port). Thus I assume this has to do with SSPD using the same port.

1 Like
10

It’s actually resolvdd. I didn’t look at the right port, due to miss reading in the docs or so.

I’ll mark this as solved.