[ZBX-8992] IPMI problem with zabbix 2.4.1 Created: 2014 Nov 04  Updated: 2017 May 30  Resolved: 2014 Dec 05

Status: Closed
Project: ZABBIX BUGS AND ISSUES
Component/s: Proxy (P), Server (S)
Affects Version/s: 2.4.1
Fix Version/s: 2.2.8rc1, 2.4.3rc1, 2.5.0

Type: Incident report Priority: Major
Reporter: ufocek Assignee: Unassigned
Resolution: Fixed Votes: 0
Labels: ipmi, sensors
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

uname -a
Linux zabbix2 3.12.4-031204-generic #201312081207 SMP Sun Dec 8 17:08:59 UTC 2013 x86_64 GNU/Linux
cat /etc/debian_version
7.7
dpkg -l |grep ipmi
ii ipmitool 1.8.11-5 amd64 utility for IPMI control with kernel driver or LAN interface
openipmi-2.0.21 from source..

Attachments: File ipmi2.log     File preferring-threshold.patch     HTML File zabbix2013_ipmi_values     HTML File zabbix2013_ipmi_values     PNG File zabbix2013_ipmi_values.png     HTML File zabbix241_ipmi_values     PNG File zabbix241_ipmi_values.png     Text File zabbix_log_ipmi_fan2.txt    

 Description   

Hi,

I have problem with zabbix-2.4.1 and ipmi, because I received wrong information about sensor:

$ ipmitool -I lanplus -H 192.168.249.34 -L USER -A MD5 -U  -P  sdr, show
Ambient          | 21 degrees C      | ok
Systemboard      | 29 degrees C      | ok
CPU1             | 48 degrees C      | ok
CPU2             | 44 degrees C      | ok

This is a data from ipmitool command line, and show good value for FAN2 SYS:

$ ipmitool -I lanplus -H 192.168.249.34 -L USER -A MD5 -U -P sensor get "FAN2 SYS"
Sensor ID              : FAN2 SYS (0x27)
 Entity ID             : 29.1
 Sensor Type (Analog)  : Fan
 Sensor Reading        : 6240 (+/- 60) RPM
 Status                : ok
 Lower Non-Recoverable : na
 Lower Critical        : 1920.000
 Lower Non-Critical    : na
 Upper Non-Critical    : na
 Upper Critical        : na
 Upper Non-Recoverable : na
 Assertion Events      : 
 Assertions Enabled    :

In zabbix gui i check data, and fan2 sys have value: 1 RPM... or is not supported...

For test I try configure fan2 sys and configure in zabbix like this:

Now I add for test in zabbix key:

Name: FAN2 SYS
Type: ipmi agent
Key: ipmi.fan2.sys.rpm
Host interface: ip:623
IPMI sensor: FAN2 SYS (I put space between FAN1 and SYS)
Type of information: Numeric
Units: RPM

Zabbix show me information about item: not_supported, sensor data is not available or show value: 1 RPM
What I set wrong in zabbix, that isn't work? This is a problem zabbix or ipmi?

 Comments   
Comment by Aleksandrs Saveljevs [ 2014 Nov 04 ]

This might be similar to ZBX-8395, where ipmitool sees an analog sensor, but Zabbix sees a discrete sensor. What kind of hardware are you monitoring?

Could you please also post the output of "grep FAN2 ..." of DebugLevel=4 log? Note that since Zabbix 2.4.0 log level can be increased at runtime and only for a specific type of processes: see http://blog.zabbix.com/zabbix-2-4-features-part-6-runtime-loglevel-changing/ .

Comment by ufocek [ 2014 Nov 04 ]

Aleksandrs - I try monitor servers RX200S6/7 from Fujitsu Technology Solutions.. Ok, I increase a log and check this when I have access to this machine..

Comment by ufocek [ 2014 Nov 05 ]

Log file for FAN2

Comment by Aleksandrs Saveljevs [ 2014 Nov 05 ]

The attached log shows a case where that item becomes not supported. However, you mentioned in the issue description that sometimes it has a value of 1. Could you please show a longer part of the log where the latter case is observable, too?

Comment by ufocek [ 2014 Nov 06 ]

Hi Aleksandrs,

In attachment I put log file from ipmi debug, maybe this log help yoy and I put screen from zabbix what I see when I turn on ipmi, what values I get from ipmi for: FANs, CPUs,Power....
I have a weird data.. because from command line e.g Total Power show me 178W, but in zabbix gui only 1W...

Comment by Aleksandrs Saveljevs [ 2014 Nov 06 ]

Attached "zabbix241_ipmi_values.png" with the correct extension:

Comment by Aleksandrs Saveljevs [ 2014 Nov 06 ]

