cannot create folder

[jwhitener]

I have sab running on windows 10 in my office. On that computer I have a link to a NAS. I did that by using windows mklink. I forget the exact command, but it was basically something like 'mklink \\myNAS\myShare c:\tempdir'

I did that because I was having issues with Sab and mapped network drives. Sab couldn't see mapped drives. That may have changed in newer versions, so if that is so, please let me know.

If I go into Sab's folder config, I am able to browse to c:\tempir (which is actually a mklink to \myNAS\myShare).

So Sab sees the network link my in config. But ever time I come home at night, the Sab error log is filled with messages that say "ERROR cannot create c:\tempdir".

I am not sure if this is an issue with Windows not exposing mklink network paths after sleep or an issue with Sab. Any suggestions welcome.

[jwhitener]

Odd. Sab is still complaining that it cannot create directory c:\tempir. This despite me actively browsing around in c:\tempdir and being able to browse to that folder in the Sab folder config.

I just double checked permissions also. Every user on the system has full control of that c:\tempdir. Not sure what else to check.

[shypike]

For SABnzbd all drives are the same, it's only the Operating system that know the underlying reality.
Having said that, there are a few odd bugs in the Python libraries that we use.
Have SABnzbd use (create) a new folder within c:\tempdir, by setting the folder to c:\tempdir\workdir

[jwhitener]

For SABnzbd all drives are the same, it's only the Operating system that know the underlying reality.
Having said that, there are a few odd bugs in the Python libraries that we use.
Have SABnzbd use (create) a new folder within c:\tempdir, by setting the folder to c:\tempdir\workdir

Maybe it was sickbeard that couldn't see a mapped drive then. Or more likely some issue with windows not reconnecting mapped drives through sleep or something.

I deleted the temp drive and hopefully sab will recreate during the next download attempt.

edit: Sab didn't recreate the directory. Still complaining that it cannot create it. Is there a specific way to tell Sab to create the directory?

edit2: Downloads still work though. Maybe the error message is just informational and can be ignored?

[shypike]

If SABnzbd did not create the folder, it either couldn't or did not need it.
But it isn't clear to what comes from SABnzbd and what comes from Sickbeard.

[nzbtuxnews]

I have the same issue, when I start SAB (or after restarting it), it complains that it cannot create the incomplete folder (although it already exists).

I tried changing the folder perms to 777 (I am on centos linux) and SAB still complains it cant create the incomplete folder. This doesnt reoccur after the startup.

Whats weird is that SAB uses the folder successfully (I am running a few jobs right now and SAB is storing the files in the folder).

Seems to be a minor bug because it doesnt reoccur after initial startup and everything appears to be running fine.

SABnzbd: 0.8.x [unknown].
Python: 2.7.5 (default, Nov 20 2015, 02:00:19) [GCC 4.8.5 20150623 (Red Hat 4.8.5-4)].

[shypike]

You're not using an official release. What are you using?

[nzbtuxnews]

Pretty sure I installed SAB from GIT.... its been a while though, ls shows last modified date for the folder ".git" of Jan 30 2016

[shypike]

That's some arbitrary release.
Please sync to an official release, from master or 1.0.x

[nzbtuxnews]

Should I finish my queue first? Then should I use Git to install or is it better to install from the zip (or tar.gz) file?

[shypike]

Git should work fine, if you run tools/make_mo.py after every pull.
If you're already on a 1.0.0 pre release, the queue is Ok.
When using git, set it to master or 1.0.x