Open ohadlevy opened 8 years ago
Ill take a look at the parser. I have heard others complain but your the first to provide output.
lucky me ;) thanks @logicminds
What version of freeipmi are you using?
So I am assuming the output you posted is from the result of the same command rubyipmi used. If it is this looks to be a vendor issue with sensor data. If you look at my fixtures, which is what I based the parser on the output is different and provides much more detail: https://github.com/logicminds/rubyipmi/blob/master/spec/fixtures/freeipmi/sensors.txt
Can you run the sensor command again without the flag (--no-header-output) so I can see what your system is returning and which headers are for which sensor?
I created a new branch: https://github.com/logicminds/rubyipmi/tree/gh-37 and added some unit tests that parse the output you provided. The parser seems to work as is, but I am wondering if the output you provided is different than the output given by freeipmi somehow.
You can test this out on your system by checking out gh-37
branch and running bundle exec rspec spec/unit/freeipmi/sensors_spec.rb
when using:
/usr/sbin/ipmi-sensors --hostname=fox02 --driver-type=LAN_2_0 --no-header-output --output-sensor-state --entity-sensor-names --config-file=/tmp/20151102-15221-ce12l
the following is observed:
this is using dell PowerEdge C6220