Simon Wilson

Can confirm that both commits work as expected. First commit adds CPU temp and fan to dashboard; second commit exposes full set of data when adding a new system monitor. Thank you @rostovtsev - awesome.

asus-wmi-sensors is an open source driver to access Asus-provided WMI sensor data on certain motherboards. See https://github.com/electrified/asus-wmi-sensors asus-isa-0000 is found by stock sensors-detect, but does not read anything useful or accurate (all it tells me is CPU Fan 0rpm, which is wrong).

Correct, Webmin Dashboard has nevershown the lm-sensors CPU output on this system, and the asus-wmi-sensors have never been available to select in a "System and Server Status" monitor. sensors output is as follows, note that the output is highly customised with a .conf file, including ignoring a lot of irrelevant data - which was why I posted the raw output above. The CPU Fan (fan1) and CPU Temperature (temp1) are clearly marked: [root@emp80 log]# sensors asus-isa-0000 Adapter: ISA adapter asuswmisensors-isa-0000...

Hi Webmin team, This server has the following lm-sensors output (note "raw output" switch so it shows actual input names, and note that there are a heap of hidden non-sensible or zero values): [root@emp80 ~]# sensors -u asus-isa-0000 Adapter: ISA adapter asuswmisensors-isa-0000 Adapter: ISA adapter CPU Core Voltage: in0_input: 1.417 CPU Fan: fan1_input: 2014.000 Chassis Fan (rear): fan2_input: 909.000 Chassis Fan (bottom): fan3_input: 766.000 Chassis Fan (front): fan4_input: 948.000 CPU Temperature:...

OK, with the following config: Show records in zones? - No Can edit module configuration? - Yes txt instead of raw - No, still using RAW Show DNSSEC expired zones on system information page - No The system works OK. No OOM issues, although I obviously have to manually make any edits required. On balance I'm happy with the position - thank you. Sorry for delayed confirmation.

OK, I changed the "Can edit module configuration" back to yes so I could make that change, and then set "Show DNSSEC expired zones on system information page" to No. When I went to the Dashboard an OOM cycle was triggered. That is with this config: - Show records in zones? - No - Can edit module configuration? - Yes - txt instead of raw - NOT DONE, still raw - Show DNSSEC expired zones on system information page - No I'll try again tomorrow and see if it triggers again, then will back out the settings...

Unfortunately I'm still seeing the issue on 1.980 if left at default config. So, after still not working with 1.980 from your recommendations above I have: - Show records in zones? to No (for large zones) - DONE - Can edit module configuration? option to No. - DONE - txt instead of raw - NOT DONE and I can access dashboard without OOM... Out of the box with 1.980 the memory race conditions still occur until OOM processes trigger. Attempt to load Webmin dashboard, it calls a sync of the RPZ zone and...

1.980 now released - before I re-enable can you confirm if fix is included please.