These are known issues regarding the working of SABnzbd in its environment.
They are not registered as bugs of SABnzbd, because we cannot solve them.
It's more an incompatibility with other systems or outright bugs in these other systems.
Size limit
To prevent unexpectedly large NZBs from eating your quotum you can set the option 'size_limit' in the INI file.
Any NZB larger than this size will be set to paused and get a low priority.
Hangup of post-processing
When PAR2 or UNRAR hang up, you should never just stop SABnzbd.
Instead use your operating system's task manager to stop the PAr2 or UNRAR program.
Forcing SABnzbd to quit may damage your queues.
Windows-only:
If you keep having trouble with par2 multicore you can disable it in Config->Switches.
This will force the use of the old and tried, but slower par2-classic program.
Firewall bug in Windows
A bug in Windows 7 may cause severe memory leaks when you use SABnzbd in combination with some virus scanners and firewals.
Install this hotfix:
Description: http://support.microsoft.com/kb/979223/en-us
Download location: http://support.microsoft.com/hotfix/KBHotfix.aspx?kbnum=979223&kbln=en-us
Long paths in Windows
Windows cannot handle path names longer than 254 characters.
Currently, SABnzbd doesn't handle this problem gracefully.
We have added INI-only option "folder_length_max" in which you can set a maximum folder name size.
For Windows the default is 128 and for others 256.
A quite safe value for Windows would be 64.
SABnzbd will take care of overlapping names.
64bit Windows
Some 64bit Windows systems have problems with the 64bit versions of par2 and unrar.
There is an INI-only setting "allow_64bit_tools" which, when set to 0, will force the use of 32bit versions.
Unreliable servers
Some Usenet servers have intermittent login (or other) problems.
For these, the server blocking method is not very favorable.
There is an INI-only setting no_penalties which, when set to 1, will limit blocks to 1 minute
(No, 2 doesn't mean 2 minutes).
OSX and foreign characters
On OSX you may encounter downloaded files with foreign characters (e.g. é and ä).
The par2 repair may fail when the files were created on a Windows system.
The problem is caused by the PAR2 utility and we cannot fix this now.
This does not apply to files inside RAR files.
Linux and foreign characters
On Linux when you download files they may have the wrong character encoding.
You will see this only when downloaded files contain accented characters.
You need to fix it yourself by running the convmv utility (available for most Linux platforms).
Files remain in Watched Folder
The "Watched Folder" sometimes fails to delete the NZB files it has processed.
This happens when other software still accesses these files.
Some third-party utilities supporting SABnzbd are known to do this.
We cannot solve this problem, because the Operating System (read Windows) prevents the removal.
SABnzbd does try about 10 times with 5 second intervals, but after that it gives up.
The NZB will not be processed again, unless changed or overwritten.
Files left behind
Jobs deleted from the queue will leave downloaded files behind in the "incomplete" folder.
You will have to remove these files manually.1
Memory usage
Memory usage can sometimes have high peaks.
This makes using SABnzbd on very low memory systems (eg a SAN device) a challenge.
Your total system memory should be above 256 MByte (assuming a Linux variant is used).
Incompatible firewalls
SABnzbd is not compatible with some software firewall versions.
The Mircosoft Windows Firewall works fine, but remember to tell this firewall that SABnzbd is allowed to talk to other computers.
Blocked email
When SABnzbd cannot send notification emails, check your virus scanner, firewall or security suite.
It may be blocking outgoing email.
Mounting external drives and network shares
When you are using external drives or network shares on OSX or Linux make sure that the drives are mounted.
The operating system will simply redirect your files to alternative locations.
You may have trouble finding the files when mounting the drive later.
Memory leaks
Some users have complained about ever growing memory use by SABnzbd.
So far we have not been able to reproduce this behavior, but that doesn't mean it can never happen.
We would like to receive information on how to reproduce this problem.
Logging stops
Sometimes logging stops.
This is a notorious bug in Python logging. SABnzbd will function as normal.
If you run from sources or use the —console option with the Win32-binary, you will see that logging continues in the console window, but nothing will be written to the log-files.
