SABnzbd Forums

This may qualify as a bug, but perhaps it could use some thought anyway.

In my scenario, i often place .nzb's in a watched folder via windows networking over a vpn. The problem comes with larger nzb files; which are taking a while to copy across.

It appears if sabnzbd realises the file is there, but it has not finished copying, so it errors when trying to read it.

This could be more gracefully handled? perhaps check again in another x secs before erroring?

I currently had scan ever set to 5 seconds, but i may increase this to 10.

SABnzbd waits until all attributes of the file (including size) are stable for 1 second.
This still gives problems for slow connections.
Work-around: save the file with a different extension and rename afterwards.

We are looking at a better solution, but that's for a later release.

Thanks for the response.

Release 0.4.3 will have a solution for this problem.

Thanks I was having the exact same problem, I was coming here to report that bug also... I'm using too as IPSec VPN connection to copy my nzb to my server and I get warning too, what I do is change the name by adding a character at the end of the filename and SABnzbd recatch it and process it.

MageMinds wrote: Thanks I was having the exact same problem, I was coming here to report that bug also... I'm using too as IPSec VPN connection to copy my nzb to my server and I get warning too, what I do is change the name by adding a character at the end of the filename and SABnzbd recatch it and process it.

I set my interval to 30 seconds.  Seems to be long enough for any nzb I've sent remotely (and I do use ssh to put nzbs into my watch folder on occasions)

Will be fixed the the coming 0.4.3 release.