Jump to content
bonienl

Dynamix - V6 Plugins

2468 posts in this topic Last Reply

Recommended Posts

Also, another thing I noticed about notifications today with my monthly parity check. I got emails about the check starting, but only after accessing the webGUI, several hours after the check actually started. And again when the check finished, I got an email that it had finished, but only after accessing the webGUI, several hours after the check actually finished. Not a big deal, but not ideal.

 

I've noticed this too, some notifications don't get sent out until I open the webgui.

Share this post


Link to post

Bonienl

 

When I run there smart extended test, it gets to 90% and then aborts, the log shows aborted by user. Have you come across this?

Share this post


Link to post

it's probably getting stopped when your disk spins down.  Try extending the spindown time a bit longer, and try again.

 

*Don't forget to change it back once finished.  This post made me remember to change mine back from 5 hours, which was long enough for the extended test on my system.  :P

Share this post


Link to post

Hi bonienl,

 

Unfortunately my motherboard doesn't report fan speed, 'sensors' just reports:

  fan1: 0 RPM  (min = 0 RPM)

  fan2: 0 RPM  (min = 0 RPM)

 

So I added this to my sensors.conf file:

  ignore fan1

  ignore fan2

 

This suppressed the fan readout from 'sensors' and removed it from the dashboard, but with the 1.31c version of dynamix.system.temp it shows "## rpm" in the footer.  Could you hide the fan icon and text when there is no fan speed information?

 

Thanks!

Share this post


Link to post

Hi, i want to know if someone with a supermicro x10sll-f board successfully able to detect the fan speed sensors.

 

I downloaded the latest sensors-detect and I load the right module for the temps,  but their is one that sensors detected as jc42 and when I try loading it with modprobe, I got an error : module not found.

 

How can I load it then??  Do I need someone at lime tech to insert it in the kernel?

Share this post


Link to post

Also, another thing I noticed about notifications today with my monthly parity check. I got emails about the check starting, but only after accessing the webGUI, several hours after the check actually started. And again when the check finished, I got an email that it had finished, but only after accessing the webGUI, several hours after the check actually finished. Not a big deal, but not ideal.

 

I've noticed this too, some notifications don't get sent out until I open the webgui.

 

I have made a correction for the upcoming version. It has to do with the way emhttp updates its variables, which is different in v6 and need some more tweaking.

 

Share this post


Link to post

Hi bonienl,

 

Unfortunately my motherboard doesn't report fan speed, 'sensors' just reports:

  fan1: 0 RPM  (min = 0 RPM)

  fan2: 0 RPM  (min = 0 RPM)

 

So I added this to my sensors.conf file:

  ignore fan1

  ignore fan2

 

This suppressed the fan readout from 'sensors' and removed it from the dashboard, but with the 1.31c version of dynamix.system.temp it shows "## rpm" in the footer.  Could you hide the fan icon and text when there is no fan speed information?

 

Thanks!

 

Will add the possibility to select which icons are displayed, thanks for the suggestion.

 

Share this post


Link to post

Thanks!  I've also got a request for the stats page :)

 

I have 8 GB of RAM in my system, but the graph goes from 0 to 10 GB.  Would it be possible for Y-axis of the graph to max out at 8 GB (or whatever the actual amount of RAM is in the system)?

Share this post


Link to post

Hi, i want to know if someone with a supermicro x10sll-f board successfully able to detect the fan speed sensors.

 

I downloaded the latest sensors-detect and I load the right module for the temps,  but their is one that sensors detected as jc42 and when I try loading it with modprobe, I got an error : module not found.

 

How can I load it then??  Do I need someone at lime tech to insert it in the kernel?

Yeah I have.

Its an Atom board and I think i posted my settings in this thread.  If you can't find it, send me a reminder and I'll help you out

Share this post


Link to post

Will add the possibility to select which icons are displayed, thanks for the suggestion.

 

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer.

 

Also inactive/unused probes are removed from the dropdown menu, making the selection easier.

 

Use the plugin manager to update to the new version.

Share this post


Link to post

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer.

 

Thanks! I was easily able to remove the fan speed from the footer using the new checkboxes.  Works perfectly :)  Thank you very much bonienl! 

Share this post


Link to post

While it's working OK for me it takes ~3minutes after clicking the system temp in settings for the page to load.

After that everything works as expected, it is just the long time to access the settings that is a bit annoying but then again how many times does one access the settings.

 

Thanks for the added features on this plugin.

Share this post


