So My unraid server has been running like ass for the past few months.

• I'm not able to download diagnostic
• I'm not able to load plugins
• I need to reboot my server once a day or else it locks up
• Dockers and VM work fine during that 24hour period
• the Server still locks up in safe mode, or regular mode with docks and VMs disabled.

 

the only thing I can view is the syslog.

 

and they are spammed with this:
Jan 27 10:19:16 Tower nginx: 2021/01/27 10:19:16 [alert] 4277#4277: worker process 14256 exited on signal 6

Jan 27 10:19:16 Tower nginx: 2021/01/27 10:19:16 [alert] 4277#4277: worker process 14256 exited on signal 6

 

 

What can I do to fix this?

syslog

Edited February 2, 20215 yr by DannyG

I remove 3 or 4 plugins that I've had for a while.

I think ALL my issues were resolved after I removed them. no more rebooting my server every 24 hours. no more GUI SLOWNESS where certain pages take forever to load.

 

I'm sorry to say that I don't recall which plugins were at fault. I think it was like "folder cache" it's been too long now, I don't recall.

found this https://futurestud.io/tutorials/nginx-solve-reponse-status-0-worker-process-exited

I was having this issue now for quite a while. and could not figure out why that message spammed so often in the logs. 

and it seems it got worse everytime I tried to debug it.. with several logs entries per second.

 

restarting the web gui (nginx), the docker daemon, the whole array or even a reboot did not fix this.

 

turns out that I had open the web gui several times, in different browser, locally, on the phone etc. once some kind of error state happens (in my case a full syslog partition), any open websocket (used to show e.g. current cpu load, docker state etc.) would close. and any request to reopen them would trigger such a message (as it misses some context data in the request as described in the article). the problem is, that this reconnect seems to happen constantly, even if you just have the page open somewhere in the browser.

once I closed all browser session the logs stopped. opening the page again seems to properly initialize it and the GUI is finally working.

hope this helps someone.

 

On 11/5/2024 at 1:02 PM, h4de5 said:

I was having this issue now for quite a while. and could not figure out why that message spammed so often in the logs. 

and it seems it got worse everytime I tried to debug it.. with several logs entries per second.

 

restarting the web gui (nginx), the docker daemon, the whole array or even a reboot did not fix this.

 

turns out that I had open the web gui several times, in different browser, locally, on the phone etc. once some kind of error state happens (in my case a full syslog partition), any open websocket (used to show e.g. current cpu load, docker state etc.) would close. and any request to reopen them would trigger such a message (as it misses some context data in the request as described in the article). the problem is, that this reconnect seems to happen constantly, even if you just have the page open somewhere in the browser.

once I closed all browser session the logs stopped. opening the page again seems to properly initialize it and the GUI is finally working.

hope this helps someone.

 

Thanks from the future - your response held the key to fixing my issue.