Yesterday my server became unresponsive and I thought it was related to 7.0.0.  Looking through my logs I can see I was getting

 

Jan 13 07:46:16 Tower php-fpm[9270]: [WARNING] [pool www] child 1928487 exited on signal 9 (SIGKILL) after 12.167421 seconds from start

 

Then some time between 13:30 and 13:40 the server became unresponsive and there is a bunch of additional errors in that time.  Does anyone know what the root cause for these errors is?

 

tower-diagnostics-20250113-1339.zip

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

I’m facing a similar issue and wanted to add my experience.

 

- I’ve also encountered frequent SIGKILL messages, even before version 7.0.

- I only keep one browser tab open for the GUI and tried downloading diagnostics, but the process gets stuck—this has happened multiple times.

- I checked for memory issues since SIGKILL is often linked to the OOM Killer, but I have 32GB of RAM and consistently about 5GB free when I monitor it.

 

It seems like there’s a common cause here. Have you found any patterns, or has anyone else managed to resolve this? Could there be something other than OOM at play?

 

Here is a part that I could capture; perhaps the other two errors can help identify the cause:

Jan 14 17:31:36 Tower nginx: 2025/01/14 17:31:36 [error] 18812#18812: *7842 open() "/usr/local/emhttp/webGui/javascript/ace/mode-log.js" failed (2: No such file or directory) while sending to client, client: 192.168.178.100, server: , request: "GET /webGui/javascript/ace/mode-log.js HTTP/2.0", host: "192.168.178.24", referrer: "https://192.168.178.24/Docker/Browse?dir=%2Fmnt%2Fbackupssd%2FBackup"
Jan 14 17:31:49 Tower php-fpm[12283]: [WARNING] [pool www] child 139972 exited on signal 9 (SIGKILL) after 24.006957 seconds from start
Jan 14 17:31:49 Tower nginx: 2025/01/14 17:31:49 [crit] 18812#18812: *7842 connect() to unix:/var/run/ttyd.sock failed (2: No such file or directory) while connecting to upstream, client: 192.168.178.100, server: , request: "GET /webterminal/ttyd/ HTTP/2.0", upstream: "http://unix:/var/run/ttyd.sock:/", host: "192.168.178.24", referrer: "https://192.168.178.24/Docker/Browse?dir=%2Fmnt%2Fbackupssd%2FBackup"

192.168.178.24 =  Unraid

192.168.178.100 = VM

Edited January 14, 20251 yr by sNyteX
added ip = XX

Quote

Try booting in safe mode and/or closing any browser windows open to the GUI, only open when you need to use it then close again.

I will try and leave the browser window closed.  It did run fine for about 48 hours.  In the past the window was left open alot and never had an issue.  Is this a known issue with 7?

Now, but it appears to help in some cases, with v6.12 was the same.