#921914 minissdpd: Lots of "Address already in use" syslog messages (again)

Package:
minissdpd
Source:
minissdpd
Description:
keep memory of all UPnP devices that announced themselves
Submitter:
Matijs van Zuijlen
Date:
2026-10-22 20:21:01 UTC
Severity:
normal
Tags:
#921914#5
Date:
2019-02-10 07:54:19 UTC
From:
To:
Dear maintainer,

With the most recent upgrade of minissdpd, the 'Address already in use'
messages from #903783 seem to have returned. They now appear every five
minutes or so:

    Feb  9 17:02:58 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:02:58 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:02:58 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:01 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:01 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:01 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:09 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:09 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:03:09 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:11:18 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:11:18 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use
    Feb  9 17:11:18 bean minissdpd[2321]: setsockopt(udp, IPV6_JOIN_GROUP)(FF02::C, wlan0): Address already in use

I do not recall consciously having set the MiniSSDPd_INTERFACE_ADDRESS
option, which was modified on 2019-02-08, it seems when the latest
release was installed. Maybe this has something to do with it?

Regards,
Matijs
#921914#10
Date:
2019-02-10 09:13:28 UTC
From:
To:
Dear maintainer,

After sending this report, I started editing my logcheck configuration
to ignore these messages for the time being, and I discovered that a
similar message was already filtered out, but with a blank interface
name. I'm guessing I added this filter while #903783 was open.

Indeed, looking at older logs, I can see that these messages were
present at least as long ago as January:

    Jan 09 14:42:54 bean minissdpd[9821]: setsockopt(udp,
IPV6_JOIN_GROUP)(FF02::C, ): Address already in use

I'm not sure #903783 was actually fixed, at least for my system.

Kind regards,
Matijs van Zuijlen
#921914#15
Date:
2019-02-20 07:13:57 UTC
From:
To:
No idea. Could you please attach an example of log, 'ip a' 'ip r'
'sudo netstat -anup' output, and its corresponding wireshark capture?
#921914#20
Date:
2019-02-26 15:07:52 UTC
From:
To:
can't reproduce by any possible means I can image
#921914#31
Date:
2026-02-13 10:00:19 UTC
From:
To:
Dear maintainer,

These messages no longer occur so as far as I'm concerned this issue can
be closed. I guess it was fixed in
https://github.com/miniupnp/miniupnp/pull/473.
#921914#36
Date:
2026-10-22 20:18:57 UTC
From:
To:
I tried to debug the problem. It seems that the router (a Fritz!box) sends an
RTM_NEWADDR even if the address has not changed.

For some unknown minissdpd wants to update the multicast groups FF02::C and
FF05::C, without leaving these groups and without checking whether it is
connected to these groups.

In the following minissdpd is unresponsive to requests from the network. That
means minidlna will not be recognised from other machines. I'm currently not
sure wether  this is a new topic or the same.

Some debug messages:

minissdpd[110548]: ProcessInterfaceWatchNotify RTM_NEWADDR index=2 fam=10
prefixlen=64 flags=0 scope=0
minissdpd[110548]:  rta_len=20 rta_type=1
'2a02:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx'
minissdpd[110548]:  rta_len=20 rta_type=6 'valid=7200 preferred=3600'
minissdpd[110548]:  rta_len=8 rta_type=8 '*unknown*'
minissdpd[110548]:  rta_len=5 rta_type=11 '*unknown*'
minissdpd[110548]: RTM_NEWADDR: 2a02:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64
minissdpd[110548]: setsockopt(s=5, IPV6_JOIN_GROUP)(FF02::C, eth0): Address
already in use
minissdpd[110548]: setsockopt(s=5, IPV6_JOIN_GROUP)(FF05::C, eth0): Address
already in use
minissdpd[110548]: SSDP request: 'M-SEARCH' (1) unknown st=ssdp:all
minissdpd[110548]: SSDP M-SEARCH from 192.168.207.211:39967 ST:ssdp:all
minissdpd[110548]: ** i=0 deltadev=0 **
minissdpd[110548]: ProcessInterfaceWatchNotify RTM_NEWADDR index=2 fam=10
prefixlen=64 flags=0 scope=0
minissdpd[110548]:  rta_len=20 rta_type=1
'fd00:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx'
minissdpd[110548]:  rta_len=20 rta_type=6 'valid=7200 preferred=3600'
minissdpd[110548]:  rta_len=8 rta_type=8 '*unknown*'
minissdpd[110548]:  rta_len=5 rta_type=11 '*unknown*'
minissdpd[110548]: RTM_NEWADDR: fd00:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx/64
minissdpd[110548]: setsockopt(s=5, IPV6_JOIN_GROUP)(FF02::C, eth0): Address
already in use