OMV Sensos not working anymore

jhmiller · 3. Dezember 2016

If you had the dashboard enabled you will need to delete the cache from the browser you were using or use another browser or incognito mode.

ovidiur · 3. Dezember 2016

Thanks you. On incognito mode I manage to get the web interface

ovidiur · 4. Dezember 2016

I reinstalled Sensor plugin and now when I activate only CPU Temp I get this error message after applying the changes:

Code

Error #0:
exception 'OMV\ExecException' with message 'Failed to execute command 'export PATH=/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin; export LANG=C; omv-mkconf sensors balls 2>&1' with exit code '1': # sensors-detect revision $Revision$
# System: MSI MS-7865 [2.0]
# Board: MSI AM1I (MS-7865)
# Kernel: 3.16.0-4-amd64 x86_64
# Processor: AMD Sempron(tm) 3850 APU with Radeon(tm) R3 (22/0/1)


Running in automatic mode, default answers to all questions
are assumed.


Some south bridges, CPUs or memory controllers contain embedded sensors.
Do you want to scan for them? This is totally safe. (YES/no):
Module cpuid loaded successfully.
Silicon Integrated Systems SIS5595...                       No
VIA VT82C686 Integrated Sensors...                          No
VIA VT8231 Integrated Sensors...                            No
AMD K8 thermal sensors...                                   No
AMD Family 10h thermal sensors...                           No
AMD Family 11h thermal sensors...                           No
AMD Family 12h and 14h thermal sensors...                   No
AMD Family 15h thermal sensors...                           No
AMD Family 16h thermal sensors...                           Success!
    (driver `k10temp')
AMD Family 15h power sensors...                             No
AMD Family 16h power sensors...                             Success!
    (driver `fam15h_power')
Intel digital thermal sensor...                             No
Intel AMB FB-DIMM thermal sensor...                         No
Intel 5500/5520/X58 thermal sensor...                       No
VIA C7 thermal sensor...                                    No
VIA Nano thermal sensor...                                  No


Some Super I/O chips contain embedded sensors. We have to write to
standard I/O ports to probe them. This is usually safe.
Do you want to scan for Super I/O sensors? (YES/no):
Probing for Super-I/O at 0x2e/0x2f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               No
Trying family `ITE'...                                      No
Probing for Super-I/O at 0x4e/0x4f
Trying family `National Semiconductor/ITE'...               No
Trying family `SMSC'...                                     No
Trying family `VIA/Winbond/Nuvoton/Fintek'...               Yes
Found `Fintek F71808A Super IO Sensors'                     Success!
    (address 0xa00, driver `f71882fg')


Some systems (mainly servers) implement IPMI, a set of common interfaces
through which system health data may be retrieved, amongst other things.
We first try to get the information from SMBIOS. If we don't find it
there, we have to read from arbitrary I/O ports to probe for such
interfaces. This is normally safe. Do you want to scan for IPMI
interfaces? (YES/no):
Probing for `IPMI BMC KCS' at 0xca0...                      No
Probing for `IPMI BMC SMIC' at 0xca8...                     No


Some hardware monitoring chips are accessible through the ISA I/O ports.
We have to write to arbitrary I/O ports to probe them. This is usually
safe though. Yes, you do have ISA I/O ports even if you do not have any
ISA slots! Do you want to scan the ISA I/O ports? (yes/NO):


Lastly, we can probe the I2C/SMBus adapters for connected hardware
monitoring devices. This is the most risky part, and while it works
reasonably well on most systems, it has been reported to cause trouble
on some systems.
Do you want to probe the I2C/SMBus adapters now? (YES/no):
Using driver `i2c-piix4' for device 0000:00:14.0: AMD Hudson-2 SMBus
Module i2c-dev loaded successfully.


Next adapter: SMBus PIIX4 adapter at 0b00 (i2c-0)
Do you want to scan it? (yes/NO/selectively):


Next adapter: SMBus PIIX4 adapter at 0b20 (i2c-1)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x90 (i2c-2)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x91 (i2c-3)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x92 (i2c-4)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x93 (i2c-5)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x94 (i2c-6)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x95 (i2c-7)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x96 (i2c-8)
Do you want to scan it? (yes/NO/selectively):


Next adapter: Radeon i2c bit bus 0x97 (i2c-9)
Do you want to scan it? (yes/NO/selectively):




Now follows a summary of the probes I have just done.


Driver `f71882fg':
  * ISA bus, address 0xa00
    Chip `Fintek F71808A Super IO Sensors' (confidence: 9)


Driver `k10temp' (autoloaded):
  * Chip `AMD Family 16h thermal sensors' (confidence: 9)


Driver `fam15h_power' (autoloaded):
  * Chip `AMD Family 16h power sensors' (confidence: 9)


Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):
To load everything that is needed, add this to one of the system
initialization scripts (e.g. /etc/rc.d/rc.local):


#----cut here----
# Chip drivers
modprobe f71882fg
/usr/bin/sensors -s
#----cut here----


You really should try these commands right now to make sure everything
is working properly. Monitoring programs won't work until the needed
modules are loaded.


Unloading i2c-dev... OK
Unloading cpuid... OK
' in /usr/share/php/openmediavault/system/process.inc:175
Stack trace:
#0 /usr/share/openmediavault/engined/module/sensors.inc(33): OMV\System\Process->execute()
#1 /usr/share/openmediavault/engined/rpc/config.inc(163): OMVModuleSensors->applyConfig()
#2 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
#3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(150): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
#5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(528): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatuspg...', '/tmp/bgoutputJt...')
#6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(151): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
#7 /usr/share/openmediavault/engined/rpc/config.inc(208): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
#8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
#9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(124): call_user_func_array(Array, Array)
#10 /usr/share/php/openmediavault/rpc/rpc.inc(84): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
#11 /usr/sbin/omv-engined(516): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
#12 {main}

Alles anzeigen

I also run your update you proposed earlier:

Code

rm /usr/share/openmediavault/mkconf/sensors
wget -O /usr/share/openmediavault/mkconf/sensors https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/openmediavault-sensors/master/usr/share/openmediavault/mkconf/sensors
chmod +x /usr/share/openmediavault/mkconf/sensors
/usr/share/openmediavault/mkconf/sensors

Then sensors-detect and still nothing, error message and sad faces in graph.

I am lost :)... probable I have to give up This proves me I am still beginner in linux

jhmiller · 4. Dezember 2016

Try disabling the cpu temp, save and apply then re-enable it. Check the graph after refreshing the webui.
If you still see sad faces try the refresh button on the graph tab.

Another idea is too first check that the file /usr/share/openmediavault/mkconf/collectd.d/sensors is there and that the file /etc/collectd/collectd.conf has the line LoadPlugin sensors near the bottom.
Check /usr/sbin/omv-mkgraph you should see (near the bottom)
rrdtool graph ${IMGDIR}/sensors-hour.png --start ..... DEF:cpupavg=${DATA}/sensors-YOUR SENSOR HERE/temperature-temp1.rrd .........................
If both are correct try doing

service collectd restart
/usr/sbin/omv-mkgraph

ovidiur · 4. Dezember 2016

I mamged to make it work again. I removed Sensor plugin again, removed lm-sensors, apt-get autoclean, apt-get update....then just installed sensor plugin.
Now it shoes the mb temp or gpu temp in graph which is around 26^o C. CPU shloud be around 39^o C.

Should I run that update again?

ovidiur · 4. Dezember 2016

Somehow we have to get in graph the readings from temp2 and fan1 from f71808a-isa-0a00.
If we can also get other Items would be nice but not necessary.

Code

f71808a-isa-0a00
Adapter: ISA adapter
+3.3V:        +3.25 V  
in1:          +1.21 V  
in2:          +0.96 V  
in3:          +1.09 V  
3VSB:         +3.23 V  
Vbat:         +3.38 V  
fan1:        1762 RPM
fan2:           0 RPM  ALARM
fan3:           0 RPM  ALARM
temp1:          FAULT  (high = +85.0°C, hyst = +81.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)  sensor = transistor
temp2:        +39.0°C  (high = +85.0°C, hyst = +81.0°C)
                       (crit = +100.0°C, hyst = +96.0°C)  sensor = transistor


k10temp-pci-00c3
Adapter: PCI adapter
temp1:        +26.0°C  (high = +70.0°C)
                       (crit = +70.0°C, hyst = +69.0°C)


fam15h_power-pci-00c4
Adapter: PCI adapter
power1:        0.00 W  (crit =  24.98 W)


radeon-pci-0008
Adapter: PCI adapter
temp1:        +27.0°C  (crit = +120.0°C, hyst = +90.0°C)

Alles anzeigen

jhmiller · 4. Dezember 2016

Until a new package is released you will need to run the update commands, this is to avoid releasing a bad package.

I have just updated the script as it was looking for temp1.rrd file but your sensor is using the temp2.rrd, that was the cause of the wrong numbers graph issue (i think)

ovidiur · 4. Dezember 2016

Thank you very much.
CPU is now showing correctly in graph, but no fan speed graph even if it is activated in plugin.

jhmiller · 4. Dezember 2016

What is in this file /usr/share/openmediavault/mkconf/collectd.d/fan

Run cat /usr/share/openmediavault/mkconf/collectd.d/fan

The file will only be there if you have cpu fan activated on the plugin page, if it is still not there please run the debug command again.

ovidiur · 4. Dezember 2016

The file is there and this is the content

Code

set -e
. /etc/default/openmediavault
. /usr/share/openmediavault/scripts/helper-functions
OMV_COLLECTD_CONFIG=${OMV_COLLECTD_CONFIG:-"/etc/collectd/collectd.conf"}
OMV_COLLECTD_RRDTOOL_MKGRAPH=${OMV_COLLECTD_RRDTOOL_MKGRAPH:-"/usr/sbin/omv-mkgraph"}
cat <<EOF >> ${OMV_COLLECTD_CONFIG}
LoadPlugin fan
EOF
cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
# <<< [openmediavault] fan-script
# Plugin: fan
TITLE_LOAD="CPU fan speed"
COLOR_CPU1_FAN="#000000" # black
COLOR_CPU2_FAN="#ff0000" # red
COLOR_SYS_FAN="#00CC00" # black
EOF
for ucperiod in HOUR DAY WEEK MONTH YEAR; do
        lcperiod=$(echo ${ucperiod} | tr '[:upper:]' '[:lower:]')
        cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
rrdtool graph \${IMGDIR}/fan-${lcperiod}.png --start \${${ucperiod}START} \${DEFAULTS} --title "\${TITLE_LOAD}\${${ucperiod}TITLE}" --slope-mode --upper-limit 2000 --lower-limit 0 --units-exponent 0 \
  DEF:fan1avg=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:AVERAGE \
  DEF:fan1pmin=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:MIN \
  DEF:fan1pmax=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:MAX \
  LINE1:fan1avg\${COLOR_CPU1_FAN}:"CPU Fan" \
  GPRINT:fan1pmin:MIN:"%4.2lf Min" \
  GPRINT:fan1avg:AVERAGE:"%4.2lf Avg" \
  GPRINT:fan1pmax:MAX:"%4.2lf Max" \
  GPRINT:fan1avg:LAST:"%4.2lf Last\l" \
COMMENT:"\${LASTUPDATE}" >/dev/null
EOF
done
cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
# >>> [openmediavault] fan-script
EOF

Alles anzeigen

Looks like the reference to "/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd" is ok but I am not an expert.

Sorry to bothering you so much...you spend a lot of time helping me

jhmiller · 4. Dezember 2016

Take a look in /var/lib/rrdcached/db/localhost/sensors-f71808a-isa-0a00/
See if fanspeed-fan1.rrd is there.

Run sh -x /usr/share/openmediavault/mkconf/sensors again and give me the output.

I am happy to help as it will help others with the same senors.

ovidiur · 4. Dezember 2016

fanspeed-fan1.rrd is there.

Debug output see attached:

jhmiller · 4. Dezember 2016

Can you show what is in the file /usr/share/openmediavault/mkconf/collectd.d/fan

Everything looks good in the debug log but it does not show what is written to the fan file.

ovidiur · 4. Dezember 2016

This is the content of the fan file:

Bash

#!/bin/sh
#
# This file is part of OpenMediaVault.
#
# @license   http://www.gnu.org/licenses/gpl.html GPL Version 3
# @author    Volker Theile <volker.theile@openmediavault.org>
# @copyright Copyright (c) 2009-2015 Volker Theile
#
# OpenMediaVault is free software: you can redistribute it and/or modify
# it under the terms of the GNU General Public License as published by
# the Free Software Foundation, either version 3 of the License, or
# any later version.
#
# OpenMediaVault is distributed in the hope that it will be useful,
# but WITHOUT ANY WARRANTY; without even the implied warranty of
# MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the
# GNU General Public License for more details.
#
# You should have received a copy of the GNU General Public License
# along with OpenMediaVault. If not, see <http://www.gnu.org/licenses/>.


set -e


. /etc/default/openmediavault
. /usr/share/openmediavault/scripts/helper-functions


OMV_COLLECTD_CONFIG=${OMV_COLLECTD_CONFIG:-"/etc/collectd/collectd.conf"}
OMV_COLLECTD_RRDTOOL_MKGRAPH=${OMV_COLLECTD_RRDTOOL_MKGRAPH:-"/usr/sbin/omv-mkgraph"}


cat <<EOF >> ${OMV_COLLECTD_CONFIG}
LoadPlugin fan


EOF


cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
# <<< [openmediavault] fan-script
# Plugin: fan
TITLE_LOAD="CPU fan speed"
COLOR_CPU1_FAN="#000000" # black
COLOR_CPU2_FAN="#ff0000" # red
COLOR_SYS_FAN="#00CC00" # black
EOF
for ucperiod in HOUR DAY WEEK MONTH YEAR; do
        lcperiod=$(echo ${ucperiod} | tr '[:upper:]' '[:lower:]')
        cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
rrdtool graph \${IMGDIR}/fan-${lcperiod}.png --start \${${ucperiod}START} \${DEFAULTS} --title "\${TITLE_LOAD}\${${ucperiod}TITLE}" --slope-mode --upper-limit 2000 --lower-limit 0 --units-exponent 0 \
  DEF:fan1avg=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:AVERAGE \
  DEF:fan1pmin=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:MIN \
  DEF:fan1pmax=\${DATA}/sensors-f71808a-isa-0a00/fanspeed-fan1.rrd:value:MAX \
  LINE1:fan1avg\${COLOR_CPU1_FAN}:"CPU Fan" \
  GPRINT:fan1pmin:MIN:"%4.2lf Min" \
  GPRINT:fan1avg:AVERAGE:"%4.2lf Avg" \
  GPRINT:fan1pmax:MAX:"%4.2lf Max" \
  GPRINT:fan1avg:LAST:"%4.2lf Last\l" \
COMMENT:"\${LASTUPDATE}" >/dev/null
EOF
done
cat <<EOF >> ${OMV_COLLECTD_RRDTOOL_MKGRAPH}
# >>> [openmediavault] fan-script
EOF

Alles anzeigen

I think its the same as posted earlier but at that time I deleted the commented lines.

jhmiller · 4. Dezember 2016

Check in the folder /var/lib/openmediavault/rrd/ for fan-day.png and other png files starting with fan-
If they are there then you should only need to refresh the OMV webui

ovidiur · 4. Dezember 2016

fan-day.png is there and the other fan-*.png files.
Refreshed the webui...no fan speed graph

Am I doing something wrong? I only activated CPU temp and CPU fan speed in the plugin settings. Added the OMV Sensor widget on the dashboard but this only show the CPU temperature related graphs (by day, week, month, year). No CPU fan speed graph. Do I miss something?

jhmiller · 4. Dezember 2016

I do not know whats up, everything is as it should be as far as i can tell.
Just something about your fan sensor that does not want to play ball.

ovidiur · 4. Dezember 2016

I looked at /usr/share/openmediavault/mkconf/sensors and noticed that in the do_fan1() section, in case "$cpu_fan" in the "sensors-f71808a"*) rrd=2 ;; was missing.

I added it backed up the original file and replace it....but no go with CPU fan speed graph

Code

do_fan1() {
if [ ! -z $cpu_fan ]; then
    if [ "$cpu_fan" = "sensors-emc6d103-i2c-1-2e" ]; then
        cat <<EOF >> $FANoutfile
  DEF:fan1avg=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan2.rrd:value:AVERAGE ${end}
  DEF:fan1pmin=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan2.rrd:value:MIN ${end}
  DEF:fan1pmax=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan2.rrd:value:MAX ${end}
  LINE1:fan1avg\\\${COLOR_CPU1_FAN}:"${LINEcpuFAN}1" ${end}
  GPRINT:fan1pmin:MIN:"%4.2lf Min" ${end}
  GPRINT:fan1avg:AVERAGE:"%4.2lf Avg" ${end}
  GPRINT:fan1pmax:MAX:"%4.2lf Max" ${end}
  GPRINT:fan1avg:LAST:"%4.2lf Last\l" ${end}
  DEF:fan2avg=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan1.rrd:value:AVERAGE ${end}
  DEF:fan2pmin=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan1.rrd:value:MIN ${end}
  DEF:fan2pmax=\\\${DATA}/sensors-emc6d103-i2c-1-2e/fanspeed-fan1.rrd:value:MAX ${end}
  LINE1:fan2avg\\\${COLOR_CPU2_FAN}:"${LINEcpuFAN}2" ${end}
  GPRINT:fan2pmin:MIN:"%4.2lf Min" ${end}
  GPRINT:fan2avg:AVERAGE:"%4.2lf Avg" ${end}
  GPRINT:fan2pmax:MAX:"%4.2lf Max" ${end}
  GPRINT:fan2avg:LAST:"%4.2lf Last\l" ${end}
EOF


    else


    case "$cpu_fan" in
        "sensors-nct6792*"*) rrd=2 ;;
        "sensors-nct6776"*) rrd=2 ;;
        "sensors-nct6779"*) rrd=2 ;;
        "sensors-w83627thf"*) rrd=2 ;;
        "sensors-fschds-"*) rrd=2 ;;
	"sensors-f71808a"*) rrd=2 ;; ### added this ###
        *) rrd=1 ;;
    esac
        cat <<EOF >> $FANoutfile
  DEF:fan1avg=\\\${DATA}/${cpu_fan}/fanspeed-fan${rrd}.rrd:value:AVERAGE ${end}
  DEF:fan1pmin=\\\${DATA}/${cpu_fan}/fanspeed-fan${rrd}.rrd:value:MIN ${end}
  DEF:fan1pmax=\\\${DATA}/${cpu_fan}/fanspeed-fan${rrd}.rrd:value:MAX ${end}
  LINE1:fan1avg\\\${COLOR_CPU1_FAN}:"${LINEcpuFAN}" ${end}
  GPRINT:fan1pmin:MIN:"%4.2lf Min" ${end}
  GPRINT:fan1avg:AVERAGE:"%4.2lf Avg" ${end}
  GPRINT:fan1pmax:MAX:"%4.2lf Max" ${end}
  GPRINT:fan1avg:LAST:"%4.2lf Last\l" ${end}
EOF


    fi
fi
}

Alles anzeigen

It was just a beginner try, don't laugh

ovidiur · 4. Dezember 2016

Changed this "sensors-f71808a"*) rrd=2 ;; into this "sensors-f71808a"*) rrd=1 ;; becouse my fan readings is at fan1.rrd

but still no go

jhmiller · 4. Dezember 2016

All fans use a value of 1 unless its in the list *) rrd=1

I have been looking at the code and your latest output and can not find anything amiss

Jetzt mitmachen!