check your permissions for the TV directory, its the only thing I can think of that would stop it from accessing. I didn't see anything of use in the log

I'm not sure where the unmenu script saves everyything, but I believe it puts everything in the install directory, if not it will require a little more investigation.

 

Thanks, that pretty much worked, except for CP.  I tried to find the files, they weren't were I thought they were so I just re installed and I don't keep any history on CP.

 

One thing I found is that I had to create the data directory manually and chmod / chown them appropriately to get the install to finish.  Without doing that the intall would just sit there doing not much.

 

So all up now, thanks.

oh heck its never ending...some thing messed up with my server and I had to hard reset it... its parity checking now.. but now my sabtosick.py script isn't showing up or working. I have the path defined in the folders setting, but on categories drop down for scripts I don't see them all

 

-=Jason=-

I'm going to be upgrading my cache drive and i'm worried about losing settings for SickBeard/SABnzbd.

 

In the past, if I ever moved the SickBeard/SABnzbd folders, SABnzbd would no longer show "sabtosickbeard.py", no matter what I tried. I'm well aware how to set it all up, but it seems like moving the directories bugs something out. The only way i've found to fix this issue after it happens is to completely wipe SickBeard/SABnzbd and start from scratch. Even running permissions on the files did not fix it, and I made sure they had the same permissions before and after the transfers. I never figured it out, I just stopped moving them around.

 

Now I need to transfer these off my cache drive before I wipe it and re-add a new cache drive, then I will transfer them back. I'm 99% sure I will encounter this again and I was wondering if this is common and if there is a better workaround then starting from scratch.

 

Side note:

Influencer, I want to try your up to date plugins.. but I don't get github. All I can download from there is "darkstat-3.0.712-i486.txz", and I just want SickBeard/SABnzbd.

 

oh heck its never ending...some thing messed up with my server and I had to hard reset it... its parity checking now.. but now my sabtosick.py script isn't showing up or working. I have the path defined in the folders setting, but on categories drop down for scripts I don't see them all

 

-=Jason=-

 

Just read this after posting, that's pretty much my issue whenever I re-run permissions or move the folder. I've found no way to fix it other than starting from scratch and let the plugin re-create all the folders. I'm signed in under "Nobody", and run the plugin as "Nobody". I have no users on my unRAID other than root.

 

Hopefully someone can chime in on a easier fix.

tyrindor, while browsing 'master' branch, click on the ZIP icon towards the top.

Fresh install of everything, set data dir to /mnt/cache/.Services/Sabnzbd, it has created the directory as root, server freezes at loading.

Fresh install of everything, set data dir to /mnt/cache/.Services/Sabnzbd, it has created the directory as root, server freezes at loading.

 

Running as 'root' is likely the problem. You should run it as the default 'nobody', 5.0 doesn't like signing in as "root" to access your server (minus webGUI). In RC4, he is making that impossible to do because so many users did that in pre-5.0. Make sure you make a new user and tell windows (or whatever you are using to access your data) to use that user, or leave the fields blank and it will use "nobody", which is the easiest solution but requires your user shares to be set to public. So don't use this method unless you trust everyone on your network.

 

Do this:

1. Start fresh

2. Make sure Enabled SABnzbd to set to "No"

3. Set installdir to "/mnt/cache/.Services/Sabnzbd"

4. Put checkbox in datadir

5. Set datadir to "/mnt/cache/.Services/Sabnzbd"

6. Keep user as "nobody"

7. Set Enabled SABnzbd to "Yes"

8. Hit apply and wait for it to finish

 

oh wow.... I think the beta was seriously messing me up....

1.with server up and running and no plugins started

2.renamed sabnzbd folder to sabnzbd.bak

3.changed install directories of sab,sick,CP to /mnt/cache.apps/xxx

4. told sab NOT to install beta

5. fired it off.

 

after shutting sab down I copied my config.ini file over and all my settings seem to copied over just fine.

 

all systems are a go for starting sab, sick and CP, now sure how powering down is going to work or not..

 

-=Jason=-

 

EDIT: FML scrips are not working at all.. I have defined my script folder, yet in categories I have no scripts to choose from

 

