Steps to reproduce:

1. Upgrade from zabbix-proxy-mysql-6.0.37-release1.el8.x86_64.rpm to zabbix-proxy-mysql-6.0.38-release1.el8.x86_64.rpm
2. Enable at least one IPMI poller in zabbix_proxy.conf - e.g. set StartIPMIPollers=3
3. Start zabbix proxy: systemctl start zabbix-proxy

Result:

[root@MYZABBIXPROXY ~]# systemctl start zabbix-proxy
Job for zabbix-proxy.service failed because the control process exited with error code.
See "systemctl status zabbix-proxy.service" and "journalctl -xe" for details.

journalctl -xe:

Jan 30 12:17:21 MYZABBIXPROXY.domain.local systemd[1]: Starting Zabbix Proxy...
– Subject: Unit zabbix-proxy.service has begun start-up
– Defined-By: systemd
– Support: https://support.oracle.com
–
-- Unit zabbix-proxy.service has begun starting up.
Jan 30 12:17:21 MYZABBIXPROXY.domain.local zabbix_proxy[129531]: zabbix_proxy [129531]: "StartIPMIPollers" configuration parameter cannot be used: Zabbix proxy was compiled without IPMI support
Jan 30 12:17:21 MYZABBIXPROXY.domain.local systemd[1]: zabbix-proxy.service: Control process exited, code=exited status=1
Jan 30 12:17:21 MYZABBIXPROXY.domain.local systemd[1]: zabbix-proxy.service: Failed with result 'exit-code'.
– Subject: Unit failed
– Defined-By: systemd
– Support: https://support.oracle.com
–

Expected:

Zabbix proxy starts.