Scheduler Not Resuming Low Priority Downloads
Posted: June 22nd, 2016, 6:44 am
EDIT: OS is Windows 10 Pro, SAB Version is 1.0.3 [927ba3c]
I had originally posted this problem in the beta area because I was playing with release 1.1.0 beta 1; in my investigation I decided to roll back to stable, to see if the issue persisted there or not and it does. I finally have the right logs and screen shots showing exactly my problem, not sure if I need to just start completely over or not as I've reinstalled 1.0.3 (maintaining my cfg files, which seemed to work fine, however, if this is a possible cause of the issue, I'll just start over from scratch).
The problem is that I have some files I only want to download at night between 11:30 PM and 7 AM, so I add them to the queue en masse as low priority and then I'd like them to download at night, the problem is that nothing is happening when the scheduler is telling the queue to resume. If I manually pause the top file then manually resume, it will start downloading jobs; also, if a normal priority job hits the queue and downloads between 1130 PM and 7 Am, then the rest of the queue will download as well. I have logs showing this exact behavior, but they're not sterile and they're 5MB, so I'd rather PM them to someone for review rather than post them publicly.
So, copying this from my other post:
1. Have scheduler set to pause low priority jobs
2. Add low priority job to queue (should be paused)
3. Have scheduler resume low priority jobs
4. Job will resume/unpause but will not begin downloading until user manually pauses, then resumes job.
5. Rest of queue will download fine once user has paused/resumed first job in queue.
6. Any new downloads added to queue with normal priority download fine. Only seems to affect jobs that would be affected by scheduler (in this case, low priority jobs)
Schedule:
Queue after being resumed by scheduler(but note that it's not downloading):
Top Job Manually paused:
Top Job Manually resumed (note that all downloads below resume as well)
Is it time to just scrap everything and start over? As I said, I have logs, but they're not sterile and contain job names that should not be publicly posted.
I had originally posted this problem in the beta area because I was playing with release 1.1.0 beta 1; in my investigation I decided to roll back to stable, to see if the issue persisted there or not and it does. I finally have the right logs and screen shots showing exactly my problem, not sure if I need to just start completely over or not as I've reinstalled 1.0.3 (maintaining my cfg files, which seemed to work fine, however, if this is a possible cause of the issue, I'll just start over from scratch).
The problem is that I have some files I only want to download at night between 11:30 PM and 7 AM, so I add them to the queue en masse as low priority and then I'd like them to download at night, the problem is that nothing is happening when the scheduler is telling the queue to resume. If I manually pause the top file then manually resume, it will start downloading jobs; also, if a normal priority job hits the queue and downloads between 1130 PM and 7 Am, then the rest of the queue will download as well. I have logs showing this exact behavior, but they're not sterile and they're 5MB, so I'd rather PM them to someone for review rather than post them publicly.
So, copying this from my other post:
1. Have scheduler set to pause low priority jobs
2. Add low priority job to queue (should be paused)
3. Have scheduler resume low priority jobs
4. Job will resume/unpause but will not begin downloading until user manually pauses, then resumes job.
5. Rest of queue will download fine once user has paused/resumed first job in queue.
6. Any new downloads added to queue with normal priority download fine. Only seems to affect jobs that would be affected by scheduler (in this case, low priority jobs)
Schedule:
Queue after being resumed by scheduler(but note that it's not downloading):
Top Job Manually paused:
Top Job Manually resumed (note that all downloads below resume as well)
Is it time to just scrap everything and start over? As I said, I have logs, but they're not sterile and contain job names that should not be publicly posted.
