[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.

    • David B wrote:

      What's the problem? I know I haven't been much help so far, but perhaps I can try to solve it?
      There are a few issues still to resolve but the main one is the tabs, they do not update. Well, they do but you have to clear the browsers cache for them to show, this make me wonder if the plugin is feasible any more.
      We could use main tabs instead of sub-tabs but this would make the page a little cluttered.

      BTW your help is much appreciated, 2 heads are better than 1 :)
      [IMG:http://widgets.trakt.tv/users/1f5d0f5ed67f98ed9d06d9849b42dd0e/watched/banner@1x.jpg]
      What I am watching/watched on my Popcorn Hour media player
      omv 2.1.1 stoneburner | 64 bit | omvextrasorg 1.29
      MySQL (Percona) | Newznab | Sonarr | CP | HP | NZBget | YAMJ | CUPS
    • jhmiller wrote:


      There are a few issues still to resolve but the main one is the tabs, they do not update. Well, they do but you have to clear the browsers cache for them to show, this make me wonder if the plugin is feasible any more.We could use main tabs instead of sub-tabs but this would make the page a little cluttered.

      BTW your help is much appreciated, 2 heads are better than 1 :)
      Thanks! I'm glad to hear that I'm contributing in some way.

      I will have a look at the caching thing if time permits. I've dealt with this before when designing websites. Let's see if I can figure out how to deal with it in the context of the plugin.
    • What I do not understand about the caching problem is that whenever the graph updates, the URL for the graph image changes, meaning that even if the image is cached, you should not be loading the same image.

      For example, here are two different URLs for the same image.
      localhost/rrd.php?name=sensors-hour.png&time=1526497062980
      localhost/rrd.php?name=sensors-hour.png&time=1526497195462

      I am currently testing in a VM which does not work very well with this plugin since no sensors are detected. Does this version of the plugin at least work for monitoring CPU and motherboard temperatures? As long as it keeps an accurate documentation of this information, I can live with the defects while continuing to test on my production server.

      Update: I just tried installing a build of this plugin on my production server running OMV 4, and although the plugin installs fine, trying to change the settings results in this error:

      Source Code

      1. Error #0:
      2. OMV\ExecException: 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$
      3. # System: ASUSTeK COMPUTER INC. VM62N
      4. # Kernel: 4.9.0-0.bpo.6-amd64 x86_64
      5. # Processor: Intel(R) Core(TM) i3-4030U CPU @ 1.90GHz (6/69/1)
      6. Running in automatic mode, default answers to all questions
      7. are assumed.
      8. Some south bridges, CPUs or memory controllers contain embedded sensors.
      9. Do you want to scan for them? This is totally safe. (YES/no):
      10. Module cpuid loaded successfully.
      11. Silicon Integrated Systems SIS5595... No
      12. VIA VT82C686 Integrated Sensors... No
      13. VIA VT8231 Integrated Sensors... No
      14. AMD K8 thermal sensors... No
      15. AMD Family 10h thermal sensors... No
      16. AMD Family 11h thermal sensors... No
      17. AMD Family 12h and 14h thermal sensors... No
      18. AMD Family 15h thermal sensors... No
      19. AMD Family 16h thermal sensors... No
      20. AMD Family 15h power sensors... No
      21. AMD Family 16h power sensors... No
      22. Intel digital thermal sensor... Success!
      23. (driver `coretemp')
      24. Intel AMB FB-DIMM thermal sensor... No
      25. Intel 5500/5520/X58 thermal sensor... No
      26. VIA C7 thermal sensor... No
      27. VIA Nano thermal sensor... No
      28. Some Super I/O chips contain embedded sensors. We have to write to
      29. standard I/O ports to probe them. This is usually safe.
      30. Do you want to scan for Super I/O sensors? (YES/no):
      31. Probing for Super-I/O at 0x2e/0x2f
      32. Trying family `National Semiconductor/ITE'... No
      33. Trying family `SMSC'... No
      34. Trying family `VIA/Winbond/Nuvoton/Fintek'... Yes
      35. Found `Nuvoton NCT6791D Super IO Sensors' Success!
      36. (address 0x290, driver `nct6775')
      37. Probing for Super-I/O at 0x4e/0x4f
      38. Trying family `National Semiconductor/ITE'... No
      39. Trying family `SMSC'... No
      40. Trying family `VIA/Winbond/Nuvoton/Fintek'... No
      41. Trying family `ITE'... No
      42. Some systems (mainly servers) implement IPMI, a set of common interfaces
      43. through which system health data may be retrieved, amongst other things.
      44. We first try to get the information from SMBIOS. If we don't find it
      45. there, we have to read from arbitrary I/O ports to probe for such
      46. interfaces. This is normally safe. Do you want to scan for IPMI
      47. interfaces? (YES/no):
      48. Probing for `IPMI BMC KCS' at 0xca0... No
      49. Probing for `IPMI BMC SMIC' at 0xca8... No
      50. Some hardware monitoring chips are accessible through the ISA I/O ports.
      51. We have to write to arbitrary I/O ports to probe them. This is usually
      52. safe though. Yes, you do have ISA I/O ports even if you do not have any
      53. ISA slots! Do you want to scan the ISA I/O ports? (yes/NO):
      54. Lastly, we can probe the I2C/SMBus adapters for connected hardware
      55. monitoring devices. This is the most risky part, and while it works
      56. reasonably well on most systems, it has been reported to cause trouble
      57. on some systems.
      58. Do you want to probe the I2C/SMBus adapters now? (YES/no):
      59. Found unknown SMBus adapter 8086:9c22 at 0000:00:1f.3.
      60. Sorry, no supported PCI bus adapters found.
      61. Module i2c-dev loaded successfully.
      62. Next adapter: SMBus I801 adapter at f040 (i2c-0)
      63. Do you want to scan it? (YES/no/selectively):
      64. Client found at address 0x48
      65. Probing for `National Semiconductor LM75'... No
      66. Probing for `National Semiconductor LM75A'... No
      67. Probing for `Dallas Semiconductor DS75'... No
      68. Probing for `National Semiconductor LM77'... No
      69. Probing for `Analog Devices ADT7410/ADT7420'... No
      70. Probing for `Analog Devices ADT7411'... No
      71. Probing for `Maxim MAX6642'... No
      72. Probing for `Texas Instruments TMP435'... No
      73. Probing for `National Semiconductor LM73'... No
      74. Probing for `National Semiconductor LM92'... No
      75. Probing for `National Semiconductor LM76'... No
      76. Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
      77. Probing for `NXP/Philips SA56004'... No
      78. Probing for `SMSC EMC1023'... No
      79. Probing for `SMSC EMC1043'... No
      80. Probing for `SMSC EMC1053'... No
      81. Probing for `SMSC EMC1063'... No
      82. Client found at address 0x4f
      83. Probing for `National Semiconductor LM75'... No
      84. Probing for `National Semiconductor LM75A'... No
      85. Probing for `Dallas Semiconductor DS75'... No
      86. Probing for `Maxim MAX6642'... No
      87. Probing for `Texas Instruments TMP421'... No
      88. Probing for `Texas Instruments TMP422'... No
      89. Probing for `Texas Instruments TMP435'... No
      90. Probing for `Texas Instruments TMP441'... No
      91. Probing for `Maxim MAX6633/MAX6634/MAX6635'... No
      92. Probing for `NXP/Philips SA56004'... No
      93. Client found at address 0x50
      94. Probing for `Analog Devices ADM1033'... No
      95. Probing for `Analog Devices ADM1034'... No
      96. Probing for `SPD EEPROM'... Yes
      97. (confidence 8, not a hardware monitoring chip)
      98. Probing for `EDID EEPROM'... No
      99. Client found at address 0x51
      100. Probing for `Analog Devices ADM1033'... No
      101. Probing for `Analog Devices ADM1034'... No
      102. Probing for `SPD EEPROM'... Yes
      103. (confidence 8, not a hardware monitoring chip)
      104. Next adapter: i915 gmbus ssc (i2c-1)
      105. Do you want to scan it? (yes/NO/selectively):
      106. Next adapter: i915 gmbus vga (i2c-2)
      107. Do you want to scan it? (yes/NO/selectively):
      108. Next adapter: i915 gmbus panel (i2c-3)
      109. Do you want to scan it? (yes/NO/selectively):
      110. Next adapter: i915 gmbus dpc (i2c-4)
      111. Do you want to scan it? (yes/NO/selectively):
      112. Next adapter: i915 gmbus dpb (i2c-5)
      113. Do you want to scan it? (yes/NO/selectively):
      114. Next adapter: i915 gmbus dpd (i2c-6)
      115. Do you want to scan it? (yes/NO/selectively):
      116. Next adapter: nvkm-0000:05:00.0-bus-0003 (i2c-7)
      117. Do you want to scan it? (yes/NO/selectively):
      118. Next adapter: nvkm-0000:05:00.0-bus-0005 (i2c-8)
      119. Do you want to scan it? (yes/NO/selectively):
      120. Next adapter: DPDDC-C (i2c-9)
      121. Do you want to scan it? (yes/NO/selectively):
      122. Now follows a summary of the probes I have just done.
      123. Driver `coretemp':
      124. * Chip `Intel digital thermal sensor' (confidence: 9)
      125. Driver `nct6775':
      126. * ISA bus, address 0x290
      127. Chip `Nuvoton NCT6791D Super IO Sensors' (confidence: 9)
      128. Do you want to generate /etc/sysconfig/lm_sensors? (yes/NO):
      129. To load everything that is needed, add this to one of the system
      130. initialization scripts (e.g. /etc/rc.d/rc.local):
      131. #----cut here----
      132. # Chip drivers
      133. modprobe coretemp
      134. modprobe nct6775
      135. /usr/bin/sensors -s
      136. #----cut here----
      137. You really should try these commands right now to make sure everything
      138. is working properly. Monitoring programs won't work until the needed
      139. modules are loaded.
      140. Unloading i2c-dev... OK
      141. Unloading cpuid... OK
      142. in /usr/share/php/openmediavault/system/process.inc:175
      143. Stack trace:
      144. #0 /usr/share/openmediavault/engined/module/sensors.inc(33): OMV\System\Process->execute()
      145. #1 /usr/share/openmediavault/engined/rpc/config.inc(168): OMVModuleSensors->applyConfig()
      146. #2 [internal function]: OMVRpcServiceConfig->applyChanges(Array, Array)
      147. #3 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      148. #4 /usr/share/php/openmediavault/rpc/serviceabstract.inc(149): OMV\Rpc\ServiceAbstract->callMethod('applyChanges', Array, Array)
      149. #5 /usr/share/php/openmediavault/rpc/serviceabstract.inc(565): OMV\Rpc\ServiceAbstract->OMV\Rpc\{closure}('/tmp/bgstatusb4...', '/tmp/bgoutputVm...')
      150. #6 /usr/share/php/openmediavault/rpc/serviceabstract.inc(159): OMV\Rpc\ServiceAbstract->execBgProc(Object(Closure))
      151. #7 /usr/share/openmediavault/engined/rpc/config.inc(213): OMV\Rpc\ServiceAbstract->callMethodBg('applyChanges', Array, Array)
      152. #8 [internal function]: OMVRpcServiceConfig->applyChangesBg(Array, Array)
      153. #9 /usr/share/php/openmediavault/rpc/serviceabstract.inc(123): call_user_func_array(Array, Array)
      154. #10 /usr/share/php/openmediavault/rpc/rpc.inc(86): OMV\Rpc\ServiceAbstract->callMethod('applyChangesBg', Array, Array)
      155. #11 /usr/sbin/omv-engined(536): OMV\Rpc\Rpc::call('Config', 'applyChangesBg', Array, Array, 1)
      156. #12 {main}
      Display All

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

    • epicfail wrote:

      Any updates on this? I really liked the plugin on OMV 3
      As I expected, I've been too busy to dedicate any further time to this.

      Full disclosure: I am not the main developer of this plugin. I am just a random guy who would also like to see this plugin ported to OMV 4 and put some effort into porting it but did not make much progress. @jhmiller's the lead developer, and last I heard from him, he was having issues with his OMV machine which slowed his progress.