Link to post

Hi, i want to know if someone with a supermicro x10sll-f board successfully able to detect the fan speed sensors.

 

I downloaded the latest sensors-detect and I load the right module for the temps,  but their is one that sensors detected as jc42 and when I try loading it with modprobe, I got an error : module not found.

 

How can I load it then??  Do I need someone at lime tech to insert it in the kernel?

Yeah I have.

Its an Atom board and I think i posted my settings in this thread.  If you can't find it, send me a reminder and I'll help you out

 

Ok, i'll look for it.  Mine is a Xeon E3 CPU on it, but i'm only looking for the Fan Speed.  I already have the Temp working for CPU & System.

Share this post


Link to post

Run a disk check on your USB stick.

 

You can take the stick out and connect it to a windows machine, run the check + corrections from there.

 

I got the same "no space errors" updating 3 plugins (Statistics, Streams, & System info). All updated to new versions and I can see it wrote to the USB just fine.

 

It could be that the file system under /var/log is full. The Stats plugin writes its log files in there, you can verify those files (none of them should have a zero size):

 

ls -l /var/log/sa

-rw-r--r-- 1 root root 6582108 Feb  1 23:04 sa01

-rw-r--r-- 1 root root 4619532 Jan 22 23:59 sa22

-rw-r--r-- 1 root root 7281228 Jan 23 23:59 sa23

-rw-r--r-- 1 root root 6527884 Jan 24 22:35 sa24

-rw-r--r-- 1 root root 3065628 Jan 25 23:59 sa25

-rw-r--r-- 1 root root 6843468 Jan 26 23:59 sa26

-rw-r--r-- 1 root root 6843468 Jan 27 23:59 sa27

-rw-r--r-- 1 root root 6843468 Jan 28 23:59 sa28

-rw-r--r-- 1 root root 6843468 Jan 29 23:59 sa29

-rw-r--r-- 1 root root 6843468 Jan 30 23:59 sa30

-rw-r--r-- 1 root root 6843468 Jan 31 23:59 sa31

 

Hi, I verified mine, as you can see, lots of them are at "0".  How to fix that ?? :

 

root@Unraid:/var/log# ls -l /var/log/sa
total 6604
-rw-r--r-- 1 root root       0 Feb  1 23:59 sa01
-rw-r--r-- 1 root root       0 Feb  2 20:01 sa02
-rw-r--r-- 1 root root 1549740 Jan 22 23:59 sa22
-rw-r--r-- 1 root root 5210112 Jan 23 23:59 sa23
-rw-r--r-- 1 root root       0 Jan 24 23:59 sa24
-rw-r--r-- 1 root root       0 Jan 25 23:59 sa25
-rw-r--r-- 1 root root       0 Jan 26 23:59 sa26
-rw-r--r-- 1 root root       0 Jan 27 23:59 sa27
-rw-r--r-- 1 root root       0 Jan 28 23:59 sa28
-rw-r--r-- 1 root root       0 Jan 29 23:59 sa29
-rw-r--r-- 1 root root       0 Jan 30 23:59 sa30
-rw-r--r-- 1 root root       0 Jan 31 23:59 sa31

Share this post


Link to post

AFTER you have rebuilt the data on this drive, it might be well to look at the Health of all your other drives.  You are particularly interested in Perimeters with ID# of 5, 196, 197,198 and 199 under the 'Disk attributes' tab on the Health Page.  Ideally, they should all be zero.  (Don't worry if one or two of the ID# numbers are not reported.)  If you have some that are not zero, ask about them.  (Oh, Perimeter ID# 199 does not indicate a potential drive failure but it is an indication of a problem in other hardware.)

 

You get to the 'Health' page for each drive by double-clicking on the assigned name of the drive under the 'Device' heading on the 'Main' page.

Is this in the wrong thread? I went back a few pages and couldn't figure out who you intended this for.

Share this post


Link to post

Will add the possibility to select which icons are displayed, thanks for the suggestion.

 

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer.

 

Also inactive/unused probes are removed from the dropdown menu, making the selection easier.

 

Use the plugin manager to update to the new version.

 

I updated to the latest version of Dynamix SystemTemp and now the Web UI went completely rogue and non-responsive for 10 minutes when I tried navigating to "System Temp" Settings via http://tower/Settings/TempSettings . Eventually it came up and allowed me to make selections. Now when I clicked on "Apply" its sitting non-responsive again for at least 5 minutes.

 

The tailing of syslog only showed these relevant entries:

 