Attached log contains lines like the following, which shows that Zabbix indeed sees this sensor as a discrete sensor:

 15987:20141106:073522.823 In read_ipmi_sensor() sensor:'FAN2 SYS@[192.168.249.34]:623'
 15987:20141106:073522.825 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 0 value is 1]
 15987:20141106:073522.825 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 1 value is 0]
 15987:20141106:073522.825 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 2 value is 0]
 15987:20141106:073522.826 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 3 value is 0]
 15987:20141106:073522.826 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 4 value is 0]
 15987:20141106:073522.826 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 5 value is 0]
 15987:20141106:073522.826 State [FAN2 SYS | fan_cooling | invalid | sensor specific | state 7 value is 0]

So this issue is the same as ZBX-8395. Not sure whether there is anything that can be done about it.

Comment by ufocek [ 2014 Nov 06 ]

I wonder what happened to that previously worked....

Comment by Aleksandrs Saveljevs [ 2014 Nov 06 ]

Do you mean that it used to work in a previous version of Zabbix? If so, which version that is?

Comment by ufocek [ 2014 Nov 06 ]

If I good memory it's work with zabbix 2.0.x version.

Comment by ufocek [ 2014 Nov 06 ]

Good data values from ipmi source with zabbix 2.0.13, the same configuration on zabbix-2.4.2 return bad values.

Comment by ufocek [ 2014 Nov 06 ]

Aleksandrs - I installed for test zabbix 2.0.13 and add the same source ipmi. Zabbix 2.0.13 show me a good values, in attachment I put screen with zabbix data.
So for me something change in zabbix-2.2 or 2.4.x version... It's possible to solve this problem?

Comment by Aleksandrs Saveljevs [ 2014 Nov 06 ]

Reattaching "zabbix2013_ipmi_values.png" with a proper extension:

Comment by Aleksandrs Saveljevs [ 2014 Nov 06 ]

ufocek, thank you, the fact that it used to work before is valuable information. We shall investigate.

Comment by ufocek [ 2014 Nov 06 ]

Ok. It's possible to get a patch before you public a new version, I can test in my environment..?

Comment by Aleksandrs Saveljevs [ 2014 Nov 07 ]

Yes, when the development is complete (we will let you know here), we would appreciate if you would test the new version. Zabbix IPMI works well with the hardware we have locally.

Comment by Aleksandrs Saveljevs [ 2014 Dec 02 ]

In one of the attached logs we can see the following lines:

$ grep FAN2.SYS ipmi2.log
 ...
 15983:20141106:080104.052 In allocate_ipmi_sensor() sensor:'FAN2 SYS@[192.168.249.34]:623'
 15983:20141106:080104.052 Added sensor: host:'192.168.249.34:623' id_type:0 id_sz:9 id:'FAN2 SYS' reading_type:0x6f ('sensor specific') type:0xe6 ('invalid') full_name:'(29.1).FAN2 SYS'
 15983:20141106:080104.071 In allocate_ipmi_sensor() sensor:'FAN2 SYS@[192.168.249.34]:623'
 15983:20141106:080104.071 Added sensor: host:'192.168.249.34:623' id_type:0 id_sz:9 id:'FAN2 SYS' reading_type:0x1 ('threshold') type:0x4 ('fan') full_name:'(29.1).FAN2 SYS'
 ...

Here, the same sensor is seen by Zabbix as both a threshold sensor and a discrete sensor. This is dubious, but we can work around this by preferring the threshold sensor, if both are available.

This solution has been implemented in development branch svn://svn.zabbix.com/branches/dev/ZBX-8992 for 2.2.

Comment by Aleksandrs Saveljevs [ 2014 Dec 02 ]

ufocek, please try attached "preferring-threshold.patch" and let us know your results. It was created for Zabbix 2.4.1.

Comment by ufocek [ 2014 Dec 02 ]

Aleksandrs, I download your patch and apply for zabbix 2.4.2, becuase I have that version. Then I add my templates for ipmi and now everything looks correct, I have a good values from ipmi for all my sensor.

Comment by Alexander Vladishev [ 2014 Dec 04 ]

(1) Made some code simplification in r51001. Please review.

asaveljevs Looks good. CLOSED.

Comment by Aleksandrs Saveljevs [ 2014 Dec 04 ]

Fixed in pre-2.2.8 r51007, pre-2.4.3 r51008, and pre-2.5.0 (trunk) r51009.

Comment by Aleksandrs Saveljevs [ 2014 Dec 05 ]

(2) Documented at the following locations:

sasha it should be mentioned in:

REOPENED

asaveljevs Added notes at the bottom. RESOLVED.

sasha Thanks a lot! CLOSED

Generated at Mon Jul 07 08:23:13 EEST 2025 using Jira 9.12.4#9120004-sha1:625303b708afdb767e17cb2838290c41888e9ff0.