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