Emby Docker Causing Extreme Latency

[Netbug]

UnRAID 6.9.2

 

Issue: Starting earlier today, all of a sudden my unRAID system has been causing extreme latency and packet loss on my network. After a little trial and error, I've determined that this is being caused by the EmbyServer docker. When I stop this docker, my network traffic returns to normal.

 

I've never had an issue like this before. I use Emby daily and it is quite important to me.

 

I'm not quite sure how to go about troubleshooting this.

 

As soon as I start the docker, the network goes bananas. I've attached some screenshots.

 

Any ideas where I can start troubleshooting this? If I need to troubleshoot with Emby support, I can try that.

 

Please advise.

 

Dockers:

• binhex-radarr4k
• binhex-sabnzbd
• mylar3
• radarr
• binhex-sonarr
• EmbyServer

 

Plugins:

• CA Auto Update Applications
• CA BAckup / Restore Appdata
• CA Cleanup Appdata
• Community Applications
• Dynamix S3 Sleep
• Dynamix SSD Trim
• Synamix System Information
• Fix Common Problems
• Nerd Tools
• Open Files
• Unassigned Devices
• Unraid Nvidia
• User Scripts

 

Hardware:

• Case: Lian-Li PC-A77F
• Motherboard: SuperMicro X9SCM-F
• Processor: Intel Core i3-2120 Sandy Bridge Dual-Core 3.3 GHz LGA 1155
• RAM: Kingston 8GB
• SATA Extender: Supermicro AOC-SASLP-MV8 SATA Extender
• Hot-swap Bays: SuperMicro CSE-M35T-1B (x 2)
• Power Supply: CORSAIR Enthusiast Series TX750M
• USB (unRAID): Lexar JD Firefly 8GB

 

Drives:

• Parity    WDC_WD80EFAX-68KNBN0_VDHBX7VD - 8 TB (sdb)
• Disk 1    WDC_WD20EADS-00R6B0_WD-WCAVY5374796 - 2 TB (sdf)
• Disk 2    WDC_WD30EZRX-19D8PB0_WD-WMC4N0J7D8TT - 3 TB (sdd)
• Disk 3    WDC_WD20EARS-00MVWB0_WD-WCAZA9034298 - 2 TB (sde)
• Disk 4    WDC_WD80EFAX-68KNBN0_VDH2MGVD - 8 TB (sdh)
• Disk 5    ST4000DM005-2DP166_WGY0E53A - 4 TB (sdj)
• Disk 6    ST3000DM001-1CH166_W1F23145 - 3 TB (sdm)
• Disk 7    WDC_WD30EZRX-00SPEB0_WD-WCC4E0NP7NLR - 3 TB (sdl)
• Disk 8    ST8000DM004-2CX188_ZR128XVM - 8 TB (sdk)
• Disk 9    ST4000DM005-2DP166_WDH2S61F - 4 TB (sdg)
• Disk 10    ST4000DM004-2CV104_ZFN0BNMN - 4 TB (sdi)
• Disk 11    ST8000DM004-2CX188_ZCT3VH40 - 8 TB (sdc)    
• Cache INTEL_SSDPEKNW512G8_PHNH929303YD512A - 512 GB (nvme0n1)
• Flash JD_FireFly - 8 GB (sda)

tower-diagnostics-20220405-2056.zip

[Netbug]

So I reinstalled the docker last weekend and the issue went away.

 

All of a sudden when I got home today, it had started again. This leads me to believe there is some automated process that is running that is causing the issue. Any suggestions as to how to look for it?

 

Updated log attached.

tower-diagnostics-20220410-1700.zip

[ChatNoir]

Are there tasks that run in Emby on regular interval that could cause this ?  (full library scan, metadata update, etc ?)

[Netbug]

Thanks so much for the reply. That's what I've been trying to figure out. The "scheduled tasks" area of the Emby settings is not very helpful, unfortunately.

 

What's really odd is that it seems to be completely outbound traffic according to what I'm seeing on the unRAID dashboard.

 

I'm also attaching the emby logs here. Not sure if anybody knows how to interpret them.

 

Here's what it shows when the emby docker is running:

 

And here it is with the docker stopped:

embyserver.txt hardware_detection-63785207120.txt

[Netbug]

Issue seems to have been resolved by disabling DLNA in the Emby settings.