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
Beiträge von jhmiller
-
-
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.
-
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.
-
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.
-
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)
-
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 doingservice collectd restart
/usr/sbin/omv-mkgraph -
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.
-
I think that its due to the first graph that was showing, maybe try deleting the old .rrd files rm /var/lib/rrdcached/db/localhost/sensors-f71808a*/*.rrd
There maybe a command to reset the rrd cache but ATM i do not know what it is.You should run sensors-detect after that.
Have a look at /usr/share/openmediavault/mkconf/collectd.d/fan this is the file that creates the fan graph, post it if you would like me to take a look at it.
-
The fix was not in that output, checked on github and was not there either. I forced it now so it should work now if you update again.
-
There was a typo when i added the cpu section so that has now been fixed. The cpu fan should still have shown the graph though.
You can re-run the update commands again to get the latest script to see if it fixes your issue. Before you do that try refreshing the OMV webui and click the refresh button on the cpu fan tab to see if it does show the graph.
-
sh -x /usr/share/openmediavault/mkconf/sensors
Run that and let me see the output
-
Hi,
OMV-sensors plug-in is working fine on my system but the graph on the dashboard are only showing CPU-temp by hour, by day, etc., which I don't think is the right one. Graph is showing 22°C for CPU which is probably the GPU temp
The output of the sensors command is this:Code
Alles anzeigenf71808a-isa-0a00 Adapter: ISA adapter +3.3V: +3.25 V in1: +1.16 V in2: +0.96 V in3: +1.10 V 3VSB: +3.25 V Vbat: +3.38 V fan1: 1746 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: +38.0°C (high = +85.0°C, hyst = +81.0°C) (crit = +100.0°C, hyst = +96.0°C) sensor = transistor fam15h_power-pci-00c4 Adapter: PCI adapter power1: 0.00 W (crit = 24.98 W) k10temp-pci-00c3 Adapter: PCI adapter temp1: +22.0°C (high = +70.0°C) (crit = +70.0°C, hyst = +69.0°C) radeon-pci-0008 Adapter: PCI adapter temp1: +22.0°C (crit = +120.0°C, hyst = +90.0°C)
How can I make graph showing the right cpu temp (temp2: 38°C) and the FAN speed (fan1: 1746 RPM)
Thanks.
Your sensor is not in the list, i have added it now so you should run
Coderm /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
to install the latest version of the script.
-
On the plugin page you should only have enabled "CPU Temperature" and "Show Cores"
You do not have sensors to monitor anything else, if you have different then above try it and let me know.
-
That does not show any errors??
-
sh -x /usr/share/openmediavault/mkconf/sensors
Run that and let me see the output
-
Im trying your todo list, and ends up with the following error when enabling in web-interface after new script:
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 '139': Warning: unrecognized option '-n' Segmentation fault
any idea?
You are running OMV2 so the wget line should be wget -O /usr/share/openmediavault/mkconf/sensors https://raw.githubusercontent.com/OpenMediaVault-Plugin-Developers/openmediavault-sensors/2.x/usr/share/openmediavault/mkconf/sensors
Run all commands again substituting the above line.
-
Try getting the latest main script
Coderm /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
If you still have issues run sh -x /usr/share/openmediavault/mkconf/sensors and let me take a look at the output@DJ-AS Are you running OMV2 or OMV3?
Try above to update the main script and if you still have problems run the debug command and let me see the output. -
The sabnzbd user is a system user so it will not show up under the users tab.
You might have used a very old version of the plugin that used a normal user.I have made the changes for the new version and just need to get it into a package
-
The OMV2 version of the plugin needs to be updated but the OMV3 version should now update without issue.
I hope to have the OMV2 version updated this weekend. -
Yes you need to enable the repo that holds the files, in this case erasmus-testing