[Sensors] OMV-Sensors in OMV 4.1.x

    • OMV 4.x

    This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

    • [Sensors] OMV-Sensors in OMV 4.1.x

      Hi,

      After several years, I'm back here ;) OMV have really upgraded since I left and I'm please to see that. For several personal reasons (kids ;) ) I left the project at some time, but I will have more time to come as the kids grows up !
      Anyway, I'm planning to move my actual NAS witch is running on a Windows Server 2012 Essential (fine but getting old...) to OMV ;)

      I'm trying to do everything I was doing with it with OMV and I'm near the goal, except to with the ability to watch for my CPU & HDD temp.

      I have seen some posts in the forums but cannot find the answer for OMV 4.x.

      Is the plugin OMV-sensors available as I cannot see it in the plugins with OMV-extras installed?
      I'm actually running with a backport 4.14 kernel.

      Thanks for the answer,
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • The plugin is not in the OMV 4.x repo but the 3.x plugin might work. @jhmiller should be able to answer that and put it in the 4.x repo if it does work.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hi Aaron ;)

      Thanks for your answer and the next question is :

      how can I install an OMV v3 plugin in OMV v4 ? ;)

      Download .deb file and install it the hard way (dpkg -i ...) ?

      Cheers,
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • sbocquet wrote:

      how can I install an OMV v3 plugin in OMV v4 ?

      Download .deb file and install it the hard way (dpkg -i ...) ?
      Download it from here. Then you can either upload it to the omv web interface in the plugin tab or use dpkg.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Here the install log for info.

      Shell-Script

      1. Reading package lists...
      2. Building dependency tree...
      3. Reading state information...
      4. The following NEW packages will be installed:
      5. openmediavault-sensors
      6. 0 upgraded, 1 newly installed, 0 to remove and 0 not upgraded.
      7. Need to get 0 B/53.6 kB of archives.
      8. After this operation, 295 kB of additional disk space will be used.
      9. Get:1 file:/var/cache/openmediavault/archives openmediavault-sensors 3.0 [53.6 kB]
      10. Selecting previously unselected package openmediavault-sensors.
      11. (Reading database ... (Reading database ... 5%(Reading database ... 10%(Reading database ... 15%(Reading database ... 20%(Reading database ... 25%(Reading database ... 30%(Reading database ... 35%(Reading database ... 40%(Reading database ... 45%(Reading database ... 50%(Reading database ... 55%(Reading database ... 60%(Reading database ... 65%(Reading database ... 70%(Reading database ... 75%(Reading database ... 80%(Reading database ... 85%(Reading database ... 90%(Reading database ... 95%(Reading database ... 100%(Reading database ... 56881 files and directories currently installed.)
      12. Preparing to unpack .../openmediavault-sensors_3.0_all.deb ...
      13. Unpacking openmediavault-sensors (3.0) ...
      14. Setting up openmediavault-sensors (3.0) ...
      15. Initial configuration.
      16. WARNING: The function 'omv_config_add_element' is deprecated.
      17. WARNING: The function 'omv_config_add_element' is deprecated.
      18. WARNING: The function 'omv_config_add_element' is deprecated.
      19. WARNING: The function 'omv_config_add_element' is deprecated.
      20. WARNING: The function 'omv_config_add_element' is deprecated.
      21. WARNING: The function 'omv_config_add_element' is deprecated.
      22. WARNING: The function 'omv_config_add_element' is deprecated.
      23. WARNING: The function 'omv_config_add_element' is deprecated.
      24. WARNING: The function 'omv_config_add_element' is deprecated.
      25. WARNING: The function 'omv_config_add_element' is deprecated.
      26. WARNING: The function 'omv_config_add_element' is deprecated.
      27. WARNING: The function 'omv_config_add_element' is deprecated.
      28. WARNING: The function 'omv_config_add_element' is deprecated.
      29. WARNING: The function 'omv_config_add_element' is deprecated.
      30. WARNING: The function 'omv_config_add_element' is deprecated.
      31. WARNING: The function 'omv_config_add_element' is deprecated.
      32. WARNING: The function 'omv_config_add_element' is deprecated.
      33. WARNING: The function 'omv_config_add_element' is deprecated.
      34. # sensors-detect revision $Revision$
      35. # System: Microsoft Corporation Virtual Machine [Hyper-V UEFI Release v1.0]
      36. # Kernel: 4.14.0-0.bpo.3-amd64 x86_64
      37. # Processor: Intel(R) Xeon(R) CPU E5-2667 v3 @ 3.20GHz (6/63/2)
      38. Running in automatic mode, default answers to all questions
      39. are assumed.
      40. Some south bridges, CPUs or memory controllers contain embedded sensors.
      41. Do you want to scan for them? This is totally safe. (YES/no):
      42. Module cpuid loaded successfully.
      43. Silicon Integrated Systems SIS5595... No
      44. VIA VT82C686 Integrated Sensors... No
      45. VIA VT8231 Integrated Sensors... No
      46. AMD K8 thermal sensors... No
      47. AMD Family 10h thermal sensors... No
      48. AMD Family 11h thermal sensors... No
      49. AMD Family 12h and 14h thermal sensors... No
      50. AMD Family 15h thermal sensors... No
      51. AMD Family 16h thermal sensors... No
      52. AMD Family 15h power sensors... No
      53. AMD Family 16h power sensors... No
      54. Intel digital thermal sensor... No
      55. Intel AMB FB-DIMM thermal sensor... No
      56. Intel 5500/5520/X58 thermal sensor... No
      57. VIA C7 thermal sensor... No
      58. VIA Nano thermal sensor... No
      59. Some Super I/O chips contain embedded sensors. We have to write to
      60. standard I/O ports to probe them. This is usually safe.
      61. Do you want to scan for Super I/O sensors? (YES/no):
      62. Probing for Super-I/O at 0x2e/0x2f
      63. Trying family `National Semiconductor/ITE'... No
      64. Trying family `SMSC'... No
      65. Trying family `VIA/Winbond/Nuvoton/Fintek'... No
      66. Trying family `ITE'... No
      67. Probing for Super-I/O at 0x4e/0x4f
      68. Trying family `National Semiconductor/ITE'... No
      69. Trying family `SMSC'... No
      70. Trying family `VIA/Winbond/Nuvoton/Fintek'... No
      71. Trying family `ITE'... No
      72. Some systems (mainly servers) implement IPMI, a set of common interfaces
      73. through which system health data may be retrieved, amongst other things.
      74. We first try to get the information from SMBIOS. If we don't find it
      75. there, we have to read from arbitrary I/O ports to probe for such
      76. interfaces. This is normally safe. Do you want to scan for IPMI
      77. interfaces? (YES/no):
      78. Probing for `IPMI BMC KCS' at 0xca0... No
      79. Probing for `IPMI BMC SMIC' at 0xca8... No
      80. Some hardware monitoring chips are accessible through the ISA I/O ports.
      81. We have to write to arbitrary I/O ports to probe them. This is usually
      82. safe though. Yes, you do have ISA I/O ports even if you do not have any
      83. ISA slots! Do you want to scan the ISA I/O ports? (YES/no):
      84. Probing for `National Semiconductor LM78' at 0x290... No
      85. Probing for `National Semiconductor LM79' at 0x290... No
      86. Probing for `Winbond W83781D' at 0x290... No
      87. Probing for `Winbond W83782D' at 0x290... No
      88. Lastly, we can probe the I2C/SMBus adapters for connected hardware
      89. monitoring devices. This is the most risky part, and while it works
      90. reasonably well on most systems, it has been reported to cause trouble
      91. on some systems.
      92. Do you want to probe the I2C/SMBus adapters now? (YES/no):
      93. Sorry, no supported PCI bus adapters found.
      94. Module i2c-dev loaded successfully.
      95. Sorry, no sensors were detected.
      96. Either your system has no sensors, or they are not supported, or
      97. they are connected to an I2C or SMBus adapter that is not
      98. supported. If you find out what chips are on your board, check
      99. http://www.lm-sensors.org/wiki/Devices for driver status.
      100. Processing triggers for openmediavault (4.1.0-1) ...
      101. Updating locale files ...
      102. >>> *************** Error ***************
      103. Failed to read from socket: Connection reset by peer
      104. <<< *************************************
      105. Updating file permissions ...
      106. Purging internal cache ...
      107. Restarting engine daemon ...
      108. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f110f1ba8c8>
      109. Traceback (most recent call last):
      110. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      111. TypeError: 'NoneType' object is not callable
      112. Exception ignored in: <function WeakValueDictionary.__init__.<locals>.remove at 0x7f110f1ba8c8>
      113. Traceback (most recent call last):
      114. File "/usr/lib/python3.5/weakref.py", line 117, in remove
      115. TypeError: 'NoneType' object is not callable
      116. Done ...
      Display All
      As I'm testing all my stuff in a VM, I'm not surprise by the no sensors detected, but it seems to install correctly...

      I have some Python error at the end, but I have read that it should be resolved sooner or later ?
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • Ok... got errors but the answer was post several times... If someone could delete post 6 to 10 !!!

      When I try to activate the plugin, I have this error. It seems that omv-mkgraph is no more present in v4.x...
      Maybe some works to do on the plugin to have it running on OMV v4.

      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 '2': sed: can't read /usr/sbin/omv-mkgraph: No such file or directory
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • sbocquet wrote:

      I have some Python error at the end, but I have read that it should be resolved sooner or later ?
      This is a python bug. While there is a fix on the forum, I am waiting for debian to fix it.

      sbocquet wrote:

      When I try to activate the plugin, I have this error. It seems that omv-mkgraph is no more present in v4.x...
      Maybe some works to do on the plugin to have it running on OMV v4.
      It probably still works on systems that have upgraded from 3.x to 4.x because omv-mkgraph is still around. I guess the plugin needs more changes for OMV 4.x. While I use lm-sensors, I don't use the graphs in OMV and none of my test OMV boxes are physical.

      sbocquet wrote:

      got errors but the answer was post several times
      If you see an error message, it is actually the spam filter putting the post in moderation (long posts and/or links in posts do that). So, no need to re-submit.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • ryecoaaron wrote:



      It probably still works on systems that have upgraded from 3.x to 4.x because omv-mkgraph is still around. I guess the plugin needs more changes for OMV 4.x. While I use lm-sensors, I don't use the graphs in OMV and none of my test OMV boxes are physical.
      I upgraded from OMV 3 to OMV 4. But since the Sensors plugin is not available for OMV 4, I removed it from OMV 3 before upgrading to OMV 4.

      The plugin seems to have installed OK on OMV 4, but it bombs later when setting it up because omv-mkgraph is missing.
      OMV 4.x - ASRock Rack C2550D4I - 16GB ECC - Silverstone DS380
    • ryecoaaron wrote:

      It probably still works on systems that have upgraded from 3.x to 4.x because omv-mkgraph is still around. I guess the plugin needs more changes for OMV 4.x. While I use lm-sensors, I don't use the graphs in OMV and none of my test OMV boxes are physical.
      I understood from a post some time ago that you are running OMV4 on your QNAP TS451. Do you use lm-sensors to manage fan control on that box? How exactly? If not then how is it done?

      Thanks
    • namirda wrote:

      you are running OMV4 on your QNAP TS451
      Yep.

      namirda wrote:

      Do you use lm-sensors to manage fan control on that box?
      Nope. I have lm-sensors installed but I just let the system manage the fan.
      omv 4.1.13 arrakis | 64 bit | 4.15 proxmox kernel | omvextrasorg 4.1.13
      omv-extras.org plugins source code and issue tracker - github

      Please read this before posting a question and this and this for docker questions.
      Please don't PM for support... Too many PMs!
    • Hi there !

      Now that OMV 4 is considered as stable, any chance to have an update to let this plugin run on it ?

      Cheers,
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • I'l trying to make it work even if the GUI seems broken with the omv-mkgraph command (replaced by omv-mkrrdgraph)

      First step -> Catch and generate the datas => done

      - apt-get install lm-sensors and run sensor-detect

      - added a /etc/collectd/collectd.conf.d/sensors.conf file filled with
      LoadPlugin sensors

      - added a /etc/collectd/collectd.conf.d/smart.conf file filled with
      LoadPlugin smart

      - apt-get install libatasmart4 (for sata datas)

      - service collectd restart



      # ls -al /var/lib/rrdcached/db/localhost/
      total 196
      drwxr-xr-x 49 root root 4096 avril 11 15:42 .
      drwxr-xr-x 3 root root 4096 mars 15 10:13 ..
      drwxr-xr-x 2 root root 4096 mars 15 10:13 cpu-0
      drwxr-xr-x 2 root root 4096 mars 15 10:13 cpu-1
      drwxr-xr-x 2 root root 4096 mars 15 10:13 df-root
      drwxr-xr-x 2 root root 4096 mars 15 10:31 df-srv-dev-disk-by-id-ata-SAMSUNG_MZ7LN512HCHP-000L1_S1ZKNXAG526958-part5
      drwxr-xr-x 2 root root 4096 avril 5 12:38 df-StoragePool
      ...
      drwxr-xr-x 2 root root 4096 mars 15 10:13 interface-enp3s0
      drwxr-xr-x 2 root root 4096 mars 15 10:13 interface-lo
      drwxr-xr-x 2 root root 4096 mars 15 10:13 load
      drwxr-xr-x 2 root root 4096 mars 15 10:13 memory
      drwxr-xr-x 2 root root 4096 mars 15 10:13 rrdcached
      drwxr-xr-x 2 root root 4096 mars 21 16:27 sensors-coretemp-isa-0000
      drwxr-xr-x 2 root root 4096 avril 9 23:04 sensors-it8718-isa-0290
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sda
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdb
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdc
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sde
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdf
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdg
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdh
      drwxr-xr-x 2 root root 4096 avril 11 15:42 smart-sdi

      Now, I need to understand how omv-mkrrdgraph works...

      As far as I can see, a conf file is need in /usr/share/openmediavault/mkrrdgraph/plugins.d to generate the .png file displayed in the GUI...

      Any help is welcome for those who wants... ;)
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • ryecoaaron wrote:

      Nope. I have lm-sensors installed but I just let the system manage the fan.

      Sorry to keep coming back on this one!

      OMV4 is running fine on my TS-451 except that the fan runs all the time where it never used to do so using qnap software.

      I have installed lm-sensors and fancontrol but I am concluding from "sensors-detect" and "pwmconfig" that there are no pwm-capable sensor modules installed.

      Does that sound right to you?
      What does the output of "sensors" look like on your machine?
      Does your fan also run 24/7?
      What have you got in your lm-sensors config file?
      In what way does the "system manage the fan"?

      Thanks for your help.

      N

      EDIT - Please ignore these questions. The problem was that SmartFan was enabled in BIOS which somehow hides the fan from lm-sensors. With SmartFan disabled in BIOS all works as expected.

      The post was edited 1 time, last by namirda ().

    • Yes. The plugin need to be upgraded.

      I managed to get it work the hard way, without the plugin. The dark side is that I must redo the changes at each OMV update. I saved those and just copy back the conf files.
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • First, you need to collect the datas => see post 12

      Second, you need to generate the graphs with omv-mkrrdgraph

      Source Code

      1. root@home-server:/# cd /usr/share/openmediavault/mkrrdgraph/plugins.d/
      2. root@home-server:/usr/share/openmediavault/mkrrdgraph/plugins.d# ls -al
      3. total 88
      4. drwxr-xr-x 3 root root 4096 mai 9 21:22 .
      5. drwxr-xr-x 3 root root 4096 mars 15 10:11 ..
      6. -rwxr-xr-x 1 root root 3849 avril 27 10:51 cpu-0.py
      7. -rwxr-xr-x 1 root root 3849 avril 27 14:44 cpu-0.sav
      8. -rwxr-xr-x 1 root root 3846 avril 30 10:05 cpu-1.py
      9. -rwxr-xr-x 1 root root 3846 avril 30 10:23 cpu-1.sav
      10. -rwxr-xr-x 1 root root 3254 mars 30 18:40 cpu.sav
      11. -rwxr-xr-x 1 root root 3455 mai 8 20:50 df.py
      12. -rwxr-xr-x 1 root root 3455 avril 19 00:25 df.sav
      13. -rwxr-xr-x 1 root root 8701 avril 27 09:44 disk.py
      14. -rwxr-xr-x 1 root root 8701 avril 27 09:52 disk.sav
      15. -rwxr-xr-x 1 root root 3762 mai 8 20:51 interface.py
      16. -rwxr-xr-x 1 root root 3762 avril 19 00:26 interface.sav
      17. -rwxr-xr-x 1 root root 3302 mai 8 20:51 load.py
      18. -rwxr-xr-x 1 root root 3302 avril 19 00:26 load.sav
      19. -rwxr-xr-x 1 root root 4077 mai 8 20:51 memory.py
      20. -rwxr-xr-x 1 root root 4077 avril 19 00:26 memory.sav
      Display All
      For example, I added the CPU core temp to the CPU usage graph like this (add the lines with sensors-coretemp-*/*.rrd generated by collectd):

      Source Code

      1. import openmediavault.mkrrdgraph
      2. import openmediavault.subprocess
      3. class Plugin(openmediavault.mkrrdgraph.IPlugin):
      4. def create_graph(self, config):
      5. # http://paletton.com/#uid=33r0-0kwi++bu++hX++++rd++kX
      6. config.update({
      7. 'title_cpu': 'CPU-0 usage & temperature',
      8. 'color_cpu_idle': '#e7e7e7',
      9. 'color_cpu_nice': '#00df00',
      10. 'color_cpu_user': '#0000fd',
      11. 'color_cpu_waitio': '#fdaf00',
      12. 'color_cpu_system': '#fd0000',
      13. 'color_cpu_softirq': '#fd00fd',
      14. 'color_cpu_irq': '#9f009f',
      15. 'color_cpu_steal': '#000000'
      16. })
      17. args = []
      18. args.append('{image_dir}/cpu-0-{period}.png'.format(**config))
      19. args.extend(config['defaults'])
      20. args.extend(['--start', config['start']])
      21. args.extend(['--title', '"{title_cpu}{title_by_period}"'.format(**config)])
      22. args.append('--slope-mode')
      23. args.extend(['--upper-limit', '100'])
      24. args.extend(['--lower-limit', '0'])
      25. args.append('--rigid')
      26. args.extend(['--vertical-label', 'Percent/Temp.'])
      27. args.append('DEF:idle={data_dir}/cpu-0/cpu-idle.rrd:value:AVERAGE'.format(**config))
      28. args.append('DEF:nice={data_dir}/cpu-0/cpu-nice.rrd:value:AVERAGE'.format(**config))
      29. args.append('DEF:user={data_dir}/cpu-0/cpu-user.rrd:value:AVERAGE'.format(**config))
      30. args.append('DEF:waitio={data_dir}/cpu-0/cpu-wait.rrd:value:AVERAGE'.format(**config))
      31. args.append('DEF:system={data_dir}/cpu-0/cpu-system.rrd:value:AVERAGE'.format(**config))
      32. args.append('DEF:softirq={data_dir}/cpu-0/cpu-softirq.rrd:value:AVERAGE'.format(**config))
      33. args.append('DEF:interrupt={data_dir}/cpu-0/cpu-interrupt.rrd:value:AVERAGE'.format(**config))
      34. args.append('DEF:steal={data_dir}/cpu-0/cpu-steal.rrd:value:AVERAGE'.format(**config))
      35. args.append('DEF:tavg={data_dir}/sensors-coretemp-isa-0000/temperature-temp2.rrd:value:AVERAGE'.format(**config))
      36. args.append('DEF:tmin={data_dir}/sensors-coretemp-isa-0000/temperature-temp2.rrd:value:MIN'.format(**config))
      37. args.append('DEF:tmax={data_dir}/sensors-coretemp-isa-0000/temperature-temp2.rrd:value:MAX'.format(**config))
      38. args.append('AREA:steal{color_cpu_steal}:"Steal"'.format(**config))
      39. args.append('AREA:system{color_cpu_system}:"System":STACK'.format(**config))
      40. args.append('AREA:waitio{color_cpu_waitio}:"Wait-IO":STACK'.format(**config))
      41. args.append('AREA:nice{color_cpu_nice}:"Nice":STACK'.format(**config))
      42. args.append('AREA:user{color_cpu_user}:"User":STACK'.format(**config))
      43. args.append('AREA:softirq{color_cpu_softirq}:"Soft-IRQ":STACK'.format(**config))
      44. args.append('AREA:interrupt{color_cpu_irq}:"IRQ":STACK'.format(**config))
      45. args.append('AREA:idle{color_cpu_idle}:"Idle\c":STACK'.format(**config))
      46. args.append('LINE:tavg{color_cpu_system}:"Temperature"'.format(**config))
      47. args.append('GPRINT:tmin:MIN:"Min\: %5.1lf%sC"')
      48. args.append('GPRINT:tavg:AVERAGE:"Avg\: %5.1lf%sC"')
      49. args.append('GPRINT:tmax:MAX:"Max\: %5.1lf%sC\l"')
      50. args.append('COMMENT:"{last_update}"'.format(**config))
      51. openmediavault.mkrrdgraph.call_rrdtool_graph(args)
      52. return 0
      Display All
      Third, run omv-mkrrdgraph and check the new generated PNG file in /var/lib/openmediavault/rrd/*.png (download it to your pc or else)

      That's a simple example. After that, you can do more, like add a tab to have your disks temp, or have multiple graph/page with modifying the WebGUI of OMV (see attached files).



      Feel free to ask your questions if needed.
      Lian Li PC-V354 with Be Quiet fans | Gigabyte GA-G33M-DS2R | Intel E8400@3,6Ghz | 6GB DDR2 RAM
      1x500MB SSD for System/Backup | 7x2To HDD with ZFS RAIDz2 for Datas/Snapshots
      Powered by OMV v4.1.7 / Kernel 4.16.x / ZFS 0.7.9
    • 1337iceskater wrote:

      Hi,

      I tried the plugin, but it does not seem to work as smoothly as usually expected for OMV.
      Is there any further instruction or troubleshooting needed?
      I need to say, that on my machine lm-sensors is already giving correct results, but without a way to put it into a GUI.

      Thanks for the effort!
      Yeah I noticed that after releasing the build I posted. The graph doesn't update. I will see what I can do about that.