Hi folks,

 

here are some new Plugins to install and control SABnzbd+, SickBeard and CouchPotato.

Dependencies necessary to run these apps will be installed automatically.

 

If the app isn't found in the configured directory, the latest version will be downloaded and installed.

All the apps will be started, when the array is started, if they were configured and enabled previously.

 

The configured user will automatically be created, if it doesn't exist. (but i recommend using "nobody" or "root")

Additionally SABnzbd has an easy update function in the plugins webgui.

 

These Plugins uses the new Plugin Installer system, so UnRaid v5b11+ is a requirement.

 

The installation is quite simple, just download the plg files for the plugins you want to use and copy them to your flash drive into the config/plugins folder. Then reboot your server or run "installplg /boot/config/plugins/<NAME OF THE PLUGIN>.plg"

 

Download:

http://unraid.benjaminwaller.de/sabnzbd/sabnzbd-0.4c-i468-bw.plg

http://unraid.benjaminwaller.de/sickbeard/sickbeard-0.4a-i468-1bw.plg

http://unraid.benjaminwaller.de/couchpotato/couchpotato-0.5-i468-bw.plg

 

Changelog for SABnzbd+:

0.1 initial release

0.2 added Port configuration for sickbeard and couchpotato, nicer select for user and some bug fixes

0.3 added support for extra data dir, install to ramdisk, drop of sabnzbddependencies package, nicer shutdown for sabnzbd

0.4 fixed a bug, when installed to ramdisk

0.4a updated to multicore par2 (thanks prostuff1 for package and url)

0.4b workaround if shutdown via apikey doesn't work

