Dynamix - V6 Plugins

bonienl

By bonienl
in Plugin Support

Recommended Posts

Recommended

Posted by Zonediver,

Its not broken, just "vice versa" 😉 You can fix this. If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:" There is something "the other way around" - but it is working 😉👍 It seems the plugin does not recognise the array correctly (last update from 6.2020)      
Recommended by Squid
  • Confused
  • Thanks

3 reactions

Go to this post
Bluppylein Noob

Bluppylein

Posted
Posted
4 hours ago, Bluppylein said:

Hello Guys,

 

i have a problem with the Plugin. After i set the Array fan speed a lost all sensors and can not set only cpu and mainboard.

 

unload und load k10 not work. Deinstallation von Plugin und new Installation give no solution.

 

Any Idea?

i have delete all information in sensors and it work

Link to comment
  • Replies 4k
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

bonienl
bonienl

Notice: You must be running unRAID version 6.9 or later to use these plugins The easiest way of installing plugins is thru Community Applications. This is an apps installation manager develope

bonienl
bonienl

It has been some time since I visited the Unraid forums. Due to health issues I had to take a break, and unfortunately this break took way longer than anticipated. But I am back and will sta

bonienl
bonienl

Today has been a productive day   I have updated several Dynamix plugins, mainly bug fixes. Please check your plugins to get the updates.

Posted Images

SonOfTux Noob

SonOfTux

Posted
Posted
On 11/8/2022 at 1:39 AM, GeorgeJetson20 said:

What causes this error.  using Fan Control Pluggin, but getting this strange error with permission denied.  Not sure what this is.   Unraid 6.11.2 (but it has not worked on this PC) which is an x570 s MSI motherboard.   I don't know where the denied is coming from

 

This is what occurs when it tryies the detect from autofan.   Any help would be appreciated.

 

image.thumb.png.eb902ef546c2f47731337fb7e772a003.png<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon3/fan1_input

 

Hi,

It seems to be being caused by the fan speed script not being able to cope with PWM outputs that don't have an associated enable output, hence the

file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable) failed to open stream: No such file or directory

This issue with the nct6687 driver has been an ongoing issue for at least the last 2 years if you look back through these messages and is still waiting to be addressed.

  • Like 1
Link to comment
Pixelpaule Apprentice

Pixelpaule

Posted
Posted
On 3/3/2021 at 4:42 PM, Zonediver said:

If the sleep plug-in is active, you can enter all drives (which you want to monitor) under "Monitor disks outside array:"

There is something "the other way around" - but it is working 😉👍

It seems the plugin does not recognise the array correctly (last update from 6.2020)

 

Is it still the right approach, or is there already a fix here?

Link to comment
Phoenix Down Apprentice

Phoenix Down

Posted
Posted
On 11/26/2022 at 11:53 PM, Phoenix Down said:

Hi @bonienl, is this the right channel to report a bug? If not, please point me in the right direction :) 

 

I've been noticing an issue with Autofan in the last couple of months. It seems like whenever all of my HDDs are spun down and only my NVME cache drives are still active, Autofan gets confused and thinks there is no active drives, and shuts down all of my case fans. This causes my NVME drives to get pretty hot. After digging through the Autofan code, I discovered the issue in function_get_highest_hd_temp():

  

function_get_highest_hd_temp() {
  HIGHEST_TEMP=0
  [[ $(version $version) -ge $(version "6.8.9") ]] && HDD=1 || HDD=
  for DISK in "${HD[@]}"; do
    # Get disk state using sdspin (new) or hdparm (legacy)
    
    ########## PROBLEM HERE ########## [[ -n $HDD ]] && SLEEPING=`sdspin ${DISK}; echo $?` || SLEEPING=`hdparm -C ${DISK}|grep -c standby`
    
    ########## Fix is below ##########
    [[ -n $HDD ]] && SLEEPING=`hdparm -C ${DISK} |& grep -c standby`
    ##################################
    
    echo Disk: $DISK - Sleep: $SLEEPING
    if [[ $SLEEPING -eq 0 ]]; then
      if [[ $DISK == /dev/nvme[0-9] ]]; then
        CURRENT_TEMP=$(smartctl -n standby -A $DISK | awk '$1=="Temperature:" {print $2;exit}')
      else
        CURRENT_TEMP=$(smartctl -n standby -A $DISK | awk '$1==190||$1==194 {print $10;exit} $1=="Current"&&$3=="Temperature:" {print $4;exit}')
      fi
      if [[ $HIGHEST_TEMP -le $CURRENT_TEMP ]]; then
        HIGHEST_TEMP=$CURRENT_TEMP
      fi
    fi
  done

  echo Highest Temp: $HIGHEST_TEMP
}

 

