Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record

Hi Al,

I have seen the config file for the sensors with freeipmi v0.6.6, and I've tried modifying them. So far, proper messages were displayed when sensors readings reached threshold values.

But when I tried installing freeipmi-0.6.8.beta1.tar.gz, an error occurred during config (pls see complete attached output).

# ./configure
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for gawk... no
checking for mawk... no
checking for nawk... nawk
checking whether make sets $(MAKE)... yes

...CUT...

checking how to hardcode library paths into programs... immediate
checking whether make sets $(MAKE)... (cached) yes
checking for gcry_md_open in -lgcrypt... no
configure: error: libgcrypt required to build libfreeipmi

I normally do not install TAR.GZs due to some dependency errors like above.
I have been installing the previous versions automatically from mounted ports.

Thanks,

Won

----- Original Message ----
From: Al Chu <address@hidden>
To: Won De Erick <address@hidden>
Cc: address@hidden
Sent: Saturday, September 20, 2008 1:01:16 AM
Subject: Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:internal IPMI error

Hey Won,

> Also I would like to know when will the "WARNING" status of a sensor
> > be displayed? I tried changing/varying one at a time the threshold
> > (upper non-critical and upper non-recoverable) values for a CPU
> > temperature below the actual sensor reading, and only NOMINAL and
> > CRITICAL were displayed. I need to verify if this is correctly
> > displayed as I am considering creating MIBs for SNMP traps.

If you edit the ipmi_monitoring_sensors.conf file (in /etc by default)
you should be able to configure what conditions nominal vs. warning vs.
critical occur. Be sure to un-comment the field that you are editing
just in case you forgot.

If you run ipmi-sensors -v, you can see the temperature ranges that
qualify for "non-critical, critical, and non-recoverable" stages.

There was a bug in the parsing code for 0.6.7, so could you please try
this tar.gz.

http://ftp.zresearch.com/pub/freeipmi/qa-release/freeipmi-0.6.8.beta1.tar.gz

Thanks,
Al

