All of a sudden... Multiple _UNPACK/_FAILED DOWNLOAD errors.. Advice??

[JohnnyV]

Been using SAB for weeks with out a hitch. As of 24hes ago, multiple downloads are not completing. I went in the _FAILED_ETC... folders and tested them. It seems SAB is only downloading half the files then trying to unpack them. I use Newzbin service so I double checked the posts. I have only half the files that are reported on newzbin in the last 8 downloads.

I re started the Sab Service, and the PC multiple time. Seems to be getting worse. Out of the last 9 downloads, one was compled correctly.

What should I be lookign for? Has anyone seen this issue??

Thanks.

[shypike]

Examples. logfiles. Circumstances.
Do you expect us to say something useful without more info than you gave us?

I can think of many reasons besides SABnzbd.
Dodgy NZB files (yes, even on newzbin). Ill-tempered Usenet provider.
Do you have a reliable one?

[andb]

Been using SAB for weeks with out a hitch. As of 24hes ago, multiple downloads are not completing. I went in the _FAILED_ETC... folders and tested them. It seems SAB is only downloading half the files then trying to unpack them. I use Newzbin service so I double checked the posts. I have only half the files that are reported on newzbin in the last 8 downloads.

I re started the Sab Service, and the PC multiple time. Seems to be getting worse. Out of the last 9 downloads, one was compled correctly.

What should I be lookign for? Has anyone seen this issue??

Exactly same here. Sabnzbd 0.4.6 on OpenSuse 11.1, Default or plush interface, install from sources.

It happened few times since installing Sabnzbd 0.4.6. I just was able to reproduce it:

My queue file was corrupted, so I removed all files from cache directory. Ran sabnzbd and let it retrieve nzb files from my bookmarked list at newzbin. For a day or two everything was ok then all of a sudden - sabnzbd failed to unpack all downloads. Shutdown sabnzbd and rerun - now all downloads are pure trash and sabnzbd reports it'd downloading at the full speed but 0 connections to news server are active. Any shutdown/rerun wouldn't help.

This maybe related to the other problems
- shutdown from the browser gui doesn't seem to do anything. Regular 'kill' does the job only.
- any attempt to repair from par2 files is unsuccesfull (although there are plenty par2 files and I can fix the problem running par2 manually)

[shypike]

There is a potential problem in the filtering of illegal characters in filenames.
Any file name (not folder name) containing a semicolon ';' will be modified.
This will make par2 fail.

Release 0.4.7 (due soon) will correct this.

I'm not aware of any shutdown problem.

[switch]

Do any of you two use giganews? I've heard increasing complaints since New Years.
See http://filesharingtalk.com/vb3/f-newsgr ... ing-328851
and http://www.dslreports.com/forum/r214861 ... going-down

[andb]

Do any of you two use giganews? I've heard increasing complaints since New Years.
See http://filesharingtalk.com/vb3/f-newsgr ... ing-328851
and http://www.dslreports.com/forum/r214861 ... going-down

I do use Giganews.
The problem of retension is noticable for old files (like e.g. older than 100-150 days) but exactly same files which fail - are easily downloaded with eg.Newsbinpro after couple hours. But - it maybe Giganews instability - right. Will take a closer look.


On the other hand -  par2 repair problem is neither specials characters like ";" nor giganews - I checked all _FAILED_* directories, 99% of them did contain  enough par2 valid par2 files which were easily repaired with 'par2 r' command (that what SABNZBD uses - according to the logs files).

I use multithreaded par2 - maybe this is the reason?

[squatter]

Same problem here. I think the issue is caused by the PAR2 filenames being slightly different even though they are in the same NZB file. Example below the extra PAR2 files where called "abigfile-other" whereas the downloaded RAR files where "abigfile"

Example log where it failed:

Stage Download
    [Time-Taken]: 4 hours 25 minutes 39 seconds
    [Avg-Speed]: 800kB/s

Stage Par2
    [PAR-INFO] abigfile-other: => Not enough repair blocks left (have: 0, need: 92)
    [PAR-INFO] abigfile: => Verified in 155.4s, all files correct
    [DEL-INFO] abigfile: => Deleted 2 file(s)

Stage Unrar
    [UNPACK]: => No post-processing because of failed verification

[switch]

Turn "Ignore Sample Files" off. It is failed because the sample file was not downloaded.

In 0.5 I will have the option to delete sample files after the download to stop them failing like this.