"The network path was not found"

[orangeboy]

Hi-
SABnzbd+ 0.5.6
Windows Server 2003 SP2

When post processing scripts, all I ever get in return is "The network path was not found." What is telling me that? Is that the result of the script or from SABnzbd?

From sabnzbd.ini:

Code: Select all

script_dir = \\dl380-server\LAN Path

In Config > Categories, where I specify the script, I am able to successfully use the dropdown to select the script I want, so it seems to me at that point, "The network path WAS found." I'm just not sure what's happening at post-processing time...

[shypike]

Set the logging level to Debug in Connections.
Then download a small job with a pp script.
Open the logging file and search for the name of your script.
You'll see what parameters are passed.
The first parameter is the full path of the final folder.
Be aware that the working folder of the script is not the final folder.

[orangeboy]

Set the logging level to Debug in Connections.
Then download a small job with a pp script.
Open the logging file and search for the name of your script.
You'll see what parameters are passed.
The first parameter is the full path of the final folder.
Be aware that the working folder of the script is not the final folder.

Thanks. It doesn't appear that setting debug revealed anything of significance:

Code: Select all

2011-01-20 04:09:51,099::DEBUG::[tvsort:348] Renaming Series
2011-01-20 04:09:51,099::DEBUG::[tvsort:384] Rename: F:\ToTivo\Downloaded\<file name>
2011-01-20 04:09:51,099::DEBUG::[tvsort:993] Renaming files similar to:<file name>
2011-01-20 04:09:51,109::DEBUG::[misc:852] Moving. Old path:F:\ToTivo\Downloaded\<file name>
2011-01-20 04:09:51,119::INFO::[newsunpack:127] Running external script \\dl380-server\LAN Path\batch.mkv2mp4.bat(F:\ToTivo\Downloaded\<file name>)
2011-01-20 04:09:52,701::INFO::[postproc:470] Cleaning up <file name>
2011-01-20 04:09:52,752::INFO::[__init__:702] D:\SABnzbd\Cache\SABnzbd_article_hecekb removed
2011-01-20 04:09:52,762::INFO::[__init__:702] D:\SABnzbd\Cache\SABnzbd_article_dg8xwk removed
2011-01-20 04:09:52,762::INFO::[__init__:702] D:\SABnzbd\Cache\SABnzbd_article_t6javd removed
2011-01-20 04:09:52,762::INFO::[__init__:702] D:\SABnzbd\Cache\SABnzbd_article_skcacw removed
2011-01-20 04:09:52,762::INFO::[postproc:134] Saving postproc queue
2011-01-20 04:09:52,762::DEBUG::[__init__:649] Saving data for postproc1.sab in D:\SABnzbd\Cache\postproc1.sab
2011-01-20 04:09:52,772::INFO::[downloader:357] Post-processing finished, resuming download

What I'm speculating is that post-processing isn't fulling qualifying the script name and path at script execution time, though it does qualify the path at script selection time. Opening a command prompt and pasting everything following "2011-01-20 04:09:51,119::INFO::[newsunpack:127] Running external script" in the log yeilds the same "The network path was not found." message. Fully qualifying the script path and filename and passing (quoted) arguments created by SABnzbd in the command prompt does result in successful, expected results.

In the wiki, it states "Please note that in Windows the parameters will be enclosed in double quotes ("my name")." I'm not seeing this based on the log, and the arguments passed remain unquoted, and only separated by commas.

I believe these are bugs relating to post processing script handling.

[shypike]

There's a known bug in the Python library: it cannot handle spaces in the script path.
For drive letter paths, SABnzbd uses a work-around that uses the shortened 8.3 name.
The work-around cannot work for a  UNC (\\server\name) paths.
Remove the space from your share name.

[orangeboy]

There's a known bug in the Python library: it cannot handle spaces in the script path.
For drive letter paths, SABnzbd uses a work-around that uses the shortened 8.3 name.
The work-around cannot work for a  UNC (\\server\name) paths.
Remove the space from your share name.

Hmm. Easier said than done. My "Lan Path" is included in the %path% variable on the PCs on my LAN to reduce redundancy. But I get what you're saying. I'll copy any SABnzbd scripts into a local folder that has a simple name.

FWIW, I downloaded the python source. If I can come up with an alternative to circumvent the subprocess.Popen limitations, I'll be sure to pass it along!