JustinChase

sorry to keep spamming this thread I fixed it. I noticed that the network setting page in unRAID showed a MAC address that ended in D7, but my router had assigned the static IP address to the same MAC but ending in D5. I have 2 onboard NICs, and had previously been disabling one in the BIOS, but while trying to setup pfSense, I enabled them both again. As part of that same process, I'm excluding one of them to allow pfSense to use it. I must have excluded the one I had previously been using for unRAID. I have no idea why everything was mostly working (SABnzbd could download files fine). But I removed the D5 MAC from my router static table, and assigned the D7 MAC to the unRAID IP address, and BAM, I can ping google, and just installed a new plugin. frustrating, and pretty weird, but seemingly resolved now. Okay, now, so what's spamming my log file??? ***I just uninstalled ALL plugins, then rebooted the server. Still getting the messages... Feb 1 00:06:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:07:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:08:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:09:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:10:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:11:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null Feb 1 00:12:01 media crond[1696]: exit status 127 from user root /usr/local/emhttp/plugins/dyanmix/scripts/monitor &> /dev/null I looked in /usr/local/emhttp/plugins/dyanmix/scripts/monitor but it's beyond my comprehension I think I've exhausted my troubleshooting skills now. Hopefully someone else can figure out what's causing this and help me fix it.

I don't know where all these settings come from, but I just rebooted after updating the DNS in the network settings page. root@media:~# route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 192.168.20.1 0.0.0.0 UG 1 0 0 br0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 172.17.0.0 0.0.0.0 255.255.0.0 U 0 0 0 docker0 192.168.20.0 0.0.0.0 255.255.255.0 U 0 0 0 br0 192.168.122.0 0.0.0.0 255.255.255.0 U 0 0 0 virbr0 why is br0 listed twice? Where did 192.168.20.0 and 192.168.122.0 come from? I don't have these assigned in my network anywhere. the docker0 set for 172.17.0.0 is also weird, but I suspect it's correct, since I've never seen any IP quite like it, it seems too random to be a mistake.

Sadly, no. Rebooting didn't help, I get the same errors. I feel like this is a bug. So, in looking around, it seems unRAID just cannot reach github... root@media:~# ping github.com -c 3 ping: unknown host github.com I changed the DNS settings in Network (which had been working fine for over a year) to my nearest OpenNIC DNS settings, still no luck. I then checked the router, and it had 0.0.0.0 for all DNS server settings, so I added the OpenNIC settings there, and pinged github from the router and that worked fine. Checked unRAID again, and still cannot reach github. I had been trying to install pfSense, and did finally get it installed, but don't have enough NICs in the server to actually use it, so it's not even running right now. I suppose while trying to set it up it borked something, but I'm not sure what, or where to look.

It does of the actual application (if the author in question supplies the md5 within the .plg file) In the case of an md5 mismatch, you'll see an error message to that effect during installation. Personally, I'd love to see something other than all those simple_xml errors which are rather confusing to users when the download of the plg is corrupted. So wouldn't a bad download trigger the hash failure scenario? I guess I'm not sure if I got a bad download or some other problem.

Yeah, I wasn't sure if that was a document/download problem or an access/permissions/design problem. I would like to think the plugin manager verifies downloads md5 hashes before proceeding, but perhaps not. I'll work on this some more later this evening. I'd still like to know which plugin is spamming my log, so I know which one to try fixing.

Well, i figured it couldn't hurt to just reinstall the plugins and see it that helped. The first one I tried was powerdown, and I got this... plugin: installing: https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg plugin: downloading https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg plugin: downloading: https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg ... done Warning: simplexml_load_file(): /tmp/plugins/powerdown-x86_64.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/powerdown-x86_64.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error That seems bad. I paused my download and tried again. Same errors. *I tried the next plugin and got the same error... plugin: installing: https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg plugin: downloading https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg plugin: downloading: https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg ... done Warning: simplexml_load_file(): /tmp/plugins/dynamix.active.streams.plg:1: parser error : Document is empty in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): /tmp/plugins/dynamix.active.streams.plg:1: parser error : Start tag expected, '<' not found in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 Warning: simplexml_load_file(): ^ in /usr/local/emhttp/plugins/dynamix.plugin.manager/scripts/plugin on line 193 plugin: xml parse error

Thanks for the heads up. I wonder which plugin is causing my specific issue, as I'd prefer not to uninstall and reinstall all the plugins if possible. Especially since unassiged drives handles my VM and docker images. Do I have to uninstall them before installing? I assume so, as it seems the point is to remove whatever is 'bad' about them, then install them fresh. I've previously removed several that I don't use that often, so I only have these 4 installed.... https://github.com/dlandon/powerdown/raw/master/powerdown-x86_64.plg https://github.com/dlandon/unassigned.devices/raw/master/unassigned.devices.plg https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.active.streams.plg https://raw.github.com/bergware/dynamix/master/unRAIDv6/dynamix.s3.sleep.plg I wonder if one of the ones I uninstalled is causing the issues instead?

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

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?

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

i've not followed all the progress with the temps plugin, so I'm just curious if I still need this in my go file... modprobe -a coretemp or is the plugin 'self-sufficient' to get the drivers working without it now? thanks.

I think it messes things up because appdata is no longer on the cache, because mover puts it onto the array. I believe just copying appdata back, but leaving the folder on the array won't work, as having that folder in both places 'confuses' unRAID. I believe it needs to be moved back, so that it only exists on cache.