Influencers Plug-ins-[UNPLUGGED] Support & Download-Sab, CP, Sickbeard, + more!!


Recommended Posts

  • Replies 2.6k
  • Created
  • Last Reply

Top Posters In This Topic

https://github.com/Influencer/UNplugged/raw/master/sabnzbd_hardcoded.plg

 

You can always click in github, then on the next page, right click on "raw" and feed that into wget.

 

I created a simple bash script so all I have to do is change the part after /master/ to the item I need:

#!/usr/bin/bash

rm sabnzbd_hardcoded.plg
wget --no-check-certificate https://github.com/Influencer/UNplugged/raw/master/sabnzbd_hardcoded.plg
rm sickbeard_unplugged.plg
wget --no-check-certificate https://github.com/Influencer/UNplugged/raw/master/sickbeard_unplugged.plg
rm couchpotato_v2_unplugged.plg
wget --no-check-certificate https://github.com/Influencer/UNplugged/raw/master/couchpotato_v2_unplugged.plg

Link to comment

Actually, this brings up a good question.  Now that things on the plugin side are becoming more stable...would it be possible to have an update plugin button in the settings page?

 

It seems that unless there is a major change to config settings, updating a plugin can be done on the fly without having to reboot.  So having the plugin (if the app is disabled) able to update its source file and then reload would be very handy for people who don't want to get into the CLI

 

Obviously, with my script I'm fine...but I can see an update that changes the configs break things if I then installplg the new files without restarting.

 

Secondary question: Is there a way to unload a plugin short of a reboot?  Clear it out and start from scratch?

Link to comment

I'll include the link, and instructions to right click/save as to download. That is one of the shortcomings of github, :).

 

An update/uninstall would be good, I'll look at implementing those.

 

Not really a easy way to unload a plug-in, short of deleting the files manually. This would include the install directory, data directory(if you wished), and the plug-ins page from emhttp(/usr/local/emhttp/plugins/plugin-name/), and the rc file at /etc/rc.d/ if one exists

Link to comment

Well, I wasn't thinking about dependencies.

 

I was more thinking about the web section, I don't really understand how the plugin system works within emhttpd....perhaps just running installplg again will never result in stale data or confused configurations....that's more what I was worried about rather than actually removing all the dependencies (like python) because that would be tricky, 3 plugs I have use python..I don't want an uninstall on one of them to hork up the others.

 

Perhaps I'm just over-thinking things.

Link to comment

This is where the plug-in system being fleshed out will come in handy. Hopefully once it is matured some the system will handle dependencies, or atleast not allow one plug-in to clobber another's dependencies.

 

Dependencies don't really cause an issue, and can be manually removed pretty easily as they are stored on the flash drive, they would of course stay installed until reboot.

Link to comment

Actually, this brings up a good question.  Now that things on the plugin side are becoming more stable...would it be possible to have an update plugin button in the settings page?

 

It seems that unless there is a major change to config settings, updating a plugin can be done on the fly without having to reboot.  So having the plugin (if the app is disabled) able to update its source file and then reload would be very handy for people who don't want to get into the CLI

 

Obviously, with my script I'm fine...but I can see an update that changes the configs break things if I then installplg the new files without restarting.

 

Secondary question: Is there a way to unload a plugin short of a reboot?  Clear it out and start from scratch?

 

PM sent

Link to comment

I'm not sure what's going on, but it looks like SickBeard is hanging on start...both SAB and CP are up...but SB isn't and emhttp isn't responsive.  This is the same error as in the past, so I had to disable the plugins and restart.

 

If that happens again (Which I will gladly test once I finish my disk upgrades) what information should be gathered?  I looked at the processes and didn't even see a python process for SB.

Link to comment

Ok, I finally got to try starting SB from the RC script and it worked just fine.

 

However on reboot, CP and SAB came up fine, SB didn't (with no log entries in datadir or /var/log) and emhttp never became responsive.

 

Trying a boot with SB disabled to see if it comes up cleanly.

Link to comment

Ok, it isn't SB.  I found :

 

root      5942  0.0  0.0   2688  1300 ?        S    16:23   0:00 /bin/sh /etc/rc.d/rc.sabnzbd start

 

when I killed that, everything came up.  So Sab was running, but the rc script never finished.

Link to comment

Not much help:

 

root@Storage:/var/log# /etc/rc.d/rc.sabnzbd start
Starting sabnzbd:  sudo -u nobody python /usr/local/sabnzbd/SABnzbd.py -d -s 0.0.0.0:8082 --config-file /mnt/cache/.custom/SABnzbd --pid /var/run/sabnzbd > /dev/null 2>&1

 

SAB is up and running, but the rc script never exits.

Link to comment

Not intentionally, let me check the ini file.

 

....

 

Nailed it.  Must have been hanging around since I used to run it from the go script.  Not sure HOW it got enabled, I don't have a key setup...but hey, all fixed and the error was on my side.  Thanks for helping me nail it down!

 

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.