July 30, 20214 yr my server is called tower. I have a dns entry for it, and had a nginx Proxy host set up for it. I was seeing the same thing. I got rid of the tower proxy host, created a proxy host for "unraid" and a coresponding dns entry.....I did this around midnight last night and haven't seen a single Exited on signal 6 all day. I've also had many tabs open to my unraid dns and a whole bunch, maybe ALL of the docker containers i created proxys for. i'm not sure WHY that'd fix it....but it seems to have worked for me. I also posted about it here: but wanted to suggest it in both threads i found when trying to troubleshoot the issue. I'd love to hear if that helps for other people....
November 11, 20214 yr Looks like nobody's reported this issue for a while, but I've been experiencing random kernel panics that I think may be related to this issue still. I did get the spamming to stop in my syslog by killing all open unraid gui tabs. I am using the NGINX proxy manager docker container. I'm not sure if/how that's related to any of this. Anyone seen a resolution for this anywhere or are we all still trying to figure it out? Edited November 11, 20214 yr by knalbone
December 5, 20214 yr Issue seems to still be present in 6.10.0-rc2. Closed some old UNRAID tabs (that were open before restarting the machine) and the spamming stopped.
January 6, 20224 yr can also report to have this. Just found out and still looking for things to try.
February 14, 20233 yr I have this as well. It hangs my server when the log fills up. Feb 14 05:28:59 Ovi nginx: 2023/02/14 05:28:59 [alert] 5828#5828: worker process 45411 exited on signal 6
May 12, 20233 yr Yeah it's still happening on the latest version 6.11.5. I think some of us really need to push this issue and ask Unraid to drop nchan which is what is causing this error. It's been happening now for at least 3 years... I'm quite certain this is what caused some serious instability for me in previous versions of Unraid where my log would fill up and crash my entire server like many other people were reporting. I just had no idea why or where this problem was. As it's an issue specifically with Unraid and not with some Docker container, I really think it needs more eyes on it.
May 31, 20233 yr On 5/12/2023 at 2:53 PM, plantsandbinary said: Yeah it's still happening on the latest version 6.11.5. I think some of us really need to push this issue and ask Unraid to drop nchan which is what is causing this error. It's been happening now for at least 3 years... I'm quite certain this is what caused some serious instability for me in previous versions of Unraid where my log would fill up and crash my entire server like many other people were reporting. I just had no idea why or where this problem was. As it's an issue specifically with Unraid and not with some Docker container, I really think it needs more eyes on it. I would also like to understand at a higher level, why unraid fails so badly when logs fill up. Ideally logrotate or something should kick in rather than the server locking up.
May 31, 20233 yr 2 hours ago, jbrukardt said: I would also like to understand at a higher level, why unraid fails so badly when logs fill up. Ideally logrotate or something should kick in rather than the server locking up. Agreed.
July 19, 20241 yr all these years later the bug is still there. how is it the price of this software goes up but the quality remains so poor?
October 7, 20241 yr Same problem, Logs fill with nginx errors nginx: DATE/TIME [alert] 5828#5828: worker process ***** exited on signal 6 (one every two seconds) Eventually GUI becomes less responsive, stops responding requires a reboot every week or so. I've seen this discussed in several places on this forum but never a solution, just workarounds.
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.