Dynamix - V6 Plugins

[bonienl]

3 hours ago, Cessquill said:

Assuming it's because of the brackets.  Anything I can do (short of renaming my shares)?

 

Yes, these are the cause, but there is a bug in the plugin.

I'll make a correction so characters like '(', ')', '[' and ']' can be used.

[Cessquill]

Thanks for this guys.

 

@Frank1940 - interesting, thanks.  And I was expecting the same results too.  I'm planning a restructure of my file system, so I'll pull my Shares into line then, I've reverted to excluding shares for now.

 

Since the filesystem can handle the characters though, it's good that the plugin can be updated to accommodate.

[John_M]

The recent update to Dynamix System Stats displays the memory usage graph incorrectly, giving a negative value to Used. Is there a reason why the top of the graph has never coincided with the amount of RAM installed? This particular server has 8 GB but the graph extends to 10 GB, which, of course, can never be reached.

 

 

[Squid]

5 minutes ago, John_M said:

This particular server has 8 GB but the graph extends to 10 GB, which, of course, can never be reached.

Don't complain.  You gained 2 GB.  I've lost 2 GB

[bonienl]

It looks something wrong with the latest version of sysstat. I'll have a look.

[bonienl]

I reverted back to the previous version of sysstat.

[Squid]

@bonienl  Can you add in to autofan an option to disable logging (preferably disabled by default).  Don't think it's really necessary to have it spam logs every 5 minutes with this

Sep  7 06:46:55 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1060rpm) to: OFF (0% @ 235rpm)
Sep  7 06:52:00 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1062rpm)
Sep  7 06:57:05 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1066rpm) to: OFF (0% @ 202rpm)
Sep  7 07:02:11 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1051rpm)
Sep  7 07:07:16 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1073rpm) to: OFF (0% @ 218rpm)
Sep  7 07:12:21 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1057rpm)
Sep  7 07:17:26 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1065rpm) to: OFF (0% @ 200rpm)
Sep  7 07:22:32 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1047rpm)
Sep  7 07:27:37 tidehunter autofan: Highest disk temp is 36C, adjusting fan speed from: 163 (63% @ 1065rpm) to: 48 (18% @ 368rpm)
Sep  7 07:32:42 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: 48 (18% @ 334rpm) to: 163 (63% @ 1056rpm)
Sep  7 07:37:47 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1061rpm) to: OFF (0% @ 207rpm)
Sep  7 07:42:52 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1055rpm)
Sep  7 07:47:58 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1064rpm) to: OFF (0% @ 226rpm)
Sep  7 07:53:03 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1053rpm)
Sep  7 07:58:08 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1069rpm) to: OFF (0% @ 214rpm)
Sep  7 08:03:13 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1053rpm)
Sep  7 08:08:19 tidehunter autofan: Highest disk temp is 35C, adjusting fan speed from: 163 (63% @ 1072rpm) to: OFF (0% @ 201rpm)
Sep  7 08:13:24 tidehunter autofan: Highest disk temp is 41C, adjusting fan speed from: OFF (0% @ 0rpm) to: 163 (63% @ 1049rpm)
Sep  7 08:18:29 tidehunter autofan: Highest disk temp is 36C, adjusting fan speed from: 163 (63% @ 1072rpm) to: 48 (18% @ 347rpm)
Sep  7 08:23:34 tidehunter autofan: Highest disk temp is 40C, adjusting fan speed from: 48 (18% @ 333rpm) to: 140 (54% @ 934rpm)
Sep  7 08:28:39 tidehunter autofan: Highest disk temp is 37C, adjusting fan speed from: 140 (54% @ 938rpm) to: 71 (27% @ 518rpm)
Sep  7 08:33:45 tidehunter autofan: Highest disk temp is 39C, adjusting fan speed from: 71 (27% @ 513rpm) to: 117 (45% @ 807rpm)

 

[trurl]

5 minutes ago, Squid said:

@bonienl  Can you add in to autofan an option to disable logging (preferably disabled by default).  Don't think it's really necessary to have it spam logs every 5 minutes with this

+1

[interwebtech]

Reposting here due to my original being in the wrong group