On Fri, 2008-09-19 at 12:43 -0400, Al Chu wrote:
> Hey Won,
>
> On Fri, 2008-09-19 at 10:46 -0700, Won De Erick wrote:
> > Hi Al,
> >
> > I bootstrapped again bare freebsd 6.2 on IBM x3650, then added
> > freeipmi v0.6.6, and the previous error did not display.
> > However, the null debug infos were still displayed and a "segmentation
> > fault" was displayed at the end.
>
> This only happens when you run w/ --debug? If yes, that means you can
> still use the software. Which is good. I've pinged Dmitry (FreeIPMI's
> primary BSD guy) to see if he can look into the null-fields. I don't
> have a BSD system around, so I'm sort of limited in my ability to look
> into it.
>
> > Below were the workarounds made, and please see the attached file for
> > the complete result.
> >
> > # ipmimonitoring --version
> > Ipmimonitoring [ipmimonitoring-0.6.6]
> > Copyright (C) 2007-2008 Lawrence Livermore National Security, LLC.
> > This program is free software; you may redistribute it under the terms
> > of
> > the GNU General Public License. This program has absolutely no
> > warranty.
> >
> > # ipmimonitoring --debug
> > =====================================================
> > Get SDR Repository Info Request
> > =====================================================
> > [ 20h] = (null)[134669316b]
> > =====================================================
> > Get SDR Repository Info Response
> > =====================================================
> > [ 20h] = (null)[134672388b]
> > [ 0h] = (null)[134672656b]
> > [ 1h] = (null)[134672924b]
> > [ 5h] = (null)[134673192b]
> > [ 7Ah] = (null)[134673460b]
> > [ D5Bh] = (null)[134673728b]
> > [ 0h] = (null)[134673996b]
> > [ 0h] = (null)[134674264b]
> > [ 0h] = (null)[134674532b]
> > [ 1h] = (null)[134674800b]
> > [ 0h] = (null)[134675068b]
> > [ 0h] = (null)[134675336b]
> > [ 0h] = (null)[134675604b]
> > [ 0h] = (null)[134675872b]
> > [ 0h] = (null)[134676140b]
> > (ipmi_monitoring_ipmi_communication.c, _inband_init, 112): ipmi_cmd:
> > device not found
> >
> > ......[cut]
> >
> > =====================================================
> > SDR Compact Sensor Record
> > =====================================================
> > [ 3Eh] = (null)[134676484b]
> > [ 1h] = (null)[134676752b]
> > [ 5h] = (null)[134677020b]
> > [ 2h] = (null)[134677288b]
> > [ 23h] = (null)[134677556b]
> > [ 0h] = (null)[134677824b]
> > [ 10h] = (null)[134678092b]
> > [ 0h] = (null)[134678360b]
> > [ 0h] = (null)[134678628b]
> > [ 0h] = (null)[134678896b]
> > [ 3h] = (null)[134679164b]
> > [ 7h] = (null)[134679432b]
> > [ 1h] = (null)[134679700b]
> > [ 0h] = (null)[134679968b]
> > [ 1h] = (null)[134680236b]
> > [ 1h] = (null)[134680504b]
> > [ 1h] = (null)[134680772b]
> > [ 0h] = (null)[134681040b]
> > [ 0h] = (null)[134681308b]
> > [ 1h] = (null)[134681576b]
> > [ 1h] = (null)[134681844b]
> > [ 0h] = (null)[134682112b]
> > [ 0h] = (null)[134682380b]
> > [ 0h] = (null)[134682648b]
> > [ 0h] = (null)[134682916b]
> > [ 1h] = (null)[134683184b]
> > [ 0h] = (null)[134683452b]
> > [ 23h] = (null)[134683720b]
> > [ 6Fh] = (null)[134683988b]
> > [ Fh] = (null)[134684256b]
> > [ 0h] = (null)[134684524b]
> > [ Fh] = (null)[134684792b]
> > [ 0h] = (null)[134685060b]
> > [ 0h] = (null)[134685328b]
> > [ 0h] = (null)[134685596b]
> > [ 3h] = (null)[134685864b]
> > [ 0h] = (null)[134686132b]
> > [ 0h] = (null)[134686400b]
> > [ 1h] = (null)[134686668b]
> > [ 0h] = (null)[134686936b]
> > [ 0h] = (null)[134687204b]
> > [ 0h] = (null)[134687472b]
> > [ 0h] = (null)[134687740b]
> > [ 0h] = (null)[134688008b]
> > [ 0h] = (null)[134688276b]
> > [ 0h] = (null)[134688544b]
> > [ 0h] = (null)[134688812b]
> > [ C8h] = (null)[134689080b]
> > Segmentation fault
> >
> > Also I would like to know when will the "WARNING" status of a sensor
> > be displayed? I tried changing/varying one at a time the threshold
> > (upper non-critical and upper non-recoverable) values for a CPU
> > temperature below the actual sensor reading, and only NOMINAL and
> > CRITICAL were displayed. I need to verify if this is correctly
> > displayed as I am considering creating MIBs for SNMP traps.
>
> Lets see. The default configuration is that temperature sensors (which
> I assume is what you're interested in) I don't have any "warning"
> conditions. I have either nominal or critical. This can be adjusted
> with the sensors.conf file as you've already seemed to try.
>
> But, it does seem there is a bug in that part of the code. Let me look
> into it and I'll get back to you.
>
> Al
>
> >
> > Thanks,
> >
> > Won
> >
> >
> >
> >
> > ----- Original Message ----
> > From: Al Chu <address@hidden>
> > To: Won De Erick <address@hidden>
> > Cc: David Sparks <address@hidden>; address@hidden
> > Sent: Friday, September 19, 2008 8:19:08 PM
> > Subject: Re:
> > [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:internal
> > IPMI error
> >
> > Hey Won,
> >
> > Hmmmm. The final line of your debug w/ the CBh error code should
> > already be handled in FreeIPMI 0.6.6. Are you sure it's FreeIPMI
> > 0.6.6?
> > Could you accidentally running something older?
> >
> > As for the "null" debug infos, I need to figure that one out still.
> > It's something specific to FreeBSD. I'm wondering if there is a lib
> > loaded different or symbols stored different or something like that.
> >
> > Al
> >
> > On Wed, 2008-09-17 at 20:42 -0700, Won De Erick wrote:
> > > I am having the same problem on IBM x3650 box (w/ BMC outband
> > > management port). This box is built with BMC and as far the
> > > documentation can tell, the box is an IPMI compliant. I installed
> > > FreeBSD 6.2 and added freeipmi v0.6.6. Currently, I'm using the
> > inband
> > > mechanism. However, I received an internal error when I ran
> > > ipmimonitoring.
> > > Can anybody help please? Attached is the complete debug output.
> > >
> > > # ipmimonitoring --debug
> > >
> > > =====================================================
> > > Get SDR Repository Info Request
> > > =====================================================
> > > [ 20h] = (null)[134673412b]
> > > =====================================================
> > > Get SDR Repository Info Response
> > > =====================================================
> > > [ 20h] = (null)[134676484b]
> > > [ 0h] = (null)[134676752b]
> > > [ 1h] = (null)[134677020b]
> > > [ 5h] = (null)[134677288b]
> > > [ 7Ah] = (null)[134677556b]
> > > [ D5Bh] = (null)[134677824b]
> > > [ 0h] = (null)[134678092b]
> > > [ 0h] = (null)[134678360b]
> > > [ 0h] = (null)[134678628b]
> > > [ 1h] = (null)[134678896b]
> > > [ 0h] = (null)[134679164b]
> > > [ 0h] = (null)[134679432b]
> > > [ 0h] = (null)[134679700b]
> > > [ 0h] = (null)[134679968b]
> > > [ 0h] = (null)[134680236b]
> > > (ipmi_monitoring_ipmi_communication.c, _inband_init, 112): ipmi_cmd:
> > > device not found
> > >
> > > ......[cut]
> > >
> > > =====================================================
> > > Get SDR Repository Info Request
> > > =====================================================
> > > [ 20h] = (null)[134673412b]
> > > =====================================================
> > > =====================================================
> > > Get Sensor Reading Response
> > > =====================================================
> > > [ 2Dh] = (null)[134692868b]
> > > [ CBh] = (null)[134693136b]
> > > ipmi_monitoring_sensor_readings_by_record_id: internal IPMI error
> > >
> > >
> > > Thanks,
> > >
> > > Won
> > >
> > >
> > --
> > Albert Chu
> > address@hidden
> > Computer Scientist
> > High Performance Systems Division
> > Lawrence Livermore National Laboratory
> >
> >
> >
--
Albert Chu
address@hidden
Computer Scientist
High Performance Systems Division
Lawrence Livermore National Laboratory

From:	Won De Erick
Subject:	Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:internal IPMI error
Date:	Sun, 21 Sep 2008 19:56:42 -0700 (PDT)