Persistent warning - wsdd WARNING(pid 1450): no interface given, using all interfaces

[russellsouthey]

There are a number of posts referencing the error "wsdd WARNING(pid 1450): no interface given, using all interfaces" - but no solutions that I've found.

This error occurs after boot and usually shows up twice:-
Jul 23 19:02:40 XXXXX 2022-07-23T19:02:40.394872+02:00 XXXXX.local daemon 1260 - - 2022-07-23 19:02:40,354:wsdd WARNING(pid 1261): no interface given, using all interfaces
Jul 23 19:02:46 XXXXX 1 2022-07-23T19:02:46.432028+02:00 XXXXX.local daemon 1449 - - 2022-07-23 19:02:46,431:wsdd WARNING(pid 1450): no interface given, using all interfaces

Any ideas of why this happens, what it means and if it's a problem that needs to be resolved or ignored.

The only "issue" that's possibly related that I've noticed is that my network Media Subtype: sets to 100baseT... which is a total pain. I usually fiddle about with the network settings and restart the server to return to Media Subtype: 1000baseT. I don't know if the "wsdd WARNING(pid 1450): no interface given, using all interfaces" is related to the Media Subtype: 100baseT problem.

Any ideas of why this happens, and what I can do to prevent / resolve this network speed issue.

Thank you for sharing your thoughts and wisdom.

 

[danb35]

A quick web search for wsdd finds that:

wsdd implements a Web Service Discovery host daemon. This enables (Samba) hosts, like your local NAS device, to be found by Web Service Discovery Clients like Windows.

Seems entirely appropriate that it wouldn't be configured to use a particular interface, and would thus default to using all network interfaces. Edit: but it probably shouldn't be giving an error in the logs--and though it was suggested in other threads that mentioned this error, it doesn't seem that anyone actually reported a bug. I'd suggest you do so and attach a debug file (you can do this through the web UI).

As to the network speed issue, since you've given zero information to work with, really no idea. What hardware (and particularly network hardware) are you using?

 

[profwalken]

I get same messages without knowing what is the cause and what to do to fix it
Nov 14 23:06:59 1 2022-11-14T23:06:59.659513+01:00 SRV.local daemon 1437 - - 2022-11-14 23:06:59,659:wsdd WARNING(pid 1438): no interface given, using all interfaces
Nov 14 23:07:04 1 2022-11-14T23:07:04.468331+01:00 SRVL.local daemon 1659 - - 2022-11-14 23:07:04,468:wsdd WARNING(pid 1660): no interface given, using all interfaces

 

[profwalken]

I opened a TN13 support ticket today, i will post update if something is found or fixed.

 

[EtienneB]

Hello,
Today I also noticed similar warnings (at least I think similar).
"daemon 73070 - - 2022-11-29 17:04:44,183:wsdd WARNING(pid 73071): no interface given, using all interfaces"

I haven't seen them before this week and I was already updated to the latest 13 the day it came out (last week or so?).

Yesterday I did create a bridge between my 10Gb card and 1Gb connection in my Truenas Server, and my macbook uses the 10Gb ethernet to access the internet via the Truenas server. That seems to work fine. Not sure if that is related to this SMB issue?

 

[profwalken]

for now no answers on ticket and it seems it will be fixed on 13.U4

 

[profwalken]

Well, U4 is now applyed but with no change on this problem, always there and the same on all 5 NAS I have

 

[profwalken]

Always there on U5
wsdd WARNING(pid 1355): no interface given, using all interfaces
wsdd WARNING(pid 1592): no interface given, using all interfaces

 

[sretalla]

I guess there would be 2 things to try in relation to this:

1. try turning of the WS-Discovery option under Network | Global Configuration... if that makes it stop, then it's clearly what we think it is. (but that's not a long-term fix if you want to see your TrueNAS server in the Windows "Network" browsing list)

2. try specifying an IP address for the SMB service (which is the only place NETBIOS settings should come from). Maybe that will help.

 

[profwalken]

Thanks for the tips, I did the 1 only as the point 2 was already set .

 

[grapesmc]

Same here. It's still definitely happening in 13.0-U5.1, even with an interface binding set in SMB service.

 

[SweetAndLow]

The message is just a warning but with how it pop's up in messages it kinda makes it seem like it's a problem. My guess is this is just a log level mistake. I'm seeing the same message on 13.0-U5.3.

 

[anodos]

The message is just a warning but with how it pop's up in messages it kinda makes it seem like it's a problem. My guess is this is just a log level mistake. I'm seeing the same message on 13.0-U5.3.

It's not a bug. Just something that's logged at perhaps higher level than it should.