Ad Widget

Collapse

Zabbix Proxy 5.2 on Docker (Ubuntu) - cannot connect to IPMI (Unknown error 16777411)

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • sparkyjf
    Junior Member
    • Jul 2020
    • 6

    #1

    Zabbix Proxy 5.2 on Docker (Ubuntu) - cannot connect to IPMI (Unknown error 16777411)

    Hi all

    I am really struggling to get IPMI monitoring working via Zabbix Proxy (firewall restrictions mean I can't connect the IPMI machine directly to the Zabbix server). I am using the official Docker image - zabbix/zabbix-proxy-sqlite3:ubuntu-5.2-latest (I've also tried the alpine based image).

    The motherboard in question is an Asrock Rack board - I've set up IPMI access and checked it with ipmitool which works just fine using the lanplus protocol. I have set IPMI Pollers to 1 in the Docker container, and have set the Debug Level to 4. I can confirm that there is an attempt to communicate with the IPMI interface, but whenever it tried, it ends up with:

    Code:
    zabbix-proxy_1 | 180:20210410:223242.879 In zbx_connection_change_cb() host:'[192.168.xx.xx]:623' phost:0x55aa6a750890 domain:0x55aa6a72a2c0 err:16777411 conn_num:0 port_num:0 still_connected:0 cb_data:0x55aa6a750890
    zabbix-proxy_1 | 180:20210410:223242.879 zbx_connection_change_cb() fail: [16777411] Unknown error 16777411
    zabbix-proxy_1 | 180:20210410:223242.879 End of zbx_connection_change_cb():NETWORK_ERROR
    zabbix-proxy_1 | 180:20210410:223242.879 In zbx_domain_closed_cb() phost:0x55aa6a750890 host:'[192.168.xx.xx]:623'
    The username and password configured in the Zabbix UI work fine in ipmitool I have tried most Authentication Algorithms including Default, None, MD5 and RCMP+ (I can see mention of RCMP+ and MD5 configured in ipmitool output but can provide further feedback and information if anyone can provide me with more specific commands).

    I've search the forums as far as I can, and there seem to be many much older posts which describe issues with certain versions of OpenIPMI (and it not being compiled with SSL support) - is this still and issue with the 5.2 release?

    Happy to provide more information and debugging as required - I'm a bit lost at the moment and don't know where to look next to resolve this.

    Thanks in advance for any and all help,

    James
Working...