Check out the line I marked ########## PROBLEM HERE ##########. Specifically middle condition (sdspin).

  

[[ -n $HDD ]] && SLEEPING=`sdspin ${DISK}; echo $?` || SLEEPING=`hdparm -C ${DISK}|grep -c standby`

 

"sdspin" is a shell script that runs hdparm -C on the NVME device. Here's the contents of sdspin:

  

# cat /usr/local/sbin/sdspin 
#!/bin/bash

# spin device up or down or get spinning status
# $1 device name
# $2 up or down or status
# ATA only

# hattip to Community Dev @doron

RDEVNAME=/dev/${1#'/dev/'}      # So that we can be called with either "sdX" or "/dev/sdX"

hdparm () {
  OUTPUT=$(/usr/sbin/hdparm $1 $RDEVNAME 2>&1)
  RET=$?
  [[ $RET == 0 && ${OUTPUT,,} =~ "bad/missing sense" ]] && RET=1
}

if [[ "$2" == "up" ]]; then
  hdparm "-S0"
elif [[ "$2" == "down" ]]; then
  hdparm "-y"
else
  hdparm "-C"
  [[ $RET == 0 && ${OUTPUT,,} =~ "standby" ]] && RET=2
fi

 

If I run the command directly:

  

# hdparm -C /dev/nvme0

/dev/nvme0:
 drive state is:  unknown

# echo $?
25

 

This the same exit code that sdspin returns:

  

# sdspin /dev/nvme0

# echo $?
25

 

My cache drives consists of 2x Silicon Power P34A80 1TB m.2 NVME drives. Apparently hdparm cannot get their power state, and because sdspin is looking for the word "standby", it never finds it. More importantly, the middle (sdspin) condition always sets $SLEEPING to sdspin's exit code, which is 25 in this case. And because 25 is not zero, this causes the script to think all disks are in standby mode (even though my NVME drives are still active), thus causing Autofan to shut off all case fans.

 

My fix is simple: remove the middle condition:

  

[[ -n $HDD ]] && SLEEPING=`hdparm -C ${DISK} |& grep -c standby`

 

Because the last condition is looking specifically for the word "standby" and not just taking the exit code, it works. This is because hdparm says my NVME drive's state is in "unknown", which is not "standby". That means the script correctly considers the NVME drive as NOT in standby.

 

I've locally modified the Autofan script and it's been running correctly for a few weeks. Unfortunately my local changes gets wiped out every time I reboot the server, so I'd appreciate it if you or the author can update the script to fix this bug.

 

Thanks in advance!

Is there anyone actively maintaining the Autofan plug-in? I've already presented the fix. Just need the maintainer to merge in the one-line code change.

Link to comment
GeorgeJetson20 Apprentice

GeorgeJetson20

Posted
Posted
On 12/8/2022 at 11:38 AM, SonOfTux said:

 

Hi,

It seems to be being caused by the fan speed script not being able to cope with PWM outputs that don't have an associated enable output, hence the

file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon3/pwm2_enable) failed to open stream: No such file or directory

This issue with the nct6687 driver has been an ongoing issue for at least the last 2 years if you look back through these messages and is still waiting to be addressed.

So the only solution is get a different motherboard or anything else i can do?  It's been ok temp wise because i am not pushing anything and the CPU is about 42 idle (5950X) 

Link to comment
pille Rookie

pille

Posted
Posted (edited)

Anyone has got an idea why there are not temp sensores listed? They disapeared once I added the MB temp sensor. Before that, the CPU sensor was just running fine.

yCVd5ow.png

 

Same for the Fan Auto Control. I have two PWM Fans plugged into the mainboard directly.

t05Pr1H.png

Edited by pille
Link to comment
Skylinar Rookie

Skylinar

Posted
Posted (edited)
On 12/24/2022 at 6:07 PM, lightshark85 said:

Is there a way to call for the sleep function not via the gui, but with the command line?

 

