I'm after some help with diagnosing my system crashes that have been happening for the last 6 months. It could crash once a month, a week, or 3 days in a row like this week. 

It could crash in the middle of the night while I'm sleeping or while I'm watching something on Emby. 

I've taken a look at the logs and the only thing that stands out to me is FFMPEG, and go2rtc-related that my frigate docker container uses

Here is part of the log where i think the system crashed lastnight - 

 

Oct 17 20:54:58 Shibby-Nas kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=2c568eb912c78d812223dd34b52b55b2b4cbcda1ccf8f929166b80deee2522d1,mems_allowed=0,global_oom,task_memcg=/docker/4127b37ed293a84219ac2f17ff3d9d6149857b597e17c52aa41df9b67e381bf7,task=ffmpeg,pid=8866,uid=0
Oct 17 20:54:58 Shibby-Nas kernel: Out of memory: Killed process 8866 (ffmpeg) total-vm:22441644kB, anon-rss:22063848kB, file-rss:0kB, shmem-rss:0kB, UID:0 pgtables:43376kB oom_score_adj:0
Oct 17 20:55:01 Shibby-Nas kernel: oom_reaper: reaped process 8866 (ffmpeg), now anon-rss:0kB, file-rss:0kB, shmem-rss:0kB
Oct 17 21:37:23 Shibby-Nas emhttpd: spinning down /dev/sdo
Oct 17 21:37:31 Shibby-Nas emhttpd: read SMART /dev/sdo
Oct 17 21:37:33 Shibby-Nas emhttpd: spinning down /dev/sdn
Oct 17 21:37:41 Shibby-Nas emhttpd: read SMART /dev/sdn
Oct 17 22:13:13 Shibby-Nas emhttpd: spinning down /dev/sdb
Oct 17 22:37:32 Shibby-Nas emhttpd: spinning down /dev/sdo
Oct 17 22:37:41 Shibby-Nas emhttpd: read SMART /dev/sdo
Oct 17 22:37:42 Shibby-Nas emhttpd: spinning down /dev/sdn
Oct 17 22:37:51 Shibby-Nas emhttpd: read SMART /dev/sdn
Oct 17 22:38:40 Shibby-Nas kernel: SPICE Worker invoked oom-killer: gfp_mask=0x140cca(GFP_HIGHUSER_MOVABLE|__GFP_COMP), order=0, oom_score_adj=0
Oct 17 22:38:40 Shibby-Nas kernel: CPU: 0 PID: 14428 Comm: SPICE Worker Tainted: P           O       6.1.82-Unraid #1
Oct 17 22:38:40 Shibby-Nas kernel: Hardware name: Dell Inc. PowerEdge T640/0TWW5Y, BIOS 2.20.1 09/14/2023
Oct 17 22:38:40 Shibby-Nas kernel: Call Trace:
Oct 17 22:38:40 Shibby-Nas kernel: <TASK>
Oct 17 22:38:40 Shibby-Nas kernel: dump_stack_lvl+0x44/0x5c
Oct 17 22:38:40 Shibby-Nas kernel: dump_header+0x4a/0x211
Oct 17 22:38:40 Shibby-Nas kernel: oom_kill_process+0x80/0x111
Oct 17 22:38:40 Shibby-Nas kernel: out_of_memory+0x3b3/0x3e5
Oct 17 22:38:40 Shibby-Nas kernel: __alloc_pages_slowpath.constprop.0+0x7cf/0x8de
Oct 17 22:38:40 Shibby-Nas kernel: __alloc_pages+0x132/0x1e8
Oct 17 22:38:40 Shibby-Nas kernel: folio_alloc+0x14/0x35
Oct 17 22:38:40 Shibby-Nas kernel: __filemap_get_folio+0x185/0x213
Oct 17 22:38:40 Shibby-Nas kernel: ? preempt_latency_start+0x1e/0x46
Oct 17 22:38:40 Shibby-Nas kernel: filemap_fault+0x317/0x52f
Oct 17 22:38:40 Shibby-Nas kernel: __do_fault+0x2a/0x6b
Oct 17 22:38:40 Shibby-Nas kernel: __handle_mm_fault+0xa22/0xcf9
Oct 17 22:38:40 Shibby-Nas kernel: ? eventfd_write+0x19e/0x1c7
Oct 17 22:38:40 Shibby-Nas kernel: handle_mm_fault+0x13d/0x20f
Oct 17 22:38:40 Shibby-Nas kernel: do_user_addr_fault+0x2c3/0x48d
Oct 17 22:38:40 Shibby-Nas kernel: exc_page_fault+0xfb/0x11d
Oct 17 22:38:40 Shibby-Nas kernel: asm_exc_page_fault+0x22/0x30
Oct 17 22:38:40 Shibby-Nas kernel: RIP: 0033:0x150ff2a68b30
Oct 17 22:38:40 Shibby-Nas kernel: Code: Unable to access opcode bytes at 0x150ff2a68b06.
Oct 17 22:38:40 Shibby-Nas kernel: RSP: 002b:0000150fa2ffdb88 EFLAGS: 00010246
Oct 17 22:38:40 Shibby-Nas kernel: RAX: 0000000000000000 RBX: 0000150fa2866200 RCX: 0000150fabc73540
Oct 17 22:38:40 Shibby-Nas kernel: RDX: 0000000000000000 RSI: 0000000000000010 RDI: 0000150fa2ffdbf0
Oct 17 22:38:40 Shibby-Nas kernel: RBP: 0000150fac67f4a0 R08: 0000000000000000 R09: 0000000000000300
Oct 17 22:38:40 Shibby-Nas kernel: R10: 00007fff99b1c080 R11: 000000002ec48310 R12: 0000150fa2ffdbf0
Oct 17 22:38:40 Shibby-Nas kernel: R13: 0000000000000000 R14: 0000150fabcad038 R15: 0000150fabcad080
Oct 17 22:38:40 Shibby-Nas kernel: </TASK>
Oct 17 22:38:40 Shibby-Nas kernel: Mem-Info:

Would be great to get some assistance  

shibby-nas-diagnostics-20241018-2127.zip

OOM errors apparently caused by Frigate, limit its RAM usage or check its config.