SABnzbd Forums

Hi shypike

Since uograding to 0.4.6 I have noticed that all par2 files are downloaded, and then placed in the completed download folder along with completed file. Also have noticed that error messages are being generated similar to below, even when the file was transferred properly. Not sure if they are related. I had one for each file that was processed.

2008-12-29 04:08:15,968 ERROR [sabnzbd.misc] Failed moving /volumes/Family/Parts/name/name.avi to /volumes/family/NZB Downloads/TV/Jag/Season 7/_UNPACK_name/name.avi

I am running Mac OS X 10.5.5 on Dual G5, Safari 3.1.2 and SABnzbd+ 0.4.6.

Contents of ini file below

Thanks
chessman

__version__ = 18
[misc]
log_dir = logs
auto_browser = 1
permissions = ""
check_new_rel = 1
replace_spaces = 0
fail_on_crc = 0
enable_filejoin = 0
enable_unzip = 1
enable_unrar = 1
enable_par_cleanup = 1
par_option = ""
config_lock = 0
safe_postproc = 0
pause_on_post_processing = 0
cleanup_list = ,
ignore_samples = 1
send_group = 0
download_dir = /volumes/Family/Parts
download_free = 0
complete_dir = /volumes/family/NZB Downloads
script_dir = ""
nzb_backup_dir = ""
cache_dir = cache
dirscan_dir = /volumes/family/NZB Downloads/NZB Files
dirscan_speed = 300
refresh_rate = 0
rss_rate = 60
bandwith_limit = 0
cache_limit = 0
email_server = ""
email_to = ""
email_from = ""
email_account = ""
email_pwd = ""
email_endjob = 0
email_full = 0
schedlines = "0 1 * resume ", "0 7 * pause "
dirscan_opts = 3
dirscan_script = None
top_only = 1
auto_sort = 0
enable_tv_sorting = 1
tv_sort_string = %sn/Season %s/%0e. %en.%ext
web_color = ""
web_color2 = ""
host = localhost
port = 8080
web_dir = Default
web_dir2 = Default
username = ""
password = ""
replace_illegal = 1
auto_disconnect = 1
no_dupes = 0
ionice = ""
[logging]
enable_cherrypy_logging = 1
log_level = 0
max_log_size = 5M
log_backups = 5
[newzbin]
username = xxxxxx
password = xxxxxx
bookmarks = 1
unbookmark = 1
bookmark_rate = 15
[servers]
xxxxxx
port = 80
username = xxxxxx
password = xxxxxx
connections = 0
timeout = 120
fillserver = 0
ssl = 1
xxxxxx
port = 80
username = xxxxxx
password = xxxxxx
connections = 12
timeout = 120
fillserver = 0
ssl = 1
xxxxxx
port = 443
username = xxxxxx
password = xxxxxx
connections = 0
timeout = 120
fillserver = 0
ssl = 0
[rss]
[categories]
[[anime]]
newzbin = Anime
dir = Anime
[[books]]
newzbin = Books
dir = Books
[[consoles]]
newzbin = Consoles
dir = Consoles
[[emulation]]
newzbin = Emulation
dir = Emulation
[[games]]
newzbin = Games
dir = Games
[[misc]]
newzbin = Misc
dir = Misc
[[pda]]
newzbin = PDA
dir = PDA
[[resources]]
newzbin = Resources
dir = Resources
[[apps]]
pp = 3
dir = Apps
newzbin = Apps,
[[movies]]
pp = 3
dir = Movies
newzbin = Movies,
[[tv]]
pp = 3
dir = TV
newzbin = TV,
[[unknown]]
pp = 3
dir = Unknown
newzbin = Unknown,
[[music]]
pp = 3
dir = Music
newzbin = Music,

Have a look at your folder called : Family

It it like this : Family or family
As you used both in your ini

download_dir = /volumes/Family/Parts
download_free = 0
complete_dir = /volumes/family/NZB Downloads
script_dir = ""
nzb_backup_dir = ""
cache_dir = cache
dirscan_dir = /volumes/family/NZB Downloads/NZB Files

