20 minutes ago, xrichnj said:

 

this would absolutely work, but i'm not willing to do it because i'm suspicious that libssl1 has something to do with the recent vulnerabilities patched by LimeTech. 

 

they said if youre on 6.12.4 and before (which only has libssl1), then youre vulnerable.

 

if you are on 7.0.0 (which ONLY has libssl3), then youre safe from the vulnerabilities.

 

maybe someone can check what ssl libraries 6.12.15 has (which is also safe) to shed some light on this. 

 

look, i'm not a security researcher, but the above worries me about installing old and "unofficial" libraries. libssl1 is pretty antiquated at this point, maybe the discovery of these vulnerabilities is what led to it being dropped from 7.0.0. i'm sure Lime had a good reason for removing/replacing it, i dont think they would remove old libraries that would break things "because they felt like it", there needed to be good reason. 

 

having better fan control isnt worth leaving my server potentially vulnerable to xss and csrf

I have compiled a version of ipmitools.

 

Copy onto you system and let me know if it works under 7

 

installpkg filename

 

 

ipmitool-1.8.19-x86_64-1_SBo.tgz

45 minutes ago, SimonF said:

Happy to change what do you want it to say.

here are the changes i proposed:

 

// temperature sensor Spundown
echo '<dl class="fanctrl-settings">',
     '<dt><dl><dd>HDD Spundown Temperature sensor:</dd></dl></dt><dd>',
     '<select', $disabled, ' name="', $temphdd, '" class="fanctrl-temp fanctrl-settings">',
     '<option value="0">None</option>',
     get_temp_options($fancfg[$temphdd]),
     '</select></dd></dl>';

// Check if the Spundown vales should be shown
if ($fancfg[$temphdd] != 0) {
    // high temperature threshold Spundown
    echo '<dl class="fanctrl-settings">',
         '<dt><dl><dd>High temperature threshold Spundown (&deg;', $display_unit, '):</dd></dl></dt>',
         '<dd><select name="', $temphio, '" class="', $tempid, ' fanctrl-settings">',
         get_temp_range('HI', $fancfg[$temphio], $display_unit),
         '</select></dd></dl>';

    // low temperature threshold Spundown
    echo '<dl class="fanctrl-settings">',
         '<dt><dl><dd>Low temperature threshold Spundown (&deg;', $display_unit, '):</dd></dl></dt>',
         '<dd><select name="', $temploo, '" class="', $tempid, ' fanctrl-settings">',
         get_temp_range('LO', $fancfg[$temploo], $display_unit),
         '</select></dd></dl>';

    // fan control maximum speed Spundown
    echo '<dl class="fanctrl-settings">',
         '<dt><dl><dd>Fan speed maximum Spundown (%):</dd></dl></dt><dd>',
         '<select name="', $fanmaxo, '" class="', $tempid, ' fanctrl-settings">',
         get_minmax_options('HI', $fancfg[$fanmaxo]),
         '</select></dd></dl>';

    // fan control minimum speed Spundown
    echo '<dl class="fanctrl-settings">',
         '<dt><dl><dd>Fan speed minimum Spundown (%):</dd></dl></dt><dd>',
         '<select name="', $fanmino, '" class="', $tempid, ' fanctrl-settings">',
         get_minmax_options('LO', $fancfg[$fanmino]),
         '</select></dd></dl>&nbsp;';
}

 

Edited January 24, 20251 yr by spl147

1 hour ago, SimonF said:

What motherboard do you the plugin does not have support for all platforms.

Dell R730XD 

Dell Inc. 0599V5 , Version A03
Dell Inc., Version 2.19.0
BIOS dated: Tue 12 Dec 2023 12:00 AM

1 minute ago, Edival76 said:

Dell R730XD 

Dell Inc. 0599V5 , Version A03
Dell Inc., Version 2.19.0
BIOS dated: Tue 12 Dec 2023 12:00 AM

it works fine on you board!

 

under settings network connection: no

fan control:

change values to suit

1 minute ago, spl147 said:

it works fine on you board!

 

under settings network connection: no

fan control:

change values to suit

As I said, it works fine as long as I load that script, but not if I keep it from loading. I will need to do some additional testing later when no one is home or using the server, I guess.

7 minutes ago, Edival76 said:

As I said, it works fine as long as I load that script, but not if I keep it from loading. I will need to do some additional testing later when no one is home or using the server, I guess.

as we have said. the IPMI plugin talked about here DOES NOT use ipmitools, if you are talking about the old school poweredge quiet script. that is not what we are refering to.

 

remove it and the script you have loading above. install the ipmi plugin from here and it will work! i am running the same board different chassis and it works fine! @xrichnj is running the same exact server as you and his works fine!

 

 

Edited January 24, 20251 yr by spl147

1 hour ago, SimonF said:

I have compiled a version of ipmitools.

 

Copy onto you system and let me know if it works under 7

 

installpkg filename

 

 

ipmitool-1.8.19-x86_64-1_SBo.tgz 632.88 kB · 2 downloads

 

 

