[Freeipmi-devel] Re: Fw: ipmi-sensors and ipmimonitoring mismatch
--- On Fri, 4/3/09, Al Chu ch...@llnl.gov wrote: Hey Won, The reason for what you're seeing is described in the ipmimonitoring manpage. --- Interpretation rules have not been written for all sensors permutations and types. Users may notice some sensors output in ipmi-sensors(8) do not output in ipmimonitoring. If sensor interpretation rules are needed, please contact the FreeIPMI maintainers. --- Looking at your sensors output below, there are three OEM sensors that I can't interpret b/c I don't know the interpretation rules for them. The Power Unit Device Install and Fan transition interpretations were recently added in 0.7.3. So if you update to atleast 0.7.3, those readings should show up in ipmimonitoring. As for why Temperature Sensors aren't showing up, this corner case for HP machines also appears to have been fixed in 0.7..3. Thank you for the tip. I installed the latest, 0.7.6, instead. hpdl380-fbsd71r# ipmi-sensors 1: UID Light (OEM Reserved): [OEM State = h] 2: Int. Health LED (OEM Reserved): [OEM State = h] 3: Ext. Health LED (OEM Reserved): [OEM State = h] 4: Power Supply 1 (Power Supply): [Presence detected] 5: Power Supply 2 (Power Supply): [NA] 6: Power Supplies (Power Supply): [Non-redundant:Sufficient Resources from Redun dant] 8: VRM 1 (Power Unit): [Device Inserted/Device Present] 9: VRM 2 (Power Unit): [Device Inserted/Device Present] 10: Fan 1 (Fan): [transition to Running] 11: Fan 2 (Fan): [transition to Running] 12: Fan 3 (Fan): [transition to Running] 13: Fan 4 (Fan): [transition to Running] 14: Fan 5 (Fan): [transition to Running] 15: Fan 6 (Fan): [transition to Running] 16: Fans (Fan): [Fully Redundant] 18: Temp 1 (Temperature): 35.00 C (NA/70.00): [OK] 19: Temp 2 (Temperature): 17.00 C (NA/39.00): [OK] 20: Temp 3 (Temperature): 30.00 C (NA/127.00): [OK] 21: Temp 4 (Temperature): 30.00 C (NA/127.00): [OK] 22: Temp 5 (Temperature): 46.00 C (NA/77.00): [OK] 23: Temp 6 (Temperature): 30.00 C (NA/127.00): [OK] 24: Temp 7 (Temperature): 30.00 C (NA/127.00): [OK] 25: Power Meter (Current): [Device Enabled] hpdl380-fbsd71r# ipmimonitoring Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading 4 | Power Supply 1 | Power Supply | Nominal | N/A | 'Presence detected' 6 | Power Supplies | Power Supply | Critical | N/A | 'Non-redundant:Sufficient Resources from Redundant' 8 | VRM 1 | Power Unit | Nominal | N/A | 'Device Inserted/Device Present' 9 | VRM 2 | Power Unit | Nominal | N/A | 'Device Inserted/Device Present' 10 | Fan 1 | Fan | Nominal | N/A | 'transition to Running' 11 | Fan 2 | Fan | Nominal | N/A | 'transition to Running' 12 | Fan 3 | Fan | Nominal | N/A | 'transition to Running' 13 | Fan 4 | Fan | Nominal | N/A | 'transition to Running' 14 | Fan 5 | Fan | Nominal | N/A | 'transition to Running' 15 | Fan 6 | Fan | Nominal | N/A | 'transition to Running' 16 | Fans | Fan | Nominal | N/A | 'Fully Redundant' 18 | Temp 1 | Temperature | Nominal | C | 35.00 19 | Temp 2 | Temperature | Nominal | C | 17.00 20 | Temp 3 | Temperature | Nominal | C | 30.00 21 | Temp 4 | Temperature | Nominal | C | 30.00 22 | Temp 5 | Temperature | Nominal | C | 46.00 23 | Temp 6 | Temperature | Nominal | C | 30.00 24 | Temp 7 | Temperature | Nominal | C | 30.00 hpdl380-fbsd71r# One thing left is how i can into the SEL. I tried this with other tools. None of them gave an output. :( The box is IPMI v2.0-compliant. I can see a lot of logs using iLO. Thanks, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Re: Fw: ipmi-sensors and ipmimonitoring mismatch
Hi All, sending the debug output. Thanks, Won --- On Fri, 4/3/09, Al Chu ch...@llnl.gov wrote: Hey Won, One thing left is how i can into the SEL. I tried this with other tools. None of them gave an output. :( Do you mean you can't access the SEL in multiple IPMI software? Can you send me the --debug output from running ipmi-sel? Let's see what the problem is. Al On Fri, 2009-04-03 at 11:57 -0700, Won De Erick wrote: --- On Fri, 4/3/09, Al Chu ch...@llnl.gov wrote: Hey Won, The reason for what you're seeing is described in the ipmimonitoring manpage. --- Interpretation rules have not been written for all sensors permutations and types. Users may notice some sensors output in ipmi-sensors(8) do not output in ipmimonitoring. If sensor interpretation rules are needed, please contact the FreeIPMI maintainers. --- Looking at your sensors output below, there are three OEM sensors that I can't interpret b/c I don't know the interpretation rules for them. The Power Unit Device Install and Fan transition interpretations were recently added in 0.7.3. So if you update to atleast 0.7.3, those readings should show up in ipmimonitoring. As for why Temperature Sensors aren't showing up, this corner case for HP machines also appears to have been fixed in 0.7..3. Thank you for the tip. I installed the latest, 0.7.6, instead. hpdl380-fbsd71r# ipmi-sensors 1: UID Light (OEM Reserved): [OEM State = h] 2: Int. Health LED (OEM Reserved): [OEM State = h] 3: Ext. Health LED (OEM Reserved): [OEM State = h] 4: Power Supply 1 (Power Supply): [Presence detected] 5: Power Supply 2 (Power Supply): [NA] 6: Power Supplies (Power Supply): [Non-redundant:Sufficient Resources from Redun dant] 8: VRM 1 (Power Unit): [Device Inserted/Device Present] 9: VRM 2 (Power Unit): [Device Inserted/Device Present] 10: Fan 1 (Fan): [transition to Running] 11: Fan 2 (Fan): [transition to Running] 12: Fan 3 (Fan): [transition to Running] 13: Fan 4 (Fan): [transition to Running] 14: Fan 5 (Fan): [transition to Running] 15: Fan 6 (Fan): [transition to Running] 16: Fans (Fan): [Fully Redundant] 18: Temp 1 (Temperature): 35.00 C (NA/70.00): [OK] 19: Temp 2 (Temperature): 17.00 C (NA/39.00): [OK] 20: Temp 3 (Temperature): 30.00 C (NA/127.00): [OK] 21: Temp 4 (Temperature): 30.00 C (NA/127.00): [OK] 22: Temp 5 (Temperature): 46.00 C (NA/77.00): [OK] 23: Temp 6 (Temperature): 30.00 C (NA/127.00): [OK] 24: Temp 7 (Temperature): 30.00 C (NA/127.00): [OK] 25: Power Meter (Current): [Device Enabled] hpdl380-fbsd71r# ipmimonitoring Record_ID | Sensor Name | Sensor Group | Monitoring Status| Sensor Units | Sensor Reading 4 | Power Supply 1 | Power Supply | Nominal | N/A | 'Presence detected' 6 | Power Supplies | Power Supply | Critical | N/A | 'Non-redundant:Sufficient Resources from Redu ndant' 8 | VRM 1 | Power Unit | Nominal | N/A | 'Device Inserted/Device Present' 9 | VRM 2 | Power Unit | Nominal | N/A | 'Device Inserted/Device Present' 10 | Fan 1 | Fan | Nominal | N/A | 'transition to Running' 11 | Fan 2 | Fan | Nominal | N/A | 'transition to Running' 12 | Fan 3 | Fan | Nominal | N/A | 'transition to Running' 13 | Fan 4 | Fan | Nominal | N/A | 'transition to Running' 14 | Fan 5 | Fan | Nominal | N/A | 'transition to Running' 15 | Fan 6 | Fan | Nominal | N/A | 'transition to Running' 16 | Fans | Fan | Nominal | N/A | 'Fully Redundant' 18 | Temp 1 | Temperature | Nominal | C | 35.00 19 | Temp 2 | Temperature | Nominal | C | 17.00 20 | Temp 3 | Temperature | Nominal | C | 30.00 21 | Temp 4 | Temperature | Nominal | C | 30.00 22 | Temp 5 | Temperature | Nominal | C | 46.00 23 | Temp 6 | Temperature | Nominal | C | 30.00 24 | Temp 7 | Temperature | Nominal | C | 30.00 hpdl380-fbsd71r# One thing left is how i can into the SEL. I tried this with other tools. None of them gave an output. :( The box is IPMI v2.0-compliant. I can see a lot of logs using iLO. Thanks, Won -- Albert Chu ch...@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory hpdl380-fbsd71r# ipmi-sel --debug = Get SDR Repository Info Request = [ 20h] = cmd[ 8b] = Get SDR Repository Info Response = [ 20h] = cmd[ 8b] [ 0h] = comp_code[ 8b] [ 1h] = sdr_version_major[ 4b] [ 5h] = sdr_version_minor[ 4b] [ 1Ah] = record_count[16b] [h] = free_space[16b] [h
[Freeipmi-devel] Re: Fw: ipmi-sensors and ipmimonitoring mismatch
--- On Sat, 4/4/09, Al Chu11 ch...@llnl.gov wrote: Hey Won, This output looks familiar, I think I have worked on this before with another FreeIPMI user ... CBh = sensor not present Something seems amiss in the HP IPMI. Do you have any HP software that works? Maybe it only works for HP software and none of the open source software out there. I am using an 60-day evaluation edition of HP iLO 2 (embedded). The iLO 2 is as good as an out-of management system. I am accessing it via the dedicated iLO management port (Ethernet). I should at least want to manage the BMC via in-band. Thanks, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
RE: [Freeipmi-devel] Re: ibmx3650 reboots after ipmi-sel is unable toget SEL record
--- On Wed, 3/18/09, Andy Cress andy.cr...@us.kontron.com wrote: Hmmm. I just thought of something. Are there any ipmi-related apps that are doing SetSelTime on this system? That could cause problems like this if used indiscriminately. That command should generally be used once per OS boot, if at all. The system is synced to an NTP Server during bootup, then updated every 5 hours. I don't know if the process is related to SetSelTime though. The user can only use and control bmc-watchdog. Other freeipmi tools are not allowed, and are not visible to the user. No other apps that use ipmi-related tools. Please let me know if you need more information. Andy ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] SEL datestamp 01-Jan-1970?
Hi Al, I noticed the following erroneous datestamps when viewing SEL. #ipmi-sel 144:08-Feb-2009 03:51:08:System Event System Event:Timestamp Clock Synch 164:08-Feb-2009 03:51:03:System Event System Event:Timestamp Clock Synch 184:08-Feb-2009 03:51:25:System Event System Event:OEM System Boot Event 444:01-Jan-1970 08:00:11:Power Supply Power Supply 2:Power Supply input lost (AC/DC) 464:01-Jan-1970 08:00:12:Power Unit Power Redundancy:Entered from Non-redundant:Insufficient Resources 484:01-Jan-1970 08:00:50:System Event System Event:Timestamp Clock Synch 504:10-Feb-2009 11:45:09:System Event System Event:Timestamp Clock Synch I've replicated this to several machines. Though the CMOS battery could be the potential reason, I want to know if ipmi-sel is related to this, or has something to do with this. Thanks, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: Fw: [Freeipmi-devel] ibmx3650 reboots after ipmi-sel is unable to get SEL record
- Original Message From: Al Chu ch...@llnl.gov Hey Won, On Mon, 2009-01-26 at 18:53 -0800, Won De Erick wrote: - Original Message From: Al Chu Hey Won, On Sun, 2009-01-25 at 23:00 -0800, Won De Erick wrote: I am forwarding this to the FreeIPMI users mailing list. Hope, I can get hints from you all. Thank you. - Forwarded Message From: Won De Erick To: Albert Chu Cc: freeipmi-devel@gnu.org Sent: Saturday, January 24, 2009 11:55:24 AM Subject: Re: [Freeipmi-devel] ibmx3650 reboots after ipmi-sel is unable to get SEL record Pls disregard previous email. I forgot to attach the file. :) Did you send me the wrong debug file? I see debug output from ipmi-sensors?? I'm sorry, attached is the correct one. Seems that this has a successful ipmi-sel execution in it. So not much I can debug with :-( Hi Al, With IBM x3650, I noticed that ipmi-sel is unable to get the SEL record. # ipmi-sel --version IPMI Sensors [ipmi-sel-0.6.10] # ipmi-sel ibm3650-dsc2075-sel.txt ipmi_cmd_get_sel_entry: BMC busy ipmi-sel: unable to get SEL record After the above, the box automatically rebooted. Is this normal? I have never seen this behavior before, and I wouldn't consider it good in any definition. This is likely a bug in the IBM implementation. The BMC busy means exactly what it says, the BMC is busy and cannot respond to IPMI requests. It by itself is not a problem. For example, some other IPMI tasks are hogging resources. But you should presumably be able to reach the card eventually. Is it possible you have other IPMI things running in the background? bmc-watchdog (as daemon) was the only thing running in the background. This shouldn't be enough to cause enough IPMI to be *that* busy. Here's a thought. Perhaps the ipmi-sel logs went full, the BMC card went busy, and thus the bmc-watchdog couldn't perform IPMI and timed out, thus leading to a reboot?? Obviously, it depends on how you setup the bmc-watchdog. this is my setup: #bmc-watchdog -d -u 4 -p 0 -n -i 300 -l 0 I forgot to tell you that I am using in-band mechanism. IBM x3650 should be installed with an RSA II card to get BMC card (think this is the built-in LAN management port that goes with the box) working. I then cleared the SEL records, thinking that the reboot might have been triggered due to a full SEL. I think this is a reasonable guess. It could be anything really. # ipmi-sel -c # reboot # ipmi-sel 1:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 # ipmi-sel 1:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 # reboot # ipmi-sel 1:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 2:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 3:OEM defined = 02 00 00 FF 00 00 00 00 20 00 00 00 00 Then retried the previous command that caused an error. # ipmi-sel ibm3650-dsc2075-sel.txt # cat ibm3650-dsc2075-sel.txt 1:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 2:OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00 3:OEM defined = 02 00 00 FF 00 00 00 00 20 00 00 00 00 Then the problem didn't occur anymore. Besides, what is the meaning of this OEM defined? I can't see any log that is more specific, or something like The system event log is allowed to store OEM defined information. Since the information is defined by (in this case) IBM, I have no way to convert the hex into something like what you're used to :-( I think this is cool. So, is it safe to assume that the system rebooted if I see similar OEM defined info ( in this case OEM defined = 00 00 00 00 00 E3 25 86 80 00 00 FF 00)? Is there any possibility to integrate IBM's OEM defined info in the future too? :D I'd be willing to integrate any vendors OEM defined This is nice to know. :) interpretation/parsing into FreeIPMI. The problem is, I do not know how to interpret/parse any of their information :-( As a customer, you should tell your vendor support about this. Each user that complains makes it more possible for them to release the information. Al 220:19-Sep-2008 14:24:56:Power Unit Sys pwr monitor:Power Off/Power Down 221:19-Sep-2008 14:25:16:Power Unit Sys pwr monitor:Power Off/Power Down I've attached here the ipmi-sel debug output. Then one side question, I want to ask the possible reasons of the ff log obtained prior to clearing. I didn't change any in the system. I just noticed that the system halted serving and went back after 4-5 minutes, w/out any other records in SEL that says the box hang and rebooted. 54:23-Jan-2009 11:28:55:System Event #0:System Reconfigured
[Freeipmi-devel] Last digit of threshold values, can't be changed?
Hi, I noticed that when I changed the last digit of a threshold value, the new value was not reflected when checking it out. I did this to other sensor threshold values (those with a 0 or 00 last), and same thing happened. Is this normal? # ipmi-sensors-config -c -e 24_Processor1_Temp:Upper_Non_Critical_Threshold=75.01 # ipmi-sensors-config -o -S 24_Processor1_Temp Section 24_Processor1_Temp ## Give valid input for sensor type = Temperature; units = degrees C Lower_Non_Critical_Threshold -5.00 ## Give valid input for sensor type = Temperature; units = degrees C Lower_Critical_Threshold -10.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Non_Critical_Threshold 75.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Critical_Threshold 80.00 EndSection # ipmi-sensors-config -c -e 24_Processor1_Temp:Upper_Non_Critical_Threshold=75.10 # ipmi-sensors-config -o -S 24_Processor1_Temp Section 24_Processor1_Temp ## Give valid input for sensor type = Temperature; units = degrees C Lower_Non_Critical_Threshold -5.00 ## Give valid input for sensor type = Temperature; units = degrees C Lower_Critical_Threshold -10.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Non_Critical_Threshold 75.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Critical_Threshold 80.00 EndSection # ipmi-sensors-config -c -e 24_Processor1_Temp:Upper_Non_Critical_Threshold=75.10 # ipmi-sensors-config -o -S 24_Processor1_Temp Section 24_Processor1_Temp ## Give valid input for sensor type = Temperature; units = degrees C Lower_Non_Critical_Threshold -5.00 ## Give valid input for sensor type = Temperature; units = degrees C Lower_Critical_Threshold -10.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Non_Critical_Threshold 75.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Critical_Threshold 80.00 EndSection # ipmi-sensors-config -c -e 24_Processor1_Temp:Upper_Non_Critical_Threshold=76.10 # ipmi-sensors-config -o -S 24_Processor1_Temp Section 24_Processor1_Temp ## Give valid input for sensor type = Temperature; units = degrees C Lower_Non_Critical_Threshold -5.00 ## Give valid input for sensor type = Temperature; units = degrees C Lower_Critical_Threshold -10.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Non_Critical_Threshold 76.00 ## Give valid input for sensor type = Temperature; units = degrees C Upper_Critical_Threshold 80.00 EndSection Thanks, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel] Errors in Compiling FreeIPMI-0.7.3.beta1.tar.gz on FreeBSD7.1Beta2
Hi Al, Adding that environment variable has solved the problem. But there were unsupported dependencies when configuring: checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no checking for pgf77... no checking for fort77... no checking for fl32... no checking for af77... no checking for f90... no checking for xlf90... no checking for pgf90... no checking for epcf90... no checking for f95... no checking for fort... no checking for xlf95... no checking for ifc... no checking for efc... no checking for pgf95... no checking for lf95... no checking for gfortran... no However, I can able to use the tools. I am still undetermined of the problems that the above may bring. Thanks, Won - Original Message From: Al Chu [EMAIL PROTECTED] To: Won De Erick [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; freeipmi-devel@gnu.org; Dmitry Frolov [EMAIL PROTECTED] Sent: Friday, November 21, 2008 7:31:36 PM Subject: Re: [Freeipmi-devel] Errors in Compiling FreeIPMI-0.7.3.beta1.tar.gz on FreeBSD7.1Beta2 I have to punt to Dmitry at this point, since I don't know FreeBSD. The pthread library isn't being linked in. Not really sure why. You may want to set the environment variable LIBS=-lpthread and see if that does anything. AL On Thu, 2008-11-20 at 22:47 -0800, Won De Erick wrote: Hi Al, Based from that, I tried the following: # setenv CPPFLAGS -I/usr/local/include # setenv LDFLAGS -L/usr/local/lib # setenv PTHREAD_LIBS -pthread # ./configure --disable-init-scripts --disable-logrotate-config --disable-logdir --localstatedir=/var --with-ipmi-monitoring-sdr-cache-dir=/var/db/freeipmi/ipmimonitoringsdrcache --sysconfdir=/usr/local/etc/freeipmi --prefix=/usr/local Then, a Makefile was successfully created. When compiling w/ gmake: *** Warning: Linking the executable bmc-config against the loadable module *** libfreeipmi.so is not portable! gcc -g -O2 -o .libs/bmc-config bmc-config.o bmc-config-argp.o bmc-config-channel-common.o bmc-config-map.o bmc-config-sections.o bmc-config-utils.o bmc-config-user-sections.o bmc-config-lan-channel-section.o bmc-config-serial-channel-section.o bmc-config-lan-conf-section.o bmc-config-lan-conf-auth-section.o bmc-config-lan-conf-security-keys-section.o bmc-config-lan-conf-misc-section.o bmc-config-rmcpplus-conf-privilege-section.o bmc-config-serial-conf-section.o bmc-config-pef-conf-section.o bmc-config-sol-conf-section.o bmc-config-misc-section.o bmc-config-validate.o -L/usr/local/lib ../../common/src/configtool/.libs/libconfigtoolcommon.a ../../common/src/toolcommon/.libs/libtoolcommon.a ../../common/src/toolhostrange/.libs/libtoolhostrange.a ../../common/src/miscutil/.libs/libmiscutils.a ../../common/src/portability/.libs/libfreeipmiportability.a ../../ipmidetect/src/libipmidetect/.libs/libipmidetect.so ../../libfreeipmi/src/.libs/libfreeipmi.so /usr/local/lib/libgcrypt.so /usr/local/lib/libgpg-error.so /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -largp -lm -Wl,--rpath -Wl,/usr/local/lib .../../common/src/toolhostrange/.libs/libtoolhostrange.a(libtoolhostrange_la-pstdout.o)(.text+0x166a): In function `pstdout_launch': /root/freeipmi-0.7.3.beta1/common/src/toolhostrange/pstdout.c:1424: undefined reference to `pthread_create' gmake[2]: *** [bmc-config] Error 1 gmake[2]: Leaving directory `/root/freeipmi-0.7.3.beta1/bmc-config/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/root/freeipmi-0.7.3.beta1/bmc-config' gmake: *** [all-recursive] Error 1 the above errors were displayed. Are there some more things that i need to configure? Thanks, Won - Original Message From: Al Chu [EMAIL PROTECTED] To: Won De Erick [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; freeipmi-devel@gnu.org; Dmitry Frolov [EMAIL PROTECTED] Sent: Friday, November 21, 2008 10:44:29 AM Subject: Re: [Freeipmi-devel] Errors in Compiling FreeIPMI-0.7.3.beta1.tar.gz on FreeBSD7.1Beta2 Hey Won, Dmitry posted this some time ago as what needs to be done to build on FreeBSD. env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib PTHREAD_LIBS=-pthread \ ./configure \ --disable-init-scripts --disable-logrotate-config --disable-logdir --localstatedir=/var --with-ipmi-monitoring-sdr-cache-dir=/var/db/freeipmi/ipmimonitoringsdrcache --sysconfdir=/usr/local/etc/freeipmi --prefix=/usr/local gmake hopefully that helps Al On Thu, 2008-11-20 at 18:37 -0800, Won De Erick wrote: Hi, The installation of freeipmi from tarbal has been my problem in FreeBSD(even in 6.2 before). No problem when installing this from ports, but I should want to try the latest one as the ported one is not automatically updated. AFAIK, the dependencies are the below: security/libgpg-error security/libgcrypt devel/argp-standalone I started installing
Re: [Freeipmi-devel] Errors in Compiling FreeIPMI-0.7.3.beta1.tar.gz on FreeBSD7.1Beta2
Hi Al, Based from that, I tried the following: # setenv CPPFLAGS -I/usr/local/include # setenv LDFLAGS -L/usr/local/lib # setenv PTHREAD_LIBS -pthread # ./configure --disable-init-scripts --disable-logrotate-config --disable-logdir --localstatedir=/var --with-ipmi-monitoring-sdr-cache-dir=/var/db/freeipmi/ipmimonitoringsdrcache --sysconfdir=/usr/local/etc/freeipmi --prefix=/usr/local Then, a Makefile was successfully created. When compiling w/ gmake: *** Warning: Linking the executable bmc-config against the loadable module *** libfreeipmi.so is not portable! gcc -g -O2 -o .libs/bmc-config bmc-config.o bmc-config-argp.o bmc-config-channel-common.o bmc-config-map.o bmc-config-sections.o bmc-config-utils.o bmc-config-user-sections.o bmc-config-lan-channel-section.o bmc-config-serial-channel-section.o bmc-config-lan-conf-section.o bmc-config-lan-conf-auth-section.o bmc-config-lan-conf-security-keys-section.o bmc-config-lan-conf-misc-section.o bmc-config-rmcpplus-conf-privilege-section.o bmc-config-serial-conf-section.o bmc-config-pef-conf-section.o bmc-config-sol-conf-section.o bmc-config-misc-section.o bmc-config-validate.o -L/usr/local/lib ../../common/src/configtool/.libs/libconfigtoolcommon.a ../../common/src/toolcommon/.libs/libtoolcommon.a ../../common/src/toolhostrange/.libs/libtoolhostrange.a ../../common/src/miscutil/.libs/libmiscutils.a ../../common/src/portability/.libs/libfreeipmiportability.a ../../ipmidetect/src/libipmidetect/.libs/libipmidetect.so ../../libfreeipmi/src/.libs/libfreeipmi.so /usr/local/lib/libgcrypt.so /usr/local/lib/libgpg-error.so /usr/local/lib/libintl.so /usr/local/lib/libiconv.so -largp -lm -Wl,--rpath -Wl,/usr/local/lib .../../common/src/toolhostrange/.libs/libtoolhostrange.a(libtoolhostrange_la-pstdout.o)(.text+0x166a): In function `pstdout_launch': /root/freeipmi-0.7.3.beta1/common/src/toolhostrange/pstdout.c:1424: undefined reference to `pthread_create' gmake[2]: *** [bmc-config] Error 1 gmake[2]: Leaving directory `/root/freeipmi-0.7.3.beta1/bmc-config/src' gmake[1]: *** [all-recursive] Error 1 gmake[1]: Leaving directory `/root/freeipmi-0.7.3.beta1/bmc-config' gmake: *** [all-recursive] Error 1 the above errors were displayed. Are there some more things that i need to configure? Thanks, Won - Original Message From: Al Chu [EMAIL PROTECTED] To: Won De Erick [EMAIL PROTECTED] Cc: [EMAIL PROTECTED]; freeipmi-devel@gnu.org; Dmitry Frolov [EMAIL PROTECTED] Sent: Friday, November 21, 2008 10:44:29 AM Subject: Re: [Freeipmi-devel] Errors in Compiling FreeIPMI-0.7.3.beta1.tar.gz on FreeBSD7.1Beta2 Hey Won, Dmitry posted this some time ago as what needs to be done to build on FreeBSD. env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib PTHREAD_LIBS=-pthread \ ./configure \ --disable-init-scripts --disable-logrotate-config --disable-logdir --localstatedir=/var --with-ipmi-monitoring-sdr-cache-dir=/var/db/freeipmi/ipmimonitoringsdrcache --sysconfdir=/usr/local/etc/freeipmi --prefix=/usr/local gmake hopefully that helps Al On Thu, 2008-11-20 at 18:37 -0800, Won De Erick wrote: Hi, The installation of freeipmi from tarbal has been my problem in FreeBSD(even in 6.2 before). No problem when installing this from ports, but I should want to try the latest one as the ported one is not automatically updated. AFAIK, the dependencies are the below: security/libgpg-error security/libgcrypt devel/argp-standalone I started installing libcrypt. This was successfully installed. Then proceed w/ freeipmi (http://ftp.zresearch.com/pub/freeipmi/qa-release/freeipmi-0.7.3.beta1.tar.gz) compilation. I always get errors like: checking how to run the C++ preprocessor... g++ -E checking for g77... no checking for f77... no checking for xlf... no checking for frt... no . Then end up with . checking whether make sets $(MAKE)... (cached) yes checking for gcry_md_open in -lgcrypt... no configure: error: libgcrypt required to build libfreeipmi Attached are the logs for installing libcrypt and compiling freeipmi. Any help pls. Thanks, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http:// lists.gnu.org/mailman/listinfo/freeipmi-devel -- Albert Chu [EMAIL PROTECTED] Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
[Freeipmi-devel] Obtain an error when changing a threshold value... but echo $ returns 0 value
Hi Al, Box/Platform: IBM x3650, freebsd 6.2, freeipmiv0.6.6 I was trying to change the threshold value for a fan (see below), but got an error. This is OK. However, what I was expecting to receive is a non-zero return value to distinguish it from the one without an error message. ~# ipmi-sensors-config -o -S 16_Fan_9_Tach Section 16_Fan_9_Tach ## Give valid input for sensor type = Fan; units = RPM ## Lower_Critical_Threshold 750.00 EndSection ~# echo $? 0 ~# ipmi-sensors-config -c -e 16_Fan_9_Tach:Lower_Critical_Threshold=760.0 ERROR: `16_Fan_9_Tach:Lower_Critical_Threshold' is not writeable ~# echo $? 0 Thanks again, Won ___ Freeipmi-devel mailing list Freeipmi-devel@gnu.org http://lists.gnu.org/mailman/listinfo/freeipmi-devel
Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:interna l IPMI error
How I wish I could have the FreeBSD version so as to install the package straithforward. I encountered other dependency errors before aside from the libgcrypt, and got lost in the middle. So I ended up installing this as port, automatically getting the latest ported freebsd version. - Original Message From: Dmitry Frolov [EMAIL PROTECTED] Subject: Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:interna l IPMI error Hi, Won! Assuming You already installed some version of freeipmi and all dependencies are met, you will need to pass some parameters to configure. FreeBSD port builds FreeIPMI this way: env CPPFLAGS=-I/usr/local/include LDFLAGS=-L/usr/local/lib PTHREAD_LIBS=-pthread \ ./configure \ --disable-init-scripts --disable-logrotate-config --disable-logdir --localstatedir=/var --with-ipmi-monitoring-sdr-cache-dir=/var/db/freeipmi/ipmimonitoringsdrcache --sysconfdir=/usr/local/etc/freeipmi --prefix=/usr/local gmake * Al Chu [EMAIL PROTECTED] [22.09.2008 10:06]: Hey Won, Ahhh. You need libgcrypt libraries to compile. In redhat/fedora linux, this is the libgcrypt + libgcrypt-devel RPMs. I'm not too sure what it is in BSD land. If you can't find it, hopefully Dmitry can reply and let us know. Sorry I can't be more help on how to compile on BSD. Al On Sun, 2008-09-21 at 19:56 -0700, Won De Erick wrote: 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 [EMAIL PROTECTED] To: Won De Erick [EMAIL PROTECTED] Cc: freeipmi-devel@gnu.org 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
Re: [Freeipmi-devel]ipmi_monitoring_sensor_readings_by_record_id:internal IPMI error
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 [EMAIL PROTECTED] To: Won De Erick [EMAIL PROTECTED] Cc: freeipmi-devel@gnu.org 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
