Jump to content

  • [6.9.2] Networking issues (not present in 6.8.3) that are dramatically effecting Dockers, VM's, and the Unraid webUI

    Kudagra

    By Kudagra

      • Solved Urgent

    I recently upgraded to 6.9.2 and oddly enough- all was working well for the first couple days. Then randomly this network problem arose once again (with no server changes done on my end between then and now). This has been an issue from 6.9.0+ (issue exists in 6.10.0 rc-1 when I tested that as well). I experienced this the first time I upgraded to 6.9.1 and was unable to fix the issue.

     

    I've spent HOURS searching and troubleshooting to no avail. Below are my thorough notes on such. I've attached my diagnostics along with a LatencyMon test result (done in my Windows 10 VM). Just trying to cover all possible bases, so here's my VM XML's as well.

     

    Windows 10 VM XML - https://pastebin.com/UnD7D4vU

    Big Sur VM XML - https://pastebin.com/Y1Xd7ZCi

     

    ------------------------

     

    Problems

        • Intermittent slow/unresponsive Unraid webUI
        
        • Extremely slow dockers
            ○ Deluge
                § <650 KiB/s instead of 7 MiB/s
            ○ SABnzbd
                § <500 KiB/s instead of 14 MiB/s
                    □ Without VPN enabled- right after starting this docker, I see full speed (14 MiB/s) and then a steady decline until it reaches it's current slow amount (<500 KiB/s)
                    
        • Intermittent slow/unresponsive internet in VMs, and games have high FPS but certain aspect of the game stutter (offline games function 100%)
            ○ https://www.reddit.com/r/VFIO/comments/phechz/vm_gaming_high_fps_but_stutter_every_15_seconds/
            ○ https://www.reddit.com/r/unRAID/comments/phec5i/69x_vm_gaming_high_fps_but_stutter_every_15/
            ○ https://forums.unraid.net/topic/113331-69x-vm-gaming-high-fps-but-stutter-every-15-seconds-affecting-in-game-unitscharacters-but-nothing-else/?tab=comments#comment-1031327

       

         • GUI Mode Black Screen with blinking cursor (probably not network related, but it's still a current issue I can't get resolved)

     

    -------------

     

    Attempted Fixes

        1. Updating to 6.10.0 rc-1
            a. No effect (now restored to 6.9.2)
            
        2. Baremetal boot from VM drive (W10)
            a. Baremetal functions 100% without issue
            
        3. Boot in SAFE mode
            a. No effect (tested dockers and VM's)
            
        4. Boot Legacy
            a. No effect (now restored to UEFI)
            
        5. Disable Dockers
            a. No effect (dockers now restored)
                i. https://forums.unraid.net/topic/104194-691-any-screen-with-docker-data-extremely-slow/
                    1) Others with docker problems
                        a) https://forums.unraid.net/topic/100031-69-docker-causing-slow-networking/
                        b) https://forums.unraid.net/topic/105466-docker-slow-after-upgrading-to-69/
                        c) https://www.reddit.com/r/unRAID/comments/m1am0l/unraid_6_9x_docker_containers_will_not_start/
                        
        6. Delete/rename network.cfg and network-rules.cfg in the flash drive and reboot
            a. Won't boot to network access, attempted to access GUI mode and will not complete boot (files now restored)
                i. https://forums.unraid.net/topic/107759-network-issues-after-upgrade-to-692/
                
        7. Deleted "/config/vfio-pci.cfg" and "/config/vfio-pci.cfg.bak to attempt correcting GUI mode issue
            a. Hangs at "vfio-pci 0000:0e:00.0: vgaarb: changed VGA decodes: olddecodes=io+mem,decodes=io+mem:owns=io+mem", for GUI, but network is accessible with no improved results. (All items now restored from backup)
                i. https://forums.unraid.net/topic/101444-unraid-not-booting/
                
        8. Replace “GO” file from /config/ with default file from downloaded 6.9.2 package
            a. No result (file restored from backup)
                i. https://forums.unraid.net/topic/104929-solved-no-web-gui-after-upgrade-from-683-to-691/
                
        9. Disable RAM X.M.P. profile in BIOS
            a. No result (setting now restored)
            
        10. Change Unraid Network setting -> SSL/TLS from "Auto" to "No"
            a. No result (setting restored)
                i. https://forums.unraid.net/topic/104448-unraid-691-web-interface-down/
            
        11. No "GPU Stats" plugin, no "Nvidia Driver" plugin.
            a. https://forums.unraid.net/topic/105885-constant-crashes-since-updating-to-69x/
            b. https://forums.unraid.net/bug-reports/prereleases/690-rc2-gui-mode-blinking-cursor-gt-710-r1271/
        
        12. Change BIOS settings -> Advanced CPU Settings ->
            a. "C-State" -> "Disabled"
            b. "Power Supply Idle" -> "Typical Current Idle"
                i. No results (settings now restored)
                    1) https://www.reddit.com/r/unRAID/comments/od7ehp/upgrading_to_692_from_682_crashing/

     

    command.center-diagnostics-20210907-1920.zip LatencyMon Results (Windows 10 VM).txt

    Go to reports Stable Releases

    User Feedback

    Recommended Comments

    Kudagra

    Couple other thing's I've noticed-

     

    • Docker Related
      • Plex - Can't automatically find media matches (random, I know)

     

    • VM Related
      • VPN connection causes full loss of network (for just the VM)
      • Very poor audio/video quality in video calls
      • Have difficulty connecting, and staying connected, to online account services (email accounts, game launchers, ect..)
    Edited by Kudagra
    Link to comment
    Kudagra

    Any other ideas for additional network testing or anything else?

     

    I'm getting desperate and really don't want to have to be limited to 6.8.3 for the foreseeable future.

    Link to comment
    Vr2Io

    Could you use another USB for fresh OS ( 6.10.0 rc-1 ) install ( no need licence ) then verify Unraid GUI access thr network have problem or not.

    Edited by Vr2Io
    Link to comment
    Kudagra
    17 hours ago, Vr2Io said:

    Could you use another USB for fresh OS ( 6.10.0 rc-1 ) install ( no need licence ) then verify Unraid GUI access thr network have problem or not.

     

    I feel like I should have tested this long before your suggestion... I have both GUI access and network UI access with a fresh install of 6.10.0 rc-1.

     

    That eliminates any hardware incompatibilities!

     

    EDIT: I did some testing with various network settings on fresh installs (my main server uses UEFI + Static)-

     

    • 6.10.0 rc-1 (UEFI + DHCP) = GUI and webUI success
    • 6.10.0 rc-1 (UEFI + Static) = GUI and webUI success
    • 6.9.2 (UEFI + DHCP) = NO GUI (black screen with blinking cursor) but webUI success
    • 6.9.2 (UEFI + Static) = NO GUI (black screen with blinking cursor) but webUI success (sluggish)
    Edited by Kudagra
    Link to comment
    Kudagra

    I manually updated my main server to 6.10.0 rc-1 by copying over the "bz" files (there was no option to upgrade in the UI), and then replaced the network.cfg with that from the fresh "6.10.0 rc-1 (UEFI + Static)" install.

     

    Now I can no longer access github (fix common problems scan) nor the community applications store. I've tried adjusting the DNS servers to no avail, and I'm seeing errors like-

    • nginx: ..... [error] 12411#12411: *4229 upstream timed out (110: Connection timed out) while reading response header from upstream, client: ....
    • Error: Unable to communicate with GitHub.com
    • Download to appfeed failed

     

     

    command.center-diagnostics-20210915-1529.zip

    Link to comment
    Squid

    I'd try a different ethernet cable / port on the switch.  just to see if it makes a difference.  While it doesn't mean much in and by itself, but you receive errors are ~75% on the packets

    Link to comment
    Kudagra
    On 9/15/2021 at 4:09 PM, Squid said:

    I'd try a different ethernet cable / port on the switch.  just to see if it makes a difference.  While it doesn't mean much in and by itself, but you receive errors are ~75% on the packets

    Thanks for the tip. Randomly enough, it looks like my UPS (network port) is causing the recent issues with connectivity to github and whatnot. I tried a couple different cables, but the only way for me to get a stable connection now is by bypassing the UPS's Ethernet port all together? My mobo's Intel LAN port doesn't play well with my UPS port, but the Realtek LAN port works fine with it... Odd.

     

    I'm still having the same original issues listed in the OP, though (slow dockers, VM network connection issues, ect..).

    command.center-diagnostics-20210916-1350.zip

    Edited by Kudagra
    Link to comment
    Kudagra

    Changed Status to Solved

     

    I've resolved all issues listed in the OP. Tested successfully in both 6.9.2 and 6.10.0 rc-1.

     

    I'm not sure what exact setting did it, but after tinkering more and more in the network settings, I managed to strike gold after adjusting "Bonding" and "Interface Rules" enough times. Something to do with within those areas was fine prior to 6.8.3 and below, but wasn't 100% compatible with 6.9.x and above.

    command.center-diagnostics-20210916-1350.zip

    Edited by Kudagra
    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.

×
×
  • Create New...