8 minutes ago, xrichnj said:

 

 

DOOD, you do not need ipmitools! use the plugin from this thread!

Edited January 24, 20251 yr by spl147

17 minutes ago, xrichnj said:

 

 

Found an issue, Will see if I can apply the patch tomorrow, but work around is the following.

 

curl -o ~/enterprise-numbers https://www.iana.org/assignments/enterprise-numbers.txt

mv ~/enterprise-numbers /usr/share/misc/enterprise-numbers

5 minutes ago, spl147 said:

DOOD, you do not need ipmitools! use the plugin from this thread!

 

this plugin is not where i need it to be yet. i will certainly be keeping an eye on its progress and development, but the script has served me well for years with basically infinite customizability and no issue. i dont know how, but it also keeps the fans quiet through restarts, which is REALLY useful for me, as a lot of the time i have to do server maintenance is when it is not being used is late at night. with the plugin, as soon as i hit restart the fans go to full blast, which on an r730xd are REALLY loud and would wake up every person (and cat) in my house. 

 

 

i (as well as others in this thread and different threads) would like to get the script working again. not looking to threadjack this plugins support thread, but the other threads were closed and its the only place ive found of people discussing ipmi fan control.

1 minute ago, xrichnj said:

 

this plugin is not where i need it to be yet. i will certainly be keeping an eye on its progress and development, but the script has served me well for years with basically infinite customizability and no issue. i dont know how, but it also keeps the fans quiet through restarts, which is REALLY useful for me, as a lot of the time i have to do server maintenance is when it is not being used is late at night. with the plugin, as soon as i hit restart the fans go to full blast, which on an r730xd are REALLY loud and would wake up every person (and cat) in my house. 

 

 

i (as well as others in this thread and different threads) would like to get the script working again. not looking to threadjack this plugins support thread, but the other threads were closed and its the only place ive found of people discussing ipmi fan control.

so just update the script to use freeipmi instead of ipmitools?

3 minutes ago, spl147 said:

so just update the script to use freeipmi instead of ipmitools?

 

lol if only. i wouldn't even know where to begin. 

16 minutes ago, SimonF said:

Found an issue, Will see if I can apply the patch tomorrow, but work around is the following.

 

curl -o ~/enterprise-numbers https://www.iana.org/assignments/enterprise-numbers.txt

mv ~/enterprise-numbers /usr/share/misc/enterprise-numbers

 

thank you, i will check back tomorrow!

6 minutes ago, xrichnj said:

 

thank you, i will check back tomorrow!

is this the script you are using? https://gist.github.com/kaysond/35f63c32a0a11daa9e0a53a9c200c1a4

 

9 minutes ago, spl147 said:

is this the script you are using? https://gist.github.com/kaysond/35f63c32a0a11daa9e0a53a9c200c1a4

 

no this is the script:

https://github.com/White-Raven/PowerEdge-shutup/blob/main/fancontrol.sh

13 minutes ago, xrichnj said:

no this is the script:

https://github.com/White-Raven/PowerEdge-shutup/blob/main/fancontrol.sh

Here is a patched version.

ipmitool-1.8.19-x86_64-1_SBo.tgz

14 minutes ago, xrichnj said:

no this is the script:

https://github.com/White-Raven/PowerEdge-shutup/blob/main/fancontrol.sh

just goto chatgpt and tell it to update the script to use freeipmi instead of ipmitool

 

18 minutes ago, xrichnj said:

no this is the script:

https://github.com/White-Raven/PowerEdge-shutup/blob/main/fancontrol.sh

the main issue with using that script vs using the ipmi plugin is that the script does not monitor HDD's and the ipmi plugin can do both

 

10 hours ago, jademonkee said:

Hi there,

I just upgraded my server (see sig) and have been so happy to find this plugin to control my fans.

My motherboard supports two cooling zones - Fans 1-5 and Fans A-B - for a total of 7 fans.

I have had my server running well with this plugin for a few days, but had my fans connected as follows:

 

FAN_1: CPU (dual fans on a splitter)
FAN_2: top front (inflow)
FAN_3: middle front (inflow)
FAN_4: bottom front (inflow)
FAN_5: rear (outflow)
FAN_A: SAS Card Fan

FAN_B: (none)

 

This is as the motherboard recommended it: FANS 1-5 are for CPU Temp, FANS A-B are for System temp.

 

I had them all set to respond to the CPU temp. Note that the SAS card fan isn't PWM, so just runs at full speed all the time.

 

However, I noticed under heavy IO load that the CPU didn't really rise much, but the HDDs did, so I decided to split the CPU cooler to the FANA & FANB zone (despite what the manual recommends), and the case fans all on the same zone. So now it is set up as:

 

FAN_A: CPU (top)
FAN_B: CPU (bottom)
FAN_1: top front (inflow)
FAN_2: middle front (inflow)
FAN_3: bottom front (inflow)
FAN_4: SAS Card Fan (non PWM)
FAN_5: rear (outflow)

 

