No, the new users only apply to the SMB shares.  What I am saying is that you should not manipulate data via disk shares when logged into the server as root.

 

 

If you log in via putty as root and manipulate data it will have the same effect.  After everything you do you will need to reset the permissions/etc for what you just did.  I have used and do use MC to move/copy files and there should be a "preserve attributes" box that can be checked.  Use that when possible and the move/copy should not change the permissions.

 

Fair enough - the only times I use the putty log in to move files is when Windows insists on copying a file and deleting rather than actually moving, meaning it takes a long long time. I didn't know Midnight Commander had that functionality, and I'll use it in future. I'm still rather confused about what happened with the Sick Beard .py file whilst I was away though.

 

EDIT: It seems that the new permissions script makes my sabToSickBeard.py non-executable. No idea why though

probably because it is expecting all files on the server to be only media files.  It is setting the perms for all files to something that is not executable.

My sabToSickBeard.py file is on my cache drive and works fine. Maybe unRaid doesn't mess with permissions on the cache drive?

My sabToSickBeard.py file is on my cache drive and works fine. Maybe unRaid doesn't mess with permissions on the cache drive?

 

Mine is on the cache drive too, but the newperms changes it anyway.

 

I've also found that files downloaded by couchpotato and sick beard often have the wrong perms after renaming, but not always. I'm having to run the newperms script on a daily basis at the moment

 

The plugins are all running as nobody, does anyone know what could be causing this?

set the download perms in SAB to 770

Hi,

 

looks like there is a conflict between the plugins and the "simple features plugin". Like stated above the plugins start and are available after enabling them through the unraid web admin interface but then the admin interface of unraid is inaccessible.

I can't seem to get the install/data directory working correctly. The only one I've successfully got up and running is sickbeard, but whenever I reboot, all of the configuration files are blown away. Not sure why

 

install dir: /usr/local/sickbeard

data dir: /mnt/cache/.sickbeard

 

I tried getting couchpotato working as well, but it simply won't run with a similar set up. Seems like the config files are getting deleted out of the install files (probably moved to the data dir) and can't be found.

 

What am I doing wrong?

 

On a side note, has anyone considered using a flash drive for this stuff? Would completely prevent disk spin-up. I know people say that you reduce the life of the flash drive, but if you aren't using your boot flash, shouldn't be a big issue, no?

ZestyChicken:

install dir: /usr/local/sickbeard

This is on the ram disk and gets erased after every reboot

ZestyChicken:

install dir: /usr/local/sickbeard

This is on the ram disk and gets erased after every reboot

 

I understand that. But shouldn't the way it works is all the static data such as config.ini gets saved on the data directory and the install directory is reinstalled on reboot with the files that don't really change.

 

On a side note, what are people using for the log directory? I have been using "/var/log" which I have to change the permissions on to be able to access with the nobody user. Freaking unRAID permissions are a mess...

On a side note, what are people using for the log directory? I have been using "/var/log" which I have to change the permissions on to be able to access with the nobody user.

use a folder inside /var/log

 

Freaking unRAID permissions are a mess...

No they are not.  I have my production system running 5.0b6a and have no issues.  Once you understand the permissions they all make sense.

 

use a folder inside /var/log

 

 

So you are saying "/var/log/sickbeard" ?

 

This will resolve everything?

 

use a folder inside /var/log

 

 

So you are saying "/var/log/sickbeard" ?

 

This will resolve everything?

/var/log/sickbeard, /var/log/sabnzbd, etc.  It is what I default to for all of my unMenu packages.  From there the permissions (nobody:users) can be set on the sickbeard and sabnzbd folder without issue.  You should NEVER be changing the permission on /var/log itself.

/var/log/sickbeard, /var/log/sabnzbd, etc.  It is what I default to for all of my unMenu packages.  From there the permissions (nobody:users) can be set on the sickbeard and sabnzbd folder without issue.  You should NEVER be changing the permission on /var/log itself.

 

Thanks for the reply.

