Eddie Seelke

Members
  • Posts

    12
  • Joined

  • Last visited

Eddie Seelke's Achievements

Newbie

Newbie (1/14)

1

Reputation

  1. No, I have to use a specific IP for this service and using a VLAN would change it. Well, I don't have to, but it would be too much work to change it. lol
  2. I have been having this issue as well. I do have one docker that is using br0, but unfortunately I cannot move it to a VLAN. Is there any other way to fix this? Or is there an update on when a permanent fix will be out?
  3. I had the same exact issue and after several weeks of trying to get it working I came across Tdarr. It's not as easy to setup, but hasn't crashed my system once. Not trying to knock Unmanic. Just saying there are other options.
  4. Is it because I don't have GPU that Unmanic does not work?
  5. Right after I posted last message, I changed the container to use the staging image. I didn't make any other changes. The webui will come up, but it will not scan for media. I even tried changing the option to scan on start and then restarted container, but still no scans.
  6. Ok, I started over completely from scratch. I created a new USB drive of Unraid 6.9.1. I setup the transcode share as requested above and installed only two docker apps, Resilio-Sync and Unmanic. I only started Resilio Sync until it synced all of my movies back over. This took almost 5 days. After sync finished, I started Unmanic at 12:42PM. I then accessed the webui and clicked on Rescan. It started three workers. One minute later I could no longer access webui. Right before webui stopped working I could see a process called unmanic in the screenshot above.
  7. Ok, I deleted everything and started completely over. I created a share called transcode and chose Only for cache. I used all default settings except I did add "--cpus='.5'" under Extra Parameters. Unfortunately, it gave the same results as before. After a few minutes entire server became unresponsive and I had to kill all ffmpeg processes to get back to it. On the temp server, I also deleted everything, created a share called transcode (No cache in this server), and used only default settings. I hit scan in Unmanic. It started, but after a few minutes I could no longer access webui. I was trying to think of what may have changed as this did work a few days. I am thinking it stopped working when I upgraded Unraid to version 6.9.2. In fact, that's the only thing that changed on the temp server. I am downgrading the temp server and will post back the results. Thank you for your help!
  8. I didn't create a share. I created a folder called .unmanic in /mnt/user using putty. The path is now /mnt/user/.unmanic/cache.
  9. Ok, I made that change on my main server and everything became unresponsive after 10 minutes. Even Plex stopped working until I stopped Unamnic. I also changed this servers extra parameters to "--cpus='.25'", but it still crashed. I made your suggested change on the temp server as well. After about 5 minutes I could no longer access the webui. I then added the extra parameter of "--cpus='.9'" to this server and restarted. I still lost access to the webui after a few minutes. Am I doing something wrong? This worked for several days straight and then all of a sudden stopped working a couple of days ago. I may have added more apps to my main server, but I made no changes whatsoever on the temp server other than what was asked for here today.
  10. 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.