PhAzE

My instance seems to stop working quite often, how is the service / app watched? Is it using supervisord or some other method to keep the service alive?

Worked perfectly. Is it running the latest version? I seemed to have hit a bug that was fixed in the release 7 days ago, not sure if this includes that change from github. Sent from my SM-T817W using Tapatalk

Hey Thanks for this. One problem, when you set /config to a mapped directory, rather than using the directory you specified, it creates another subdirectory called 'mylar'. Can this be changed so it just uses the one i specified in the docker config for the mapping? Coming from another docker to this one, I can't seem to get it to use the current DB and files without having to move everything into a unneeded subfolder. (Not sure if thats mylar or the docker container doing it) EDIT: Forget it, i just moved my files into that new folder. Got the old DB working again. Still hoping ComicTagger can be added to this EDIT 2: Seems comic tagger is already there but "configparser" is missing.

Ok I wasn't sure about the mixing and matching. Thanks!

Looks like a promising plugin. Quick question, sorry if it's the wrong thread, if I have 4 disks formatted as RiserFS and I want to change them to XFS, (one being parity) can I use this plugin to move files off one disk, format it to XFS and copy files back to it and format the next? Will the newly formatted disk still be part of the array even though it's a different format than the remaining disks? Cause if so, then this is what i was looking for. A time saving plugin

I'm having problems with the old Nginx docker (unable to start due to missing init file or something along those lines) so looking forward to the new docker. EDIT: I blew away my docker.img file and reinstalled everything. Nginx is working fine, so i guess my image file was just messed up.

NONE is a dangling (left over but unused) container. Run this to remove it: docker rmi $(sudo docker images -f "dangling=true" -q) ------------------------------------------------------------------------ My utilization i still going up, and when i compated my container sizes from 3 weeks ago to now, no change, but I've gone up 30% utilization (which is 3gb out of my 10gb. No temp or log files remain in the containers, and I just can't figure out what is making it grow.

i didn't have any large logs in any of my dockers. It appears my utilization is still growing, even with TMP mapped to native TMP drive, and dangling images gone. Docker containers do not appear to be growing in size, so that leaves me to believe that it is an issue with something outside the containers. Perhaps docker has it's own log file outside the containers but still in the image, or maybe there are history entries growing the image usage.

I just wanted to point out, if you need to clear some space in the image and happen to have dangling images, it's best to remove them. First, run: docker images -f "dangling=true" and if you see anything listed then you have unused images that can be cleared out with the following code: docker rmi $(sudo docker images -f "dangling=true" -q) For me, that got my image back into acceptable utilization levels. Enough to clear the unRaid alert for over utilization. If docker updates are in fact leaving images behind, then I suppose you could 'cron' this for a weekly run to clear out leftover images. That is assuming that your containers themselves are not growing. In my case, I found that after mapping /tmp to /tmp for all the containers, the images still grew, but likely due to application auto updates which were in fact leaving empty image files after the updates.

So after updating all of my dockers to map /tmp out to /tmp (in ram) the docker is still growing only slightly slower now. I think that may have been only a partial solution. I can see some apps are indeed leaving files in /tmp (like Calibre, and Sonarr). I believe some of these apps are also growing log files in /var/log in each container, but i'm not sure if it's enough to bloat 10GB of docker.img space.

Ok like the container size grows but doesn't shrink once expanded. Sounds like we need a way to shrink containers via cron or something.

I had a look ag the tmp folder for sonarr sab and ubooquity and they are all pretty clean. Nothing stands out as bloat yet my docker is filling up still. Needs more investigating.

Im getting this same problem but im not using plex as a docker. I haven't had time to inspect yet but i did notice sonarr had a queue of shows to process but couldn't until the docker was restarted, that or sab. Ill verify but i also suspect sab may be unpacking rar files in the tmp folder during the unrar process and crashing if the docker image fills.

I noticed with recent builds of unraid 6 (especially the final) when a plugin echo's text, it is handled differently now than older versions. In unraid 5 - the echo'd lines would show stacked In unraid 6 - the echo'd lines now show one after another in a single line, bu tin the betas they would clear the previous entry before displaying the new echo. Is there a better way to convey messages about what the plugin is doing that doesn't mash them all into a single line across the bottom of the page? Edit: Ideally, the stacked layout of unraid 5 looks best and shows text long enough for users to see what's happening.

That's a good way to some the error. I have mine running anonymously but that gives the error on v5 still. I'll likely update to this. Quick question, I saw plugins can now have an info cjangelog. How do I add that?

I assume they couldn't all be named Appname.page, which would be the only file the link looks for. In fact its already doing that. If a plugin doesn't have the .page file currently in beta 12, the link is disabled already. For example, dynamix plugin has no link. Ideally the plugins tab will be the first tab a new user checks for when looking for the plugins settings and plugins that are installed. Having redundancy would be up to the plugin Dev, but not required.

Hmm I had a look at the page code, it's only a link if appname.page is detected. But the link goes no where.

So on the plugin manager page it shows you the plugins you have installed. The icons are clickable. I assume this is so you can go to the gui php page but I'm not sure how to set it. Does that makes sense?

Anyone figure out how to get the link working for their plugin on the plugins page? My apps show up, with their icons, and all info but when I click on the icon (under the plugin manager page) it goes to a blank page.

Thanks jonp, just to confirm, the following are still used? Any other items i'm missing? name="&name;" author="&author;" version="&plgVersion;" pluginURL="&pluginURL;"

Anyone know what we should be filling in for 'category' entity? Just a category for the plugin type, like "downloader" or "movie organizer" or is there anything specific we should be using?

For package removal, I've now got them installed into a common folder, and the app is started with a wrapper that exports the environment path to that common folder. When the plugin is removed it deletes the associated common folder too.

Actually the net check is more of a gateway check, when you reboot the server it won't attempt to download the files that might be missing until the nic can at least reach the router. People had failing plugins because the download would start before their slow nic cards. It skips instantly if there is a default gateway that is reachable.

It's looking for a .page file in /usr/local/emhttp I tried symlinking to the plugin page file but it just brings up the text cause it doesn't know what to do with .page. Also I made a file in /usr/local/emhttp/virtMan.page and added some html code but no luck. I'll have to look through the plgman code again and see if there's an error. Ya those are the same steps I took Maybe its just not a finished feature of the plugin manager yet.

Here's my beta for Sabnzbd plugin 2.0.0. If you want to test it for suggestions, or to use some of the code, feel free. Use this on a development unraid server just in case, not one that already has sab installed. I haven't really added any new features to the sab plugin yet (have a few in mind) but this should allow you to start your server and install even if your internet isn't working (assuming the app was downloaded once before with internet working). All png files are in a zip file along with the page, php, rc and css files. This simplifies the plugin file and makes all supporting files and dependency files "external" on my git. If you get a chance, let me know if anything seems broken so i can fix them. I'll probably change all my plugins over to this format since it's more versatile and easier to update because the support files and dependency files are separate. Sabnzbd.plg