Hello. I am trying to get to the bottom of why this is happening but having trouble deciphering the logs. Any help would be greatly appreciated!

 

 

 

tower-syslog-20220112-1820.zip

attach diagnostics to your NEXT post in this thread

Here it is. I knew I was forgetting something. Thank you.

tower-diagnostics-20220112-1112.zip

Looks like python getting OOMed. What are you using that for?

That's why I am confused. I'm nut sure what is using python. Midnight Commander has been locking up at times. Here is the docker containers I'm running if there is a clue there.

 

So, I am pretty sure it is being caused by SABnzbd. Does that track with the log file and diagnostic? If I stop the container my ram and cpu utilization return to normal. Any ideas why this just started happening? 

SAB does use python. Is yours up-to-date?

 

Post docker run for that

Yes. It is up to date. I uninstalled and started a fresh installation and am having the same problem.

 

Here is the docker run:

 

root@localhost:# /usr/local/emhttp/plugins/dynamix.docker.manager/scripts/docker create --name='sabnzbd' --net='bridge' -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e 'PUID'='99' -e 'PGID'='100' -e 'UMASK'='022' -p '8080:8080/tcp' -v '/mnt/user/Media/Downloads/Complete/':'/downloads':'rw' -v '/mnt/user/Media/Downloads/Incomplete/':'/incomplete-downloads':'rw' -v '/mnt/user/Media/Laptop Downloads/':'/watchfolder':'rw' -v '/mnt/user/appdata/sabnzbd':'/config':'rw' 'lscr.io/linuxserver/sabnzbd'

e246a13cf8f9508d1624cd947fae3d3d460e7d135d54ee3bfcb46d502293bfe9

The command finished successfully!

 

 

 

One thing I notice is the Media share is configured to Use Cache=Yes, but does not seem to have the pool to use for caching specified.   Not sure if if it is the cause of the problem but that seems a bit strange to me.

I figured it out. There was some kind of file in my watch folder that SAB was trying to load. Cleared my watch folder and problem gone.