Fetches with an error should not disappear without warning, an error will be visible in Connections.
The idea is that you remove the entry yourself.
An improvement would be the show the actual error message in the queue entry, I'll have a look at that.
BTW: the queue does not lock up.
another case of the queue "locking up"
Forum rules
Help us help you:
Help us help you:
- 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: another case of the queue "locking up"
Last edited by shypike on June 10th, 2008, 8:31 am, edited 1 time in total.
Re: another case of the queue "locking up"
Fetches (failed or waiting) do NOT block the queue.
Re: another case of the queue "locking up"
Correction. A blocked fetch will block the queue, unless option "Only get articles for top of the queue" is off.
This is not correct and will be dealt with for the next release.
This is not correct and will be dealt with for the next release.
Re: another case of the queue "locking up"
This thing only occurs with Plush.
The rotating thingy will not stop until I restart SAB.
This problem does not occur in Default and Smpl.
The rotating thingy will not stop until I restart SAB.
This problem does not occur in Default and Smpl.
Re: another case of the queue "locking up"
Also, I have no problems removing these failed jobs. Not even with Plush and the rotating thingy.
Which Subversion rev do you use?
Which Subversion rev do you use?