Hi, I don’t have an alert rule currently, even though the PSU status doesn’t appear anywhere obvious in LibreNMS I can see that the output of ipmitool is determined the same the same for both good and bad PSUs based on other servers because includes/polling/ipmi.inc.php takes only the first four comma separated fields and discards everything else:
Good Server:
PS1 Status,C8h,ok,10.1,Presence detected
PS2 Status,C9h,ok,10.2,Presence detected
Bad Server:
PS1 Status,C8h,ok,10.1,Presence detected, Failure detected
PS2 Status,C9h,ok,10.2,Presence detected
ipmi.inc.php:
foreach (explode("\n", $results) as $row) {
list($desc, $value, $type, $status) = explode(',', $row);
So the resulting SQL statement attempts to set sensors.sensor_current to ‘c8h’ or ‘c9h’ where sensor_current appears to be a numeric column so always ends up as zero with a warning returned from mysql.
After some googling I found the following ipmitool ticket: https://sourceforge.net/p/ipmitool/bugs/386/ where there’s a discussion around the “ok” status of the PSU output, where it seems the “ok” status relates to the status of the sensor reading and not its value.
It seems that in order to parse the output of the PSx sensors the output needs to be interpreted differently, however I don’t know if this is something specific to Supermicro or lanplus?