tjsyl

So far I've went down a rabbit hole and found the PLEX DB had some errors.   Full rebuild of the Plex DB via (https://www.reddit.com/r/PleX/comments/z7i4va/repair_a_corrupted_database_on_unraid_updated/) this helpful guide, I couldn't get ChuckPaPlex's script to play nice with UR, I think I may have been executing it from the wrong directory.  After manual full repair I am 80% through the parity check and no issues.

Just kidding. I was checking on it as I was typing this and I see something is running a muck on the RAM (98% of 160GB).  I had UNMANIC set to use the ramdisk long ago, (/tmp/xxxxxx) but I am 99% sure when I added the 4- 1TB ssd's (4-6 months ago?) changed it to one of the 2, 2TB cache pools I have set up.  I noticed Unmanic running out of space on very large Linux ISO's.   
 
I had the syslog writing to my other UR server and it looked useless, after working on some stuff for work I came back to it and noticed the server was responsive and it had the syslog had jumped from 14kb to 80+kb.  Apparently Unmanic was running a muck.  It would seem I don't have enough patients to wait it out the last few times this happened and took action before UR fixed itself.  For now I shut down Unmanic and disabled autostart, will try to see what's going on with that container.  Maybe move it to another server. 
 
Anything else helpful in this log?  I know exactly what the "smb_panic" was about.   I also omitted a few things *****.  Not sure why the tab open in chrome on my phone feels the need to log back in every 15 minutes but, meh..    I think all is well now but let me know if anything looks strange please.  I will disable writing the syslog to the flash drive for now but keep it mirrored to my other UR server.
 

syslog-10.xxx.xxx.xxx.log

Rebooting solved this issue.