SABnzbd Forums

Hey guys,
my specs are:
- Ubuntu 20.04
- sabnzbdplus-3.3.1
- Firefox 91.0

Yesterday i rearranged some downloads by using the "push on top" arrow keys, and afterwards i realized the webinterface was frozen with my laptop fan going nuts, which was caused by unrar. I tried to reboot sab and used the repair queue button, it all had the same effect: Sab loads for a while, probably like 30 - 50 MB and then freezes again with unrar again going crazy. I looked into the incomplete folder and found out that there is one .rar file missing and another one seems to have loaded only about 99%.
I restarted sab with debugging level and these are the only sections that could be useful: The Debug message above says: Decoding part of $$$.rar which is the number of the .rar file that is only downloaded 99%.

Also when i started sab from commandline and i send it interrupt signal it didnt end the app first, only after the second interrupt. Same with SIGTERM, it didn't react to normal kill only with hard kill I was able to shut sab down.

Is there a simple way to tell sab to resume downloading from a certain .rar file? Like just continuing downloading from 5 .rar files before the one that is currently resumed on? I tried to move the latest 3 .rar files but sab didnt care and downloaded the next number anyway.
Or is there another way to fix this? Its a really big downloaded i really dont want to start fresh.
Thanks for your help in advance.

Edit: I paused that specific download and all the other downloads work, so its not a problem with my connection.

Update: I tried something: Removed every file out of __ADMIN__ folder besides the gzipped nzb file. Removed all .rar files that are newer than the missing and the curropt one, and those 2 aswell. Repaired the queue. Same effect still! sab loaded one more .rar file (which was the last okay one) and then freezes again with unrar going crazy. Interesting: Shutting down sab again hangs, pgrep doesn't even find sab at this point anymore so i killed unrar itself, and voila sab shuts down regularly. Strange :S

What CPU & RAM?

What if you unrar manually?

sander wrote: ↑August 17th, 2021, 4:33 pm What CPU & RAM?

What if you unrar manually?

CPU: Intel(R) Core(TM) i7-3632QM CPU
RAM: 8GB

What i did is: I found out unrar is blocking the interface and freezing it, but as soon as i kill it sab can continue to download the next .rar package (or at least the next part of one). Even though i deactivated the option to unpack during the download unrar got started every 10 to 20 secs. So i just used the most brutal straight forward way to asure sab could continue to download: I ran a 'while true' loop, that killed unrar every 2 secs. When the download was finished and par2 took over i ended the while loop and after that everything went normal, after par2, unrar unpacked everything.
So i guess problem solved, if anyone still has an idea what went wrong and what i could do if such a case returns i would appreciate your feedback a lot.

@sander I was not really sure if you misunderstoof the topic or if you really meant to unrar the existing packages. Would that help in the future to just delete the so far unpacked stuff and manually run unrar?

If problem solved: OK

(My suggestion / reasoning was this: if unrar blocks, let's find out on unrar level if that is true/reproducible)