Uploaded image for project: 'ZABBIX BUGS AND ISSUES'
  1. ZABBIX BUGS AND ISSUES
  2. ZBX-15967

Zabbix agent unable to read SMBIOS 3.0

XMLWordPrintable

    • Icon: Problem report Problem report
    • Resolution: Fixed
    • Icon: Major Major
    • 4.2.0
    • Agent (G)
    • System Information
      Manufacturer: HPE
      Product Name: ProLiant DL380 Gen10
      Version: Not Specified
      Serial Number: ...
      UUID: ...
      Wake-up Type: Power Switch
      SKU Number: 868704-B21
      Family: ProLiant
    • Sprint 51 (Apr 2019), Sprint 52 (May 2019)
    • 0.25

      We are running the Zabbix agent 4.2 with root on Ubuntu 16.04. Only on our newer ProLiant Gen10 servers the agent is unable to retrieve any information from system.hw.chassis[].

      # zabbix_agentd -t system.hw.chassis[serial]
      system.hw.chassis[serial] [m|ZBX_NOTSUPPORTED] [Cannot obtain hardware information.]
      

      Strace gives:

      ...
      fstat(1, {st_mode=S_IFCHR|0600, st_rdev=makedev(136, 14), ...}) = 0
      open("/sys/firmware/dmi/tables/DMI", O_RDONLY) = 4
      fstat(4, {st_mode=S_IFREG|0400, st_size=12327, ...}) = 0
      read(4, "\302\5\0\0\21\0\0\307(\1\0+\0\0\200\26 \10\2Q\6\5\0004\0\0\200\26 \2\22R"..., 12327) = 4096
      close(4) = 0
      write(1, "system.hw.chassis[serial] "..., 105system.hw.chassis[serial] [m|ZBX_NOTSUPPORTED] [Cannot obtain hardware information.]
      ) = 105
      close(3) = 0
      exit_group(0) = ?
      +++ exited with 0 +++
      

      I compared the /sys/firmware/dmi/tables/smbios_entry_point to other hardware we use and it seems to be, that the Gen10 have a SM3 header for SMBIOS 3.0. I think Zabbix agent tries to read the tables as SMBIOS, not supporting SMBIOS 3.0 or not reading the entry point. Fallback to /dev/mem does not happen as it looks like. Dmidecode works fine.

            viktors.tjarve Viktors Tjarve
            cubic Waldemar Faist
            Team A
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: