January 16Jan 16 My Unraid system in the past few months has developed a situation whereby if left the GUI becomes very slow and sluggish eventually to the point of being unusable. The only cure I've found thus far is a reboot. if Im lucky I get to logon and reboot cleanly from the GUI (it can take 30minutes between clicking reboot and the system going down) but in recent days Ive had to shutdown from the console which continues to work fine throughoutThis evening I am struggling to do anything in he GUI at all and its looking like I may well have to reboot from the console again, this can't be doing the array any good although they are normally spun down.When I shutdown from the console I use powerdown I see a lot of these warnings every few seconds, but no errors per seJan 16 17:16:32 Tower php-fpm[8834]: [WARNING] [pool www] child 2829636 exited on signal 9 (SIGKILL) after 62.915653 seconds from startWhere do I start, what do you need to help me? I have no idea where to start looking/troubleshooting so any assistance you can give would be really appreciated.Unraid 7.14Unraid OS PlusModel:CustomM/B:Gigabyte Technology Co., Ltd. A520M H Version x.x s/n Default stringBIOS:American Megatrends International, LLC. Version F15 Dated 08/26/2022CPU:AMD Ryzen 5 5500 @ 3600 MHzHVM:EnabledIOMMU:EnabledCache:L1 - Cache: 384 KiB, L2 - Cache: 3 MiB, L3 - Cache: 16 MiBMemory:8 GiB DDR4 (max. installable capacity 128 GiB)Network:bond0: fault-tolerance (active-backup), mtu 1500Kernel:Linux 6.12.24-Unraid x86_64OpenSSL:3.5.0Uptime:14 days, 6 hours, 46 minutes
January 16Jan 16 Community Expert 11 minutes ago, sailingbikeruk said:Jan 16 17:16:32 Tower php-fpm[8834]: [WARNING] [pool www] child 2829636 exited on signal 9 (SIGKILL) after 62.915653 seconds from startIn my experience, these errors can be the result of the server being close to exhausting the memory, GUI can become extremely slow, like 1 minute to open the dashboard, try limiting the memory for VMs/docker services, or adding a little more RAM.It could also be one or more containers hogging the CPU, try pinning only some cores to them, and leave cores 0/1 available for Unraid.Also, recommend trying a couple of other things, go to Settings - Global share settings and set the Number of fuse File Descriptors to the max, and enable this:https://docs.unraid.net/unraid-os/release-notes/7.0.0/#excessive-flash-drive-activity-slows-the-system-downYou can also try running the attached script using the CLI/Tmux, and see if there's any info there when the GUI starts slowing down slowlog
January 31Jan 31 Author Apologies for the very late reply.I don't have any docker or VMs running, i've migrated them to Proxmox on a different host simply because I never really got to understand how they worked in Unraid. Any legacy ones that are still present because they are unraid related like Krusader and vm_custom_icons are all stopped as part of my own troubleshooting.I will have a look at your other suggestions, bizarrely it hasn't happened again since I made this post, after happening regularly for several months.I also now have the Unraid logs coming into Graylog so hopefully I can search these more easily and look for any anomaliesThanks for the response. Edited January 31Jan 31 by sailingbikeruk
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.