a second EDIT:.... turns out for some odd freaking reason I have to chmod +x  myscriptname.py  where myscriptname= what ever the name of your script is for me it was sabToSickBeard.py

Sorry I have been absent, haven't had a free second to really say/do much here the past few days.

 

FloMaster, linux is designed with security in mind(atleast security from the user) so scripts generally have to be chmod+x'd to work. And sab won't pick up a script if its not allowed to be executed as...well...that'd be kinda pointless,

 

I run the beta's and haven't had an issue. BUT, as with all software, it is best practice to use the last known stable first, confirm everything works, then upgrade/try the beta. This way you know that everything should run correctly, and if there's a problem, its most likely the beta causing it.

 

I will give you an award for patience, although I notice from your text tone you are/were getting quite agitated, you didn't throw the server out the window. If I had as much trouble getting it all set up as you have the past few days, I'd have sold the server for scrap metal by now(but only if they allowed me watch them crush/shred/mutilate/melt the server).

 

I should have said something earlier but didn't think about it, always run your applications as nobody unless you have an explicit and very good reason to run it as root. Root is like the Admin account on windows, its there if its needed, but shouldn't be used on a day-to-day basis. Which is why its hidden by default and requires a bit of cryptic command line action to enable. 5-beta's do NOT like root user at all, and it creates nothing but headaches for file sharing. Wait until you download a bunch of stuff and try to play it on your PC, and don't have access to anything.

 

