Wrong cache folder location when using Sickbeard

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Wrong cache folder location when using Sickbeard

Post by ta0801 »

I'm using sabnzbd 0.7.14 on my Qnap TS-469L.

I changed all the default folder locations to a different directory and when I manually start any download, everything works as it should.

When sickbeard controls sabnzbd via API, sabnzbd creates a new sabnzbd/cache folder in the default download location.

Is there anything I can do about it?
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Wrong cache folder location when using Sickbeard

Post by shypike »

Did you changes paths of the TV category too?
SickBeard always sets the category to "TV".
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Re: Wrong cache folder location when using Sickbeard

Post by ta0801 »

Yes, you are right, the category is set to "tv".
But I just checked in my sabnzbd settings, there is no catergory configured.

But however, I will delete the "tv" and see what happens. Thanks for the help so far!
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Re: Wrong cache folder location when using Sickbeard

Post by ta0801 »

I just figured, that the problem has nothing to do with Sickbeard.

Every time I start up sabnzbd, the sabnzbd/cache folder is created (in the loaction I don't want it).

Does anybody has another idea?
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Wrong cache folder location when using Sickbeard

Post by shypike »

This happens when the set location is not available when needed.
External drive?
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Re: Wrong cache folder location when using Sickbeard

Post by ta0801 »

no, everthing runs on my Qnap:

Default Base Folder:
/share/MD0_DATA/.qpkg/SABnzbdplus/Config

/share/Web/sabnzbd/incomplete
/share/Download
/share/Web/sabnzbd/nzb
/share/Web/sabnzbd/scripts
/share/Web/sabnzbd/logs
/share/Web/sabnzbd/nzb/backup

I don't see, where the cache folder is configured.
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Wrong cache folder location when using Sickbeard

Post by shypike »

SABnzbd 0.7.14 doesn't create a cache folder, isn't SickBeard doing that?
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Re: Wrong cache folder location when using Sickbeard

Post by ta0801 »

I'm pretty sure, that it is not Sickbeard:

I disabled it and everytime I restart sabnzbd the cache folder is created.
User avatar
shypike
Administrator
Administrator
Posts: 19773
Joined: January 18th, 2008, 12:49 pm

Re: Wrong cache folder location when using Sickbeard

Post by shypike »

Weird, there's still some old code in SABnzbd to support upgrades from older versions.
It should not trigger.
In case it does, you can set it to a dummy location of your liking by editing the sabnzbd.ini file directly.
Just make sure SABnzbd isn't running when you edit.
Look for the "cache_dir" parameter and enter a full path behind it.
ta0801
Newbie
Newbie
Posts: 6
Joined: August 12th, 2013, 3:25 am

Re: Wrong cache folder location when using Sickbeard

Post by ta0801 »

I directly edited the sabnzbd.ini and it worked, thanks!

The path was wrong and appreantly your guess regarding the old code was right, it still triggers.
Post Reply