Hi. Just setting up on Mac. Ive set up numerous times before but had to reinstall due to HDD failure. I'm running Sabnzbd+ on Mavericks.
When I go to config - folders and put in the folder for the sickbeard post processing script, even though I click save changes, if I go to another menu option when I return to Folders the post processing script folder has disappeared.
Any ideas?
Thanks,
sabnzbd keeps losing post processing scripts folder - on Mac
Forum rules
Help us help you:
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.
Re: sabnzbd keeps losing post processing scripts folder - on
Does the folder actually exist and is it readable for the account SABnzbd runs under?
Re: sabnzbd keeps losing post processing scripts folder - on
Hi. Yes to both questions.
Re: sabnzbd keeps losing post processing scripts folder - on
Is it local or does it reside on a mounted volume.
You could try to edit the sabnzbd.ini file directly (when SABnzbd isn't running).
The location is: /Users/user/Library/Application Support/SABnzbd/sabnzbd.ini
Look for dirscan_dir
You could try to edit the sabnzbd.ini file directly (when SABnzbd isn't running).
The location is: /Users/user/Library/Application Support/SABnzbd/sabnzbd.ini
Look for dirscan_dir
Re: sabnzbd keeps losing post processing scripts folder - on
Hello. Your point about local got me investigating. I think I've resolved it. It was installed locally (not on a volume) but it was also running on another profile - so 2 instances running at once. To be sure I deleted Sabnzdb (moved to the trash), killed all instances of it running in Activity Monitor and then removed the Sabnzdb folder from Application Support in Library. Re-installed and it is retaining the settings.
Yesterday I tried deleting the app by moving to Trash and then re-installing but it didn't work. Today I tried the above step but didn't kill the process in the other profile, and it didn't work. Only after killing the process in the 2nd profile did it start to work.
Thanks for your help.
Yesterday I tried deleting the app by moving to Trash and then re-installing but it didn't work. Today I tried the above step but didn't kill the process in the other profile, and it didn't work. Only after killing the process in the 2nd profile did it start to work.
Thanks for your help.
Re: sabnzbd keeps losing post processing scripts folder - on
I know this is a fairly old topic but I ran across this same issue in Linux which will probably be the same issue on OSX as well. Every time I tried to add a directory to the Post-Processing Scripts Folder setting it would remove it after leaving the page. So I opened up the /.sabnzbd/sabnzbd.ini file and noticed the path for script_dir had two set of quotes in it ("") signifying no value. So I manually edited the .ini and saved it and restarted the daemon and it worked. So it appears the no value was overriding anything you tried to type via the UI. I also noticed other no value settings in other settings within the UI so this may be the case for other settings that have a similar behaviour.
Re: sabnzbd keeps losing post processing scripts folder - on
Two causes for those problems:YankeeUK wrote:I know this is a fairly old topic but I ran across this same issue in Linux which will probably be the same issue on OSX as well. Every time I tried to add a directory to the Post-Processing Scripts Folder setting it would remove it after leaving the page. So I opened up the /.sabnzbd/sabnzbd.ini file and noticed the path for script_dir had two set of quotes in it ("") signifying no value. So I manually edited the .ini and saved it and restarted the daemon and it worked. So it appears the no value was overriding anything you tried to type via the UI. I also noticed other no value settings in other settings within the UI so this may be the case for other settings that have a similar behaviour.
1) webbrowser caching stuff
2) permission problems on sabnzbd.ini

