Page 1 of 1

post processing help?

Posted: May 13th, 2008, 10:41 am
by monkee
i've upgraded from 0.4.0 beta 2 to beta 5, and now my postprocessing is just stuck as queued for some reason

before, it would just par, extract, and delete automatically after download.. now it just stays in the incomplete folder

any idea on how to fix this? thanks in advance!

Re: post processing help?

Posted: May 13th, 2008, 1:22 pm
by shypike
Not with so little information.
Have you looked at the logging (after setting logging level to "Debug" in the Connections page) ?

Re: post processing help?

Posted: May 13th, 2008, 3:46 pm
by neilt0
I had this problem. Deleted cache, works fine now.

Re: post processing help?

Posted: May 13th, 2008, 7:31 pm
by monkee
i deleted the files in cache and the whole thing just went bonkers.. like new files wouldn't download it would just get stuck at 0.0/(whatever MB)

i uninstalled and reinstalled beta 5 and everything's working great now

i think i made the nub mistake of installing beta 5 on top of beta 2.. and that somehow things went south from there


thanks for all the help anyways guys!

Re: post processing help?

Posted: May 14th, 2008, 1:43 am
by shypike
This is strange. We took some extra measures to prevent such problems.
The only two problematic files queue.sab and bytes.sab are called
queue7.sab and bytes7.sab now, to prevent these kinds of problems.

More to investigate now.

Re: post processing help?

Posted: May 15th, 2008, 7:11 am
by lost101
I also had this problem. A fresh install and clear cache fixed it.

Re: post processing help?

Posted: May 16th, 2008, 6:19 am
by monkee
hrm i had another bug that popped up where sabnzbd was taking up a lot of the cpu cycles and i had to restart the sabnzbd process..

when i restarted i found out that sabnzbd was still downloading (before i restarted the process) but the post-processing was frozen (think it was the post processing that made the cpu utilization to shoot up).. and the entire download queue and history was erased

AND the whole problem with the post-processing staying queued popped up again