I have set the FAN A-B zone to react to CPU temps, and the FANS 1-5 zone to react to HDD temps. You can see my setup in the attached screenshot (please ignore the floating footer - a quirk of the screencap plugin I use).

 

One of my disks is set to never spin down, so I don't need to use the secondary sensor option for HDD temps.

 

However, since moving to the new fan configuration, my case fans now no longer spin down to their lower values (they used to drop to about 140 RPM, sitting mostly at 280 RPM), but now they sit around 500-700 RPM.

Taking a look in the ipmifan log, I see the following entries:

2025-01-24 11:04:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:05:12 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:07:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:08:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:10:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:11:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C)
2025-01-24 11:12:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:15:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(29%):CPU Temp(46 °C)
2025-01-24 11:16:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(44%):CPU Temp(51 °C)
2025-01-24 11:17:13 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(23%):CPU Temp(44 °C)
2025-01-24 11:20:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C)
2025-01-24 11:21:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(26%):CPU Temp(45 °C)
2025-01-24 11:23:14 Fan:Temp, FAN1234(52%):HDD Temp(46 °C), FANA(32%):CPU Temp(47 °C)

 

Looking at the other attached screenshot, you can see that the HDD temp reported by the plugin actually 33C. Though I do have an NVME in my server that is 46. I have unchecked that NVME (and my other NVME and SSDs) from the "Available HDDs" list, so they shouldn't be monitored. Indeed, as the IPMI dashboard shows, they are not.

Yet is seems that the Fan Control is still including the excluded NVME drive(s).

Can you please confirm if this is the case, or if I have some other setting that needs changing?

 

FWIW, all the case fans are the same Noctua model, while the CPU fans are a different Noctua model. As Noctua fans can go to very low RPMs, I therefore had to set "Lower_Critical_Threshold"  (using the config editor) to 0 for all of the fans - otherwise I was getting the pulsing problem where the mobo thinks fans have failed (anoher reason why this plugin has been so valuable for me - thank you).

 

Also FWIW, I've never gotten the network connection to work, but it seems to work fine without it, so I never bothered troubleshooting it to get it to work.

 

FINALLY AND ALSO:

Since either the recent plugin update or the swap to FAN A-B, I now have the options to set:

    High temperature threshold Overide(°C):

    Low temperature threshold Overide(°C):

    Fan speed maximum Overide(%):

    Fan speed minimum Overide(%):

 

Can you explain what these are used for? Is it so that if something goes extremely wrong (ie temps out of control), it will ignore the previously set max fan speed settings to ensure things get cool again? Similarly, if the temp gets unusually cool, it can slow the fans down even further?

 

Thanks for your help, insight, and this great plugin - a real life saver.

I think my post has gotten buried in all the talk of the script.

I think there's a bug in the way that HDD temperature is being monitored.

Am I right in thinking this?

25 minutes ago, jademonkee said:

I think my post has gotten buried in all the talk of the script.

I think there's a bug in the way that HDD temperature is being monitored.

Am I right in thinking this?

The plugin uses highest drive temp. If they spin down you can select a 2nd metric to use like CPU. The override which I will rename is ranges for the 2nd metric when the disks are spun down as may need to be different.

9 hours ago, SimonF said:

The plugin uses highest drive temp. If they spin down you can select a 2nd metric to use like CPU. The override which I will rename is ranges for the 2nd metric when the disks are spun down as may need to be different.

Sorry, maybe I wasn't being clear enough: I detailed it in my original post, but it appears to be using my NVMe drive's temperature (as seen in the log - 47C), when I've set it to ignore the NVMe and SSDs in my system.

Even though it's correctly showing the HDD temperature on the sensors page/dashboard (33C), the logs show it's reacting to the (much higher) NVMe temperature (47C).

Thanks.

 

Re the override: thanks for the clarification.

Edited January 25, 20251 yr by jademonkee

2 hours ago, jademonkee said:

Sorry, maybe I wasn't being clear enough: I detailed it in my original post, but it appears to be using my NVMe drive's temperature (as seen in the log - 47C), when I've set it to ignore the NVMe and SSDs in my system.

Even though it's correctly showing the HDD temperature on the sensors page/dashboard (33C), the logs show it's reacting to the (much higher) NVMe temperature (47C).

Thanks.

 

Re the override: thanks for the clarification.

Ok, after a reboot, it looks like the logs are now showing the correct temperature (ie ignoring the NVMe), so I don't know what was happening.

So all good from me. Thank you!

15 minutes ago, jademonkee said:

Ok, after a reboot, it looks like the logs are now showing the correct temperature (ie ignoring the NVMe), so I don't know what was happening.

So all good from me. Thank you!

It is working ok for me. I have excluded the two pool drives

 

i am using a supermicro x11sca-f. though the manufacturer says Enginetech and some where product name. Is it not compatible with this plug in? i'm trying to control the board that is running opnsense on another box. it successfully connected, but no fan control tab show up. when i use override, and choose supermicro x11, it seems to work. i can hear the fans slowed down. i used it to monitor the cpu temps. is there a away without me using the override options?

thanks!