My suggestion, chown your user shares now to nobody:users, make sure all apps are running as nobody, and chown their directories as well. Chmod the app directories to a minimum of 764(user=rwx, group=rw, others=r), user shares to a minimum of 760(though I still would recommend 764). Those settings I find to be a good middle ground, not the tightest security but then again you should be able to do just about anything you need with those permissions(and unraid shouldn't be accessible from the internet anyway).

 

Those settings should avoid just about all of the permission problems you could face. If you add or move files while logged in as root on telnet, chown them before you exit as they will be owned by root and you WILL forget until you try to access the file, believe me, I know from many experiences,

Yeah I need to  a nobody user asap I have been logging add root on putty and doing everything. I think I have all my shares in working order. I ran the fix permissions thing on the server but not sure if it finished out or not.  I copied my  fro my old folder but some how the root must have messed it up.

 

EDIT:looks like i have to stop the array to add a user. I'll have to wait until the wife is done watching her Tv show.

 

-=Jason=-

 

edit: been trying to search for more info on user account.. I created one but can't log into it via putty as soon as I type in my password the putty session is closed. I use putty all the time and if only root can log in it seems I have a lot of extra work for myself. chmoding every file I move or touch.

It's all a learning experience. Better go through the trouble now instead of in the future when there could be many more directories or files affected. I believe you can inky log into telnet from root. Not entirely sure. Just best to remember if you do to chown the file afterwards. With everything set to run as nobody and everything set up right it should become a hands free operation. My server does everything in its own. Of course I had one up in that as I've had a basically identical setup on another os so there was very little learning curve when I switched to running them on unraid.

ok I think I finally have it tinker free for the time being... so long as it doesn't need a reboot in which case who knows if it will shut down correctly  or get hung up from the plugins.

 

but I can log in via my user name I just followed this little trick

You can give another user shell access using the command below:

 

usermod -s /bin/bash insertusernamehere

 

 

 

Give that a try and see how you get on

 

For those that have CP running from an array disk instead of a cache drive, please try the plugin from the "Influencer" branch.

 

I added a line testing if the array is mounted before installing the plugin. It SHOULD do this already with the disks_mounted event, hopefully this fixes problems with the array getting stuck in a "starting" loop.

 

Of course, it may break the install too so backup your data dir first

Hey any chance of adding plex to this nice collection of plugins for the ultimate media experience?  A new unraid build was just released as well.

Plex has already been added, there are plug-ins in the forums and also a slightly modified version on our github.

I'm not sure what happened on my end.  I am pointing SABnzbd and Sickbeard to my cache drive as my data directory.  The plugins installed fine and I got it all configured and going.  Then I needed a reboot, upon reboot, SABnzbd starts, but I also noticed that my unraid web page the site on port 80 is no longer available.  If I remove the plugin, my webpage is back.  I'm running this on rc4.

I haven't upgraded to rc4 yet, so not 100% if this is an issue going forward, but I can't think of anything that would cause that.

 

Check your sabnzbd.cfg in /boot/config/plugins/sabnzbd/(flash drive /config/plugins/sabnzbd/) and make sure that the port didn't get changed to port 80 by accident.

I haven't upgraded to rc4 yet, so not 100% if this is an issue going forward, but I can't think of anything that would cause that.

 

Check your sabnzbd.cfg in /boot/config/plugins/sabnzbd/(flash drive /config/plugins/sabnzbd/) and make sure that the port didn't get changed to port 80 by accident.

 

I did a quick check and it says port 9090.

 

 

Post a syslog with sabnzbd installed.

 

cp /var/log/syslog /boot/syslog.txt

 

I'll have to update to RC4 this weekend and see if its an issue....

 

Any other users already updated and experiencing similar issues?

Post a syslog with sabnzbd installed.

 

cp /var/log/syslog /boot/syslog.txt

 

I'll have to update to RC4 this weekend and see if its an issue....

 

Any other users already updated and experiencing similar issues?

 

it looks like the sabnzbd start is hanging, which doesn't let the rest of unraid to initialize

is it because my cache drive isn't ready?

 

 

thanks for your help!

syslog.zip

Do you have it set to install beta? I think there is an issue with it right now... I run the stable and haven't had an issue. Try running stable for now

 

EDIT: To clarify, I don't think its an issue with the beta itself, so much as its not being downloaded properly. I haven't had a chance to look at it(had to factory reset my phone and trying to get it set up again, )

Do you have it set to install beta? I think there is an issue with it right now... I run the stable and haven't had an issue. Try running stable for now

 

EDIT: To clarify, I don't think its an issue with the beta itself, so much as its not being downloaded properly. I haven't had a chance to look at it(had to factory reset my phone and trying to get it set up again, )

 

originally i was using the old 0.4c-bw version.  i've now switch to the latest on the ww site, 05-29 release.  I did choose the stable version and when enabling the plugin, i notice that it hangs here as well, when i hit apply to enable the plugin

 

no

installing latest Version (0.6.15)

Starting sabnzbd: sudo -u nobody python /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:9090 --config-file /mnt/cache/.custom/apps/sabnzbd --pid /var/run/sabnzbd > /dev/null 2>&1

 

 

It just spins and never ends.  If I go to the page again it still has Status: Stopped.  So it's freezing here, but I am still able to access sabnzbd from port 9090 when I hit it on the browser

Ok so its installing but from the webgui its hanging. Are you using https? Since you have the port set to 9090 and its appearing there everything should work fine. Post the output of

 ls -l /var/run/sabnzbd/ 

 

I won't be able to reply for the rest of the night but it'll give me a starting point for tomorrow.

 

Sent from my HTC Vivid[/code]

 

Ok so its installing but from the webgui its hanging. Are you using https? Since you have the port set to 9090 and its appearing there everything should work fine. Post the output of

 ls -l /var/run/sabnzbd/ 

 

I won't be able to reply for the rest of the night but it'll give me a starting point for tomorrow.

 

Sent from my HTC Vivid[/code]

 

It was enabled in my sabnzbd configuration.  Once i disabled it, it just flows through and it's working now.  I continued more troubleshooting as you had me go down looking at the /var/run path, the ssl was configured for 9080

 

root@nas:/var/run/sabnzbd# ls -la /var/run/sabnzbd/
total 4
drwxrwxrwx 2 nobody users 0 2012-06-07 21:11 ./
drwxr-xr-x 6 root   root  0 2012-06-07 21:11 ../
-rw------- 1 nobody users 5 2012-06-07 21:11 sabnzbd-9080.pid

 

thanks for all your help!

No problem. That's a known issue I plan in dealing with soon. One option is to set the port in the plugin settings to the same that https is configured for. I'll have a more elegant solution up soon.

 

Glad its all working now, its time for bed

4 am calls early

Sent from my HTC Vivid