7/21/2023 0 Comments Sabnzbd connection refused![]() ![]() System doesn't appear to be doing much, occasionally there's a single core cpu processing. 12:52:31,463::WARNING:: Unwanted Extension in file RARBG_DO_NOT_MIRROR.exe (.264-GGWP-xpost) 21:19:55,497 INFO success: shutdown-script entered RUNNING state, process has stayed up for > than 0 seconds (startsecs) 21:19:55,497 INFO success: sabnzbd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 21:19:54,495 INFO reaped unknown pid 8 (exit status 0) 21:19:54,495 INFO spawned: 'shutdown-script' with pid 66 21:19:53,490 INFO supervisord started with pid 7 21:19:53,482 INFO Set uid to user 0 succeeded 21:19:53,482 INFO Included extra file "/etc/supervisor/conf.d/nf" during parsing :/mnt/cache/downloads/sabnzbd/movies/completes# df -hįilesystem Size Used Avail Use% Mounted onĬgroup_root 8.0M 0 8.0M 0% /sys/fs/cgroup Both the download disk and the cache disk are Samsung SSD EVO. My setup is on two disks outside of the array, so caching shouldn't be playing into it. ![]() ![]() It very slowly processes but based on those times, some of the unrar actions are over 12hrs? I set off a colossal amount of downloads so everything is stuck direct unpacking, unraring and post-processing. Unrar has always been quite slow, but this seems to be taking the mickey a bit. :/mnt/cache/downloads/sabnzbd/movies/completes# date :/mnt/cache/downloads/sabnzbd/movies/completes# ps -ef | grep unrar I have some unrar actions that seem to be incredibly slow: I'm being hit by incredibly slow unrar performance. I can do a Force update and those work fine. Of my dockers are no longer able to check for updates and when I chick on the button to Check, they all spin for a long time and then it times out.
0 Comments
Leave a Reply. |