I noticed that there's something odd going on with joining multi-part files.
I'll file a ticket, so that we won't forget to investigate further.

Hey Rascalll

Well spotted. 'Family' is correct. I have changed all of them to read correct. I am not sure that this explains the other behaviour that I have seen, and in 0.4.5 didn't seem to affect the outcome as 0.4.6.

Thanks
chessman

Instead of starting my own thread for was is also a problem with post processing on Mac os 10.5 I figured I'd post here too.

When I download something that needs repaired. sabnzbd will download the pars required, however it will not repair/extract the file, and what's left in the folder are all the rars (broken and unbroken), along with broken rar.1 files.

I've attached what the client looks like, and included in the screenshot what happens if no repair is needed (the report below the failed one), I apologize for the image width.

I'm running the latest version of sabnzbd 0.4.6, on an intel macbook pro.

Are you saving a lot of newzbin reports into one file? When downloading click "In zip file, Individually". What you are doing should still work, not sure why par2 is getting caught up, but sabnzbd is meant to have one "job" per nzb and you are giving it one nzb with a lot of "jobs".

This happens regardless of how many 'jobs' I give it. This has never happened before the latest version.

I've also been getting more errors unpacking/unparing/etc. in 0.4.6 on Mac OS X 10.5. I chalked it up to some NZBs I downloaded, but when I tried 0.4.5, they processed correctly. Unfortunately I haven't come across any in the past week or so since I've been busy, so I can't produce any exact examples of my issues. However, descriptions of others' issues sounds similar to mine.

The par2 utility for OSX was replaced between 0.4.5 and 0.4.6.
This might have something to do with it.
I'll check with our OSX guru.

Now I'm by no means an expert on how the par2 routine works, but I can point out my observations on the matter. It almost appears as if the par2 routine is not correctly renaming the files. Instead of naming the repaired file .r14 for example, and the broken file .r14.1; it does the opposite, leaving the broken file as .r14 and creating a new file .r14.1 for the fixed file. This then causes the unrar routine to choke. The observations that have lead to me to this conclusion are that when I open the file set in MacPAR Deluxe, it says that the .r14 files are broken and that the .r14.1 files have XX blocks from .r14. Leading me to assume that the r14.1 are repaired. Of course this is only speculation but perhaps it will help you guys out.

@shypike
you're right, the only difference between 0.4.5 and 0.4.6 is the par2 binary.

@Arithmeicae
I've been using 0.4.6 and no problems for me but maybe the last par2 binary have a bug, i try to do some tests.
I you want to test you can grab the par2 binary of 0.4.5 and put it on the 0.4.6. (right click on SABnzbd, select "Show Package Content" and browse Content/Resources/osx/par2).

rAf wrote: I've been using 0.4.6 and no problems for me but maybe the last par2 binary have a bug, i try to do some tests.
I you want to test you can grab the par2 binary of 0.4.5 and put it on the 0.4.6. (right click on SABnzbd, select "Show Package Content" and browse Content/Resources/osx/par2).

I'm doing as you suggested and will report back with results. But let me reiterate, this problem only arrises if there are errors in the rar files.

EDIT:
After reverting to the old par2 binary, (only the par2 binary was change, all other settings and preferences remained the same) everything works like it should, files that are corrupt/broken are successfully repaired and unrared.

Do the files contain accented characters>?

For Windows we fall back the "classic" par2 program, because the "new" one fails for accented characters.
The guy  who created the new one decided to start using Unicode for accented characters,
while the "classic" one still uses 8-bit ASCII.

Nope, there is nothing abnormal about the report. No accented characters or special symbols.

I've noticed that quiet often sabnzb+ fails to process an unrar event.  At that point, the only way to recover is to shut down sabnzd+, kill the stuck unrar process from the CLI, manually unrar the files (I never see any error on the manual unrar), move them aside, and then restart sabnzd+.

By 'quite often' I mean a couple of times a week. (OS X 10.5.6).