Hello,

 

    I just wanted to ask a quick question, i have installed sab, sick, and Couch as said in the post. There is one thing that i would like to understand.

 

    When i power down, i have took the array offline first then powered down, however on reboot, all the settings for ALL three had returned to there default. Is there something i should or shouldnt be doing. As this is starting to get a little annoying!

 

Thanks

Found my problem. forgot to:

chmod +x /usr/bin/python

is it possible to change the owner ship of sabnzbd.cfg in the plugin folder from root:root to nobody:users?

I always get:

chown: changing ownership of `/boot/config/plugins/sabnzbd/sabnzbd.cfg': Operation not permitted

seems like this is another problem. because running the plugins as root and on the flash drive works

Help!!!

 

Hi all. Having problems again.

 

i recently added a disk to my server so was forced to power down and reboot.

 

upon reboot sickbeard just doesnt want to start. Again!

 

i have read this thread over and over but nothing seems to work. Its not as simple as refreshing the page.

if i enable SB through the webGUI it hangs indefinitely. when i do a ps aux or ps -ef and kill the process the webGUI comes back to life instantly. if i try to start SB from command line then it moans about SUDOERS permissions i have opened the SUDOERS file with visudo and saved it (while logged in as root). but this doesnt help it still doesnt like the permissions.

 

any ideas?

 

tell me what to post  in terms of logs to help you guys to help me

 

Thanks

HI Redstorm,

 

Sounds like the same problem I've experienced. I am still tracking it down. What works for me is the following combination:

install dir: usr/local/SB

data dir : mnt/cache/usenet/SB

start as: root

 

nobody and/or install dir on cache drive do not work for me.

well I've just rebooted the server and as usual the webGUI hangs when i start the array.

 

But this time instead of killing the sickbeard process i navigated to the /etc folder and did this

 

chown nobody:users sudoers

 

and SB came up no probs and the webGUI unfroze. i did this as i discovered that when i did a ls -l sudoers it was owned by root

 

this fixed it for me manually but can anyone here tell me how to fix it permanently so it doesn't happen again please?

 

thanks

 

 

I am still looking for a response that answers the question of were to install these Apps/Plugins so the configuration doesn't get wiped out every reboot.  I have tons of RAM and want to run them in RAM though.

 

I am still looking for a response that answers the question of were to install these Apps/Plugins so the configuration doesn't get wiped out every reboot.  I have tons of RAM and want to run them in RAM though.

Here is what I did. I upgraded from 4.7 to 5 b14. I followed the upgrade instruction including running the "New Permissions" utility. After that was done I then installed the plugins one at a time. I used the following paths:

 

SABnzbd:

Install path:/usr/local/sabnzbd

Data Directory:/mnt/cache/.sabnzbd

run as user:nobody

 

SickBeard:

Install path:/usr/local/sickbeard

Data Directory:/mnt/cache/.sickbeard

run as user:nobody

 

CouchPotato:

Install path:/usr/local/couchpotato

Data Directory:/mnt/cache/.couchpotato

run as user:nobody

 

Thereby the apps are running from RAM but the settings are preserved on the cache drive. Maybe I just got lucky, but I have no permission issues.

^^^

Sweet!!!  I will try this right now.

Quick question, when shutting your server down, do you have to stop all three applications so that it doesnt reset them. As i have them in the same locations. However the last time i shut down my server it reset them back to there default settings??

I've only shut down once since I installed them, as my server sleeps when not needed. I did manually shutdown each application before I shutdown the server. I've not tested it otherwise or looked into modifying the shutdown process to cleanly shut them down (that is if the plugin doesn't already take care of that).

I've only shut down once since I installed them, as my server sleeps when not needed. I did manually shutdown each application before I shutdown the server. I've not tested it otherwise or looked into modifying the shutdown process to cleanly shut them down (that is if the plugin doesn't already take care of that).

 

 

Ok ill keep that in mind, as im going to need to put in a new HDD soon, and i took it down once before and it deleted everything. However i didnt stop each application first.