I am having an issue where Cache_Dirs stops running. Go into setting to check and the setting is still set to Enable but it is not running. Reapplying Enable gets it running again but it eventually turns itself back off next reboot. 

 

Edited September 13, 2018 by interwebtech

[Fireball3]

Same issue with cachedirs here.

Attaching my diagnostics.

tuerke-diagnostics-20180913-2047.zip

[dlandon]

cache.dirs is not starting when the array is started.  i.e. on reboot.

[Fireball3]

For some reason my server didn't shut down last night (as usual).

This evening I found it running with one cpu pinned @100%

After stopping cache_dirs the cpu load returned to idle.

tuerke-diagnostics-20180914-2316.zip

Edited September 14, 2018 by Fireball3

[bigfoot18]

So I installed System Temp after installing Perl. Initially, everything worked fine. But when I attempt to save the settings, the drop down boxes for the senors only have one option "Not Used"

[Hoopster]

12 minutes ago, bigfoot18 said:

So I installed System Temp after installing Perl. Initially, everything worked fine. But when I attempt to save the settings, the drop down boxes for the senors only have one option "Not Used"

I had to run "sensors" on the console to see what sensors my MB had and then specify the appropriate sensor names (coretemp nct6775 in my case) in the plugin.  Once I did that, the appropriate sensors appeared in the drop downs.

 

The next time I tried to detect sensors it seemed to work, but, not initially.

 

Edited September 15, 2018 by Hoopster

[bigfoot18]

1 minute ago, Hoopster said:

I has to run "sensors" on the console to see what sensors my MB had and then specify the appropriate sensor names (coretemp nct6775 in my case) in the plugin.  Once I did that, the appropriate sensors appeared in the dropdowns

 

All I get from running that in console is a list of errors.

 

Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 8: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 10: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced
sensors_init: Can't parse bus name

 

 

[Hoopster]

6 minutes ago, bigfoot18 said:

All I get from running that in console is a list of errors.

 

Error: File /etc/sensors.d/sensors.conf, line 2: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 4: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 6: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 8: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 10: Undeclared bus id referenced
Error: File /etc/sensors.d/sensors.conf, line 14: Undeclared bus id referenced
sensors_init: Can't parse bus name

 

 

If you run cat sensors.conf from /etc/sensors.d what is the result?

 

This is mine for example:

 

[bigfoot18]

2 minutes ago, Hoopster said:

If you run cat sensors.conf from /etc/sensors.d what is the result?

 

This is mine for example:

 

This is what I get.

 

# sensors
chip "w83795adg-i2c-0-2f"
ignore "fan1"
chip "w83795adg-i2c-0-2f"
ignore "fan3"
chip "w83795adg-i2c-0-2f"
ignore "fan4"
chip "w83795adg-i2c-0-2f"
ignore "fan5"
chip "w83795adg-i2c-0-2f"
ignore "fan7"
chip "coretemp-isa-0000"
label "temp4" "CPU Temp"
chip "w83795adg-i2c-0-2f"
label "fan8" "Array Fan"

 

 

[Hoopster]

7 minutes ago, bigfoot18 said:

This is what I get.

 

# sensors
chip "w83795adg-i2c-0-2f"
ignore "fan1"
chip "w83795adg-i2c-0-2f"
ignore "fan3"
chip "w83795adg-i2c-0-2f"
ignore "fan4"
chip "w83795adg-i2c-0-2f"
ignore "fan5"
chip "w83795adg-i2c-0-2f"
ignore "fan7"
chip "coretemp-isa-0000"
label "temp4" "CPU Temp"
chip "w83795adg-i2c-0-2f"
label "fan8" "Array Fan"

 

 

It shows you the names of your sensors; w83795adg  and coretemp

 

Try entering "coretemp w83795adg" (without the quotes) in the plugin.

 

EDIT: just noticed this is post #1000 for me.  Well, that milestone went by with a whimper 😀

Edited September 15, 2018 by Hoopster

[bigfoot18]

21 minutes ago, Hoopster said:

It shows you the names of your sensors; w83795adg  and coretemp

 

Try entering "coretemp w83795adg" (without the quotes) in the plugin.

 

EDIT: just noticed this is post #1000 for me.  Well, that milestone went by with a whimper 😀

