spl147

what are your fan settings set to? post the impifan log (link is at the bottom of the fan control page)

you have not configured the fans at all! here is mine:

it's quite simple really: Min PWM Value = the slowest you want to spin the fans when at or below LOW Temp Threshold ( play with this to find your prefered cooling/noise ratio) LOW Temp Threshold = temp in witch the fans will spin down to Min PWM Value (temps the nVME drives idle at) HIGH Temp Threshold = temp in witch the fans will spin up to 100% (max operating temp) Refresh Interval = time in mins. to check drive temps (1 Min.) fan speed changes are auto calculated based on min PWM value and LOW and HIGH thresholds just a FYI nVME drives have much different max temp the HDD's, google you nvme to see

i just installed the OpenVPN-AIO-Client on 6.12.6 and got this in the log: and the container does not start kill: usage: kill [-s sigspec | -n signum | -sigspec] pid | jobspec ... or kill -l [sigspec] [15:53:23.766594] STUBBY: Stubby version: Stubby 0.3.0 [15:53:23.769075] STUBBY: Read config from file /config/stubby/stubby.yml /nftables.rules:11:38-42: Error: syntax error, unexpected sport add rule ip filter INPUT tcp4-client sport counter accept ^^^^^ /nftables.rules:18:39-43: Error: syntax error, unexpected dport add rule ip filter OUTPUT tcp4-client dport counter accept ^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT tcp sport 853 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT tcp dport 853 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT tcp sport 53 counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT tcp dport 53 counter accept ^^^^^^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter INPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter OUTPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter INPUT handle ^ Error: No such file or directory list table filter ^^^^^^ Error: syntax error, unexpected newline, expecting number delete rule filter OUTPUT handle ^ Error: Could not process rule: No such file or directory add rule ip filter INPUT ip saddr 127.2.2.2 tcp sport 53 ct state established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT ip daddr 127.2.2.2 tcp dport 53 ct state new,established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter INPUT ip saddr 127.2.2.2 udp sport 53 ct state established counter accept ^^^^^^ Error: Could not process rule: No such file or directory add rule ip filter OUTPUT ip daddr 127.2.2.2 udp dport 53 ct state new,established counter accept ^^^^^^ [info] Creation complete [info] stubby fixed. [info] danted fixed. [info] tinyproxy fixed. [info] torsocks fixed. [info] privoxy fixed. [info] Initialisation complete [info] Run stubby in background on port 53 [warn] Your ISP public IP is 99.35.193.151 [info] Setting up nftables rules... [info] Flusing ruleset [info] Added route 10.172.69.0/24 via 172.17.0.1 dev eth0 [info] Apply rules [info] Quick block test. Expected result is time out. Actual result is 99.35.193.151 [info] All rules created [info] Setting up OpenVPN tunnel... [info] Create tunnel device [info] Allow DnS for openvpn to lookup VPN server [info] Connecting to VPN on port with proto tcp4-client... [info] Your VPN public IP is 99.35.193.151 [info] Block DnS to force traffic through tunnel [info] Change DNS servers to 127.2.2.2 [info] Adding 127.2.2.2 to /etc/resolv.conf [info] Allowing DNS lookups (tcp, udp port 53) to server '127.2.2.2' [info] Tunnel created [info] Enabling healthcheck... [info] Healthcheck enabled [info] Runing apps... ** Press ANY KEY to close this window **

Im pretty sure all, but i can not test. Maybe just have a button to load/unload

Your cpu fan should be controlled by bios! The other 2 should be set to hdd

nVME drives run hot the temp threshold is alot higher then a hdd. Including it will make your fan spin faster/louder. I use a heatsink on my nVME cache and it works well. If your nVME is not in your fans path then adding it will not result in what you think

@SimonF can this be incorporated into the plugin?

Read people read, i just explained this up a bit, this is a local connection NOT lan! You do not need to use ip, your local on the device, ip control is for a remote machine. You need to modprobe ipmi-si ipmi-devintf

Thats the system temp plugin,

@SimonF have you had a chance to look into adding the ability to use seperate high and low values for CPU fan curve?

Yea mine says asrock as well, i have a T430

You do not need to use ip, your local on the device, ip control is for a remote machine. You need to modprobe ipmi-si ipmi-devintf

nope

beta key has expired, time to buy a license!

thats not very detailed nor is it dell specific

Seperate panel

i was thinking of adding a Dell Server section to the dashboard to show info, firmware versions, service tag, etc. have it only show if it's a dell server. any chance you could whip up a template? maybe an example or 2? For Service Tag dmidecode -t 1 | grep 'Serial Number' | awk -F 'r:' '{print $2}' | awk '{print $1}' MainBoard Firmware dmidecode -t 0 | grep 'Version' | awk -F ':' '{print $2}' | awk '{print $1}' Firmware Release Date dmidecode -t 0 | grep 'Release Date' | awk -F ':' '{print $2}' | awk '{print $1}' Serial Number dmidecode -t 2 | grep 'Serial Number' | awk -F '.' '{print $3}'

No Problem, thanks for the quick release

