February 9, 20242 yr I think this may be the cause of some other issues. The steps were, I was going to reassign one of my cache pool drives, stopped array, decided not to and then restarted the array and Fix Common Problems caught OOM error. Diagnostics attached, please help! tower-diagnostics-20240209-1143.zip
February 9, 20242 yr Community Expert 11 minutes ago, heppy said: attached, please help! It happened back on the 5th and the reaper killed Plex's DLNA server - if it happens again look for the process it killed and start from there (fix the configuration, limit the containers allowed memory etc.) Feb 5 11:05:25 Tower kernel: oom-kill:constraint=CONSTRAINT_NONE,nodemask=(null),cpuset=13dc51434939c086b93a15dee381a8eb0637c5dcb2ed94866efc8c7fbebc0eba,mems_allowed=0,global_oom,task_memcg=/docker/31eeb4a9239178cb651112815262fab86c3a64c9ad5750805a77ec668d3bb3ba,task=Plex DLNA Serve,pid=29993,uid=99 Feb 5 11:05:25 Tower kernel: Out of memory: Killed process 29993 (Plex DLNA Serve) total-vm:14685364kB, anon-rss:11423304kB, file-rss:0kB, shmem-rss:0kB, UID:99 pgtables:24164kB oom_score_adj:0
February 24, 20242 yr Author Solution To close this out, I turned off Plex’s DLNA option and the problem hasn’t reoccurred so the issue must be with Plex.
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.