[PhAzE] Plugins for Unraid 5/6


3606 posts in this topic Last Reply

Recommended Posts

Ok I understand.  My plugin has never shipped with ffmpeg or lamemp3, however I have just put out an update for headphones to include lameMp3 as it is lightweight where as ffmpeg and libav require a lot of sub dependencies.

 

Anyways, after you update your plugin, restart headphones for it to take effect.

 

To access from command line, you need to first use the headphones environment shortcut.  This command lets you access the files in the Headphones environment:

 

Headphones-env <commands>

 

So, if you wanted to check for python for Headphones, you would type:

 

Headphones-env python -V

 

 

That will show the version.  Or see which lame is used, type:

 

Headphones-env which lame

 

And that will show the lame binary that will be used.  To do the commands for lame manually, you can try:

 

Headphones-env lame --help

 

Whatever you need from the Headphones environment can be reached by starting your command off with the Headphones-env shortcut.  The same goes for any of my plugins, they all have this new shortcut feature added in on the V3 plugins. :)  Let me know if that helps.

Link to post
  • Replies 3.6k
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

Popular Posts

Just a quick update, unRaid 6.4 looks like it will be using nginx for the web front end over emhttp (which is a good switch IMO) but that means there is a good chance all of my plugins will not work o

Important info regarding unRAID 6.2 and beyond.          ***unRAID 6.2 Compatible*** Hello again!   I've done another overhaul of the plugins

Unfortunately, @PhAzE no longer seems to be active at all within these forums.  His last time online was March 23, and his last posting was on February 22.  I'm sure I speak for all of us in hoping th

Posted Images

hi phaze, big thanks for the v3 updates. nice work.

 

i got a bug with NZBMegasearch. when i stop the array, after closing all apps and plugins, it hangs on "Retry unmounting user share(s)..." until i connect with ssh to the server and kill the mega2.py process (NZBmegasearch) by hand.

after that i can reboot and work again with the server. is it a bug in the power down plugin or in your nzbmegasearch plugin?

 

thanks in advance to look into it. not a big bug but a especially annoying one

Link to post

hi phaze, big thanks for the v3 updates. nice work.

 

i got a bug with NZBMegasearch. when i stop the array, after closing all apps and plugins, it hangs on "Retry unmounting user share(s)..." until i connect with ssh to the server and kill the mega2.py process (NZBmegasearch) by hand.

after that i can reboot and work again with the server. is it a bug in the power down plugin or in your nzbmegasearch plugin?

 

thanks in advance to look into it. not a big bug but a especially annoying one

I can't seem to reproduce the problem, it stops for me each time.  What unraid version are you running?

Link to post

Hey guys!

 

Looking for some testers for the new NZBGet plugin.

 

Get it here!

 

As far as I can tell, it's all working perfectly but I don't use this app so I need someone to try it and make sure it works as expected, if your interested, use the link above.

 

-=PhAzE=-

Link to post

Seems to be a bug in sab startup that prevents it from starting at boot. Probably due to the "https_9090 "

 

On boot:

 

Sep 11 05:02:40 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:https_9090 8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

 

It starts fine if I manually click the start button or click "apply" in the plugin config.

 

Sep 11 05:05:10 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

Link to post

PhAzE, I'm getting a similar error to another error in this thread, but with the SickRage plugin (though I was getting it with the SickBeard-Alt plugin as well) -- Start failed: No PID Created

 

I've tried changing the port and also rebooting the server, to no avail.

unRAID is at version 6.1.2

 

Any ideas for things I could try in order to fix this? I miss having my TV shows trickling in automatically!

Thanks!

Link to post

That fixed it... weird.  :o

 

The error actually had been happening for about a month and I just kept occasionally checking this thread when I thought of it to see if I was the only one having the problem. I actually tried Sonarr as an alternative and didn't really like it, which is why I finally asked for help.

 

Thanks so much for all your work on these plugins and for your help with this issue. Can you explain at all what you think might have been causing the error?

Link to post

Seems to be a bug in sab startup that prevents it from starting at boot. Probably due to the "https_9090 "

 

On boot:

 

Sep 11 05:02:40 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:https_9090 8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

 

It starts fine if I manually click the start button or click "apply" in the plugin config.

 

Sep 11 05:05:10 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

Could you screen shot your settings from the plugin settings page? It is a problem with how it grabs the port variable but I can't seem to reproduce this either.

Link to post

Seems to be a bug in sab startup that prevents it from starting at boot. Probably due to the "https_9090 "

 

On boot:

 

Sep 11 05:02:40 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:https_9090 8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

 

It starts fine if I manually click the start button or click "apply" in the plugin config.

 

Sep 11 05:05:10 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

Could you screen shot your settings from the plugin settings page? It is a problem with how it grabs the port variable but I can't seem to reproduce this either.

 

Also, try this plugin to see if the problem persists, this may have fixed it. (removed from post, now live, just update from plugin settings page)

Link to post

That fixed it... weird.  :o

 

The error actually had been happening for about a month and I just kept occasionally checking this thread when I thought of it to see if I was the only one having the problem. I actually tried Sonarr as an alternative and didn't really like it, which is why I finally asked for help.

 

Thanks so much for all your work on these plugins and for your help with this issue. Can you explain at all what you think might have been causing the error?

Found the problem, during start up instead of 'checking' if forceupdate was set to yes, it was setting it to yes and always making it on.  SickRage doesn't use that option so it wouldn't start. (all because the code was = instead of == just missing that second equals sign)

 

