Tybio

That makes perfect sense to me, I've updated the recommended port for CouchPotato to 8083 I think we should add a bit more detail about port assignments, I'm going to expand the section under the SABnzbd install to let people know what impact changing the port will have.

I think the issue with SABnzbd was isolated, most of us haven't had a problem with permissions. It is solid in terms of installing them, but the port situation is still in flux. Just make sure you have unMenu turned off while doing the install process, then use the various UIs to change the servers ports before you fire up unMenu (if you even use it). That's the only area that we are still working on that I know of

Someone gave the steps in this post: http://lime-technology.com/forum/index.php?topic=2903.msg100592#msg100592 I haven't tried them, so I haven't put them in the wiki because I don't know if they will work.

Heh, all good! Now we can get back to the topic of setting things up so unMenu and SABnzbd living in peace

They are being included in the user share until the mover script can move them onto the array. Unless a directory starts with a ., it is considered to be a "cache" of data waiting to be written to the user share. mkdir /mnt/cache/.downloads/<whatever>

The only way to over-ride the default port is to start with the -s switch. I've installed it on 3 different OSs this morning and the initial configuration shows up on port 8080. You can test this yourself on a Windows, OS X or Linux box...with a fresh install, as I've done.

Ok, I followed the link to your walk-trough, and you did this: # If Cache drive is online, start SABNzbd if [ -d /mnt/cache ]; then # Start SABnzbd and sickbeard installpkg /boot/custom/SABnzbdDependencies-1.3-i486-unRAID.tgz python /mnt/cache/.custom/sabnzbd/SABnzbd.py -d -s 192.168.1.6:88 nohup python /mnt/cache/.custom/sickbeard/SickBeard.py & fi The command line option -s <address>:<port> overrides the default, and shouldn't be called every time SABnzbd is started...well, it can, but there is no point in it as the port should be controlled via the config file so it can be changed from the UI rather than having to change the go script. That's my opinion mind you. So the default port is 8080, but the instructions you used forced it to be 88. We should stay away from any port under 1024 for previously stated reasons.

The point is that unMenu uses 8080, and the default SABnzbd port is 8080. Not sure what to say, I just installed it on Windows, OS X and Linux and it defaulted to port 8080.

Odd, every time I've installed it it's been 8080. And that's the port the documentation states: http://wiki.sabnzbd.org/configure-general Installing to port 88 would require root to start it (Even if root starts it as user nobody) on UNIX. That's generally frowned upon, most if not all servers like SABnzbd will use a port over 1024 by default.

Nice additions all! We do need to sort out the conflict between unMenu and SABnzbd, I've put in some proposed port values, also tracking other services in use (But clearly I don't know all of them!) in a table at: http://lime-technology.com/wiki/index.php?title=Install_Python_based_servers#unRAID_Common_port_list These are the ports I used, and I decided to leave unMenu on 8080 as it was very easy to change the SABnzbd port and I was more confidant in doing that than moving unMenu. However, I'd like us all as a group to find a good recommendation so the wiki page can make sense from section to section.

Did you use the command prompt to run make_bootable.bat? It sounds a bit like you did it from Explorer again...just thought I'd ask

Try checking the BIOS, some motherboards require you enabling boot from removable devices, or if it is older you might even need to force it to see the USB stick as a drive, then put it into the boot sequence.

Because I haven't done it, so I can't be sure the steps will work, and I have no need to set it up myself. I try not to guess on documentation.

Fantastic updates to the wiki page for those who've been adding. I think we are almost ready to start sending people that way for initial questions. I've added a header for config options to let the cache drive sleep...I've not done it yet, so hopefully someone will update it .

I have user level security and no problem with root running the python servers.

I just tossed one together: http://lime-technology.com/wiki/index.php?title=Install_Python_based_servers Obviously it needs a lot of work, so get out there and contribute if you can! I haven't even started on the configuration section, but at least the core of the install is recorded .

I prefer to start them all as Daemons so they function to POSIX standards: /mnt/cache/.custom/SABnzbd/SABnzbd.py -d /mnt/cache/.custom/sickbeard/SickBeard.py --daemon /mnt/cache/.custom/couchpotato/CouchPotato.py -d Keeps it all nice and clean, and means that they can operate without the baggage of a shell or whatnot .

You can also edit /mnt/cache/.custom/sickbeard/config.ini and define the cache and log directory so they are always absolute. Also, start SickBeard like this now: /mnt/cache/.custom/sickbeard/SickBeard.py --daemon And you don't have to mess with nohup or forking into the background (&) at all.

I was running 4.5 (I believe, it's early) until yesterday when I moved up to 4.7Beta1

That's odd, I'm running SABnzbd as root along with Sick Beard and CouchPotato, both of which move the files to the shares. SABnzbd doesn't do the moving, so having that run as another user wouldn't do anything for the permissions. I'm also seeing the files that Sick Beard and CouchPotato put in place on the shares without issue, and they are owned by root: drwxr-xr-x 1 root root 256 Jan 18 13:56 ./ drwxr-xr-x 1 root root 3.4K Jan 15 12:11 ../ -rwx------ 1 root root 46K Jan 18 13:56 Wanted.jpg* -rw-r--r-- 1 root root 6.6G May 3 2010 Wanted.mkv -rwx------ 1 root root 5.7K Jan 18 13:56 Wanted.nfo* Perhaps there is some other configuration or issue that's causing root owned files to not be seen on shares?

Unraid 5 will have a plugin system, what that entails is still in flux but you can take a look at the Beta forums for more information. As to installing unmenu, I too did without it for years...but after installing it last night (Took putting one file on the flash and running one command, not exactly something that you have to be a linux guru to do) I'll not be without the abilities it gives again. Items I enabled in under 15 minutes once unmenu was installed: 1> Swap file, gives Linux swap area (I used a cache drive) 2> Email allerts 3> Bandwidth Monitoring

Perfect, I didn't know there was a package for a swap file in unmenu!

Greetings, I was wondering if there was any way to use the cache disk to hold a swap partition? The reason for this is that I'm running SABnzbd, Sick Bear and CouchPotato and the 2G of RAM that I thought was more than enough a few years back is quite gobbled up. It would be handy to create a 4G swap partition on the cache disk and let things spill over into that rather than have processes just bomb out.

I'm looking at it, but there are only 93G of files in lost+found and disk usage went down by ~450G So I'm going to see if I can get valid data off that bad drive before I RMA it.

Lost about half my data...not...good really. Now I need to figure out how to know what data was lost...going to try to get the old bad disk working enough to get a file list off of it I suppose . But that's another issue, this one is resolved. Thanks Joe!