Closed aieri closed 5 years ago
Can you test commit 8273dbce4c0c85174a7a9c2cae3ee3423584fab8? Please use: --seloptions '--system-event-records'
Wow that was fast! Thanks!
The new commit does work:
$ check_ipmi_sensor --seloptions --assume-system-event-records
IPMI Status: Critical [16 system event log (SEL) entries present] | 'Current Power'=244 'Temp 1'=34.00;;~:42.00 'Temp 2 (CPU 1)'=52.00;;~:81.00 'Temp 3 (CPU 2)'=43.00;;~:81.00 'Temp 4 (MemD1)'=61.00;;~:87.00 'Temp 5 (MemD2)'=56.00;;~:87.00 'Temp 7 (IIOH)'=70.00;;~:105.00 'Temp 8 (PCIR)'=51.00;;~:85.00 'Temp 9 (PCIR)'=49.00;;~:85.00 'Temp 10 (PCIR)'=40.00;;~:70.00 'Temp 11 (PCIR)'=42.00;;~:65.00 'Temp 12 (PCIR)'=50.00;;~:75.00 'Temp 13 (PCIR)'=53.00;;~:87.00 'Temp 14 (PCIR)'=43.00;;~:65.00 'Temp 15 (IOH2)'=0.00;;~:105.00
I have however added a couple of in-line comments to the actual commit, as there are some typos in the documentation.
THX for the feedback! Fixing typos with 268eb36f0c20b060fd04f4c9d1ff1fcd17d3269f Cheers, Georg
I have a server with a bunch of entries in the SEL that don't play nice with ipmi-sel unless I use the
--system-event-records option
. Compare:Those output errors cause errors in the check script:
Option
-O
does work, but only for passing options to ipmi-sensors. I suggest creating independent 'extra-flags' options for both ipmi-sensors and ipmi-sel.