Update has been put out for SickBeard, SickBeard_Alt, and SickRage plugins to correct this, and I have removed the option entirely from SickRage.  Should be no more problems with that now.

Link to post

That fixed it... weird.  :o

 

The error actually had been happening for about a month and I just kept occasionally checking this thread when I thought of it to see if I was the only one having the problem. I actually tried Sonarr as an alternative and didn't really like it, which is why I finally asked for help.

 

Thanks so much for all your work on these plugins and for your help with this issue. Can you explain at all what you think might have been causing the error?

Found the problem, during start up instead of 'checking' if forceupdate was set to yes, it was setting it to yes and always making it on.  SickRage doesn't use that option so it wouldn't start. (all because the code was = instead of == just missing that second equals sign)

 

Update has been put out for SickBeard, SickBeard_Alt, and SickRage plugins to correct this, and I have removed the option entirely from SickRage.  Should be no more problems with that now.

 

Thanks for a quick fix! Much appreciated!  8)

Link to post

Seems to be a bug in sab startup that prevents it from starting at boot. Probably due to the "https_9090 "

 

On boot:

 

Sep 11 05:02:40 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:https_9090 8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

 

It starts fine if I manually click the start button or click "apply" in the plugin config.

 

Sep 11 05:05:10 Tower sudo:    root : TTY=unknown ; PWD=/ ; USER=nobody ; COMMAND=/bin/bash -c . /mnt/cache/.PhAzE-Common/Sabnzbd/startcfg.sh; python /mnt/cache/.apps/SABnzbd/SABnzbd.py -d -s 0.0.0.0:8081 --config-file /mnt/cache/.apps/SABnzbd/config --pidfile /var/run/Sabnzbd/Sabnzbd.pid $stuff$

Could you screen shot your settings from the plugin settings page? It is a problem with how it grabs the port variable but I can't seem to reproduce this either.

 

Also, try this plugin to see if the problem persists, this may have fixed it. (removed from post, now live, just update from plugin settings page)

 

New update fixed the issue. Cheers!

Link to post

Been trying to install Coachpotato v3 on 6.1 unsuccessfully. Sonarr is installed and running without a problem, but for coachpotato I keeping being blocked on the same error messages.

Anybody any help here ?

 

This is the log appearing on the popup screen when installing the .plg :

-----------------------------------------------------------------------------------------------

plugin: installing: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg ... done

Installing Couchpotato plugin

Checking for current bundle files

Control file: Found correct version

Dependency file: Not found

Check OK!

Downloading new dependency file

Install failed: Downloaded dependency file failed MD5 check

plugin: run failed: /bin/bash retval: 1

Link to post

Has the installing/starting of the plugins always been bound to the start of the array button? For some reason I thought that some of that was done during boot. Starting and stopping the array seems super slow now....

 

EDIT: To clarify, I just went thru upgrade from v5 plugin with an old version of these to the most up to date. So I may have had something in the go file that preloaded it or something, just wondering if I messed something up in the process.

Link to post

Been trying to install Coachpotato v3 on 6.1 unsuccessfully. Sonarr is installed and running without a problem, but for coachpotato I keeping being blocked on the same error messages.

Anybody any help here ?

 

This is the log appearing on the popup screen when installing the .plg :

-----------------------------------------------------------------------------------------------

plugin: installing: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg ... done

Installing Couchpotato plugin

Checking for current bundle files

Control file: Found correct version

Dependency file: Not found

Check OK!

Downloading new dependency file

Install failed: Downloaded dependency file failed MD5 check

plugin: run failed: /bin/bash retval: 1

Got finally couchpotato installed after uninstalling every other plugin. But now Sonarr is not installing anymore..it seems those plugins are depending on each other in some way. Would using Docker be the solution ?

Link to post

Been trying to install Coachpotato v3 on 6.1 unsuccessfully. Sonarr is installed and running without a problem, but for coachpotato I keeping being blocked on the same error messages.

Anybody any help here ?

 

This is the log appearing on the popup screen when installing the .plg :

-----------------------------------------------------------------------------------------------

plugin: installing: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg

plugin: downloading: https://github.com/PhAzE-Variance/unRAID/raw/master/Plugins/Couchpotato.plg ... done

Installing Couchpotato plugin

Checking for current bundle files

Control file: Found correct version

Dependency file: Not found

Check OK!

Downloading new dependency file

Install failed: Downloaded dependency file failed MD5 check

plugin: run failed: /bin/bash retval: 1

Got finally couchpotato installed after uninstalling every other plugin. But now Sonarr is not installing anymore..it seems those plugins are depending on each other in some way. Would using Docker be the solution ?

The problem your having is a connection issue to github. Change your DNS to 8.8.8.8 and install them then change it back, or download the files manually from my git and put them on the usb in their folder and run the install again.

Link to post

Has the installing/starting of the plugins always been bound to the start of the array button? For some reason I thought that some of that was done during boot. Starting and stopping the array seems super slow now....

 

EDIT: To clarify, I just went thru upgrade from v5 plugin with an old version of these to the most up to date. So I may have had something in the go file that preloaded it or something, just wondering if I messed something up in the process.

Yes the plugins now install the dependencies upon start instead of when the plugin is installed. Faster boot times, slower start times. But if you have a cache drive that slowness is greatly reduces since dependencies will remain after reboot in the cache drive. It's not really that much of a difference in start time though, only a few seconds. Considering that you don't start and stop them too often it shouldn't be much of a problem though.

 

Link to post

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.