i have submitted a pull request with the fix: ipmi_check.php <? /* board info */ $boards = ['ASRock'=>'','ASRockRack'=>'', 'Dell' =>'','Supermicro'=>'']; $board = ( $override == 'disable') ? trim(shell_exec("dmidecode -t 2 | grep 'Manufacturer' | awk -F 'r:' '{print $2}' | awk '{print $1}'")) : $oboard; $board_model = ( $override == 'disable') ? rtrim(ltrim(shell_exec("dmidecode -qt2|awk -F: '/^\tProduct Name:/ {print $2}'"))) : $omodel; $board_status = array_key_exists($board, $boards); $sm_gen=""; if ($board == "Supermicro") { $smboard_model = ( $override == 'disable') ? intval(shell_exec("dmidecode -qt2|awk -F: '/^\tProduct Name:/{p=\$2} END{print substr(p,3,1)}'")) : $omodel; if ($smboard_model == '1') $smboard_model = ( $override == 'disable') ? intval(shell_exec("dmidecode -qt2|awk -F: '/^\tProduct Name:/{p=\$2} END{print substr(p,3,2)}'")) : $omodel; $sm_gen="Gen:$smboard_model"; } if ($board == "Dell") { $board_model = ( $override == 'disable') ? rtrim(ltrim(shell_exec("dmidecode -qt1|awk -F: '/^\tProduct Name:/ {print $2}'"))) : $omodel; } ?>

Motherboard and Model on my dell server is displaying: Dell 0KX11M and not Dell PowerEdge T430 0KX11M is actually the Mainboard Part Number root@Server:~# dmidecode # dmidecode 3.4 Getting SMBIOS data from sysfs. SMBIOS 2.8 present. 67 structures occupying 2870 bytes. Table at 0x7AF09000. Handle 0xDA00, DMI type 218, 11 bytes OEM-specific Type Header and Data: DA 0B 00 DA B2 00 17 20 0E 10 03 Handle 0x0000, DMI type 0, 24 bytes BIOS Information Vendor: Dell Inc. Version: 2.18.2 Release Date: 10/18/2023 Address: 0xF0000 Runtime Size: 64 kB ROM Size: 16 MB Characteristics: ISA is supported PCI is supported PNP is supported BIOS is upgradeable BIOS shadowing is allowed Boot from CD is supported Selectable boot is supported EDD is supported Japanese floppy for Toshiba 1.2 MB is supported (int 13h) 5.25"/360 kB floppy services are supported (int 13h) 5.25"/1.2 MB floppy services are supported (int 13h) 3.5"/720 kB floppy services are supported (int 13h) 8042 keyboard services are supported (int 9h) Serial services are supported (int 14h) CGA/mono video services are supported (int 10h) ACPI is supported USB legacy is supported BIOS boot specification is supported Function key-initiated network boot is supported Targeted content distribution is supported UEFI is supported BIOS Revision: 2.18 Handle 0x0100, DMI type 1, 27 bytes System Information Manufacturer: Dell Inc. Product Name: PowerEdge T430 Version: Not Specified Serial Number: CXPLHL2 UUID: 4c4c4544-0058-5010-804c-c3c04f484c32 Wake-up Type: Power Switch SKU Number: SKU=NotProvided;ModelName=PowerEdge T430 Family: Not Specified Handle 0x0200, DMI type 2, 8 bytes Base Board Information Manufacturer: Dell Inc. Product Name: 0KX11M Version: A05 Serial Number: .CXPLHL2.CNFCP0078L0077. changing 'dmidecode -qt2' to 'dmidecode -qt1' returns the proper Product name dmidecode -qt2|awk -F: '/^\tProduct Name:/ {print $2}' 0KX11M dmidecode -qt1|awk -F: '/^\tProduct Name:/ {print $2}' PowerEdge T430

this is in my php logs: [06-Dec-2023 18:40:22 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:22 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:23 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:23 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:27 America/Chicago] PHP Deprecated: preg_match(): Passing null to parameter #2 ($subject) of type string is deprecated in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 80 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $conn in /usr/local/emhttp/plugins/dynamix/include/DefaultPageLayout.php(709) : eval()'d code on line 48 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $options in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 223 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $options in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 223 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $options in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 517 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $options in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 517 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:27 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:47 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:47 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:55 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:55 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:57 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:40:57 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:17 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:17 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:38 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:38 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:58 America/Chicago] PHP Warning: Undefined variable $display in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8 [06-Dec-2023 18:41:58 America/Chicago] PHP Warning: Trying to access array offset on value of type null in /usr/local/emhttp/plugins/ipmi/include/ipmi_helpers.php on line 8

looks great, would it be possible to seperate the hdd hi/low temp/speed and the CPU hi/low temp/speed? as cpu runs hotter then hdds, so the settings for the hdds don't work well for cpu. IE fans are alway spinning more when hdds spin down vs when hdds are spun up

Very Nice! looking forward to the update

when the array is spundown i get this in the log: 2023-12-04 18:21:37 Fan:Temp, FAN123456(13%):HDD Temp(32F) in turn it used to say 0C, i think it would be better to state (NA) or (spundown) or (sleep) or something