No change..

[Cessquill]

On 8/27/2018 at 4:08 PM, bonienl said:

 

Yes, these are the cause, but there is a bug in the plugin.

I'll make a correction so characters like '(', ')', '[' and ']' can be used.

Thanks for looking into this - I've just had time to check and unfortunately the form does not appear to be storing shares with brackets in.  Apologies for delay in checking - been buried in other things.

 

Also, I've just noticed that whilst it's cache-dirs is enabled on my machine, it wasn't running (something another user pointed out above).  Which would probably explain frequent temporary lockups of my machine as drives are spun.  I'm remote at the moment, but will look into it more later today.

 

 

As a side issue, has Unraid/Linux always paused the system whilst drives spin up?  I've seen others with the issue, but don't recall an answer.  I don't think it used to happen (8-10 years ago), but that could have just been fewer drives, data and requirements back then.  Now everything from downloads, transfers, Plex transcodes, log viewer, etc. is unavailable for a minute whilst 19 data drives are spun up (although the main Web GUI appears fine).

[Cessquill]

As mentioned, when rebooting cache_dirs does not start, event though it is enabled in settings.  Force saving the settings by changing a value and back again starts it up fine...

 

 

Diagnostics attached.  Any ideas, or anything I need to do?  Thanks!

 

 

Edit: this was happening in 6.5.3 also

Edited April 8 by Cessquill
Clarified text & added 6.5.3 info; removed diagnostics for safety

[Alex R. Berg]

On 9/14/2018 at 11:38 PM, Fireball3 said:

For some reason my server didn't shut down last night (as usual).

This evening I found it running with one cpu pinned @100%

After stopping cache_dirs the cpu load returned to idle.

tuerke-diagnostics-20180914-2316.zip

 

I cannot see the cache-dirs script executing in your syslog, because its not logging that start/stop behaviour. I've added that to my system, so I can see what is being done. The cache-dirs starts on the array-start event if enabled.

 

I've added some files that change the \usr\local\sbin\emhttp_event so that it logs what it does to syslog. I recommend not keeping it in the custom folder when your done testing, in case limetech changes the file at some time in the future. Be sure not to overwrite any existing files if you don't want to lose them. Though the only risk is your /boot/config/go script and it seemed that was the default.

 

Maybe there are better ways to get unRaid to log what happens in the events, but I'm not aware of them.

 

Unzip the file to /boot (or rather unzip to /tmp and investigate, then unzip or copy to /boot).

 

Best Alex

 

flash-log-events.zip

[Alex R. Berg]

On 9/14/2018 at 11:38 PM, Fireball3 said:

For some reason my server didn't shut down last night (as usual).

This evening I found it running with one cpu pinned @100%

After stopping cache_dirs the cpu load returned to idle.

tuerke-diagnostics-20180914-2316.zip

@Fireball3

 

by the way, you have a cron-problem.

 

from your syslog:

Sep 14 23:05:11 Tuerke crond[1500]: failed parsing crontab for user root: /usr/local/sbin/mover |& logger
 

maybe its related to the dynamix.mover plugin

Sep 13 19:17:17 Tuerke emhttp: shcmd (86): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#012 /usr/local/sbin/mover |& logger#012"
 

you can do 'sudo cronjob -l' to investigate

 

best Alex

 

[Fireball3]

4 hours ago, Alex R. Berg said:

I cannot see the cache-dirs script executing in your syslog, because its not logging that start/stop behaviour.

Yes, because it is not running! Issue #1

 

3 hours ago, Alex R. Berg said:

maybe its related to the dynamix.mover plugin

Sep 13 19:17:17 Tuerke emhttp: shcmd (86): cat - > /boot/config/plugins/dynamix/mover.cron <<< "# Generated mover schedule:#012 /usr/local/sbin/mover |& logger#012"
 

you can do 'sudo cronjob -l' to investigate

Thanks, definitely a dynamix entry.

You mean:

crontab -l

 

I will give your modified logging a try when I have a couple of minutes.

Maybe the other guys with the same issue can also contribute...

[zoggy]

with active streams and latest 6.6 ui.. its easily to accidentally cancel a stream when you go to click on the 'top' image