[ZBX-16061] Zabbix reporting incorrect IPMI sensor values on since upgrading from v3.2.7 Created: 2019 Apr 30 Updated: 2020 Jul 03 Resolved: 2020 Jun 16 |
|
Status: | Closed |
Project: | ZABBIX BUGS AND ISSUES |
Component/s: | Server (S) |
Affects Version/s: | 4.2.1 |
Fix Version/s: | None |
Type: | Problem report | Priority: | Trivial |
Reporter: | SimG | Assignee: | Kristians Pavars |
Resolution: | Cannot Reproduce | Votes: | 0 |
Labels: | None | ||
Remaining Estimate: | Not Specified | ||
Time Spent: | Not Specified | ||
Original Estimate: | Not Specified | ||
Environment: |
Zabbix 4.2.1 installed on fully patched CentOS 7 |
Attachments: | DIMM 1 Example.JPG DIMM1 Latest Data.JPG zabbix_server.zip |
Description |
We have an issue since upgrading from Zabbix 3.2.7 to 4.2.1. Here is an example a DIMM sensor. [root@DWSMON1 ~]# ipmitool -H X.X.XX.XX -U XXXX -P XXXX sensor get "DIMM 1" This is Sensor Type 0Ch and Offset 06h. Here's an example of CPU sensor. [root@DWSMON1 ~]# ipmitool -H X.X.XX.XX -U XXXX -P XXXX sensor get "CPU 1"
This is Sensor Type 07h and Offset 07h.
I have attached:
|
Comments |
Comment by SimG [ 2019 Sep 23 ] |
Hi Any further news or information on this yet?
Thanks |
Comment by Kristians Pavars [ 2020 Jun 15 ] |
Hi SimG,
Sorry for the long delay on this issue. Can you please attach your item configuration with any preprocessing steps?
Thanks, |
Comment by Kristians Pavars [ 2020 Jun 16 ] |
Hi SimG,
Please consider upgrading to latest versions 4.4.x or 5.x, as 4.2 is non-LTS version and thus is no longer supported. I will be closing this issue.
Regards, |