Done Package unrar is not available, but is referred to by another package. Bug fix in 1.2.2 Windows: job-directory incorrectly passed to PostProcessing-script Whats new in 1.2. I've been trying to find a way to install SAB directly on my Pi without Docker, but perhaps that's overlooking the bigger question - Is there something wrong with my docker? is there something I can do to tweak docker to have similar performance to installing it directly on the system? I've seen people complain about a 2MB/s difference, but this is 4x faster without docker. And when I try and install unrar I get: sudo apt install unrar Reading package lists. Windows: Fix hanging Unrar Windows: Unzip was not working Windows: Incomplete folders would sometimes end in a dot Starting with '-w' parameter would fail Unblock Server button did not work Changes for v1.2.0 - v1.2.2. So clearly using docker is causing HUGE performance differences. Reran the test a few times and averaged over 40MB/s. Laptop Windows 10 Without Docker Speed Test Just running docker-compose stop sabnzbd had no effect. Maybe higher nice value to unrar process (being more friendly to other processes) might leave some air for it to pass the stopping command to the sabnzbd process. At least as far as Internet Bandwidth:įinally, I decided to install SABnzbd directly on my laptop, and these were the results. I also noticed in situation one that sabnzbd docker wasnt able to stop properly. ![]() Much to my surprise I got very similar results. I decided to install docker on my (gaming) laptop and try running it there. I'm capped at about 10MBs here which seems insanely low. I know I'm going bottlenecked by my read/write speed here, but bear with me. I'm currently running SAB in Docker in a Raspi 3 b+. We will probably ask you to do a test using only basic settings. Do you experience problems during downloading Check your connection in Status and Interface settings window. I simply had to flush the docker to make it stop.So I've seen similar issues posted here there and everywhere but they all seem to be much less extreme than mine, and also without any real resolution?įor starters, my internet provides up to 700Mbs download. Are you using the latest stable version of SABnzbd Downloads page. Just running 'docker-compose stop sabnzbd' had no effect. I have never see this bevor on other versions. I use latest SABnzbd-3.1.0Beta1 and always whene i start a download i get a DOS Windows from urar.exe. I also noticed in situation one that sabnzbd docker wasn't able to stop properly. SABnzbd-3.1.0Beta1 open always unrar window. Open Couch Potato, click the cog wheel, click the Renaming option. Couch Potato files could face the same issue, and as seen with Sick Beard, it’s just a matter of a setting. What isn't explained is why during the unrar process sabnzbd warns about "Unable to stop the unrar process." during this 'normal' routine. That’s all there is to it (under the assumption that you did setup SABnzbd to use the sabToSickBeard.py post processing script (more details in the installation guide). In that situation one could argue it's working as expected. I didn't see any dangling unrar processes after it finished downloading. Though even having quite a lot of time having 100% load the queue ended and finished all tasks. ![]() ![]() Two: 300Gig of queue downloading and creating 8-9 "Unable to stop the unrar process." hourly. I did manage to kill it by for killing it (docker rm -f It will start up since sabnzbd docker is still running and revamping the process. In order to regain control over the disk killing the unrar process isn't enough. This time the queue was still filling up and there seemed to be a lot of IO backlog present. One: 100% disk usage cause by sabnzbd and prolly by sickbeard moving the finished file.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |