JustinChase

I did a search, but didn't find this exact thing, so sorry if I missed it. I'm getting these posted to my syslog every minute... Jan 31 12:31:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:32:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:33:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:34:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:35:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:36:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:37:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:38:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:39:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:40:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:41:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:42:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:43:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:44:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:45:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:46:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:47:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:48:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:49:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:50:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:51:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:52:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:53:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:54:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Jan 31 12:55:01 media crond[1752]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null I'm guessing they are related to the Local Master plugin, which I had installed for awhile, but uninstalled a week or so ago.

Hi binhex, I was going to ask for a (very low importance) favor of you. I've been using the gfjardim docker for owncloud and needos docker for mariadb, but he's gone AWOL, as you know, and OwnCloud is telling me there is a new version to update to, but I suspect he won't be back to update his docker for the new version any time soon, so... ...in all your abundance of free time (hehe), can you either take over, or create dockers for this (or both of these?) I'm in no hurry, it's working fine, I just thought it'd be nice to have it updated, and even better to have them based on your docker base, like pretty much all my other dockers. PLEASE no not feel compelled to do it, I completely understand that you may not want to take on any more work for yourself, but you've always been so generous with your time, I thought it worth at least asking. Thanks again, and take it easy.

I was looking for a list of the changes in the new build, and ended up here... https://hub.docker.com/r/binhex/arch-sabnzbdvpn/ From there, there is a link to the support page, but it takes you to the old support thread, which you just closed. No big deal, just letting you know it didn't get updated in all your recent changes

So, I've made some updates to my server; I replaced my (unassigned) SSD with a larger one, replaced my cache drive with a new one and added more memory. When I restarted the server, the cache tab was missing, so I had to stop the array then select my new drive for the cache drive. However, prior to realizing I had to stop the array to add the cache drive I saw it and the new SSD listed in the unassigned drives tab. After adding the cache as the cache drive, it is still showing in the unassigned drive tab. It didn't use to show the cache as an unassigned drive previously, so I'm not sure what's going on there. Also, I'm unable to open or format the SSD from the unassigned drive tab. I can see it, but can't use it now. I'm sure I'm missing something simple, but it's late, and I'm frustrated, so I'm asking for help. Thanks!

Great, thanks for letting me know that; great pro tip!!

okay, for some reason, the name of the unasigned drive changed. it no longer has "-part1" in the name. I just tried pointing both docker and the VM disk from their setup pages to the unassigned drive and both seem to be working again now. Not sure why it's no longer using partition 1 in the name/description, but I think I'm good. Thanks again for updating this for us!!

first, thanks so much for jumping in and working to get this plugin working again. However, I don't think I had any of the issues that just got fixed (never checked my log, maybe I did and just didn't know it), but after updating to the very latest version of unassigned devices (installed your plugin and installed version c, then updated from the plugin system to version d), then updated to unRAID 6.1.7, then rebooted, I've lost my dockers. Settings shows dockers as enabled, but I don't have my docker tab, and going to community applications warns me I need dockers enabled for it to work. I've just rebooted the server again, and still no dockers. Unassigned devices tab does show my drive, and the sizes look fine, and I can drill down to see the files on the drive, but dockers are just not working. I suspect the unassigned drive did not mount prior to docker trying to use the drive, but that's just a guess. My VM also resides on the unassigned drive, and it also did not start. diagnostics file attached. media-diagnostics-20160117-2039.zip

How would I verify if mine is "modern" enough to have it built in? I think it does, but would like to verify, just to be sure. thanks!

I thought trim was done automatically if one had an SSD installed. Do I need to install SSD Trim plugin to keep the SSD 'clean', or is it just to force it to happen on a regular basis? Thanks

Thanks for the nice explanation of the local master scheme. Since I have my SMB share on unRAID set for local master:yes, is there any reason to install the plugin? Can I just assume unRAID will continue to serve as the local master and I can just not worry about it? I've not seen any problems in the last few years that would make me concerned it's an issue; so...good enough? thanks again

What exactly is a "Local Master" and why would I need/want to know information about it? I didn't realize there was a plugin for it until the errors, and the description in the first post explains it, but it doesn't explain what a local master is or why it's important. Also, I remember there was a 'hack' to show the active streams on the dashboard page, but it doesn't persist thru a reboot. Could this be made optional to always show active streams on the dashboard? it's very helpful to me there. Thanks!

Wow, you guys have been busy! I haven't checked this thread for quite a while and the number of dockers you now have is very impressive; nice work. Sadly, the one I really want isn't available, so I'm putting in a request for some help. I use JRiver Media Center for my main media client, mostly on Windows, but they do make a Linux variant now, which isn't quite fully featured, but I think it's far enough along that I'd like to try using it for most of my server needs. I believe they've built if specifically for any Debian variant, but there seems to be several branches that run on other flavors of Linux. So, my request is to ask if y'all could have a look and see if you could create a docker for JRiver Media Center. Here is the link to their main Linux forum, which discusses the Linux variants in more detail. They release new versions every week or 2, and they have an internal system which lets Media Center automatically update to the latest version, or to stay on the latest stable. I'm not sure how that system works internally, or how it might be used to keep a docker up to date, but I know their developers are very responsive and willing to help with things like this, so if y'all were interested in building a docker, I'm sure they will be responsive in any help you might need. Thanks in advance for anything you can do to make this happen!!

sensors-detect comes with unRAID, it is a perl script and you need to install perl to run it. after seeing dozens of posts about needing to install perl; why doesn't limetech just put it back into unRAID? What is the benefit of not having it vs. the countless problems its removal has created?

Which I assume will be here soon, based on your signature

I never installed until version c

The normal sequence is that after pressing the button a popup windows appears (see picture) telling that preparations are taking place, once these are done the normal shutdown or reboot screen is shown. You are saying none of this happening? Nor for me either. I get the 'standard' system is rebooting screen, but nothing actually happens.

Are these buttons supposed to stop/reboot instantly, without stopping the array 'normally'? i ask because I just rebooted my machine with this new button, and I got the "System is rebooting..." window instantly, not the stopping docker...spinning up drives...etc stuff I normally see when I stop the array from the regular GUI.

I just installed this; nice. I'm using Firefox, and the 3 options run off-screen to the right (see screenshot). Possible to have them extend left if they would otherwise run off-screen like this?

Hmmm... Weird that Plex uses SO MUCH space. JRiver Media Center uses 2.3GB for the same library/media as what I have imported into Plex. Windows is still counting the data in appdata, and is up to 53.4Gb on disk and 16Gb in size. What the hell does Plex have/use/store for my media files? It's already taking 20 TIMES more than JRiver. I'm amazed people don't complain about this absurdity. I also just noticed there are almost 3 times as many folders as files. WTH?!?! I guess the only way to not have Plex eat the whole cache drive is to set /config to something other than a cache location. Thanks for the feedback/help. I only installed Plex to help a friend, so I'm going to be uninstalling it now. Giving 60GB (and counting) for metadata is LUDICROUS!

I have some questions about actually setting up Plex, not about the docker, per se. Where is a good place to take these questions for help? 1) Why is my appdata folder so HUGE after installing Plex? 2) How can I minimize the size Plex requires? 3) Can something be changed to fill up some other, non-cache location? 4) Why is the size on disk so much larger than the Size of my appdata folder (when doing properties from inside windows)? i.e. the size shows as 14GB, size on disk is 33GB (and both are still growing after clicking show properties almost 10 minutes ago!) Thanks

windows VM is running of an SSD outside the array. it has 4 GB (of 8 total) assigned to it. Dockers image is on disk 1, using 8 of 10GB. I ended up having to reboot the server to get the Windows VM to restart, so I'm not sure if the logs you want are still available, but if you tell me exactly what logs you want, I'll post them up for you.

My container failed to build with the extra parameters in the config. i removed them, and the build completed. However, I tried using the program, and after getting it all set up/configured, and started it on extracting an MKV from an iso file, as soon as I confirmed I wanted it to create the directory into which it would save the file, my windows VM crashed, and the mkv file never actually started extracting. it eventually failed in the makemkv docker also. Sadly, it seems it's still not quite working right

for anyone following along, I got it resolved. Here is a wrapper which circumvents the RDP restrictions on most/all versions of windows... I had to register to get the links, but here is the download... Quick instructions are, download version 1.5, unzip it to the computer which you want to remote into, run the RDPConf.exe - which lets you set some options (like shadowing, and multiple connections), open a command prompt as administrator on the client machine, cd to the unzipped directory, run RDPWInst.exe -i and it should install everything necessary for it to work. I restarted the machine, but I'm not sure if it was necessary. Once restarted, I used the RDP built into windows to connect to the machine, and confirmed it did not disrupt the session in progress on the VM. I played a movie on the VM, extracted an MKV in one session, and installed and started configuration of a Plex docker on a 3rd connection. All worked great. In the end, it seems I didn't/don't need Guacamole for any of this (although it did work fine). The windows RDP program displays in full screen at a higher resolution, and ran at nearly full speed, even over wifi. Thanks again for all the help.

no problem, you were quite helpful to me getting this far. thanks again.

Yeah, it's installed as a service. My Windows 8 VM is my HTPC replacement. I've run a long HDMI cable from the server in the attic to the TV in the living room. Works great, just this 'issue' with mirroring. Not a big deal really, as it's better than what I had been doing, which was shut down the VM with GPU passthru, then relaunching it with VNC on my laptop so i could do what I needed, then closing that and relaunching with GPU passthru. At least this way, i can just access it in place, so I have less "hoop-jumping". I was just hoping there was another/better way to let me have full access while the VM was in use as an HTPC.