Dynamix - V6 Plugins


Recommended Posts

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.

Link to comment

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.

 

The Dynamix webGui update (2016.01.22) seemed to break a few plugins (see here) but for the most part they were fixed by reinstalling.

 

Link to comment

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?

Link to comment

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

Link to comment

The first error in each case says that the document is empty so I take that to mean that the download was corrupted, possibly zero length. I had a similar experience with the recent unRAID OS update to 6.1.7. In the end I had to update it manually.

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.

Link to comment

 

I would like to think the plugin manager verifies downloads md5 hashes before proceeding, but perhaps not.

 

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.

Link to comment

 

I would like to think the plugin manager verifies downloads md5 hashes before proceeding, but perhaps not.

 

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.

Link to comment

 

I would like to think the plugin manager verifies downloads md5 hashes before proceeding, but perhaps not.

 

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.

Dynamix never properly downloaded the .plg file (regardless of the fact that it says it did), which is why you got all the simple_xml errors.

 

If it downloaded it right, then contained within the .plg file is an MD5 for all further downloads, and a failure of that would bring an appropriate error message.

 

Generally, the only time I've seen all those simplexml errors are if your tempfs is full (possible since you're being spammed by error messages in the log), or DNS addresses need to be actually set.

 

In your case, a restart is probably going to fix all your problems

 

Link to comment

Generally, the only time I've seen all those simplexml errors are if your tempfs is full (possible since you're being spammed by error messages in the log), or DNS addresses need to be actually set.

 

In your case, a restart is probably going to fix all your problems

 

 

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.

network.png.f48e24606dc211129721cf58de853cad.png

router.png.afe7e8537d8c8bf96a70bf3a7ce62296.png

ping.png.ef72b11e97e23d929d6dd35b6a3ba706.png

Link to comment

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.

 

 

Link to comment

sorry to keep spamming this thread  :P

 

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.

spam.png.b22d57f14ad733a2f1845874aa0289f1.png

Link to comment

Okay, now, so what's spamming my log file???

That's actually an easy question.  Its the disk temperature / array status script.

 

Why its failing I have no idea since there is no line reference in the log, but to begin with, I'd look at disk settings - Poll Attributes.  Since the entries are happening every minute, I'd hazard a guess that the attribute is set to 60.  After that, I'd check your notification settings and initially try disabling all notifications, and then re-set up your smtp settings / push settings.

Link to comment

Okay, now, so what's spamming my log file???

That's actually an easy question.  Its the disk temperature / array status script.

 

Why its failing I have no idea since there is no line reference in the log, but to begin with, I'd look at disk settings - Poll Attributes.  Since the entries are happening every minute, I'd hazard a guess that the attribute is set to 60.  After that, I'd check your notification settings and initially try disabling all notifications, and then re-set up your smtp settings / push settings.

 

ha, easy for you!!

 

I don't see anything in the disk settings that would update every minute (screenshot attached).  I looked in notification settings also, but nothing seemed out of order there.

settings.png.19b996873bfc3df844b72b24ca3d7f7e.png

Link to comment

Real time updates enabled in display settings?

 

yes, but...

 

After updating a couple of options in the notification settings (enabled docker update and array status), then saving, the spamming has stopped.

 

Something must have gotten jazzed up somehow, but the issue now seems resolved.  Weird, but okay  :o

 

Thank you so much for pointing me to a resolution!!  You are a good internet citizen :)

Link to comment

Is it possible to have more than one array_fan showing in Dynamix System Temp plugin? I have 3 5in3 disk cages with one PWM fan to each Cage. Showing all 3 fans in lower right corner would be great!

 

 

JoWe

 

And it would also be nice to label the fans, like Cage1 Cage2 etc.

Link to comment

I've used the shutdown button multiple times, but it doesn't shut down the system. It stops my VM but keeps the PC running. When I power it off (after 20 minutes of waiting for the machine to stop), and come back, turning it on, it needs a parity check.

 

I don't think the Shut Down works properly.

Link to comment

I've used the shutdown button multiple times, but it doesn't shut down the system. It stops my VM but keeps the PC running. When I power it off (after 20 minutes of waiting for the machine to stop), and come back, turning it on, it needs a parity check.

 

I don't think the Shut Down works properly.

 

You need to get the Diagnostics file and attach to to your next post.  You can do this from the "Tools" tab in the GUI and then click on "Diagnostics".  You would also be helpful if you would list all of the plugins and Dockers that you have installed. 

 

I suspect that one of them is NOT shutting down and is preventing the array from stopping.  If this is occurring, the Limetech  powerdown routine will hang and not be able to shut the server down.

Link to comment

The log files unfortunately doesn't show anything since I booted up today (nothing before)

 

I just run Sonarr/Emby plugin by PhaZe, a Debian 8 VM and my main Windows 10 VM. Nothing else.

 

Will check and see if I shut down via stopping array manually and shutting down if it works or not. Thanks for the advice

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.