[6.12.0 Release Maxing out Ram & CPU]

Changed Status to Open

Changed Priority to Minor

[6.12.0 Release Maxing out Ram & CPU]

I think I have found the culprit: shinobipro docker!

even now I have rolled back still having issues with it pinning my cpu at 100% and using 100% of remaining RAM up. stopped it for now and its back ticking over at 6% CPU with all the rest of my dockers running

[6.12.0 Release Maxing out Ram & CPU]

7 hours ago, mindogas said:

Same issue: high CPU usage and practically unresponsive Web UI during docker or VM install. Htop shows then my Windows server 2019 WM uses most of CPU, but its idling inside. Docker containers uses same part of resources. 

tower-diagnostics-20230618-1005.zip

This is mora than annoying. now I have rolled back ti the earlier version, its happening again! knew I should have left it as it was and not upgraded 

[6.12.0 Release Maxing out Ram & CPU]

Anyway I've given up for now and rolled back to the previous unread version. If anyone can give me a heads up I will give e it another try

[6.12.0 Release Maxing out Ram & CPU]

24 minutes ago, ljm42 said:

Please upload the full diagnostics.zip file rather than individual files

how do you do that? when I download the diagnostics, if I drag and drop the folder. the above happens. All the individual files upload ?

[6.12.0 Release Maxing out Ram & CPU]

Well I stoped docker service, updated to 6.12.0

rebooted. locked up again everything maxed out. managed to stop parity check after a while and disabled docker service again, re-started it and turned on the dockers 1 by 1......

 

Still the same, ok for a few mins the maxes out and becomes unresponsive. Take about a min or so just to load up a GUI page??? HELP lol

domain.cfg flash.cfg secondcache.cfg cache.cfg docker.cfg smb-extra.conf editor.cfg super.dat ident.cfg share.cfg network.cfg go.txt disk.cfg listen.txt vfio-pci.cfg CT240BX500SSD1_2112E58E4145-diagnostics-20230616 cache (sdf).txt WDC_WD6003FFBX-68MU3N0_V9HZT1TL-diagnostics-20230616 disk1 (sdc).txt WDC_WD6003FRYZ-01F0DB0_V9H5ED0L-diagnostics-20230616 disk2 (sdd).txt ST1000NM0033-9ZM173_Z1W1G2M3-diagnostics-20230616 (sdg).txt V_Series_SATA_SSD_240GB_190810026401791-diagnostics-20230616 secondcache (sdi).txt ST2000VM003-1ET164_W5204F4D-diagnostics-20230616 disk4 (sdh).txt WDC_WD6003FFBX-68MU3N0_V9HZG6EL-diagnostics-20230616 disk3 (sde).txt WDC_WD141KRYZ-01C66B0_Y6H2ZLAC-diagnostics-20230616 disk5 (sdj).txt WDC_WD141KRYZ-01C66B0_Y6H31WAC-diagnostics-20230616 parity (sdb).txt SanDisk_Ultra_Fit_4C530001301226106482-0-0-diagnostics-20230616 flash (sda).txt cmdline.txt btrfs-usage.txt drm.txt unraid-api.txt plugins.txt motherboard.txt iommu_groups.txt ethtool.txt folders.txt lsmod.txt lsscsi.txt thirdparty_packages.txt loads.txt testparm.txt memory.txt lspci.txt zfs-info.txt meminfo.txt lsusb.txt urls.txt top.txt ps.txt vars.txt lscpu.txt lsof.txt df.txt ifconfig.txt dhcplog.txt docker.txt wg-quick.txt syslog.txt unraid-6.12.0.txt appdata.cfg T----------------------k.cfg M---a.cfg d-----s.cfg tv.cfg i--------e.cfg l-------t.cfg D-----------s.cfg A------V.cfg isos.cfg h--------------s.cfg O-----------------s.cfg f---s.cfg A---------s.cfg system.cfg d----r.cfg b---s.cfg G---------p.cfg d--a.cfg shareDisks.txt K-----V.cfg b------c.cfg d-------s.cfg s------e.cfg g-------e.cfg g---------------e.cfg L----------------p.cfg K--------s.cfg l--------------e.cfg b-----n.cfg T-------s.cfg P---------------r.cfg

[6.12.0 Release Maxing out Ram & CPU]

I will later on. I have rolled back at moment and served people are watching Plex in the house so will try that later and report back thanks 

[6.12.0 Release Maxing out Ram & CPU]

Thanks for the reply.

 

I turned all dockers off, still really high cpu usage compered to normal when all dockers on. Or is that not the same thing?