March 2, 20251 yr Hello everyone I've had the problem for a while that my server becomes extremely sluggish after a certain amount of time. It can take a week or 2-3 weeks for it to occur. Last Thursday, February 27, 2025, it happened again. I could no longer access Docker or a VM. The WebUI could no longer be accessed either. Nothing worked via SSH either. Everything I tried seemed as if it was still there but the server was completely overloaded, so that at some point it would time out. The HDDs were all off according to my girlfriend (i wasn't at home) and the server couldn't be turned off using the power button. So the only option was to kill the server. I've had this problem about 4 times now, although I was still able to access the WebUI somehow and restart the server properly. I had this problem once before with 6.12.14. I thought the problem might be solved with 7.0.0 but unfortunately not. Unfortunately I couldn't find anything in the logs either, as some of them get lost when you restart? Anyway, I've attached the logs. Does anyone know the problem or can help me? tower-diagnostics-20250302-2217.zip Edited March 2, 20251 yr by swiss01
March 3, 20251 yr Author thank you. then we'll wait until the server crashes next time I'll get back in a few weeks
March 26, 20251 yr Author Good evening. It's that time again. After a good 15 days and 7 hours, I can still access the web GUI, but I have to wait about 30-60 seconds each time for the page to load. It's especially slow when I switch tabs in the menu, but it's still OK. I then turned off the VM Manager. Since then, it's been running smoothly again. Only now I can't turn on the VM Manager anymore. I then turned off the Dockers, and I can start them again. Okay, now things are getting weird. I wanted to restart the server and went back to the VM tab. They're running again. The VM Manager started again after I turned off the Dockers. Well, I'll restart the server, then hopefully I'll have another 15 days of peace. Below is the diagnostic data. tower-diagnostics-20250326-2140.zip
March 27, 20251 yr Community Expert Mar 26 20:21:28 Tower php-fpm[10501]: [WARNING] [pool www] child 4031488 exited on signal 9 (SIGKILL) after 13.435677 seconds from start Mar 26 20:21:45 Tower php-fpm[10501]: [WARNING] [pool www] child 3959795 exited on signal 9 (SIGKILL) after 802.828075 seconds from start Mar 26 20:21:50 Tower php-fpm[10501]: [WARNING] [pool www] child 4031491 exited on signal 9 (SIGKILL) after 32.864403 seconds from start In 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-down
March 29, 20251 yr Author Thanks for your reply. I just implemented the excessive-flash-drive-activity-slows-the-system-down thing. Today, two days after a reboot, I had the problem again. I was just able to restart the server normally. Shutting down Docker or the VM didn't help this time. I couldn't download the diagnostics. The syslogs were flooded, even when Docker and the VM Manager were shut down. These few lines were written repeatedly. The syslog is now larger than 100MB and only contains data from March 14-29, 2025. Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [alert] 1980817#1980817: *827646 header already sent while keepalive, client: 192.168.1.10, server: 192.168.1.21:443 Mar 29 18:56:31 Tower kernel: nginx[1980817]: segfault at 0 ip 0000000000000000 sp 00007ffe4356a588 error 14 in nginx[400000+24000] likely on CPU 2 (core 4, socket 0) Mar 29 18:56:31 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [alert] 10793#10793: worker process 1980817 exited on signal 11 Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [crit] 1980818#1980818: ngx_slab_alloc() failed: no memory Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [error] 1980818#1980818: shpool alloc failed Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [error] 1980818#1980818: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserved_memory. Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [alert] 1980818#1980818: *827649 header already sent while keepalive, client: 192.168.1.10, server: 192.168.1.21:443 Mar 29 18:56:31 Tower kernel: nginx[1980818]: segfault at 0 ip 0000000000000000 sp 00007ffe4356a588 error 14 in nginx[400000+24000] likely on CPU 2 (core 4, socket 0) Mar 29 18:56:31 Tower kernel: Code: Unable to access opcode bytes at 0xffffffffffffffd6. Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [alert] 10793#10793: worker process 1980818 exited on signal 11 Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [crit] 1980819#1980819: ngx_slab_alloc() failed: no memory Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [error] 1980819#1980819: shpool alloc failed Mar 29 18:56:31 Tower nginx: 2025/03/29 18:56:31 [error] 1980819#1980819: nchan: Out of shared memory while allocating channel m/ I have 32 GB of RAM, and it should work. Memtest ran for a good 18 hours without any errors. Latest BIOS installed, and the CPU is oversized. My System Title Information System Overview Unraid system: Unraid server Pro, version 7.0.1 Model: Custom Motherboard: ASUSTeK COMPUTER INC. TUF GAMING B760M-PLUS, Version: Rev 1.xx, s/n: 230926644903196 Processor: Intel® Core™ i5-14500 @ 2574 MHz HVM: Enabled IOMMU: Enabled Cache: L1 Cache = 288 KiB (max. capacity 288 KiB) L1 Cache = 192 KiB (max. capacity 192 KiB) L2 Cache = 7680 KiB (max. capacity 7680 KiB) L3 Cache = 24 MiB (max. capacity 24 MiB) L1 Cache = 256 KiB (max. capacity 256 KiB) L1 Cache = 512 KiB (max. capacity 512 KiB) L2 Cache = 4 MiB (max. capacity 4 MiB) L3 Cache = 24 MiB (max. capacity 24 MiB) Memory: 32 GiB DDR5 (max. installable capacity 256 GiB) Controller0-DIMM1: Corsair CMK32GX5M2X7200C34, 16 GiB DDR5 @ 4800 MT/s Controller1-DIMM1: Corsair CMK32GX5M2X7200C34, 16 GiB DDR5 @ 4800 MT/s Network: eth0: 1000 Mbps, full duplex, mtu 1500 Kernel: Linux 6.6.78-Unraid x86_64 OpenSSL: 3.4.1 P + Q algorithm: 25872 MB/s + 46949 MB/s
March 30, 20251 yr Community Expert 11 hours ago, swiss01 said: nchan: Out of shared memory while allocating channel /dockerload. Increase nchan_max_reserved_memory. This is a separate but related issue, you can try updating to 7.1.0-beta.2, there's a change there that may help with these.
May 6, 20251 yr Author On 3/30/2025 at 11:26 AM, JorgeB said: This is a separate but related issue, you can try updating to 7.1.0-beta.2, there's a change there that may help with these. Thank you very much, I have 7.1.0-beta.3 installed and have had no problems for 29 days. In a week the 7.1.0 will be installed 🙂
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.