Hi,
Version:0.5.0 Final
OS: Windows 7 64
Install-type: Windows Installer
Skin : plush
IPV6 yes
Is the issue reproducible? often
I stop sabnzbd with the shutdown menu or i close the process with windows (task manager) or i shutdown the computer. When i restart windows and sabnzbd, some work stay on 0Mb/s and can't be resume.
do you know the good issue to stop that?
best regards
freeze on 0 Mb/s
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: freeze on 0 Mb/s
Stopping SABnbd with the task manager is not a good idea.
It may damage the queue integrity.
If you assigned a large memory queue to SABnzbd, shutdown may take a long time.
The safest way is to pause SABnzbd first and then shut it down.
Stuck on 0 bytes can have more than one cause.
One is that when you have a non-responding backup server a download may stall
on a missing article.
The other cause is queue corruption.
Can you remove the stalled job?
If not, set in Config->Switches the option "Only get articles for top of the queue" to off.
This will allow SABnzbd to finish the other jobs.
Once the queue is empty (except the stalled job), stop SABnzbd and restart it with the --clean option.
It may damage the queue integrity.
If you assigned a large memory queue to SABnzbd, shutdown may take a long time.
The safest way is to pause SABnzbd first and then shut it down.
Stuck on 0 bytes can have more than one cause.
One is that when you have a non-responding backup server a download may stall
on a missing article.
The other cause is queue corruption.
Can you remove the stalled job?
If not, set in Config->Switches the option "Only get articles for top of the queue" to off.
This will allow SABnzbd to finish the other jobs.
Once the queue is empty (except the stalled job), stop SABnzbd and restart it with the --clean option.