I was searching for this as well. I checked the source code a little bit on my own and it seems like you can use it via bash manually like this..

  

/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -h

 

But still not tested, only figured out a minute ago.. Let us know how you use it and if it has worked out, please ;)

Edited by Skylinar
Link to comment
lightshark85 Noob

lightshark85

Posted
Posted
28 minutes ago, Skylinar said:

 

I was searching for this as well. I checked the source code a little bit on my own and it seems like you can use it via bash manually like this..

  

/usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -V

 

But still not tested, only figured out a minute ago.. Let us know how you use it and if it has worked out, please ;)

Thanks, this totally works!

If anyone wants to copy my setup:

I use Homeassistant on a Raspy with a wake on lan switch (see documentation for homeassistant wake on lan https://www.home-assistant.io/integrations/wake_on_lan/)

I use the turn_off feature of wake on lan to call the script.

 

Here is my script to sleep the server via ssh:

 

"ssh -i /config/ssh_keys/id_YOUR_PRIVTE_KEYFILE -o 'StrictHostKeyChecking=no' [email protected] /usr/local/emhttp/plugins/dynamix.s3.sleep/scripts/s3_sleep -S"

 

bare in mind that you have to follow another guide to configure the ssh_key first, or HA can't connect to the server via ssh

Link to comment
  • 2 weeks later...
dopeytree Collaborator

dopeytree

Posted
Posted (edited)

Anyone get anywhere with the auto fan & Nct6687 driver bug?

 

The driver works for showing fan speed but if I use the autofan plugin it sets the fans to full speed or 0%.

 

For the moment just using bios settings based on CPU usage.

 

I would like to fans to turn off if selected drives (array which in future will be a ZFS cache pool) turn off for noise purposes.

 

NVMe ssds do not matter so much as on motherboard and both have heatsinks & CPU fan is very close.

Edited by dopeytree
Link to comment
undee Noob

undee

Posted
Posted

Hello everyone,

 

I'm an Unraid beginner and for now I only wanted to know if it is possibile to exewcute an automatic shutdown depending on certain IPs active on the network. Ok, found the dynamix s3 sleep plugin which after being installed is working fine - till the next reboot, then it is stopped and I have to start it again. I cannot find any errors in the syslog and cannot understand why the plugin is not starting automatically after reboot.

My setup: some old pc tower fot testing, Unraid is running in trial mode, the is only the USB key used, no array or cache disks active.

 

Thank you for your help!

Link to comment
Lordbye Rookie

Lordbye

Posted
Posted

 

Hello everybody, i have a problem with autofan. It recognizes my sensors and makes the fans go (they are pwm) but I haven't seen the % of use for a few days. I also don't know how to set the second fan which is the CPU one differently to follow the temperatures of the CPU and not the disks

 

 

 

1.png

2.png

3.png

4.png

  • Like 1
Link to comment
  • 2 weeks later...
obi-WAN-kenobi Noob

obi-WAN-kenobi

Posted
Posted (edited)
On 12/3/2022 at 9:18 PM, Bluppylein said:

i have delete all information in sensors and it work

Been struggling with making sensors work after setting array fan speed and Reinstalling/loading/unloading did not do anything.. and from the gui i cant delete something which is not there ^^ so...from where did you delete all information?


 

edit: I`m still looking for the above answer for the future endeavors; however, somehow today after i rebooted the server Ive noticed that it automatically picked the array fan speed.. so i went to check and the error disappeared and somehow all works fine (had to attach the right temp sensors for cpu +mdb tho)   😂

Edited by obi-WAN-kenobi
added footnote
Link to comment
Interstellar Enthusiast

Interstellar

Posted
Posted (edited)

Recently upgraded my motherboard and now I get this when I try and use the Fan Control software...

 

 

  

<br /><b>Warning</b>:  file_get_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: No such file or directory in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>40</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>42</b><br /><br /><b>Warning</b>:  file_put_contents(/sys/devices/platform/nct6687.2592/hwmon/hwmon2/pwm1_enable): failed to open stream: Permission denied in <b>/usr/local/emhttp/plugins/dynamix.system.autofan/include/SystemFan.php</b> on line <b>50</b><br />/sys/devices/platform/nct6687.2592/hwmon/hwmon2/fan1_input

 

 

After installing the ict6687 plugin I do have all the sensors and I can manually set the fan speed via the command line.

 

  

nct6687-isa-0a20
Adapter: ISA adapter
+12V:         12.02 V  (min = +12.00 V, max = +12.05 V)
+5V:           5.04 V  (min =  +5.03 V, max =  +5.05 V)
+3.3V:         3.35 V  (min =  +3.34 V, max =  +3.35 V)
CPU Soc:     616.00 mV (min =  +0.16 V, max =  +1.20 V)
CPU Vcore:   662.00 mV (min =  +0.66 V, max =  +0.66 V)
CPU 1P8:       0.00 V  (min =  +0.00 V, max =  +0.00 V)
CPU VDDP:      0.00 V  (min =  +0.00 V, max =  +0.00 V)
DRAM:          1.22 V  (min =  +0.23 V, max =  +2.40 V)
Chipset:     946.00 mV (min =  +0.92 V, max =  +0.95 V)
CPU SA:      898.00 mV (min =  +0.90 V, max =  +0.90 V)
Voltage #2:    1.54 V  (min =  +1.53 V, max =  +1.54 V)
AVCC3:         3.32 V  (min =  +3.32 V, max =  +3.34 V)
AVSB:          3.34 V  (min =  +3.34 V, max =  +3.36 V)
VBat:          1.06 V  (min =  +1.06 V, max =  +1.06 V)
Array Fan:    630 RPM  (min =  596 RPM, max = 3174 RPM)
Array Fan:   1532 RPM  (min =  580 RPM, max = 1540 RPM)
Array Fan:   1235 RPM  (min =    0 RPM, max = 1301 RPM)
CPU:          +30.5°C  (low  = +27.5°C, high = +87.0°C)
MB Temp:      +33.5°C  (low  = +33.0°C, high = +39.5°C)
VRM MOS:      +32.0°C  (low  = +32.0°C, high = +45.5°C)
PCH:          +46.0°C  (low  = +46.0°C, high = +53.0°C)
CPU Socket:   +31.0°C  (low  = +30.5°C, high = +56.0°C)
PCIe x1:      +29.0°C  (low  = +29.0°C, high = +30.5°C)
M2_1:         +32.0°C  (low  = +31.5°C, high = +32.0°C)

 

Searching this thread brings up the error but not the solution unless I'm being silly?

 

There is no pwm_enable, so maybe that is why it is falling over?

 

echo 255 > pwm1 for example, works.

 

  

-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan7_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 fan8_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 fan8_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in0_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in10_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in11_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in12_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in13_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in7_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in8_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 in9_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 name
drwxr-xr-x 2 root root    0 Feb  2 22:22 power/
-rw-r--r-- 1 root root 4096 Feb  5 20:19 pwm1
-rw-r--r-- 1 root root 4096 Feb  5 20:14 pwm2
-rw-r--r-- 1 root root 4096 Feb  5 20:14 pwm3
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm4
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm5
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm6
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm7
-rw-r--r-- 1 root root 4096 Feb  2 22:22 pwm8
lrwxrwxrwx 1 root root    0 Feb  2 22:08 subsystem -> ../../../../../class/hwmon/
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp1_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_input
-r--r--r-- 1 root root 4096 Feb  2 22:09 temp2_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp2_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp3_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp4_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp5_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp6_min
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_input
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_label
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_max
-r--r--r-- 1 root root 4096 Feb  2 22:08 temp7_min
-rw-r--r-- 1 root root 4096 Feb  2 22:08 uevent

 

Edited by Interstellar
Link to comment
Zonediver Community Regular

Zonediver

Posted
Posted (edited)

After the update to v 2023.02.05a, i see this:

 

grafik.thumb.png.f21f3bec774bf4f10ea48085e9e70204.png

 

...not normal (i think).

  

Feb  6 11:18:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:19:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:20:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:21:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:22:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:23:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:24:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:25:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:26:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:27:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:28:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:29:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:30:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:31:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:32:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:33:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:34:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:35:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:36:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null
Feb  6 11:37:01 Horus  crond[1123]: exit status 127 from user root /usr/local/emhttp/plugins/dynamix.system.stats/scripts/sa1 1 1 &> /dev/null

 

The Stats-Plugin was working before this update...

 

Edited by Zonediver
  • Upvote 1
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.

×
Go to topic listing