Eddie Seelke

Hi all, I have Unmanic running on two machines. 1. My NAS which is what runs everything. It is an i5 with 16GB of RAM. I started Unmanic with the flag to not use more than 50% CPU and only enabled two workers. When I woke this morning, my server was completely unresponsive and none of the apps were accessible. I was able to access it via terminal and killall ffmpeg processes. The weird thing is that even though I only had two workers enabled in Unmanic, there were 17 running ffmpeg processes running. Once I killed them the server and other apps came back up. Since I had to kill this, I have no logs for it. 2. I have a Dell Poweredge server with a Xeon CPU and 16GB of ram. This server does not belong to me, so I am just using it to convert my media. It is running a trial of Unraid with only two apps running. Resilio Sync and Unmanic. I have synced my entire 10TB media library to it. I have Unmanic pointed to the library. It has been running a few days without issue and then syncing the changed files to server 1 above. Yesterday morning I noticed that I could no longer access the webui. In Unraid, I could see CPU was at 100% until I stopped Unmanic. After restarting I could access the webui again. I noticed all 5 workers start working and could see progress. After a short while the webui was no longer accessible. I let it run overnight and event though the CPU stayed at 100%, it seems no media files were updated. I did disable watcher on both systems, but it didn't make any difference.I tried reducing workers to 1, but still having same issues. Here is the log from server 2. Running Unmanic from installed module Starting migrations There is nothing to migrate UnmanicLogger - SETUP LOGGER Clearing cache path - /tmp/unmanic/unmanic_file_conversion-1618327767.4300964 Traceback (most recent call last): File "/usr/local/bin/unmanic", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 396, in main service.run() File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 359, in run self.start_threads(settings) File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 306, in start_threads common.clean_files_in_dir(settings.get_cache_path()) File "/usr/local/lib/python3.8/dist-packages/unmanic/libs/common.py", line 119, in clean_files_in_dir shutil.rmtree(root) File "/usr/lib/python3.8/shutil.py", line 719, in rmtree onerror(os.rmdir, path, sys.exc_info()) File "/usr/lib/python3.8/shutil.py", line 717, in rmtree os.rmdir(path) OSError: [Errno 39] Directory not empty: '/tmp/unmanic/unmanic_file_conversion-1618327767.4300964' Running Unmanic from installed module Starting migrations There is nothing to migrate UnmanicLogger - SETUP LOGGER Clearing cache path - /tmp/unmanic/unmanic_file_conversion-1618327767.4300964 Traceback (most recent call last): File "/usr/local/bin/unmanic", line 8, in <module> sys.exit(main()) File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 396, in main service.run() File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 359, in run self.start_threads(settings) File "/usr/local/lib/python3.8/dist-packages/unmanic/service.py", line 306, in start_threads common.clean_files_in_dir(settings.get_cache_path()) File "/usr/local/lib/python3.8/dist-packages/unmanic/libs/common.py", line 119, in clean_files_in_dir shutil.rmtree(root) File "/usr/lib/python3.8/shutil.py", line 719, in rmtree onerror(os.rmdir, path, sys.exc_info()) File "/usr/lib/python3.8/shutil.py", line 717, in rmtree os.rmdir(path) OSError: [Errno 39] Directory not empty: '/tmp/unmanic/unmanic_file_conversion-1618327767.4300964' I also tried changing the repository to staging, but still having same issues. Not sure what to check for next.