Feb  2 21:05:18 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:07:19 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:09:21 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe

 

Share this post


Link to post

Will add the possibility to select which icons are displayed, thanks for the suggestion.

 

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer.

 

Also inactive/unused probes are removed from the dropdown menu, making the selection easier.

 

Use the plugin manager to update to the new version.

 

I updated to the latest version of Dynamix SystemTemp and now the Web UI went completely rogue and non-responsive for 10 minutes when I tried navigating to "System Temp" Settings via http://tower/Settings/TempSettings . Eventually it came up and allowed me to make selections. Now when I clicked on "Apply" its sitting non-responsive again for at least 5 minutes.

 

The tailing of syslog only showed these relevant entries:

 

Feb  2 21:05:18 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:07:19 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:09:21 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe

 

I don'r see anything in the code that may trigger this behavior. This is the only command that can be potentially problematic:

 

yes ''|/usr/sbin/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

If you can run it successfully, then I don't have any clue about where the bug is....

Share this post


Link to post

Will add the possibility to select which icons are displayed, thanks for the suggestion.

 

New version of Dynamix system temp is available. This version allows the selection of probes to be displayed in the footer.

 

Also inactive/unused probes are removed from the dropdown menu, making the selection easier.

 

Use the plugin manager to update to the new version.

 

I updated to the latest version of Dynamix SystemTemp and now the Web UI went completely rogue and non-responsive for 10 minutes when I tried navigating to "System Temp" Settings via http://tower/Settings/TempSettings . Eventually it came up and allowed me to make selections. Now when I clicked on "Apply" its sitting non-responsive again for at least 5 minutes.

 

The tailing of syslog only showed these relevant entries:

 

Feb  2 21:05:18 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:07:19 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe
Feb  2 21:09:21 REAVER emhttp: sendFile: sendfile /usr/local/emhttp/webGui/scripts/dynamix.js: Broken pipe

 

I don'r see anything in the code that may trigger this behavior. This is the only command that can be potentially problematic:

 

yes ''|/usr/sbin/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

If you can run it successfully, then I don't have any clue about where the bug is....

 

Yup, that series of commands is taking a mft amount of time on my system.

 

It might be related to unraid kernel not having the IPMI sensors modules available that i requested be added last year.

Share this post


Link to post

I timed it a few times and it ranged anywhere from 2 to 3 minutes.

 

Try this and see if it helps:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

Share this post


Link to post

I timed it a few times and it ranged anywhere from 2 to 3 minutes.

 

Try this and see if it helps:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

Tried that and it seemed to be roughly the same time-hole which seems to be the following:

Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)

 

This bit should only be done once and only once with results cached until told to re-execute again. It should not be executed on each and every page load.

Share this post


Link to post

I timed it a few times and it ranged anywhere from 2 to 3 minutes.

 

Try this and see if it helps:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

Tried that and it seemed to be roughly the same time-hole which seems to be the following:

Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)

 

This bit should only be done once and only once with results cached until told to re-execute again. It should not be executed on each and every page load.

 

I agree. Will make some mods for it.

Share this post


Link to post

I timed it a few times and it ranged anywhere from 2 to 3 minutes.

 

Try this and see if it helps:

 

wget http://www.lm-sensors.org/svn/lm-sensors/trunk/prog/detect/sensors-detect -O /tmp/sensors-detect
yes ''|perl /tmp/sensors-detect 2>&1|awk '/^modprobe/{print $2}'

 

Tried that and it seemed to be roughly the same time-hole which seems to be the following:

Do you want to probe the I2C/SMBus adapters now? (YES/no): Using driver `i2c-i801' for device 0000:00:1f.3: Intel Cougar Point (PCH)

 

This bit should only be done once and only once with results cached until told to re-execute again. It should not be executed on each and every page load.

 

I agree. Will make some mods for it.

 

Please try this (install it with installpkg): https://dl.dropboxusercontent.com/u/18726846/dynamix.system.temp.txz

 

Share this post


Link to post

A new version of the system temp plugin is available. Several significant improvements are made and all are encouraged to upgrade to this version.

 

This release solves an issue of slow GUI reponse which some people may have. The operation of the driver detection has greatly improved thanks to the wonderful help of gfjardim.  8)

 

Using the setting page is made easier by better control management and integrated dropdown menus (also note there is online information available when the 'Help' button is clicked).

 

Use the plugin manager to update to the latest version from github.

 

Enjoy!

 

Share this post


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.