• [6.10.0-rc1] wsdd-mcast-v6 recurring error in log

    kaiguy

    By kaiguy

      • Solved Annoyance

    Ever since upgrading to 6.10-rc1, I've seen these errors recurring in the syslog:

      

    Aug 10 05:03:05 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:05 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:06 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:06 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:06 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:07 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:07 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:08 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address
Aug 10 05:03:09 titan wsdd2[10826]: error: wsdd-mcast-v6: wsd_send_soap_msg: send: Cannot assign requested address

     

    Preceding many of these wsdd errors, I'm seeing log entries relating to ipv6 addresses (but only ipv4 is enabled in my network settings). It also seems to occur around the times where the docker network and avahi log entries are chatty.

     

    Diagnostics attached.

    titan-diagnostics-20210810-0628.zip

    Go to reports Prereleases

    User Feedback

    Recommended Comments

    bonienl
    8 hours ago, bonienl said:

    You likely have docker veth interfaces with ipv6 in use, causing this message.

     

    Under Settings -> SMB -> WSD options, add 

    
-4 -i br0

     

    This limits wsd to ipv4 only and let it listen to interface br0 only (assuming you have br0)

     

    Edited by bonienl
    • Like 1
    • Thanks 1
    Link to comment
    kaiguy

    Thanks, bonienl. I searched but for some reason the report and your post in the release thread didn't show up. I've made the suggested change. Marking this as solved since it probably is :)

    Link to comment


    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.

    Guest
    Add a comment...

    ×   Pasted as rich text.   Restore formatting

      Only 75 emoji are allowed.

    ×   Your link has been automatically embedded.   Display as a link instead

    ×   Your previous content has been restored.   Clear editor

    ×   You cannot paste images directly. Upload or insert images from URL.

    ×

  • Status Definitions

     

    Open = Under consideration.

     

    Solved = The issue has been resolved.

     

    Solved version = The issue has been resolved in the indicated release version.

     

    Closed = Feedback or opinion better posted on our forum for discussion. Also for reports we cannot reproduce or need more information. In this case just add a comment and we will review it again.

     

    Retest = Please retest in latest release.

    Priority Definitions

     

    Minor = Something not working correctly.

     

    Urgent = Server crash, data loss, or other showstopper.

     

    Annoyance = Doesn't affect functionality but should be fixed.

     

    Other = Announcement or other non-issue.