I have scheduling set up to pause post processing at 02:00 (everyday) and to resume at 17:00 (everyday).
What I have found is that the pause does not work until at least one download is post-processed subsequent to the pause being triggered.
eg: I had a download go through post processing at 09:30 this morning and now all subsequent downloads are queued.
Running the current version (0.7.18). Seems to be an issue (bug?) introduced in the latest version as I can't remember seeing this behaviour before I upgraded.
Pause Post Processing not working as expected
Forum rules
Help us help you:
Help us help you:
- Are you using the latest stable version of SABnzbd? Downloads page.
- Tell us what system you run SABnzbd on.
- Adhere to the forum rules.
- Do you experience problems during downloading?
Check your connection in Status and Interface settings window.
Use Test Server in Config > Servers.
We will probably ask you to do a test using only basic settings. - Do you experience problems during repair or unpacking?
Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Re: Pause Post Processing not working as expected
Could be true. The check is a bit awkward for good other reasons.
It could be possible that we goofed this one aspect.
I'll check.
It could be possible that we goofed this one aspect.
I'll check.
-
- Newbie
- Posts: 1
- Joined: September 15th, 2014, 2:42 am
Re: Pause Post Processing not working as expected
Experiencing the same behaviour as Horatio while manually pausing.
Also using version 0.7.18.
Also using version 0.7.18.
Re: Pause Post Processing not working as expected
Hi Shypike,
Is there anything else you need to assist looking at this? Happy to assist where I can.
Is there anything else you need to assist looking at this? Happy to assist where I can.
Re: Pause Post Processing not working as expected
It's just going to take time, which is the limiting factor for almost everything concerning SABnzbd.Horatio wrote:Hi Shypike,
Is there anything else you need to assist looking at this? Happy to assist where I can.
Re: Pause Post Processing not working as expected
A question.
Is it something like this scenario?
Downloading
01:55 - A job enters post-processing and is started
02:00 - Post processing pause starts
02:05 - The running post processing job is still running
03:04 - A new job enters the post processing queue and is paused
Or this one:
Downloading
02:00 - Post processing pause starts
02:05 - A job enters the post-processing and is started
02:15 - The job finishes
03:04 - A new job enters the post processing queue and is paused
Is it something like this scenario?
Downloading
01:55 - A job enters post-processing and is started
02:00 - Post processing pause starts
02:05 - The running post processing job is still running
03:04 - A new job enters the post processing queue and is paused
Or this one:
Downloading
02:00 - Post processing pause starts
02:05 - A job enters the post-processing and is started
02:15 - The job finishes
03:04 - A new job enters the post processing queue and is paused
Re: Pause Post Processing not working as expected
Hi Shypike,
It's the second one.
I have had instances where post processing pause occurred at 02:00 and a download was post processed at 09:30. This was the first after the 02:00 a.m. pause kicked in. Then all subsequent downloads were queued for post processing.
Cheers,
Horatio
It's the second one.
I have had instances where post processing pause occurred at 02:00 and a download was post processed at 09:30. This was the first after the 02:00 a.m. pause kicked in. Then all subsequent downloads were queued for post processing.
Cheers,
Horatio
Re: Pause Post Processing not working as expected
Hi Shypike,
Just wondering if you have had a chance to look at this?
Horatio
Just wondering if you have had a chance to look at this?
Horatio
Re: Pause Post Processing not working as expected
So far I cannot find anything suspicious in the code.
Therefor I would need to setup an extensive test scenario; such things cost time.
I'm not sure this will be fixed in the (already overdue) release 0.7.19
Therefor I would need to setup an extensive test scenario; such things cost time.
I'm not sure this will be fixed in the (already overdue) release 0.7.19