Jump to content

  • 6.12.13 - active-backup can changed while Docker and VM is enabled, disabling all interfaces of the backup

    adde r2

    By adde r2

      • Minor

    Hello,

    Is it intended behavior that you can change active-backup while array is running?

    I wanted to remove the active-backup from using multiple interfaces because Unifi was complaining that multiple interfaces was using the same IP, which was causing other issues.

    The active backup was set to 4 interfaces: eth1, eth2, eth3, and eth4
    I had 4 VLANs on this interface too.

    Unraid 6.12.13

    I went in while it was still running and unchecked eth2, eth3 and eth4 then pressed apply. This caused a breakup of the active backup, setting ALL interfaces of the backup (including the eth1) to inactive, deleted all VLANs (because it got set to disabled?) and somehow set the eth1 description to the last VLANs name.

    I had another unraid system with a similar setup (including VLANs) that I was going to update the same and when I did, the exact same happened.

    I set it to minor, but depending on how much configuration is deleted, it might be more serious for someone else.

    Let me know if you wanna know anything more.

    EDIT: After enabling the network again and re-entering the VLANs again, all shims and VLANs show up in the network tab (and under Interface Extras). They also show up under in the docker settings where they are enabled. But for some reason br1 and the first 3 VLANs don't show up when editing a docker, only the last VLAN show up.
    This did not happen on the other system, it worked fine after enabling the network. But the diagnostics is on the system where this happened, so might give some clues.

    EDIT 2: Nuking docker folder fixed the problems of them not showing.

    Best Regards,
    Adam

    diagnostics-20241022-0738.zip

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    JorgeB

    JorgeB 8,428

    Posted

    You can change any network setting with the array running if both Docker and VM services are disabled, AFAIK it's always been like this.

    adde r2

    adde r2 2

    Posted (edited)

    Pardon me, I forgot that you can edit without stopping the array. I normally do the network changes by just stopped the array.
    However I did have both Docker and VM services enabled while I did that change.

    Most settings in the network are locked as you say, and the message to stop VM and Docker is there.
    Bridging members is the only option that is NOT locked (Is this by design?), and making a change there brings up the apply option just like you changed something. You can then apply that option while it is hot running and that causes the problem I described.

    I changed the title to be more accurate.

    Edited by adde r2
    JorgeB

    JorgeB 8,428

    Posted

    41 minutes ago, adde r2 said:

    Bridging members is the only option that is NOT locked

    I assume you mean bond? I cannot reproduce, nothing can be changed with docker or VM service running.:

     

    image.png

     

     

    adde r2

    adde r2 2

    Posted

    Yeah I mean bonding members. Strange, do you have any VLANs attached to yours? I have 4 VLANs on that interface.

    For some reason bonding members is not locked, but all others are.
    image.png.6d6036b0c7b8df899a427d538b48c8b6.png

    adde r2

    adde r2 2

    Posted

    Can you try disconnecting eth1 on your active backup and activate bonding mode on it? For me I noticed that just eth0 was locked on both systems, but all others were open.
     

    JorgeB

    JorgeB 8,428

    Posted

    23 hours ago, adde r2 said:

    but all others were open.

    Yes, a bond on eth1 is also open for me, but not sure if that was on purpose, since eth0 in the main interface, and possibly the only one you cannot change with docker/VMs running, or an oversight.

    adde r2

    adde r2 2

    Posted

    I would say that this most likely this an oversight, since it locks everything else on it and given the disastrous effect it has when you remove interfaces from the active backup.


    It might be that the amount of unraid systems having 3+ ethernet ports, enabling bonding between the last two and changing it while running, might be small that it just doesn't get encountered.

    I had both dockers and VM running on that active-backup while I was doing that change, but it probably doesn't sense that they are running on it.



    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.

×
×
  • Create New...