unraid n00b here so please be gentle

 

I'm running rc2 and have a cache drive which is where I store config and work directories for sab,CP,SB etc.

I'm having problems with sab though, each time I restart sab (/etc/rc.d/rc.sabnzbd stop then start or powerdown etc) I loose config and the sab setup wizard runs when I connect to it.

 

While running I can see my config getting written to /mnt/cache/sabnzbd-data/config.ini and it creates .bak file too.  I dont see any hints in logs, in fact all looks fine:

2012-05-13 16:47:24,576::INFO::[sABnzbd:1222] Arguments = "/usr/local/sabnzbd/SABnzbd.py", "-d", "-s", "0.0.0.0:8080", "--config-file", "/mnt/cache/sabnzbd-data", "--pid", "/var/run/sabnzbd", ">", "/dev/null", "2>&1"

2012-05-13 16:47:24,576::INFO::[sABnzbd:1235] Read INI file /mnt/cache/sabnzbd-data/sabnzbd.ini

2012-05-13 16:47:24,577::INFO::[__init__:870] Loading data for bookmarks.sab from /mnt/cache/sabnzbd-data/admin/bookmarks.sab

2012-05-13 16:47:24,578::INFO::[__init__:870] Loading data for rss_data.sab from /mnt/cache/sabnzbd-data/admin/rss_data.sab

2012-05-13 16:47:24,578::INFO::[__init__:870] Loading data for totals9.sab from /mnt/cache/sabnzbd-data/admin/totals9.sab

2012-05-13 16:47:24,578::INFO::[postproc:89] Loading postproc queue

 

 

 

 

more than likely the mover script its moving the directory somewhere, configure your settings to use /mnt/cache/.sabnzbd and the mover will ignore your .sabnzbd dir

 

Myk

 

Or configure that share as "cache only" so mover won't touch it and you won't need to start the name with a ".".

ahh,  I have it configured as a share but configured as "both" thinking it would leave the files on the cache drive as well as protecting it all..  Is this a bad thing?

unraid n00b here so please be gentle

 

I'm running rc2 and have a cache drive which is where I store config and work directories for sab,CP,SB etc.

I'm having problems with sab though, each time I restart sab (/etc/rc.d/rc.sabnzbd stop then start or powerdown etc) I loose config and the sab setup wizard runs when I connect to it.

 

While running I can see my config getting written to /mnt/cache/sabnzbd-data/config.ini and it creates .bak file too.  I dont see any hints in logs, in fact all looks fine:

2012-05-13 16:47:24,576::INFO::[sABnzbd:1222] Arguments = "/usr/local/sabnzbd/SABnzbd.py", "-d", "-s", "0.0.0.0:8080", "--config-file", "/mnt/cache/sabnzbd-data", "--pid", "/var/run/sabnzbd", ">", "/dev/null", "2>&1"

2012-05-13 16:47:24,576::INFO::[sABnzbd:1235] Read INI file /mnt/cache/sabnzbd-data/sabnzbd.ini

2012-05-13 16:47:24,577::INFO::[__init__:870] Loading data for bookmarks.sab from /mnt/cache/sabnzbd-data/admin/bookmarks.sab

2012-05-13 16:47:24,578::INFO::[__init__:870] Loading data for rss_data.sab from /mnt/cache/sabnzbd-data/admin/rss_data.sab

2012-05-13 16:47:24,578::INFO::[__init__:870] Loading data for totals9.sab from /mnt/cache/sabnzbd-data/admin/totals9.sab

2012-05-13 16:47:24,578::INFO::[postproc:89] Loading postproc queue

You are starting SAB on port 8080.  That is the SAME port that unMENU uses.  If you have it installed, neither will work properly with both trying to use the same port.

 

Joe L.

I do run unmenu but it's on port 90.

 

Should I not use the "both" setting for the cache drive directory?