September 17, 20214 yr I am receiving the following error after an update to 6.10 RC1: HanServe wsdd2[12442]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address I am not sure which docker, vm, or plugin would be causing this? Any ideas from the anyone where I may start to look for a fix? Edited September 17, 20214 yr by Johnny Utah
September 18, 20214 yr Community Expert Boot in safe mode and disable all VM/dockers, if it doesn't do it start enabling VMs/dockers one by one, if still OK, reboot in normal mode then look at the plugins.
September 21, 20214 yr Author Pretty Sure it is all the VMs doing this. Anytime I open one (Win 10, Ubunutu, OS X) it shoots out that error. This has only been since the 6.10 update that I have been noticing this.
October 26, 20214 yr error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address Same here - Any suggestions? - with 6.9.2 no issues
November 1, 20214 yr Same error here. Is it something we can safely ignore? What impact can this have? Nov 1 19:08:00 Tower kernel: docker0: port 10(veth0351d9e) entered disabled state Nov 1 19:08:00 Tower kernel: veth29e74e4: renamed from eth0 Nov 1 19:08:00 Tower avahi-daemon[7541]: Interface veth0351d9e.IPv6 no longer relevant for mDNS. Nov 1 19:08:00 Tower avahi-daemon[7541]: Leaving mDNS multicast group on interface veth0351d9e.IPv6 with address fe80::e063:a1ff:fe3c:d18b. Nov 1 19:08:00 Tower kernel: docker0: port 10(veth0351d9e) entered disabled state Nov 1 19:08:00 Tower kernel: device veth0351d9e left promiscuous mode Nov 1 19:08:00 Tower kernel: docker0: port 10(veth0351d9e) entered disabled state Nov 1 19:08:00 Tower avahi-daemon[7541]: Withdrawing address record for fe80::e063:a1ff:fe3c:d18b on veth0351d9e. Nov 1 19:08:00 Tower wsdd2[7516]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address Nov 1 19:08:02 Tower kernel: docker0: port 10(veth51bbbe0) entered blocking state Nov 1 19:08:02 Tower kernel: docker0: port 10(veth51bbbe0) entered disabled state Nov 1 19:08:02 Tower kernel: device veth51bbbe0 entered promiscuous mode Nov 1 19:08:02 Tower kernel: docker0: port 10(veth51bbbe0) entered blocking state Nov 1 19:08:02 Tower kernel: docker0: port 10(veth51bbbe0) entered forwarding state Nov 1 19:08:02 Tower kernel: docker0: port 10(veth51bbbe0) entered disabled state Nov 1 19:08:05 Tower kernel: eth0: renamed from vethf3c118f Nov 1 19:08:05 Tower kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth51bbbe0: link becomes ready Nov 1 19:08:05 Tower kernel: docker0: port 10(veth51bbbe0) entered blocking state Nov 1 19:08:05 Tower kernel: docker0: port 10(veth51bbbe0) entered forwarding state Nov 1 19:08:06 Tower avahi-daemon[7541]: Joining mDNS multicast group on interface veth51bbbe0.IPv6 with address fe80::3485:ffff:feaf:3a45. Nov 1 19:08:06 Tower avahi-daemon[7541]: New relevant interface veth51bbbe0.IPv6 for mDNS. Nov 1 19:08:06 Tower avahi-daemon[7541]: Registering new address record for fe80::3485:ffff:feaf:3a45 on veth51bbbe0.*. Nov 1 19:08:06 Tower wsdd2[7516]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address Edited November 1, 20214 yr by hundsboog
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.