SABnzbd Forums

Pulling my hair out on this one guys.

Installed 7.11 on a RPi - fresh install.

Everything is working fine except I can't specify the scripts and watched folders.

I have tried everything I can think of, typed the folder path, used the browse to navigate to it, manually updated the ini file.

chmod the folder and file to both 755 and 777 - no change. Tried creating new folders in different locations - didn't work.

What is strange is that the completed download folder path saved...

Any help would be appreciated.

Scripts need to have their X bit set:
chmod +x script

Thanks for the help.

Tried chmod both the directory and the files but still no dice, SAB wont save the folder path.

Not saving the folderpath usually means that the path does not exist
or is not accessible for SABnzbd.
Did you use the browser button to get to the path

Yes I used the browse button to get to the path and have tried to save multiple paths to other directories as well.
I even tried using the default directory - won't save.

The strange thing is that any other setting I change in the config saves without issue. It's just the watched and scripts folder that won't save.

The completed & incomplete folder saves fine, to the same dir that I am trying to save the watched and scripts dir to - that puzzles me.

As a last resort: stop SABnzbd and edit the sabnzbd.ini file directly.
Location: http://wiki.sabnzbd.org/configure-0-7
Field: script_dir

Tried that, I can edit the file and when I reopen the file the changes stick.

However when I restart SAB it overwrites the file and deletes those two ini edits reverts back to ""

There must be something odd with the path.
Are you sure the script path is accessible at the time SABnzbd start up?
It's not on an external drive or networked share?
Set logging level to debug (Status page). Stop SABnzbd. Edit the ini file again.
Start SABnzbd.
Then inspect the log file (also on the Status page) and look for messages about your script path.

i have the same issue, did you have found a fix?

Im on MAC 10.8 and SABnzb 0.7.11

thanks
greetings yesuar

Same issue here. Any solutions?

joostp wrote:Same issue here. Any solutions?

Same questions as before.
Without more details, what can I say?

At every reboot of my machine my script folder turns back to 'scripts'.
I have tried several other options, including using the exact same path as the download folder, but without success.
Also I chmodded the directories to 777 (everything is on root / root, also the regular scripts folder that is working).

I will try to find something in the logs.

Btw: I'm using SAB on OpenELEC.

Having the same problem here.

Update: If anyone else has this problem, check your permissions to the download dirs.

Hi guys

I had exactly the same problem with folders not saving and CHMOD not having any effect. I was using a vfat formatted external hard drive which does not support user permissions and therefor user modification. I managed to get the folder to save once I changed the auto-mount script in /etc/fstab to:

/dev/sda1 /media/FUNWORLD vfat defaults,uid=65534,gid=65534,dmask=000,fmask=111 0 0

uid and gid set owner and group to 'no owner' and 'no group' thus the drive is now available for full read and write permission to all users. Seemed to solve the issue for me.

Obvisouly your pi will need a reboot after editing.

I am having the same issue as those above. I save the directory in the config of the web interface and then after restarting sabnzbd it is gone.

I have even set the ini file to 777

as well as changed my mount to: Though that should make absolutely no difference as my ini file is located on my flash drive where the rest of my rasbian files are located
/var/sabnzbd/sabnzbd.ini

which has the following permissions and ownership EDIT: I changed my scripts target to a folder located on my external hdd where the rest of my folders were located rather than pointing to the sickbeard scripts folder and it stuck. It appears I just cant set or read to / from folders located on the rasbian os flash drive. Probably some permissions or owner problems