0.4c fixed included updater (before the version number wasn't read correctly if longer than 3 numbers)

 

Changelog for Sickbeard:

0.1 initial release

0.2 added Port configuration for sickbeard and couchpotato, nicer select for user and some bug fixes

0.3 added support for extra data dir, install to ramdisk, drop of sabnzbddependencies package, nicer shutdown for sabnzbd

0.4 fixed a bug, when installed to ramdisk

0.4a added sqlite dependency package

 

Changelog for Couchpotato:

0.1 initial release

0.2 added Port configuration for sickbeard and couchpotato, nicer select for user and some bug fixes

0.3 added support for extra data dir, install to ramdisk, drop of sabnzbddependencies package, nicer shutdown for sabnzbd

0.4 fixed a bug, when installed to ramdisk

0.4a added sqlite dependency package

0.5 added installer function to webgui (used as an updater), settings are saved when plugin is disabled.

 

ToDo:

fix a hang, when starting sickbeard (workaround: wait some seconds, then reload page)

update of couchpotato doesn't work, if installdir and datadir are on different disks. (this is a bug inside of couchpotato!) (workaround: stop couchpotato and click the install button)

 

WARNING:

Don't use the update function of couchpotato. It WILL break your install (see todo above)

since version 0.5 of the plugin, you can use the install button in the webgui to reinstall the latest version of couchpotato

 

Screenshots:

can we get a port setting for SickBeard and CouchPotato please?

 

I don't use the default port for any of those apps, so setting it the first go around would be nice.

 

 

the ports of sickbeard and couchpotato can be configured in their own guis.

the plugin will read the app's config file and give you always the correct link.

 

i don't like messing around in the config file of an other app. especially if it only a few clicks to change the port after installation.

but, hmm, i will have a look at it, how it could be done safely

 

btw. if you already have an installation of these apps, simply enter that directory in the plugin and nothing else needs to be changed.

the ports of sickbeard and couchpotato can be configured in their own guis.

the plugin will read the app's config file and give you always the correct link.

 

i don't like messing around in the config file of an other app. especially if it only a few clicks to change the port after installation.

but, hmm, i will have a look at it, how it could be done safely

 

btw. if you already have an installation of these apps, simply enter that directory in the plugin and nothing else needs to be changed.

I understand that, but I might have stuff running on that port already, I need to specify the port up front (like I allow for my unMenu pakcages of these apps) so I can get to the app.

 

 

Also, the only other thing I would like to see is that the Run as user: be a dropdown.  Default it to nobody since we are running on 5.0bX and then give root and other.  If they select other, show a text box where they can specify the name of the user.  Maybe even try a check to see if the user exists and show that to the user, to make sure they did not type the name wrong.  Some Javascript confirm type stuff should work.

 

And last but not least... this is all personal preference... but I would prefer to see the use of the SABDependencies package dropped.  I understand what it does, but I would prefer to see the common files between SABnzb, SickBeard, and CouchPotato split out.

Someone's been busy the last few days. Good work on getting this started.

 

Peter

 

Some issue with CouchPotato

 

 

Warning: file_get_contents(/config.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/couchpotato/couchpotato.php on line 6

 

And enable CouchPotato , it's redirect me to tower ??

Some issue with CouchPotato

 

 

Warning: file_get_contents(/config.ini): failed to open stream: No such file or directory in /usr/local/emhttp/plugins/couchpotato/couchpotato.php on line 6

 

And enable CouchPotato , it's redirect me to tower ??

 

hi,

that warning will be fixed in the next version (coming later today, working on several requested features)

 

what do you mean, redirect to tower?

after you enabled it, you will still be at the plugin page.

but there should apear a link, which directs you to tower:port (default port is 5000)

 

the new version (as said, coming later) will feature a port select on the plugin page.

Its redirect me to tower, and no port is on the link when I click on couchpotato is running

did you enter an installation path? can you check, if the folder was actually created?

@ Benni-chan

 

Nice work, you have been busy 

 

just a question:

 

Why place the Sickbeard, Couchpotato icons under the tab ''network services'' together with AFS , SMB etc ?

 

and not under the tab ''Utils'' / User applications ?

 

 

 

 

 

Why place the Sickbeard, Couchpotato icons under the tab ''network services'' together with AFS , SMB etc ?

and not under the tab ''Utils'' / User applications ?

 

i've put them there, because Tom but his "official" slimserver plugin also under network services. and these apps are a kind of network service

 

but maybe i'll change that with one of the next versions. actually i'm waiting for some documentation of the plugin system. maybe tom will tell us his plan for structuring these apps (if he has one)

 

maybe an extra Usenet or Download section on the settings tab.

Indeed, i now installed slimserver and it also appears under this same section. You're both right.

 

I was wondering because Plex appears under the tab user applications.

 

 

 

The Plex Plugin was created before Tom released the plugin installer. so nobody knew at that time, what Tom's plans were.

 

Just pushed a new version of all three plugins.

Now the port can be configured for all three apps and the user select is somewhat nicer

also fixed a few little bugs

 

to update, delete the old plugin and download the new one.

then restart your server (you have to restart, because otherwise the files wouldn't be updated since they already exist...)

 

or delete /usr/local/emhttp/plugins/sabnzbd, /usr/local/emhttp/plugins/sickbeard and /usr/local/emhttp/plugins/couchpotato

also delete /etc/rc.d/rc.sabnzbd, /etc/rc.d/rc.sickbeard and /etc/rc.d/rc.couchpotato

then install the plugins via installplg /boot/config/plugins/<NAME>.plg

Hi Benni-chan,

 

Nice work.

But I hope I can give you some suggestions.

 

To Start and Stop SABnzbd you can use something like that:

 

SABnzbd_start() {
# no-op if not enabled
echo Starting SABnzbd.
if [ "$SERVICE" != "enable" ]; then
	echo SABnzbd not enabled.
	return
fi

if [ -d $SAB_CONFIG_DIR ]
	then
		if [ ! -z $(ps -ef | grep SABnzbd.py | grep -v grep | awk '{print$2}') ]
		then 
			echo SABnzbd is allready running.
			exit 1
		else
			echo SABnzbd is NOT running so I am starting it!
			cd $SAB_CONFIG_DIR
			chown -R nobody:users .
		fi
	else
		mkdir -p $SAB_CONFIG_DIR
		cd $SAB_CONFIG_DIR
		chown -R nobody:users .
fi
usermod -s /bin/bash nobody > /dev/null 2>&1
/bin/su nobody -c "/usr/local/SABnzbd/SABnzbd.py --daemon --server $SAB_HOST_IP:$SAB_PORT --config-file $SAB_CONFIG_DIR > /dev/null 2>&1"

}


SABnzbd_stop() {
echo "Shutting down SABnzbd."
if [ -d $SAB_CONFIG_DIR ] && [ -f $SAB_CONFIG_DIR/sabnzbd.ini ]
	then
		APIKEY=`grep -w api_key $SAB_CONFIG_DIR/sabnzbd.ini | cut -d " " -f3`
	else
		echo no Config File found.
		exit 1
fi
/usr/bin/wget -q --delete-after "http://$SAB_HOST_IP:$SAB_PORT/sabnzbd/api?mode=shutdown&apikey=$APIKEY"
}

 

With this you can have SABnzbd in the RAM and the Log and Downloads on $SAB_CONFIG_DIR.

And the Stopping is going more the "SABnzbd Way".

 

I tried it with the PID way too, but SABnzbd hasn't always created an PID File.

 

Please don't think about this as critic, its only an suggestion.

 

spidi

THis is the first time I have tried to install anything on my Unraid server...  No Joy

 

Aug 20 08:17:25 Tower acpid: waiting for events: event logging is off

Aug 20 08:17:25 Tower crond[1123]: /usr/sbin/crond 4.4 dillon's cron daemon, started with loglevel notice

Aug 20 08:17:25 Tower logger: installing plugin: *

Aug 20 08:17:25 Tower logger:

Aug 20 08:17:25 Tower logger: Warning: simplexml_load_file(): I/O warning : failed to load external entity "/boot/config/plugins/*.plg" in /usr/local/sbin/installplg on line 12

Aug 20 08:17:25 Tower logger:  xml parse error

Aug 20 08:17:25 Tower emhttp: unRAID System Management Utility version 5.0-beta11

Aug 20 08:17:25 Tower emhttp: Copyright © 2005-2011, Lime Technology, LLC

Aug 20 08:17:25 Tower emhttp: Pro key detected, GUID: 0781-5530-0572-7316AEE20A45

Aug 20 08:17:25 Tower emhttp: shcmd (1): udevadm settle

 

 

I don't know what I did wrong.  Followed your instructions.  Any help?

 

Thanks

 

Ed

it looks like the installplg can't open the plugin files.

which plugins did you install?

 

can you run the installplg ..... command in the console (like i wrote in my first post)?

I DL'ed all three and put all of them into the plugin dir.  Should I do only one t a time?

 

Ed

Same error if I try command line

 

Tower login: root

Linux 2.6.37.6-unRAID.

root@Tower:~# installplg /boot/config/plugins/sabnzbd-0.2-i486-1bw.plg

installing plugin: sabnzbd-0.2-i486-1bw

 

Warning: simplexml_load_file(): I/O warning : failed to load external entity "/b                oot/config/plugins/sabnzbd-0.2-i486-1bw.plg" in /usr/local/sbin/installplg on li                ne 12

xml parse error

 

i'll have a look, when i'm at home again. (currently at work)

 

maybe you can try to redownload the plugin file. maybe it was corrupted while downloading...

also you can check the user rights of the files. type "ls -la /boot/config/plugins"

Thanks.  I will do that.. BTW, what should the entire file name lool like.  Should it end with .plg  or .xml?

 

Thanks

 

Ed

at the moment it should end with .plg

there is a discussion going on, if the file extension should be changed to .xml.

but at beta11 it needs to be .plg

GOT IT!.. Sorry Benni.  Problem was operator head space on this end.

 

I was DL'ing with windowes by right cliking and telliong windows to save as.  The default was .xml.  I had to tell windows to save as 'all file types' and add the .plg ext.

Did a restard ant the icons are there.

 

Sorry for all the confusion and many thanks for working with me.

 

Ed

@benni-chan

 

i changed your Plugin for my needs. Now you can choose the Install and the Log directory.

 

Thanks again for your work.

 

spidi

edwilloughby: glad you got it working

 

 

spidi: nice idea. i will think about implementing this, too.

Last question.. Should I remove the .plg files after installation of the plugin's?

 

Thanks

 

Ed