From MAILER-DAEMON Mon Oct 05 16:36:04 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MuuHs-0005ke-11 for mharc-freeipmi-users@gnu.org; Mon, 05 Oct 2009 16:36:04 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MuuHp-0005iq-Q7 for freeipmi-users@gnu.org; Mon, 05 Oct 2009 16:36:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MuuHl-0005eM-GW for freeipmi-users@gnu.org; Mon, 05 Oct 2009 16:36:01 -0400 Received: from [199.232.76.173] (port=42525 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MuuHk-0005e4-Sc for freeipmi-users@gnu.org; Mon, 05 Oct 2009 16:35:56 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:40146) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MuuHj-0005hP-I8 for freeipmi-users@gnu.org; Mon, 05 Oct 2009 16:35:56 -0400 X-Attachments: NEWS Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 05 Oct 2009 13:35:55 -0700 From: Al Chu To: freeipmi-users@gnu.org Content-Type: multipart/mixed; boundary="=-QFXvZx7gsPVKDCx8vOz2" Date: Mon, 05 Oct 2009 13:35:54 -0700 Message-Id: <1254774954.20077.169.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-8.el5_2.3) X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [Freeipmi-users] FreeIPMI 0.8.0 Beta1 - Feedback Request X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 05 Oct 2009 20:36:02 -0000 --=-QFXvZx7gsPVKDCx8vOz2 Content-Type: text/plain Content-Transfer-Encoding: 7bit Hi everyone, I've put up a beta release of FreeIPMI 0.8.1.beta1 here: http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta1.tar.gz I'd appreciate any testing, input, etc. from people. There are a few feature changes that I would like to get some input on. I am open to changing, reverting, or adjusting based on user input. Attached to the e-mail is the official NEWS release that lists all the changes in glorious detail. New ipmi-sensors/ipmi-sel/ipmimonitoring default output: -------------------------------------------------------- The default output of ipmi-sensors, ipmi-sel, and ipmimonitoring has been modified for easier readability and consistency to each other. Some information is not output but by default anymore and is available through new options or increased verbosity. A variety of new options are available for alternate outputs too. A) Do people like the new output format? Is it easier to read (which is my primary goal)? B) Are there any options like --entity-sensor-names, --no-sensor-type-output, --non-abbreviated-units, etc. that people think should be default rather than an option? C) Is there an output that should be default instead, or have an option to give an alternate output? D) Does the --legacy-output option not fully maintain backwards compatability and break anybody's scripts?? Things I would appreciate testing on ------------------------------------ I'd appreciate people trying them out on their systems to make sure everything still outputs fine and I make any new corner cases. I'm particularly interested in ensuring I didn't break: A) The --bridge-sensors options on ipmi-sensors and ipmimonitoring B) Multirecords outputs on ipmi-fru. C) Workarounds, most notably the Intel workarounds D) The new ipmi-dcmi tool, which I have not been able to fully vet due to lack of a system. Any feedback would be appreciated before I release. Thanks, Al -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory --=-QFXvZx7gsPVKDCx8vOz2 Content-Disposition: attachment; filename=NEWS Content-Type: text/plain; name=NEWS; charset=UTF-8 Content-Transfer-Encoding: 7bit 0.8.0 - XX/XX/XX ---------------- Tools - High Level Description of Changes ----------------------------------------- o Support ipmi-dcmi, Data Center Management Interface (often referred to as DCM or DCMI). o Make output of ipmi-sel, ipmi-sensors, and ipmimonitoring easier to read and consistent to each other. Under default output, sensors listed in ipmi-sensors and ipmimonitoring are identical. Under default output, the sensor type of each entry is not output. Legacy output is supported through the --legacy-output option. o Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. o When querying active/inactive, allowed/unallowed, true/false, etc. status fields in ipmi-chassis, bmc-info, and bmc-device, output all fields instead of only the active/allowed/true/etc. fields. o Support exclusion equivalent options (such as --exclude-sensor-types) in various tools such as ipmi-sel, ipmi-sensors, and ipmimonitoring. o Support sensor unit percentages, rates, and modifiers (i.e. "% hit", "gigabyte per minute", "pounds / cu in") in most tools. o Support non-abbreviated units (i.e. "Amps" instead of "A") in most tools. o Output IANA Manufacturer Name when appropriate in most tools. o Output additional information in many tools. o Support Entity ID based sensor naming through the --entity-sensor-names option in many tools. o Support OEM output through the --interpret-oem-data option in many tools. o "Library-ize" much of the functionality originally only inside the tools. o Re-work libipmimonitoring to return sensor events for all sensors, not just non-threshold sensors. Resulted in an API change. o Removed many short options for more consistent command line "architecture" between tools and to ensure short options are more consistent between tools. Limit short options to only the most popular options. Short options have been removed from ipmipower, ipmiconsole, bmc-watchdog, ipmi-chassis, ipmimonitoring, ipmi-sel, and ipmi-raw. See details below for specific short options removed. o Rename pef-config to ipmi-pef-config for naming consistency. o Various new options and features added to various tools. o Various minor feature enhancements. o Various bug fixes. o Various documentation updates. Tools - Detailed Enhancements/Changes/Fixes ------------------------------------------- o ipmi-dcmi - A new tool to support the data center managemen interface (often referred to as DCM or DCMI). o ipmi-sel - Alter output to make fields easier to read, consistent to other tools, and more consistent to IPMI (legacy output option supported). - Under default output, do not report the sensor type. It is often redundant to the name of the sensor. - Use short-message event strings instead of long ones for readability. - Support --legacy-output option. - Support --verbose option to offer verbose, very verbose, and very very verbose additional SEL event information. - Support --display and --display-range options. - Support --exclude-display and --exclude-display-range options. - Support --system-event-only and --oem-event-only options. - Support --non-abbreviated-units option to output no abbreviated units (i.e. "Amps" instead of "A"). - Support --entity-sensor-names option. - Support --show-sensor-type option. - Support --interpret-oem-data option. - Support Inventec 5441/Dell Xanadu2 OEM SEL records. - Support Dell Poweredge R610/R710 OEM SEL records. - Support --comma-separated-output option. - Support --no-header-output option. - Rename --delete-all to --clear for consistency to IPMI spec. Backwards compatability maintained. - Output manufacturer name with "Manufacturer ID" if name available. - Support sensor unit percentages, rates and modifiers (i.e. "% hit", "gigabyte per minute", "pounds / cu in"). - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - Output allocation information with --info if available. - Output OEM hex code in consistent format. - Output hex code more often if translation to string not available. - Re-work to use new libfreeipmi sel-parse sub library. - Remove legacy option to dump hex output to optional filename. - Removed the following short options (long options remain). - 'c' (--delete-all) - 'd' (--delete) - 'R' (--delete-range) - 'x' (--hex-dump) - Support additional options in FreeIPMI config file. o ipmi-sensors - Alter output to make fields easier to read, consistent to other tools, and more consistent to IPMI (legacy output option supported). - Under default output, do not report the sensor type. It is often redundant to the name of the sensor. - Support --legacy-output option. - For consistency to other tools, outputs of "NA" are now "N/A". - Events are now surrounded by single quotes (') instead of square brackets ([]). - Sensors that can't be read or don't exist (i.e. "N/A", "Unknown") are now *not* surrounded by single quotes (') or square brackets ([]). - Software sensors output "N/A" instead of "Unknown" now. - Globally rename "Group" to "Sensor Type" for correctness to IPMI spec. Leads to rename of --groups option to --sensor-types and --list-groups to --list-sensor-types. Backwards compatability maintained. - Support --non-abbreviated-units option to output no abbreviated units (i.e. "Amps" instead of "A"). - Support --exclude-record-ids option. - Support --exclude-sensor-types option. - Support "all" and "none" inputs for sensor-types and record-ids options. - Support --comma-separated-output option. - Support --no-header-output option. - Support --shared-sensors option. - Rename --sensors option to --record-ids. Maintain old options for backwards compatability. - Do not output Sensor Reading for discrete sensors under verbose mode (because the result is always "N/A"). - Do not output SDR event records type under verbose output, only in very verbose output. - Support sensor unit percentages, rates and modifiers (i.e. "% hit", "gigabyte per minute", "pounds / cu in"). - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - Support --entity-sensor-names option. - Support --show-sensor-type option. - Support --interpret-oem-data option. - Support Dell Poweredge R610/R710 OEM sensors. - Support Supermicro X8DTH OEM sensors. - Output allocation information with --sdr-info if available. - Output Entity ID under verbose instead of very verbose mode. - Under very verbose output, "Sensor Status" is now "Sensor Event". - Under very verbose output, if multiple sensor states are triggered, always output a prefix of "Sensor Event". - Under very verbose output, always output a prefix of "Assertion Event Enabled" or "Deassertion Event Enabled" for assertion and deassertion event listings (changed from a single "Assertion Events Enabled" or "Deassertion Events Enabled"). - Under verbose output, do not output Nominal reading, Normal Min., or Normal Max. if SDR flags do not indicate the values are specified. - Under very verbose output, output Sensor Direction. - Under very verbose output, output Tolerance. - Under very verbose output, output Resolution. - Under very verbose output, output Accuracy. - Under very verbose output, output sensor sharing information. - Under very verbose output, output entity instance type. - Under very verbose output, output OEM bytes in generic device locator records. - Output record-type names in addition to record type hex code in very-verbose output. - Output device-type names and device-modifiers in addition to hex codes in very-verbose output. - Under very verbose output, default to abbreviated units. - Output linearization in hex in verbose outputs. - Output linearization name in verbose outputs. - Output analog data format in hex in verbose outputs. - Output analog data format name in verbose outputs. - Output manufacturer name with "Manufacturer ID" if name available. - Output Entity ID string with "Entity ID" if string available. - Output hex code of sensor type in addition to type name in very-verbose output. - Re-work to use new libfreeipmi sensor-read sub library. - Support additional options in FreeIPMI config file. o ipmimonitoring - Alter output to make fields easier to read, consistent to other tools, and more consistent to IPMI (legacy output option supported). - Under default output, do not report the sensor type. It is often redundant to the name of the sensor. - "Monitoring Status" is now listed as "Sensor State" for consistency to libipmimonitoring library definition. - Sensor events are now output for all sensors. Sensor readings are only output appropriately for non-discrete sensors. - Rename a number of config fields for overall FreeIPMI consistency, may break backwards compatability. - Globally rename "Group" to "Sensor Type" for correctness to IPMI spec. Leads to rename of --groups option to --sensor-types and --list-groups to --list-sensor-types. Backwards compatability maintained. - With default output, output same sensors as listed in ipmi-sensors, including some sensors that can't be interpreted. - Support --exclude-record-ids option. - Support --exclude-sensor-types option. - Support "all" and "none" inputs for sensor-types and record-ids options. - Support --ignore-non-interpretable-sensors option. - Rename --sensors option to --record-ids. Maintain old options for backwards compatability. - Support --legacy-output option. - Remove --regenerate-sdr-cache legacy option due to conflict with newer option. - Sensors that can't be read or don't exist (i.e. "N/A", "Unknown") are now *not* surrounded by single quotes ('). - A sensor event of "NONE" is now output instead of "OK" if no sensor events are indicated. - Support --non-abbreviated-units option to output no abbreviated units (i.e. "Amps" instead of "A"). - Support --comma-separated-output option. - Support --no-header-output option. - Support --entity-sensor-names option. - Support --show-sensor-type option. - Support --interpret-oem-data option. - Support --shared-sensors option. - Utilize libipmimonitoring callback routines to make sensors output as they are read, rather than just at the end. This removes the impression that the tool "hangs" on start. - Fix inconsistency in output, header output of "Record_ID" now "Record ID". - Support additional options in FreeIPMI config file. - Removed the following short options (long options remain). - 'c' (legacy --cache-dir) o ipmi-fru - Output hex with 'h' suffix instead of '0x' prefix for consistency to other FreeIPMI tools. - Output manufacturer name with "Manufacturer ID" if name available. - Do not output string "Info Area", the text is redundant. - Very verbose support removed. - Language codes now output under verbose mode. Language code output as string instead of hex code. - Slightly alter Base/Extended Compatibility Code Mask output for common case. - Support --interpret-oem-data option. - Various output changes under error conditions. - Re-work to use new libfreeipmi fru-parse sub library. - Check for valid device ID inputs. - Support additional options in FreeIPMI config file. o ipmipower - Removed the following short options (long options remain). - 'R' (legacy --ipmi-version) - 'j' (--pulse) - 'm' (--soft) - 'g' (--on-if-off) - 'A' (--wait-until-off) - 'G' (--wait-until-on) - 't' (legacy --session-timeout) - 'y' (legacy --retransmission-timeout) - 'q' (--retransmission--wait-timeout) - 'b' (--retransmission-backoff-count) - 'i' (--ping-interval) - 'z' (--ping-timeout) - 'v' (--ping-packet-count) - 'w' (--ping-percent) - 'x' (--ping-consec-count) o ipmiconsole - Removed the following short options (long options remain). - 'c' (legacy --cipher-suite-id, 'I' support remains) o bmc-device - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - Indicate hex code output consistently with 'h' suffix instead of '0x' prefix. - Support --get-bmc-global-eanbles, --set-system-firmware-version, --set-system-name, --set-primary-operating-system-name, and --set-operating-system-name. o bmc-info - When querying active/inactive, allowed/unallowed, true/false, etc. status fields output all fields instead of only the active/allowed/true/etc. fields. - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - Output GUID by default. - Output system info by default. - Rename --guid to --get-device-guid. Legacy option still supported. - When outputting only the GUID, don't prefix "GUID : " in the output. - Support --get-system-info. - Support --get-channel-info. - Support --get-device-id. - Support --interpret-oem-data option. Do not automatically assume OEM data is correct and output by default. - Output manufacturer name with "Manufacturer ID" if name available. o ipmi-chassis - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - When querying active/inactive, allowed/unallowed, true/false, etc. status fields output all fields instead of only the active/allowed/true/etc. fields. - Output some text more consistently to IPMI specification. - Cleanup output formats. - Rename --get-status option to --get-chassis-status. Legacy option still supported. - Rename --get-capabilities option to --get-chassis-capabilities. Legacy option still supported. - Check interval input ranges. - Removed the following short options (long options remain). - 'c' (--get-chassis-capabilities) - 's' (--get-chassis-status) - 'O' (--chassis-control) - 'i' (--chassis-identify) - 'X' (legacy --set-power-restore-policy) - 'S' (legacy --set-power-cycle-interval) - 'R' (--get-system-restart-cause) - 'H' (--get-power-on-hours-counter) - 'G' (legacy --get-boot-flags) - 'L' (legacy --set-boot-flags) o ipmi-raw - Removed the following short options (long options remain). - 'f' (--file) o bmc-config - Collapse "Password20" field into "Password" field so "Password" supports both IPMI 1.5 and IPMI 2.0 length passwords. "Password20" still supported as legacy support. - Update to include new BMC Password Threshold configuration. - Support ability to report read only field error. - Support ability to report not supported field error. - Support additional options in FreeIPMI config file. o ipmi-chassis-config - Update to include new configurable boot options in IPMI errata. - Update to include new device instance selector in IPMI errata. - Support ability to report read only field error. - Support ability to report not supported field error. - Support additional options in FreeIPMI config file. o ipmi-sensors-config - Support sensor unit percentages, rates and modifiers (i.e. "% hit", "gigabyte per minute", "pounds / cu in"). - Support ability to report read only field error. - Support ability to report not supported field error. - Support additional options in FreeIPMI config file. o ipmi-pef-config/pef-config - Rename pef-config to ipmi-pef-config for consistency to other tools. Keep backwards compatability with symlinks and such. - Make output of ipmi-chassis, bmc-info, bmc-device, and info output of ipmi-sel, ipmi-sensors, and ipmi-pef-config consistent to each other. - Support ability to report read only field error. - Support ability to report not supported field error. - Support additional options in FreeIPMI config file. o ipmi-oem - Support common 'list' command to all OEM IDs. - If user does not input OEM ID, list OEM IDs and Commands. - If user does not input OEM command, list OEM commands for a particular OEM ID. - Add additional Dell OEM commands. - Add additional Inventec OEM commands. - Add additional Sun OEM commands. o bmc-watchdog - Removed the following short options. - 'h' (legacy -?) - 'H' (legacy -?) o Make init scripts LSB compliant. o Various documentation updates. Libraries --------- o libfreeipmi - Add new fru-parse sub library. - Add new sdr-parse sub library. - Add new sel-parse sub library. - Add new sensor-read sub library. - Add new dcmi sub library. - The locate sub library now uses a context style API for consistency to the rest of libfreeipmi. - Re-architect all 'unassemble' functions to return 1 if packet fully and correctly parsed, 0 if not, and -1 on error. - Support SDR sensor sharing in sdr-cache library. - Collapse all BAD_COMPLETION_CODE variant errors into single BAD_COMPLETION_CODE error. - New 'ipmi_ctx_find_inband' call to find an inband device. - New freeipmi/template/ files to document fiid fields for fiid templates. - New error code IPMI_ERR_NOT_FOUND in libfreeipmi API sub library supported. - Add a number of 'errormsg' functions so common code of foo_strerror(foo_errnum(ctx)) can be condensed to foo_errormsg(ctx). - Various API cleanup. - Return int instead of int8_t or int32_t consistently. - Pass unsigned int instead of uint32_t for buffer lengths. - Fix function naming inconsistencies. - Fix API inconsistencies. - Appropriately indicate const pointers in parameters. - Make buffers void * instead of uint8_t * consistently. - Various fixes to maintain consistency between sub library APIs. - Add IANA Enterprise Numbers definitions. - Add Entity IDs definitions. - Remove IPMI_ERR_LIBRARY_ERROR errnum. Use IPMI_ERR_INTERNAL_ERROR errnum instead. - IPMI_*CTX_ERR* renamed to IPMI_*ERR* for consistency throughout. - The fiid sub library now includes wrapper functions for a number of fiid library functions. - Suppot FIID_FIELD_MAKES_PACKET_SUFFICIENT fiid field flags and new functions. - Support ipmi_sensor_units_string utility function to support units, percentages, rates, and units modifiers (i.e. "% hit", "gigabyte per minute", "pounds / cu in"). - Properly handle int/unsigned int potential overflow conditions. - Fix several sensor units abbreviations. - More detailed KCS and SSIF debug output with header information. - Always output debug key fields (i.e. 'raw_data' from ipmi-raw) in byte array format instead of an integer even if the field length is < 64 bits. - Update various macros, fields, etc. for IPMI errata updates. - Support 'session_handle' in close session packets (IPMI errata 387). Results in API change for all close session packet calls. - Support 'device instance locator' in chassis boot configuration. Results in API change. - Support 'change_bits' flag in Set User Access. Results in API change. - Collapse v1.5 and v2.0 "Get Authentication Capabilities" templates, functions, etc. into one. Results in API change. - Collapse v1.5 and v2.0 "Set User Password" templates, functions, etc. into one. Results in API change. o libipmimonitoring - Support callback functions in API to monitor sensors as they are read/analyzed instead of after all sensors have been read/analyzed. - Support new function ipmi_monitoring_read_sensor_bitmask() to read bitmask of each sensor. - Add IPMI_MONITORING_SENSOR_BITMASK_TYPE_THRESHOLD bitmask type. - Remove IPMI_MONITORING_SENSOR_READING_TYPE_UNSIGNED_INTEGER16_BITMASK sensor reading type. Every sensor technically has a bitmask, but not all sensors have a sensor reading. - Rename IPMI_MONITORING_SENSOR_READING_FLAGS_IGNORE_UNREADABLE_SENSORS to IPMI_MONITORING_SENSOR_READING_FLAGS_IGNORE_NON_INTERPRETABLE_SENSORS. Legacy macro still supported. - Add IPMI_MONITORING_SENSOR_READING_FLAGS_INTERPRET_OEM_DATA flag. - Add IPMI_MONITORING_SENSOR_READING_FLAGS_SHARED_SENSORS flag. - Rename a number of macros for overall FreeIPMI consistency, may break backwards compatability. - Globally rename "Group" to "Sensor Type" for correctness to IPMI spec. - Update various macros, fields, config, etc. for IPMI errata updates. - Variety of API functions reworked or renamed for new functionality. Will require recompile and rework in existing code. Contributions ------------- o Update Ganglia and Nagios plugins for changes in ipmi-sensors and ipmimonitoring. 0.7.13 - 09/30/09 ----------------- o Support --platform-event in bmc-device. o Support read/clear eeprom in ipmi-oem. o Fix corner case in system firmware progress error data2 output. o Fix documentation typos. 0.7.12 - 09/08/09 ----------------- o In bmc-config, fix SOL config corner case. Assume LAN channel if SOL channel cannot be read. o In bmc-config, configure Password before Enable_User by default for security. o Add SDR reading/loading workarounds for Fujitsu RX 100 motherboards. o Add --assume-system-event-records to ipmi-sel to workaround HP DL 380 G5 motherboards. o In bmc-config, add workarounds for Dell Poweredge servers. o In ipmi-oem, support additional Dell Poweredge OEM commands. o In ipmi-oem, support additional Supermicro OEM commands. o Document workarounds necessary for newer Supermicro motherboards. o Fix several error output corner cases. 0.7.11 - 07/28/09 ----------------- o In ipmi-fru, fix FRU output corner cases. o In ipmi-oem, support Dell poweredge, Dell Xanadu2, and new Inventec OEM commands. o In ipmi-sensors and ipmimonitoring, continue reading sensors after a "request parameter not supported" error. o In libfreeipmi, support Get System Information parameters command. o Support --without-encryption build option . o Do not require execute permissions on driver devices. o Fix portability for some embedded systems. 0.7.10 - 06/16/09 ----------------- o In all tools, properly deal with workaround flags when specifying different devices than what workaround flags are intended for. o In bmc-config, fix bug setting volatile vs. non-volatile settings. o Fix in-band probing priority ordering to fix issues with machines that support multiple drivers. o In ipmi-sensors and ipmimonitoring, continue reading sensors after a "command response cannot be provided" error. o Add additional workaround handling into Sun 2.0 workaround. o In ipmimonitoring, fix sunbmc driver interface bug. o In ipmiconsole, consider IPMICONSOLE_ERR_BMC_IMPLEMENTATION a non-fatal error. o Update workaround documentation with additional motherboards. 0.7.9 - 05/15/09 ---------------- o In bmc-config, fix diff check for "Password20" field. o In ipmi-fru, fix various output typoes and output errors. - Output "Product Name" instead of "Product Product Name". - Output "FRU Chassis Type" instead of "Chassis Type". - Output "Version" instead of "Version Type". - Fix invalid DC Output and DC Load voltage outputs. mV multiplier of 10 was previously not factored in. o In ipmi-chassis, fix chassis-identify parameter parsing bug. o In ipmi-chassis, fix output corner cases. o In ipmipower, support identify-on, identify-off, identify-status in interactive mode. o In ipmipower, fix closing session corner case bug. o Update ipmi-oem manpage with extra information. o Fix bmc-device --get-mca-auxiliary-log-status bug. o Fix debug output corner case in ipmi-oem. o Fix glibc 2.8 portability bug with ipmi-raw. o Fix freeipmi.conf comment typos. 0.7.8 - 04/10/09 ---------------- o Support and document Inventec 5441 workarounds. Most notably, added "opensesspriv" workaround to tools and OPEN_SESSION_PRIVILEGE workaround to libraries. o In ipmi-fru, do not fail on invalid chassis info area type, output that type is unknown and continue to parse area. o In bmc-info, output device ID, manufacturer ID, and product ID as integers, not hex. o Fix glibc 2.8 compile bug. 0.7.7 - 04/03/09 ---------------- o Support inventec get-nic-status, set-nic-status, get-mac-address, and set-mac-address OEM commands in ipmi-oem. o Make default privilege level ADMIN for ipmi-oem. o In bmc-info, output both chars of firmware minor revision (i.e. 1.01 instead of 1.1). o Fix libfreeipmi field validity checks for sensor units. o Support "oem_reserved" group input to ipmi-sensors. o Fix Solaris porting bugs. o Fix potential config file bug by clearing out stack data appropriatly. o Support build option (--with-dont-check-for-root) to not have tools check for root for in-band IPMI communication. Permission checks are subsequently dealt with at underlying system calls and drivers. (i.e. open() on /dev/ipmi0). o Update bmc-config manpage with Dell specific workaround. o Remove "experimental" note from SUNBMC driver documentation. 0.7.7 - 04/03/09 ---------------- o Support inventec get-nic-status, set-nic-status, get-mac-address, and set-mac-address OEM commands in ipmi-oem. o Make default privilege level ADMIN for ipmi-oem. o In bmc-info, output both chars of firmware minor revision (i.e. 1.01 instead of 1.1). o Fix libfreeipmi field validity checks for sensor units. o Support "oem_reserved" group input to ipmi-sensors. o Fix Solaris porting bugs. o Fix potential config file bug by clearing out stack data appropriatly. o Support build option (--with-dont-check-for-root) to not have tools check for root for in-band IPMI communication. Permission checks are subsequently dealt with at underlying system calls and drivers. (i.e. open() on /dev/ipmi0). o Update bmc-config manpage with Dell specific workaround. o Remove "experimental" note from SUNBMC driver documentation. 0.7.6 - 02/25/09 ---------------- o In ipmimonitoring, output sensor group names consistently to other tools: "Cable Interconnect" -> "Cable/Interconnect" "Slot Connector" -> "Slot/Connector" "Module Board" -> "Module/Board" o In ipmi-sensors, don't output threshold related fields for non-threshold sensors in verbose modes. o In bmc-config, ipmi-chassis-config, ipmi-sensors, ipmi-sensors-config, ipmimonitoring, and pef-config, support --config-file option. o In ipmi-chassis-config, fix typo of "FLOOPY" to "FLOPPY". o In ipmi-sensors-config, fix event bit bug in which assertion events were configured for deassertion events. o Fix bmc-watchdog init script portability to Suse. o Update ipmi-sel manpage. 0.7.5 - 01/12/09 ---------------- o In ipmi-fru, do not output error messages for FRU entries that do not exist on a motherboard. o In ipmi-sel, fix SEL message output corner case. o In ipmi-sel, ipmi-sensors, and ipmimonitoring, check that inputted record IDs are not illegal record ID values. o In bmc-config, fix "Enable_User" checkout corner case bug. o Fix/clarify minor documentation typos/wording. 0.7.4 - 12/15/08 ---------------- o Change -I short option (for --chassis-identify) to -i in ipmi-chassis to avoid conflicting short option with -I (for --cipher-suite-id). o Support output of "" in bmc-config for fields that require a username to be configured before data may be read/written. o Support supermicro reset-intrusion OEM ID and command in ipmi-oem. o Support --list option in ipmi-oem. o Output checksum errors by default in ipmi-fru. o Fix ipmipower/ipmiconsole corner case bugs for IPMI 2.0 with certain cipher suite IDs. o Fix bmc-config Enable_User workaround bug. o Fix Intel IPMI 2.0 workarounds in all tools/libraries. o Fix state machine cycle corner case in ipmiconsole/libipmiconsole. o Fix Suse build issue in spec file. o Fix glibc 2.8 build issues. o Fix/clarify minor documentation typos/wording. 0.7.3 - 12/01/08 ---------------- o Add workaround into ipmi-sensors and ipmi-sensors-config for motherboards that do not support the Get Sensor Thresholds command. o Output 'NA' on sensors in ipmi-sensors and ipmimonitoring that have sensor scanning disabled. In libipmimonitoring, appropriately handle sensors with sensor scanning disabled and return 'unreadable sensor'. o Add the following ipmimonitoring/libipmimonitoring interpretations. Power Unit Device Installation Fan Transition Availability Power Supply State Drive Slot State Drive Slot Predictive Failure System ACPI Power State Button Switch Button Switch State Entity Presence Device Install Processor State o Fix typos in macro names and string names for sensor types to accurately coincide with IPMI specification. May lead to slightly different inputs/outputs in ipmi-sensors and pef-config. Altered strings include: "Platform Chassis Intrusion" -> "Physical Security" "Platform Security Violation" -> "Platform Security Violation Attempt" "Post Memory Resize" -> "POST Memory Resize" "System Firmware" -> "System Firmware Progress" "Button" -> "Button/Switch" "Microcontroller" -> "Microcontroller/Coprocessor" "Cable Interconnect" -> "Cable/Interconnect" "Slot Connector" -> "Slot/Connector" "ACPI Power State" -> "System ACPI Power State" "Monitor Asic" -> "Monitor ASIC/IC" o Fix ipmi-sensors non-recoverable threshold output corner case. o Fix ipmi-sensors group selection corner cases. o Fix ipmiconsole workarounds command line parse corner case. o Fix ipmi-sel/libfreeipmi event data output corner cases. o Use a reservation ID on all SEL entry operations to workaround some manufacturer compliance issues. o Fix config option names in ipmimonitoring/libipmimonitoring. o Add forgotten bitmask flags in libipmimonitoring. o In ipmi-sensors default output, output non-recoverable or non-critical thresholds if both non-critical thresholds are not available. o Remove unused libfreeipmi workaround flags/macros. Contain tool specific workaround flags within tools. o Optionally output auxiliary information in bmc-info. o Add ipmi_monitoring_sensors.conf.5 manpage. o Various documentation updates. 0.7.2 - 11/18/08 ---------------- o Add Sensor Owner ID output to verbose and very verbose output in ipmi-sensors. Alter previous ipmi-sensors output of slave address and system software id to deal with slave address/system software ID vs. sensor owner ID semantics. o Fix ipmi-raw cmdline parsing corner case. o Fix/clarify documentation. 0.7.1 - 11/07/08 ---------------- Tools - New Significant Additions/Features ------------------------------------------ o Add new tool ipmi-chassis-config for chassis configuration, such as boot device and power restore policy configuration. o Add new tool bmc-device to support advanced BMC commands including cold reset, warm reset, setting BMC times, and more. o Support FreeIPMI configuration file for most tools (bmc-config, bmc-info, bmc-device, bmc-watchdog, ipmi-chassis, ipmi-chassis-config, ipmi-fru, ipmi-oem, ipmi-raw, ipmi-sel, ipmi-sensors, ipmi-sensors-config, ipmiconsole, ipmimonitoring, ipmipower, pef-config) to avoid typing common options on the command line. See freeipmi.conf(5) for more information. o Add hostrange support to all config tools (bmc-config, pef-config, ipmi-sensors-config, ipmi-chassis-config) to support parallel configuration on a cluster. o Support --bridge-sensors in ipmi-sensors and ipmimonitoring to access non-BMC owned sensors (experimental). o Support --sensor-config-file on ipmimonitoring to support alternate interpretation rules. o Add additional "connection timeout" error message to tools to differentiate between no IPMI communication at all vs. session timeout in the middle of a command's operations. o Support hysteresis and sensor event configuration in ipmi-sensors-config. o Support additional sensor monitoring interpretations in ipmimonitoring. o Output additional sensor information in ipmi-sensors under verbose modes, such as lun, channel and event enable information. o Support --always-prefix option in most tools for easier scripting. o Support --sdr-cache-recreate in all SDR related tools for easier scripting. o Support --guid option in bmc-info to retrieve global ID (guid). o Support "SUNBMC" in-band driver for Solaris (experimental). Please see README.sunbmc for compilation instructions. Tools - Enhancements/Changes/Bug Fixes -------------------------------------- o Global in most tools - Rename --no-probing option to --disable-auto-probe for consistency in FreeIPMI. Backwards compatability maintained. o Global in config tools (bmc-config, pef-config, ipmi-sensors-config) - More carefully check for fatal vs. non-fatal errors when performing configuration. This change may result in slight behavior differences. For example, a session-timeout may have previously been considered a non-fatal error, making the config tools continue on attempting more configuration activities. Now, it would error out on the first session-timeout indication. o ipmi-sensors - Check variety of corner cases such as whether sensor readings, hysteresis, thresholds, etc. are even available before reading them. Some sensors may output slightly different information than before. For example, suppose a power supply sensor exists for a power supply that is not installed. If the sensor is enabled on the motherboard, ipmi-sensors would likely report "OK". If the sensor is disabled on the motherboard, ipmi-sensors would now likely report "NA". Previously, "OK" would have been reported under both conditions. - Output "NA" for sensors whose slave addresses are not the BMC. - Output "Unknown" for sensors whose readings cannot be determined. - Output multiple sensor status messages on separate lines, rather than all on one line under verbose modes. - Output "Unrecognized State" if the sensor specifies a state that is unrecognized. - Busy sensors are now output with "Unknown" instead of causing errors. - When fields are not relevant, do not output as much information in verbose and very verbose mode. For example, don't output hysteresis or threshold information for power supply sensors. - Alter some output ordering for consistency to IPMI spec. - Shorten/adjust some state strings for readability under non-verbose output. For example, "Fully Redundant (formerly "Redundancy Regained")" is now just "Fully Redundant". - Change default privilege from user to operator. o ipmimonitoring - Support -v verbose option to output sensors readings that aren't readable. - Check corner case for sensor readability. May lead to slightly different output in ipmimonitoring. For example, suppose a power supply sensor exists for a power supply that is not installed. If the sensor is enabled on the motherboard, ipmimonitoring would normally report "Nominal". If the sensor is disabled on the motherboard, ipmimonitoring would normally not output a sensor state (it would output "N/A" under verbose mode). Previously, "Nominal" would have been reported under both conditions. - Consider sensors without BMC slave addresses unreadable. May result in sensors not being output like before. - Busy sensors may result in sensors not being output rather than causing errors. - Output "Unrecognized State" if the sensor specifies a state that is unrecognized. - Output multiple bitmask strings if multiple bits are set. - Output "OK", similarly to ipmi-sensors when no bitmask strings are returned from a sensor reading. - Shorten/adjust some state strings for readability. For example, "Fully Redundant (formerly "Redundancy Regained")" is now just "Fully Redundant". - Change default privilege from user to operator. o ipmipower - Removed many early experimental features from ipmipower so ipmipower is more like other tools. Removed ipmi-version, cipher-suite-id, privilege-level, and authentication-type auto discovery. Removed ability to enable/disable a number of experimental features. - Changed --config to --config-file in ipmipower for consistency to other tools. Backwards compatability maintiained. - Replace --ipmi-version option with --driver-type. Backwards compatability maintained. - Removed hostname config file option. Require users to always input atleast hostname. - Changed primary config file to /etc/freeipmi.conf. Legacy config file searched for and still supported. - Prefixed config file options with 'ipmipower' for consistency to new global FreeIPMI config file. Old options still supported. o bmc-config - Support configuration of UserN:Lan_Session_Limit and UserN:Serial_Session_Limit (where N is a user id number). - By default, do not output unsupported authentication type enables when checking out the Lan_Conf_Auth section. Output unsupported authentication type enables under verbose output. - By default, do not output serial configuration parameters on checkout. Output serial configuration under verbose output. - Remove checkout of "Misc" section and "Power_Restore_Policy" field, which is now handled by ipmi-chassis-config. Backwards compatability commit and diff maintained. - Remove case sensitivity when checking a number of fields. o ipmi-chassis - Alter ipmi-chassis output to print "unknown" when field is not known. - Alter some ipmi-chassis output text to be more consistent to IPMI spec. - Hide configuration options now supported in ipmi-chassis-config. o ipmi-fru - Output FRU device names along with IDs in ipmi-fru. - Reduce excessive newline outputs in ipmi-fru. - Output more information by default. Change the output of verbose vs. very verbose output. o ipmi-sel - Change default privilege from user to operator. - Search of SDR records by sensor number and sensor owner id. - Support SEL Event Record debug dumping. o ipmiconsole - Support --session-timeout and --retransmission-timeout options. - Removed -C short option for consistency to other tools. - Removed hostname config file option. Require users to always input atleast hostname. - Changed primary config file to /etc/freeipmi.conf. Legacy config file searched for and still supported. - Prefixed config file options with 'ipmiconsole' for consistency to new global FreeIPMI config file. Old options still supported. o bmc-watchdog - Remove legacy 'v' option for version. Libraries --------- o libfreeipmi - Add additional IPMI commands. - Support new "connection timeout" error message. - Support new "command invalid for selected interface" error message. - Support ipmb bridging in KCS, OPENIPMI, LAN, and LAN_2_0 interfaces. - Check for additional corner cases in fiid API. - Support SUNBMC driver. o libipmimonitoring - Support new "connection timeout" error message. - Handle variety of corner case situations better, such as dealing with sensor readings that are unavailable. - Provide more information to user on unreadable/uninterpretable sensor readings. - Support SUNBMC driver. - Provide new IPMI_MONITORING_SENSOR_READING_FLAGS_BRIDGE_SENSORS flag. - Support several new sensor interpretation rules. - Return short message strings in ipmi_monitoring_bitmask_string(). o Various naming consistency fixes to IPMI specification. o Various minor bug fixes. Contributions ------------- o Ganglia plugin scripts ganglia_ipmimonitoring.pl and ganglia_ipmi_sensors.pl. o Nagios plugin script nagios_ipmimonitoring.pl. 0.6.10 - 10/13/08 ----------------- o Fix ipmi-fru FRU parsing corner case. 0.6.9 - 09/26/08 ---------------- o Handle ipmiconsole/libipmiconsole non-default port corner cases. o Fix --debug portability. o Document new workarounds. 0.6.8 - 09/22/08 ---------------- o Handle "invalid parameters" error codes in ipmi-sensors and ipmimonitoring/libipmimonitoring to work around some motherboards. o Fix bug in ipmimonitoring sensors configuration file parsing. o Fix corner case in libipmimonitoring sdr-cache filename creation. o Fix config tool exit code corner case. 0.6.7 - 09/11/08 ---------------- o Handle "illegal sensor" error code in ipmi-sensors and ipmimonitoring/libipmimonitoring. 0.6.6 - 08/26/08 ---------------- o Output NA/Unknown for non-BMC owned sensors in ipmi-sensors. o Do not output readings for non-BMC owned sensors in ipmimonitoring. o libfreeipmi/ipmi-chassis fix invalid console redirection input check. 0.6.5 - 08/02/08 ---------------- o Fix ipmimonitoring group assignment bug. o Fix several invalid error outputs. o Fix several minor bugs. o Minor documentation cleanup. 0.6.4 - 06/04/08 ---------------- o Do not exit ipmi-sensors or ipmimonitoring for sensors that return "sensor data not present" errors. Output "NA", "Unknown", skip sensor output, etc. as needed. o Fix bug in ipmi-sensors and ipmimonitoring when dealing with optional sensor state assertions after a sensor read. o Fix bug in ipmi-sensors and ipmimonitoring when dealing with reserved fields in sensor state assertions after a sensor read. o Add workaround in ipmi-sensors and ipmimonitoring when dealing with sensors that improperly report sensor assertions after a sensor read (i.e. no assertions set when required, or invalid assertions set). o Fix minor corner cases. o Fix manpage typos. 0.6.3 - 05/27/08 ---------------- o Fix --eliminate option in ipmipower. o Fix --quiet-cache option to work with flushing cache. o Fix ipmi-sensors-config flush cache corner case. o Fix ipmi-fru output corner case. o Fix workarounds parsing bug. o Fix/clarify various manpage text. 0.6.2 - 05/15/08 ---------------- o Fix ipmi-fru output corner cases. o Fix ipmi-chassis boot-device configuration bug. o Fix ipmiconsole config file parsing corner case. o Fix ipmipower max password length corner case check. o Fix command line parsing error messages. o Remove excess error output messages. o Add missing manpage option listings. 0.6.1 - 04/27/08 ---------------- For Users --------- o Add new tool ipmi-sensors-config. o Add new tool ipmi-oem. o Support --groups (plural) for multiple groups listing in ipmi-sensors. Older --group (non-plural) option maintained for backwards compatability. o Support --list-groups and --flush in ipmimonitoring for consistency to ipmi-sensors. o Change --cache-dir to --sdr-cache-dir in ipmimonitoring for consistency to ipmi-sensors. o Change short option -f option to -n in pef-config and bmc-config for consistency to ipmi-sensors-config. The -f option is maintained for backwards compatability. o Support -e (--escape-char) for alternate escape character in ipmiconsole. o Change --wait-until-off short option from -B to -G. o Support -B in ipmipower for consistency to other tools, although -B offers no purpose in ipmipower. o Support -F in ipmipower for consistency to other tools. o Enhanced speed of ipmi-fru, by skipping unnecessary FRU data reads. o SSIF Inband driver will timeout after a certain period of time. o Support additional sensor monitoring interpretations in ipmimonitoring. o Provide more detailed error messages in config tools. o Support shared SDR caches for ipmi-sensors, ipmi-fru, ipmi-sel, ipmi-sensors-config, and ipmimonitoring. (libipmimonitoring will still use a different default cache directory.) This will require a new cache generation for these tools. o Support driver-type options for ipmipower ipmi version option. o Modified SDR caching output messages in ipmi-sensors, ipmi-sel, ipmi-fru, ipmi-sensors-config and ipmimonitoring to provide more useful information. o In ipmi-sensors, updated SDR output under verbose and very verbose output modes with: o More IPMI compliant field names. For example, 'Sensor Name' has been replaced with 'ID String'. o More correct output. For example, 'NA' will be output instead of '0.0' when a value is not truly available. Fields that don't exist will not have a default output. o Fix incorrect hysterisis calculation and output. o Fix incorrect OEM data output. o Support more SDR record types for output. o Output more SDR record information in general. o Added new freeipmi(7) and libfreeipmi(3) manpages. o Various other bug fixes, documentation fixes, and enhancements. For Developers -------------- o Many libfreeipmi API changes. Not counting specific tool changes listed above, these API changes should not affect FreeIPMI user tools. o locate/probing API revamped. o SMIC driver/api removed. o 'udm' renamed to 'api' globally. o 'ipmi_device_t' device context renamed to 'ipmi_ctx_t'. o New sdr-caching library added. o Code re-organized into subdirectories. o New header files for more ipmi spec subsections added. o Support new 'ipmi_monitoring_sdr_cache_filenames' function in libipmimonitoring. o Support IPMI_MONITORING_SENSOR_UNITS_WATTS sensor units in libipmimonitoring. o Store SDR with different format for ipmi-sensors, ipmi-fru, ipmi-sel, and ipmi-sensors-config, ipmimonitoring/libipmimonitoring for easier future extensibility. o Packet names added to IPMI dump outputs in all tools for easier packet identification in debugging. o Make IPMI dump outputs consistent across all tools. o Support driver timeout error codes in all drivers and APIs. o SDR record dumping added into all tools. o Various other bug fixes and enhancements. 0.5.6 - 03/27/08 ---------------- o Fix bmc-watchdog probing corner case. o Fix bmc-watchdog openipmi corner case. 0.5.5 - 02/25/08 ---------------- o Fix bmc-info firmware and IPMI version output. o Fix Sun endian bug workaround. o Fix FRU data output corner cases. o Fix workaround documentation. 0.5.4 - 02/07/08 ---------------- o Output addresses in hex in ipmi-locate. o Clarify device addresses in manpages. o Support --ignore-sdr-cache option in ipmi-sel and ipmi-fru. o Minor SDR caching bug fixes. o Minor ipmimonitoring corner case fixes. o Various SSIF corner case fixes. 0.5.3 - 01/02/08 ---------------- o Fix minor ipmimonitoring command line option combination bugs. o Fix several minor corner cases in ipmi-sel, ipmi-sensors, and ipmimonitoring. o Fix corner case in all tools by recognizing 127.0.0.1 as the same as localhost. o Fix documentation/manpage text/typos. 0.5.2 - 12/21/07 ---------------- o Clarify "Password Verification Timeout" troubleshooting information. o Fix ipmipower cmdline parse bug. o Support suffixes in hostrange inputs. 0.5.1 - 12/07/07 ---------------- For Users --------- o Added previously missing IPMI 2.0 (-D LAN_2_0) support into ipmi-chassis, ipmi-fru, ipmi-sensors, ipmi-sel, ipmi-raw, and ipmimonitoring. o Added more strict IPMI over LAN implementation into ipmi-chassis, ipmi-fru, ipmi-sensors, ipmi-sel, ipmi-raw, and ipmimonitoring. o OpenIPMI and KCS Inband drivers will timeout after a certain period of time, so tools will no longer hang if the BMC is non-functional. o Ported IPMI compliance workarounds from ipmipower, ipmiconsole, and ipmimonitoring into ipmi-chassis, ipmi-fru, ipmi-sensors, ipmi-sel, and ipmi-raw. o Updated all manpages with more instructions, information, examples, and trouble shooting tips. o Support --debug option under the non-debug builds. o Rewrote error messages to provide more accurate descriptions. o Removed CALLBACK and OEM privilege capabilities in most tools. o Removed the quiet and silent options from bmc-config. o Added openipmi driver to bmc-watchdog. o Added keypair command line support to pef-config. o Removed bmc-autoconfig tool. o Added more details comments and instructions to bmc-config checkout. o Converted ipmiconsole, ipmipower, and ipmimonitoring to use argp instead of getopt for consistency of usage output. o Re-word "ASUS 2.0" workaround into generic "IGNORE SOL PAYLOAD SIZE" workaround. o Support new "IGNORE SOL PORT" workaround. o Made many command line options, interactive prompt, and config file options consistent across FreeIPMI tools. Inconsistencies between dashes and underscores have been fixed in a number of places. Backwards compatability has been maintained when possible. Notable changes include: o --priv-level and --privilege options are now --privilege-level. o --auth-type options are now --authentication-type. o --reg-space or --register-space options are now --register-spacing. o --hostnames (plural) is now --hostname (not-plural). o --timeout is now --session-timeout. o --retry is now --retransmission. o All tools now use -W (--workarounds) to specify workarounds. o The "plain" authentication type is now the "straight_password_key" authentication type. o The short option -r for --register-spacing has been removed for consistency with other command line options. o Short options for most debugging options have been removed. o All -H and -h (help) options have been changed to -? for consistency in all tools. o All -v (version) options have been changed to -V for consistency with all tools. o The -T option and -I option in ipmipower have been flipped for consistency with other tools. o The -c option in ipmiconsole is now the -I option for consistency with other tools. o Short option -I changed to -D in bmc-watchdog for consistency with other tools. o The -i option in bmc-config is now the -c option. o The -k option in bmc-config and pef-config is now the -e option. o Various other minor bug fixes and enhancements. For Developers -------------- o Added IPMI 2.0 into UDM. o Added workaround support into UDM for IPMI 1.5 and IPMI 2.0. o Added IPMI 2.0 into the libipmimonitoring API. o Added scalability fixes into libipmiconsole for Conman. o Fix various library variable names and macros for consistency. Notable changes. 1) ipmi_ver_minor and ipmi_ver_major in struct ipmi_locate_info have been renamed to ipmi_version_minor and ipmi_version_major. 2) reg_space/register_space have been renamed to register_spacing globally. 3) privilege has been replaced to privilege_level globally. 4) Various library error codes have been renamed for consistency for error codes in other libraries. For example OUTMEM has been changed to OUT_OF_MEMORY globally. 5) Various error codes and messages have been renamed/redone to give more useful information. For example, IPMI_ERR_PRIVILEGE is now IPMI_ERR_PRIVILEGE_LEVEL_CANNOT_BE_OBTAINED and the error message has been updated appropriately. o Various bug fixes and enhancements. 0.4.6 - 10/11/07 ---------------- o Fix sdr cache corruption bug. 0.4.5 - 10/02/07 ---------------- o Fix command line parse issue in ipmidetect. o Fix rpm daemon install scripts for ipmidetectd. 0.4.4 - 09/19/07 ---------------- o Alter userncame-capabilities workaround to authentication-capabilities workaronds to cover more situations. o Fix libipmiconsole new console port corner case. o Fix manpage typos. 0.4.3 - 08/14/07 ---------------- o Add ASUS P5M2 workarounds in ipmipower, ipmiconsole, and ipmimonitoring. o Fix bad input assert corner cases. o Fix non-default install bug. o Fix range check in bmc-config SOL config that was inconsistent with IPMI spec. o Fix ipmipower config file logic bug. o Fix ipmipower config output logic bug. o Fix potential pre-processor compile bug. o Fix manpage typos. o Fix error output messages in bmc-config. o Fix legacy config option issues. o Fix usage help in ipmiconsole. 0.4.2 - 08/02/07 ---------------- o ipmimonitoring: Fixed free bug that can cause segfaults. o Fix SLES packaging issue. 0.4.1 - 07/26/07 ---------------- For Users --------- o Added hostrange support to ipmi-sensors, ipmi-sel, ipmi-raw, and bmc-info o Added ipmimonitoring o Added ipmidetect o Added pef-config o Added ipmi-chassis o Added ipmi-fru o Added -T option to ipmiconsole. o Re-architected workarounds options for Ipmipower due to increasing number of vendor specific workarounds implemented. -W, -S, -Z, -X, -Y options removed. New -W option implemented. o Adjust ipmipower options to follow hostrange convention of other tools. o -Q option added for ipmi-sensors and ipmi-sel. o -q option added for ipmi-sensors. o Add verbose checkout/commit progress information for large checkout(s)/commit(s). o Add sensor names to ipmi-sel output when possible. o Output more descriptive error messages in most FreeIPMI tools. o '0x' parsing support in ipmi-raw. o Sun IPMI 2.0 workarounds in ipmipower and ipmiconsole. o Various bug fixes throughout FreeIPMI. For Developers -------------- o Added SDR debugging capabilities to ipmi-sdr and ipmi-sensors. o Added libipmimonitoring o Added libipmidetect o Additional IPMI sub section support in libfreeipmi. o Re-architected UDM for more descriptive error codes. o Various bug fixes/performance fixes to libipmiconsole, libfreeipmi. 0.3.3 - 05/05/07 ---------------- o Support per-msg-auth in LAN udm and majority of FreeIPMI tools. o Support hex k-g input/output. o Fix ipmipower per-msg-auth. o Fix ipmiconsole k_g key corner case. o Fix libipmiconsole state machine corner case. o Fix OpenIPMI driver build bug. o Fix strdup corner case in bmc-config. o Allow OEM network functions. 0.3.2 - 03/29/07 ---------------- o -N option added to ipmiconsole. o -L option added to ipmiconsole. o -K option added to ipmipower and ipmiconsole. o -P option replaced w/ -W option in ipmipower. o -P option added to most tools. o Fix seg-fault in ipmiconsole. o Fix various bugs in in libipmiconsole and ipmiconsole. o Fix secure malloc bug. 0.3.1 - 12/18/06 ---------------- o FreeBSD Support o libfreeipmi: Header file include/C++ fixes. o ipmi-sensors, ipmi-sel: Fix SDR cache creation bug for /tmp. o ipmi-sensors: Fix SDR parsing corner case bugs. o ipmipower, ipmiconsole: Fix mem-leak possibility. 0.3.0 - 11/13/06 ---------------- For Users --------- o Added ipmiconsole. o IPMI 2.0 connection support added to ipmipower. o IPMI 2.0 ping support added to ipmiping. o IPMI 2.0 and Serial-Over-LAN (SOL) configuration added to bmc-config. o Added sectional input/output support to bmc-config (--listsections and --section options). o Added OpenIPMI driver support to bmc-info, ipmi-raw, ipmi-sel, ipmi-sensors. o ipmi-raw raw input/output style change to support luns and network functions. o bmc-info, ipmi-raw, ipmi-sel, ipmi-sensors out-of-band communication made more reliable. o Sensor reading added to ipmi-sel for better output o Intel 2.0 workarounds added to ipmipower. o Supermicro 2.0 workarounds added to ipmipower. o --wait-until-on, --wait-until-off, --retry-wait-timeout options added to ipmipower. o --delete-range option added to ipmi-sel o --flush-cache option added to ipmi-sel. o --sdr-cache-directory option added to ipmi-sel and ipmi-sensors. o Removed fish o Removed garpd o Various bug fixes throughout FreeIPMI. For Developers -------------- o IPMI 2.0 support added to libfreeipmi. o Added libipmiconsole. o ipmi-sensors, ipmi-sel, and bmc-config re-written in C. o Added OpenIPMI driver support to libfreeipmi. o Libfreeipmi Fiid interface re-implemented. o Libfreeipmi code significantly cleaned up. o In debug mode, packet dump, function trace, and various debugging added to libfreeipmi. --=-QFXvZx7gsPVKDCx8vOz2-- From MAILER-DAEMON Thu Oct 08 17:12:19 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mw0Ha-00066L-IR for mharc-freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:12:18 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mw0HV-00062O-Um for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:12:14 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mw0HP-0005uK-K7 for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:12:11 -0400 Received: from [199.232.76.173] (port=46121 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mw0HO-0005tr-Mq for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:12:06 -0400 Received: from gwnew.niksun.com ([65.115.46.162]:62069 helo=anuket.mj.niksun.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mw0HO-0008AZ-C4 for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:12:06 -0400 Received: from mgc105803 (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id n98LC2Rl045165 for ; Thu, 8 Oct 2009 17:12:02 -0400 (EDT) (envelope-from aray@niksun.com) Message-Id: <200910082112.n98LC2Rl045165@anuket.mj.niksun.com> From: "Ashish Ray" To: Date: Thu, 8 Oct 2009 17:12:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 Thread-Index: AcpIW/rkPx99hXwgRW6hDQJYyPPemQ== X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: clamav-milter 0.95 at anuket.mj.niksun.com X-Virus-Status: Clean X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Subject: [Freeipmi-users] Ipmi-sensors threshold values X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Oct 2009 21:12:14 -0000 I have inte'l SR2500 server running with freeipmi-0.3.1. I see ipmi-sensor output as "At or Below (<=) Lower Critical Thre shold" even the actual RPM is greater than threshold. Can someone please explain why it so .. Thanks, Ashish /usr/local/sbin/ipmi-sensors 13: Fan 1 (Fan): 8299.00 RPM (1720.00/NA): [OK] 14: Fan 2 (Fan): 9030.00 RPM (1720.00/NA): [At or Below (<=) Lower Critical Thre shold] 15: Fan 3 (Fan): 7955.00 RPM (1720.00/NA): [OK] 16: Fan 4 (Fan): 8901.00 RPM (1720.00/NA): [OK] 17: Fan 5 (Fan): 10478.00 RPM (2046.00/NA): [OK] 18: Fan 6 (Fan): 9672.00 RPM (2046.00/NA): [OK] From MAILER-DAEMON Thu Oct 08 17:37:39 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mw0g7-0002SH-3D for mharc-freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:37:39 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mw0g5-0002Qj-47 for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:37:37 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mw0fz-0002Lg-7s for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:37:35 -0400 Received: from [199.232.76.173] (port=34380 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mw0fy-0002LK-OM for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:37:30 -0400 Received: from nspiron-3.llnl.gov ([128.115.41.83]:55099 helo=smtp.llnl.gov) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1Mw0fy-0003AK-Db for freeipmi-users@gnu.org; Thu, 08 Oct 2009 17:37:30 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by smtp.llnl.gov with ESMTP; 08 Oct 2009 14:37:27 -0700 Subject: Re: [Freeipmi-users] Ipmi-sensors threshold values From: Al Chu To: Ashish Ray In-Reply-To: <200910082112.n98LC2Rl045165@anuket.mj.niksun.com> References: <200910082112.n98LC2Rl045165@anuket.mj.niksun.com> Content-Type: text/plain Date: Thu, 08 Oct 2009 14:37:27 -0700 Message-Id: <1255037847.3074.52.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Oct 2009 21:37:37 -0000 Hi Ashish, On Thu, 2009-10-08 at 17:12 -0400, Ashish Ray wrote: > 14: Fan 2 (Fan): 9030.00 RPM (1720.00/NA): [At or Below (<=) Lower > Critical Thre shold] (Note: 0.3.1 is quite old. I believe my statements are valid for the 0.3.1 release, but it's a release from quite some time ago, so maybe the code changed significantly.) If I had to bet there, may be a bug on your motherboard. The "At or below lower critical threshold" comes directly from the sensor. So if I had to guess: A) the 1720 rpm threshold listed by the sensor is invalid. B) the sensor indicating the "At or below lower critical threshold" flag is invalid. Any chance you could update your copy FreeIPMI and run w/ --debug? I can give you additional information if you can. Al -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Thu Oct 08 18:04:06 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1Mw15i-0007M6-A1 for mharc-freeipmi-users@gnu.org; Thu, 08 Oct 2009 18:04:06 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Mw15g-0007KC-4j for freeipmi-users@gnu.org; Thu, 08 Oct 2009 18:04:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Mw15b-0007GX-CZ for freeipmi-users@gnu.org; Thu, 08 Oct 2009 18:04:03 -0400 Received: from [199.232.76.173] (port=35486 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Mw15b-0007GB-55 for freeipmi-users@gnu.org; Thu, 08 Oct 2009 18:03:59 -0400 Received: from gwnew.niksun.com ([65.115.46.162]:62377 helo=anuket.mj.niksun.com) by monty-python.gnu.org with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1Mw15a-0007Ed-IY for freeipmi-users@gnu.org; Thu, 08 Oct 2009 18:03:58 -0400 Received: from mgc105803 (anuket [10.70.0.5]) by anuket.mj.niksun.com (8.13.6/8.13.6) with ESMTP id n98M3vYl049702; Thu, 8 Oct 2009 18:03:57 -0400 (EDT) (envelope-from aray@niksun.com) Message-Id: <200910082203.n98M3vYl049702@anuket.mj.niksun.com> From: "Ashish Ray" To: Subject: RE: [Freeipmi-users] Ipmi-sensors threshold values Date: Thu, 8 Oct 2009 18:03:57 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Mailer: Microsoft Office Outlook, Build 11.0.5510 In-reply-to: <1255037847.3074.52.camel@auk31.llnl.gov> Thread-Index: AcpIX45NVptiyU63TNS+Jmq42+AnBgAAjt+g X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1106 X-Virus-Scanned: clamav-milter 0.95 at anuket.mj.niksun.com X-Virus-Status: Clean X-detected-operating-system: by monty-python.gnu.org: FreeBSD 6.x (1) Cc: freeipmi-users@gnu.org, 'Viet Le' X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Oct 2009 22:04:04 -0000 Thanks Al. It seems that MB sensor flag is invalid. A different system (SR2500) is showing the correct value. 13: Fan 1 (Fan): 6450.00 RPM (1720.00/NA): [OK] 14: Fan 2 (Fan): 7009.00 RPM (1720.00/NA): [OK] 15: Fan 3 (Fan): 6364.00 RPM (1720.00/NA): [OK] 16: Fan 4 (Fan): 6837.00 RPM (1720.00/NA): [OK] 17: Fan 5 (Fan): 9176.00 RPM (2046.00/NA): [OK] 18: Fan 6 (Fan): 8060.00 RPM (2046.00/NA): [OK] 19: PS1 AC Current (Current): 2.60 A (NA/11.90): [OK] Thanks aray > -----Original Message----- > From: Al Chu [mailto:chu11@llnl.gov] > Sent: Thursday, October 08, 2009 5:37 PM > To: Ashish Ray > Cc: freeipmi-users@gnu.org > Subject: Re: [Freeipmi-users] Ipmi-sensors threshold values > > Hi Ashish, > > On Thu, 2009-10-08 at 17:12 -0400, Ashish Ray wrote: > > 14: Fan 2 (Fan): 9030.00 RPM (1720.00/NA): [At or Below (<=) Lower > > Critical Thre shold] > > (Note: 0.3.1 is quite old. I believe my statements are valid for the > 0.3.1 release, but it's a release from quite some time ago, > so maybe the code changed significantly.) > > If I had to bet there, may be a bug on your motherboard. The > "At or below lower critical threshold" comes directly from > the sensor. So if I had to guess: > > A) the 1720 rpm threshold listed by the sensor is invalid. > > B) the sensor indicating the "At or below lower critical > threshold" flag is invalid. > > Any chance you could update your copy FreeIPMI and run w/ > --debug? I can give you additional information if you can. since it is integrated with other software we can't upgrated to newer ver. > > Al > > -- > Albert Chu > chu11@llnl.gov > Computer Scientist > High Performance Systems Division > Lawrence Livermore National Laboratory > From MAILER-DAEMON Tue Oct 13 17:44:17 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MxpAH-0003EK-45 for mharc-freeipmi-users@gnu.org; Tue, 13 Oct 2009 17:44:17 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MxpAF-0003Dk-OV for freeipmi-users@gnu.org; Tue, 13 Oct 2009 17:44:15 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MxpAA-00039k-Tx for freeipmi-users@gnu.org; Tue, 13 Oct 2009 17:44:15 -0400 Received: from [199.232.76.173] (port=41802 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MxpA5-00034b-Hk; Tue, 13 Oct 2009 17:44:05 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:26227) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MxpA5-0004EV-6x; Tue, 13 Oct 2009 17:44:05 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 13 Oct 2009 14:44:03 -0700 From: Al Chu To: freeipmi-devel@gnu.org, freeipmi-users@gnu.org In-Reply-To: <1254774950.20077.168.camel@auk31.llnl.gov> References: <1254774950.20077.168.camel@auk31.llnl.gov> Content-Type: text/plain Date: Tue, 13 Oct 2009 14:44:03 -0700 Message-Id: <1255470243.3074.140.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: Subject: [Freeipmi-users] Re: [Freeipmi-devel] FreeIPMI 0.8.0 Beta2 - Feedback Request X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 13 Oct 2009 21:44:15 -0000 Hi everyone, I've put up a beta2 release here: http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta2.tar.gz Changes from beta 1: I've modified the ipmi-sel output so there are only 2 levels of verbosity (former level 1 verbosity is now default). Fixed some output corner cases. Added --tail to ipmi-sel. Fixed a shared sensors corner case. Al On Mon, 2009-10-05 at 13:35 -0700, Al Chu wrote: > Hi everyone, > > I've put up a beta release of FreeIPMI 0.8.1.beta1 here: > > http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta1.tar.gz > > I'd appreciate any testing, input, etc. from people. There are a few > feature changes that I would like to get some input on. I am open to > changing, reverting, or adjusting based on user input. Attached to the > e-mail is the official NEWS release that lists all the changes in > glorious detail. > > New ipmi-sensors/ipmi-sel/ipmimonitoring default output: > -------------------------------------------------------- > > The default output of ipmi-sensors, ipmi-sel, and ipmimonitoring has > been modified for easier readability and consistency to each other. > Some information is not output but by default anymore and is available > through new options or increased verbosity. A variety of new options > are available for alternate outputs too. > > A) Do people like the new output format? Is it easier to read (which is > my primary goal)? > > B) Are there any options like --entity-sensor-names, > --no-sensor-type-output, --non-abbreviated-units, etc. that people think > should be default rather than an option? > > C) Is there an output that should be default instead, or have an option > to give an alternate output? > > D) Does the --legacy-output option not fully maintain backwards > compatability and break anybody's scripts?? > > Things I would appreciate testing on > ------------------------------------ > > I'd appreciate people trying them out on their systems to make sure > everything still outputs fine and I make any new corner cases. I'm > particularly interested in ensuring I didn't break: > > A) The --bridge-sensors options on ipmi-sensors and ipmimonitoring > > B) Multirecords outputs on ipmi-fru. > > C) Workarounds, most notably the Intel workarounds > > D) The new ipmi-dcmi tool, which I have not been able to fully vet due > to lack of a system. > > Any feedback would be appreciated before I release. > > Thanks, > Al > > > _______________________________________________ > Freeipmi-devel mailing list > Freeipmi-devel@gnu.org > http://lists.gnu.org/mailman/listinfo/freeipmi-devel -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Wed Oct 14 11:53:24 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1My6AG-0003OA-Mr for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 11:53:24 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1My6AE-0003Kr-B3 for freeipmi-users@gnu.org; Wed, 14 Oct 2009 11:53:22 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1My6A9-0003EQ-9J for freeipmi-users@gnu.org; Wed, 14 Oct 2009 11:53:21 -0400 Received: from [199.232.76.173] (port=40155 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1My6A9-0003ED-3D for freeipmi-users@gnu.org; Wed, 14 Oct 2009 11:53:17 -0400 Received: from mail-vw0-f187.google.com ([209.85.212.187]:48220) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1My6A8-0008Sc-MO for freeipmi-users@gnu.org; Wed, 14 Oct 2009 11:53:16 -0400 Received: by vws17 with SMTP id 17so2883777vws.24 for ; Wed, 14 Oct 2009 08:53:15 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=0EIovJwBCpwelQ/5LKUd7iArsz8DmJWk+ddLj6XOONI=; b=bUcjEAjn4pFSB7H7DVSzxRA1/hZuCwc960uBciRcYOxJCcQY/9DSlnIqQTzCdhpEAg +w/SYfi00Rimn2DjFIFqtCcBYwIBB/EdpVUMHQ+Xn0ic2Q/Artxz6lZTknUIvYUCb7Gl 5HBCe/uybdSCNXgayS2TPhqGb9pExM/DQMXro= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=iyeAXOr8g0BmoxY/PLc8hu2hbMvTFBMNpDo/sUuHA7uI7nyHJD3r5Trut1RCFHAIJR BOgqrKTYcTLUF0aw+Y9avVPozx8aidDvVkFCLjM/p2Aig0SUbdHuJIftdAT4Z0Kxn74T Yr5pyCLeg7zNZherwhn0C10libKtzBQFiOqYI= MIME-Version: 1.0 Received: by 10.220.104.212 with SMTP id q20mr12926429vco.107.1255535595293; Wed, 14 Oct 2009 08:53:15 -0700 (PDT) Date: Wed, 14 Oct 2009 11:53:15 -0400 Message-ID: From: Chris Harwell To: freeipmi-users@gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) Subject: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 15:53:22 -0000 Greetings freeipmi users, I've really enjoyed using freeipmi - it is a great tool. I particularly like how the host range syntax works and simplifies certain tasks. I've recently run into a case where freeipmi fails and hope you can offer some help or advice. This fails: ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output --quiet-readings also where the second number is 319 fails. These invocations work: ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output --quiet-readings ipmi-sensors -g Fan -h xxxx[0001-319]-lom ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings when it fails the output looks like this: $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output --quiet-readings pstdout_launch: unknown internal error I encounter this in the several versions I could check quickly 0.6.5, 0.7.12 and 0.7.13: :bin$ ipmi-sensors -V ipmi-sensors - 0.7.13 Copyright (C) 2003-2008 FreeIPMI Core Team This program is free software; you may redistribute it under the terms of the GNU General Public License. This program has absolutely no warranty. drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p ADMIN --consolidate-output --quiet-readings pstdout_launch: unknown internal error debug output is copious, the last bit looks like this: xxxx0317-lom: IPMI Command Data: xxxx0317-lom: ------------------ xxxx0317-lom: [ 3Ch] = cmd[ 8b] xxxx0317-lom: [ 0h] = comp_code[ 8b] xxxx0317-lom: IPMI Trailer: xxxx0317-lom: -------------- xxxx0317-lom: [ 23h] = checksum2[ 8b] pstdout_launch: unknown internal error Please advise - am I running into a known limitation or just using this wrong? Is there other information I ought to provide? Thanks in advance, Chris Harwell From MAILER-DAEMON Wed Oct 14 12:41:36 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1My6ut-0001Og-Ua for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:41:35 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1My6us-0001Lg-4X for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:41:34 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1My6un-0001E3-2E for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:41:33 -0400 Received: from [199.232.76.173] (port=60675 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1My6um-0001Dn-SP for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:41:28 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:60820) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1My6um-0008DR-Ek for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:41:28 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 14 Oct 2009 09:41:27 -0700 From: Al Chu To: Moerman Nicolas In-Reply-To: <66F68487BF0EED4BA7D767E2410F30B38C6C5287F4@FRSPX100.fr01.awl.atosorigin.net> References: <66F68487BF0EED4BA7D767E2410F30B38C6C5287F4@FRSPX100.fr01.awl.atosorigin.net> Content-Type: text/plain; charset=UTF-8 Date: Wed, 14 Oct 2009 09:41:26 -0700 Message-Id: <1255538486.3074.147.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 8bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org Subject: [Freeipmi-users] Re: [FreeIPMI] default bmc X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 16:41:34 -0000 Hey Nicolas, I don't believe there is a IPMI standard way to reset the BMC back to the manufacturer defaults. A few vendors have OEM extensions to allow for this. In ipmi-oem, I currently support it for Dell Poweredge motherboards, but that's it. If you can bug your manufacturer for an OEM extension, we can add it to ipmi-oem. Al On Wed, 2009-10-14 at 16:51 +0200, Moerman Nicolas wrote: > Hi Al, > > > > I'm looking to reset to default all bmc settings (IP, users, pef > filter, … > > Is there a way to do that. > > I tryed bmc-device --warm/cold-reset but I don't understand very well > the result (only the Alert_Policy is reset). > > > > Regards > > > > ______________________________________________________________________________ > > Nicolas MOERMAN > > Technical Operations > > Tel : +33 (0)3 20 60 79 48 > > > ATOS WORLDLINE > Z.I A Rue dela Pointe 59113 SECLIN > > www.*atosworldline.com > > Atos Worldline is an Atos Origin Company: www.*atosorigin.com > > > > > > > > > > > ______________________________________________________________________ > > Ce message et les pièces jointes sont confidentiels et réservés à > l'usage exclusif de ses destinataires. Il peut également être protégé > par le secret professionnel. Si vous recevez ce message par erreur, > merci d'en avertir immédiatement l'expéditeur et de le détruire. > L'intégrité du message ne pouvant être assurée sur Internet, la > responsabilité du groupe Atos Origin ne pourra être recherchée quant > au contenu de ce message. Bien que les meilleurs efforts soient faits > pour maintenir cette transmission exempte de tout virus, l'expéditeur > ne donne aucune garantie à cet égard et sa responsabilité ne saurait > être recherchée pour tout dommage résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy > it. As its integrity cannot be secured on the Internet, the Atos > Origin group liability cannot be triggered for the message content. > Although the sender endeavours to maintain a computer virus-free > network, the sender does not warrant that this transmission is > virus-free and will not be liable for any damages resulting from any > virus transmitted. -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Wed Oct 14 12:43:37 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1My6wr-0004Ig-3o for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:43:37 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1My6wp-0004GN-KQ for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:43:35 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1My6wk-0004Al-Ul for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:43:35 -0400 Received: from [199.232.76.173] (port=49764 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1My6wk-0004AX-P0 for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:43:30 -0400 Received: from nspiron-2.llnl.gov ([128.115.41.82]:56296) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1My6wk-0008WH-AJ for freeipmi-users@gnu.org; Wed, 14 Oct 2009 12:43:30 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-2.llnl.gov with ESMTP; 14 Oct 2009 09:43:29 -0700 Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Al Chu To: Chris Harwell In-Reply-To: References: Content-Type: text/plain Date: Wed, 14 Oct 2009 09:43:28 -0700 Message-Id: <1255538608.3074.150.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 16:43:35 -0000 Hey Chris, On Wed, 2009-10-14 at 11:53 -0400, Chris Harwell wrote: > Greetings freeipmi users, > > I've really enjoyed using freeipmi - it is a great tool. I > particularly like how the host range syntax works and simplifies > certain tasks. Thanks. > I've recently run into a case where freeipmi fails and hope you can > offer some help or advice. > > This fails: > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > --quiet-readings > also where the second number is 319 fails. > > These invocations work: > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > --quiet-readings > ipmi-sensors -g Fan -h xxxx[0001-319]-lom > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings > > when it fails the output looks like this: > $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > --quiet-readings > pstdout_launch: unknown internal error > > I encounter this in the several versions I could check quickly 0.6.5, > 0.7.12 and 0.7.13: > :bin$ ipmi-sensors -V > ipmi-sensors - 0.7.13 > Copyright (C) 2003-2008 FreeIPMI Core Team > This program is free software; you may redistribute it under the terms of > the GNU General Public License. This program has absolutely no warranty. > drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p > ADMIN --consolidate-output --quiet-readings > pstdout_launch: unknown internal error > > debug output is copious, the last bit looks like this: > xxxx0317-lom: IPMI Command Data: > xxxx0317-lom: ------------------ > xxxx0317-lom: [ 3Ch] = cmd[ 8b] > xxxx0317-lom: [ 0h] = comp_code[ 8b] > xxxx0317-lom: IPMI Trailer: > xxxx0317-lom: -------------- > xxxx0317-lom: [ 23h] = checksum2[ 8b] > pstdout_launch: unknown internal error > > Please advise - am I running into a known limitation or just using > this wrong? Is there other information I ought to provide? In all liklihood there is some corner case in the hostrange parsing. I'll take a look into it and get back to you if I need any more info. Thanks, Al > Thanks in advance, > Chris Harwell > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@gnu.org > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Wed Oct 14 13:41:53 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1My7rF-000706-Qi for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 13:41:53 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1My7rD-0006yf-Tg for freeipmi-users@gnu.org; Wed, 14 Oct 2009 13:41:51 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1My7r9-0006uG-0U for freeipmi-users@gnu.org; Wed, 14 Oct 2009 13:41:51 -0400 Received: from [199.232.76.173] (port=57831 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1My7r8-0006u3-Pb for freeipmi-users@gnu.org; Wed, 14 Oct 2009 13:41:46 -0400 Received: from nspiron-3.llnl.gov ([128.115.41.83]:4020 helo=smtp.llnl.gov) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1My7r8-0000lR-Ev for freeipmi-users@gnu.org; Wed, 14 Oct 2009 13:41:46 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by smtp.llnl.gov with ESMTP; 14 Oct 2009 10:41:45 -0700 Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Al Chu To: Chris Harwell In-Reply-To: <1255538608.3074.150.camel@auk31.llnl.gov> References: <1255538608.3074.150.camel@auk31.llnl.gov> Content-Type: text/plain Date: Wed, 14 Oct 2009 10:41:44 -0700 Message-Id: <1255542104.3594.9.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 17:41:52 -0000 Hey Chris, I've reproduced this problem in the underlying hostlist library. I'm working with the maintainer of the library to figure out if there is a bug or if there is a hostrange assumption issue. I noticed your range input was: 0001-319 which internally in hostlist will lead to 0001-0319 Is your intent for xxxx[0001-319] to lead to xxxx0318, xxx0319, etc.? Inputting the later also seems to cause an error, so there probably is a bug somewhere, may it be an input checking bug or an output bug. Al On Wed, 2009-10-14 at 09:43 -0700, Al Chu wrote: > Hey Chris, > > On Wed, 2009-10-14 at 11:53 -0400, Chris Harwell wrote: > > Greetings freeipmi users, > > > > I've really enjoyed using freeipmi - it is a great tool. I > > particularly like how the host range syntax works and simplifies > > certain tasks. > > Thanks. > > > I've recently run into a case where freeipmi fails and hope you can > > offer some help or advice. > > > > This fails: > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > --quiet-readings > > also where the second number is 319 fails. > > > > These invocations work: > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > --quiet-readings > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings > > > > when it fails the output looks like this: > > $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > --quiet-readings > > pstdout_launch: unknown internal error > > > > I encounter this in the several versions I could check quickly 0.6.5, > > 0.7.12 and 0.7.13: > > :bin$ ipmi-sensors -V > > ipmi-sensors - 0.7.13 > > Copyright (C) 2003-2008 FreeIPMI Core Team > > This program is free software; you may redistribute it under the terms of > > the GNU General Public License. This program has absolutely no warranty. > > drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p > > ADMIN --consolidate-output --quiet-readings > > pstdout_launch: unknown internal error > > > > debug output is copious, the last bit looks like this: > > xxxx0317-lom: IPMI Command Data: > > xxxx0317-lom: ------------------ > > xxxx0317-lom: [ 3Ch] = cmd[ 8b] > > xxxx0317-lom: [ 0h] = comp_code[ 8b] > > xxxx0317-lom: IPMI Trailer: > > xxxx0317-lom: -------------- > > xxxx0317-lom: [ 23h] = checksum2[ 8b] > > pstdout_launch: unknown internal error > > > > Please advise - am I running into a known limitation or just using > > this wrong? Is there other information I ought to provide? > > In all liklihood there is some corner case in the hostrange parsing. > I'll take a look into it and get back to you if I need any more info. > > Thanks, > Al > > > Thanks in advance, > > Chris Harwell > > > > > > _______________________________________________ > > Freeipmi-users mailing list > > Freeipmi-users@gnu.org > > http://**lists.gnu.org/mailman/listinfo/freeipmi-users > > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Wed Oct 14 19:00:51 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MyCpv-0007is-2O for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:00:51 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyCpu-0007ih-Av for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:00:50 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyCpp-0007gO-Ij for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:00:49 -0400 Received: from [199.232.76.173] (port=39320 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyCpp-0007gL-9R for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:00:45 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:30200) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyCpo-0004gX-Lb for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:00:45 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 14 Oct 2009 16:00:42 -0700 Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Al Chu To: Chris Harwell In-Reply-To: <1255542104.3594.9.camel@auk31.llnl.gov> References: <1255538608.3074.150.camel@auk31.llnl.gov> <1255542104.3594.9.camel@auk31.llnl.gov> Content-Type: text/plain Date: Wed, 14 Oct 2009 16:00:42 -0700 Message-Id: <1255561242.3594.54.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 23:00:50 -0000 Hey Chris, Just spoke to the maintainer of the internal "hostlist" library. Short term, I can build you a beta that can get around the problem. However, you will not get a nice xxxx[0001-319]-lom output, you would instead get xxxx0001-lom,xxxx0002-lom,xxxx0003-lom,... The issue was there was a buffer overflow. My buffer was 4096 chars, which sure enough is overflowed after about 316 nodes in your format (13 chars * 316 > 4096). Now why was there a buffer overflow? The hostrange library currently can't deal with hostrange "building" (which is what is done when outputs are being consolidated) when the host has a suffix (i.e "-lom"). However, I spoke to the author and if there is only 1 "numeric range", such as in your case, perhaps that can be handled as a special case, since there is no ambiguity of how to build up the hostrange. The suffix situation is a unique situation, most commonly seen with a format like: node1-eth2 in the above, it is impossible to know if the '1' or the '2' is the hostrange part (although normal users can easily guess that it's the '1' and not the '2', code wise you really never know). On your end, a short term way to deal with this problem and have a clean output is to perhaps come up with a different host alias? Here at LLNL, we prefix all IPMI addresses with a unique prefix. Hope that helps short term and hopefully we can get a fix longer term. Al On Wed, 2009-10-14 at 10:41 -0700, Al Chu wrote: > Hey Chris, > > I've reproduced this problem in the underlying hostlist library. I'm > working with the maintainer of the library to figure out if there is a > bug or if there is a hostrange assumption issue. I noticed your range > input was: > > 0001-319 > > which internally in hostlist will lead to > > 0001-0319 > > Is your intent for xxxx[0001-319] to lead to xxxx0318, xxx0319, etc.? > > Inputting the later also seems to cause an error, so there probably is a > bug somewhere, may it be an input checking bug or an output bug. > > Al > > On Wed, 2009-10-14 at 09:43 -0700, Al Chu wrote: > > Hey Chris, > > > > On Wed, 2009-10-14 at 11:53 -0400, Chris Harwell wrote: > > > Greetings freeipmi users, > > > > > > I've really enjoyed using freeipmi - it is a great tool. I > > > particularly like how the host range syntax works and simplifies > > > certain tasks. > > > > Thanks. > > > > > I've recently run into a case where freeipmi fails and hope you can > > > offer some help or advice. > > > > > > This fails: > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > --quiet-readings > > > also where the second number is 319 fails. > > > > > > These invocations work: > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > > --quiet-readings > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom > > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings > > > > > > when it fails the output looks like this: > > > $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > --quiet-readings > > > pstdout_launch: unknown internal error > > > > > > I encounter this in the several versions I could check quickly 0.6.5, > > > 0.7.12 and 0.7.13: > > > :bin$ ipmi-sensors -V > > > ipmi-sensors - 0.7.13 > > > Copyright (C) 2003-2008 FreeIPMI Core Team > > > This program is free software; you may redistribute it under the terms of > > > the GNU General Public License. This program has absolutely no warranty. > > > drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p > > > ADMIN --consolidate-output --quiet-readings > > > pstdout_launch: unknown internal error > > > > > > debug output is copious, the last bit looks like this: > > > xxxx0317-lom: IPMI Command Data: > > > xxxx0317-lom: ------------------ > > > xxxx0317-lom: [ 3Ch] = cmd[ 8b] > > > xxxx0317-lom: [ 0h] = comp_code[ 8b] > > > xxxx0317-lom: IPMI Trailer: > > > xxxx0317-lom: -------------- > > > xxxx0317-lom: [ 23h] = checksum2[ 8b] > > > pstdout_launch: unknown internal error > > > > > > Please advise - am I running into a known limitation or just using > > > this wrong? Is there other information I ought to provide? > > > > In all liklihood there is some corner case in the hostrange parsing. > > I'll take a look into it and get back to you if I need any more info. > > > > Thanks, > > Al > > > > > Thanks in advance, > > > Chris Harwell > > > > > > > > > _______________________________________________ > > > Freeipmi-users mailing list > > > Freeipmi-users@gnu.org > > > http://***lists.gnu.org/mailman/listinfo/freeipmi-users > > > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Wed Oct 14 19:40:33 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MyDSK-0004dC-R2 for mharc-freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:40:32 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyDSI-0004Zk-CU for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:40:30 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyDSD-0004T8-0L for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:40:29 -0400 Received: from [199.232.76.173] (port=41471 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyDSC-0004Su-Sl for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:40:24 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:17585) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyDSC-0003Tv-An for freeipmi-users@gnu.org; Wed, 14 Oct 2009 19:40:24 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 14 Oct 2009 16:39:58 -0700 Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Al Chu To: Chris Harwell In-Reply-To: <1255561242.3594.54.camel@auk31.llnl.gov> References: <1255538608.3074.150.camel@auk31.llnl.gov> <1255542104.3594.9.camel@auk31.llnl.gov> <1255561242.3594.54.camel@auk31.llnl.gov> Content-Type: text/plain Date: Wed, 14 Oct 2009 16:39:58 -0700 Message-Id: <1255563598.3594.57.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 14 Oct 2009 23:40:30 -0000 Hey Chris, I went ahead and put a beta up. freeipmi-0.7.14.beta0.tar.gz at http://ftp.gluster.com/pub/freeipmi/qa-release/ want to give it a shot? Al On Wed, 2009-10-14 at 16:00 -0700, Al Chu wrote: > Hey Chris, > > Just spoke to the maintainer of the internal "hostlist" library. Short > term, I can build you a beta that can get around the problem. However, > you will not get a nice > > xxxx[0001-319]-lom > > output, you would instead get > > xxxx0001-lom,xxxx0002-lom,xxxx0003-lom,... > > The issue was there was a buffer overflow. My buffer was 4096 chars, > which sure enough is overflowed after about 316 nodes in your format (13 > chars * 316 > 4096). > > Now why was there a buffer overflow? The hostrange library currently > can't deal with hostrange "building" (which is what is done when outputs > are being consolidated) when the host has a suffix (i.e "-lom"). > However, I spoke to the author and if there is only 1 "numeric range", > such as in your case, perhaps that can be handled as a special case, > since there is no ambiguity of how to build up the hostrange. The > suffix situation is a unique situation, most commonly seen with a format > like: > > node1-eth2 > > in the above, it is impossible to know if the '1' or the '2' is the > hostrange part (although normal users can easily guess that it's the '1' > and not the '2', code wise you really never know). > > On your end, a short term way to deal with this problem and have a clean > output is to perhaps come up with a different host alias? Here at LLNL, > we prefix all IPMI addresses with a unique prefix. > > Hope that helps short term and hopefully we can get a fix longer term. > > Al > > On Wed, 2009-10-14 at 10:41 -0700, Al Chu wrote: > > Hey Chris, > > > > I've reproduced this problem in the underlying hostlist library. I'm > > working with the maintainer of the library to figure out if there is a > > bug or if there is a hostrange assumption issue. I noticed your range > > input was: > > > > 0001-319 > > > > which internally in hostlist will lead to > > > > 0001-0319 > > > > Is your intent for xxxx[0001-319] to lead to xxxx0318, xxx0319, etc.? > > > > Inputting the later also seems to cause an error, so there probably is a > > bug somewhere, may it be an input checking bug or an output bug. > > > > Al > > > > On Wed, 2009-10-14 at 09:43 -0700, Al Chu wrote: > > > Hey Chris, > > > > > > On Wed, 2009-10-14 at 11:53 -0400, Chris Harwell wrote: > > > > Greetings freeipmi users, > > > > > > > > I've really enjoyed using freeipmi - it is a great tool. I > > > > particularly like how the host range syntax works and simplifies > > > > certain tasks. > > > > > > Thanks. > > > > > > > I've recently run into a case where freeipmi fails and hope you can > > > > offer some help or advice. > > > > > > > > This fails: > > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > > --quiet-readings > > > > also where the second number is 319 fails. > > > > > > > > These invocations work: > > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > > > --quiet-readings > > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom > > > > ipmi-sensors -g Fan -h xxxx[0001-318]-lom --consolidate-output > > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > > ipmi-sensors -g Fan -h xxxx[0001-319]-lom --quiet-readings > > > > > > > > when it fails the output looks like this: > > > > $ ipmi-sensors -g Fan -h xxxx[0001-319]-lom --consolidate-output > > > > --quiet-readings > > > > pstdout_launch: unknown internal error > > > > > > > > I encounter this in the several versions I could check quickly 0.6.5, > > > > 0.7.12 and 0.7.13: > > > > :bin$ ipmi-sensors -V > > > > ipmi-sensors - 0.7.13 > > > > Copyright (C) 2003-2008 FreeIPMI Core Team > > > > This program is free software; you may redistribute it under the terms of > > > > the GNU General Public License. This program has absolutely no warranty. > > > > drdenws02:bin$ ipmi-sensors -g Fan -h drdb[0001-319]-lom -u ADMIN -p > > > > ADMIN --consolidate-output --quiet-readings > > > > pstdout_launch: unknown internal error > > > > > > > > debug output is copious, the last bit looks like this: > > > > xxxx0317-lom: IPMI Command Data: > > > > xxxx0317-lom: ------------------ > > > > xxxx0317-lom: [ 3Ch] = cmd[ 8b] > > > > xxxx0317-lom: [ 0h] = comp_code[ 8b] > > > > xxxx0317-lom: IPMI Trailer: > > > > xxxx0317-lom: -------------- > > > > xxxx0317-lom: [ 23h] = checksum2[ 8b] > > > > pstdout_launch: unknown internal error > > > > > > > > Please advise - am I running into a known limitation or just using > > > > this wrong? Is there other information I ought to provide? > > > > > > In all liklihood there is some corner case in the hostrange parsing. > > > I'll take a look into it and get back to you if I need any more info. > > > > > > Thanks, > > > Al > > > > > > > Thanks in advance, > > > > Chris Harwell > > > > > > > > > > > > _______________________________________________ > > > > Freeipmi-users mailing list > > > > Freeipmi-users@gnu.org > > > > http://****lists.gnu.org/mailman/listinfo/freeipmi-users > > > > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Thu Oct 15 09:43:11 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MyQbm-0006DT-Ph for mharc-freeipmi-users@gnu.org; Thu, 15 Oct 2009 09:43:10 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyQbk-0006B0-Lc for freeipmi-users@gnu.org; Thu, 15 Oct 2009 09:43:08 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyQbg-00063l-02 for freeipmi-users@gnu.org; Thu, 15 Oct 2009 09:43:08 -0400 Received: from [199.232.76.173] (port=47119 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyQbf-00063i-RR for freeipmi-users@gnu.org; Thu, 15 Oct 2009 09:43:03 -0400 Received: from mail-vw0-f187.google.com ([209.85.212.187]:47940) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyQbf-0004p6-G9 for freeipmi-users@gnu.org; Thu, 15 Oct 2009 09:43:03 -0400 Received: by vws17 with SMTP id 17so449622vws.24 for ; Thu, 15 Oct 2009 06:43:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=4rIBKiZpFtC9AEU2zesM8sw311xJ4AVzjbNQ1Hgf6ZU=; b=MncLgRzyJwVAhVhSZ4we3HAOeEC1wS3IN+hZj70m1itgCy8XbaoFhYSN8bcaYrCkTk r7QXKoC48BQ81RKPic78b5JNyoS1BK93QmzAVNUwrbg5DrgH1ez8i12PJV0sNEnxlFw7 fGqYJprjA1s7HktcMbFoxZyXOfblNjvjMG0M4= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=HtVNihMrPsmuJEh7uVMUw7VoMC0pyfyfx5kdBkKxTUpsv5oXfhJPFBM0LTSaOLsPM7 RILnfnzmzBw69fPm+PC8/Yjlg3fcnAK8ebdPNL3DVgw4NUQ0jU9gfbzUnTeABOh6cAwz t4o3cDJb6mFjAgGWqpOqZEuwhMhz/NFbmQC3Q= MIME-Version: 1.0 Received: by 10.220.78.167 with SMTP id l39mr198391vck.10.1255614177700; Thu, 15 Oct 2009 06:42:57 -0700 (PDT) In-Reply-To: <1255563598.3594.57.camel@auk31.llnl.gov> References: <1255538608.3074.150.camel@auk31.llnl.gov> <1255542104.3594.9.camel@auk31.llnl.gov> <1255561242.3594.54.camel@auk31.llnl.gov> <1255563598.3594.57.camel@auk31.llnl.gov> Date: Thu, 15 Oct 2009 09:42:57 -0400 Message-ID: Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Chris Harwell To: freeipmi-users@gnu.org Content-Type: text/plain; charset=ISO-8859-1 X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 13:43:08 -0000 Thanks, the provided 0.7.14.beta0 worked for my testcase, ipmi-sensors -h xxxx[0001-0576]-lom -g Fan --consolidate-output --quiet-readings For the record, in case it should help others, another longer workaround is to use IP addresss ranges which provides nice consolidation too, ipmi-sensors -h xxx.xxx.16.[10-255],xxx.xxx.17.[0-255],xxx.xxx.18.[0-73] -g Fan --consolidate-output --quiet-readings That isn't nearly as nice as Al's beta0, but it might help in some other situation :> From MAILER-DAEMON Thu Oct 15 12:31:35 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1MyTEl-0003OI-N3 for mharc-freeipmi-users@gnu.org; Thu, 15 Oct 2009 12:31:35 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MyTEa-0003KR-7V for freeipmi-users@gnu.org; Thu, 15 Oct 2009 12:31:26 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MyTEN-0003BO-P8 for freeipmi-users@gnu.org; Thu, 15 Oct 2009 12:31:16 -0400 Received: from [199.232.76.173] (port=53858 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MyTEJ-0003Ak-LL for freeipmi-users@gnu.org; Thu, 15 Oct 2009 12:31:07 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:38634) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MyTEJ-0002AN-7e for freeipmi-users@gnu.org; Thu, 15 Oct 2009 12:31:07 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 15 Oct 2009 09:29:10 -0700 Subject: Re: [Freeipmi-users] pstdout_launch: unknown internal error encountered with 319 hosts and --consolidate-output --quiet-readings From: Al Chu To: Chris Harwell In-Reply-To: References: <1255538608.3074.150.camel@auk31.llnl.gov> <1255542104.3594.9.camel@auk31.llnl.gov> <1255561242.3594.54.camel@auk31.llnl.gov> <1255563598.3594.57.camel@auk31.llnl.gov> Content-Type: text/plain Date: Thu, 15 Oct 2009 09:29:09 -0700 Message-Id: <1255624149.3594.58.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Oct 2009 16:31:34 -0000 Hey Chris, Great. I'll release a new FreeIPMI, which will likely be the last 0.7.X release before 0.8.1. Al On Thu, 2009-10-15 at 09:42 -0400, Chris Harwell wrote: > Thanks, the provided 0.7.14.beta0 worked for my testcase, ipmi-sensors > -h xxxx[0001-0576]-lom -g Fan --consolidate-output --quiet-readings > > For the record, in case it should help others, another longer > workaround is to use IP addresss ranges which provides nice > consolidation too, > > ipmi-sensors -h > xxx.xxx.16.[10-255],xxx.xxx.17.[0-255],xxx.xxx.18.[0-73] -g Fan > --consolidate-output --quiet-readings > > That isn't nearly as nice as Al's beta0, but it might help in some > other situation :> > > > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@gnu.org > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Thu Oct 22 15:53:36 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N13j6-0000zz-Ey for mharc-freeipmi-users@gnu.org; Thu, 22 Oct 2009 15:53:36 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N12nQ-0003b7-Pq for freeipmi-users@gnu.org; Thu, 22 Oct 2009 14:54:00 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N12nM-0003Tu-1B for freeipmi-users@gnu.org; Thu, 22 Oct 2009 14:54:00 -0400 Received: from [199.232.76.173] (port=50478 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N12nG-0003OA-PT; Thu, 22 Oct 2009 14:53:50 -0400 Received: from mail-pz0-f192.google.com ([209.85.222.192]:34934) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N12nG-0007YT-Kw; Thu, 22 Oct 2009 14:53:50 -0400 Received: by pzk30 with SMTP id 30so6206881pzk.24 for ; Thu, 22 Oct 2009 11:53:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:cc:content-type; bh=MtA32GPdGvnmyqkiHHVKHpu9GsQ4j/5MAY7DNUEROkQ=; b=NO6E1mbDHTpKRBWJdwQNsot9a2rH6FJHjN5Ru6pRSddJF425a8oP5qFguMq3NRZjwM R7yX8eL6Dx/u75HU+d7mM+mIgYPWwPvSL8bYoP2pwSwXg0nsx5VLut4xLCMXLGcgNUtq Wo3ZWdQBkoWXLO5DpRLAO/mgu3r7j3HuI9xeA= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:cc:content-type; b=IWXLtIR5xUOGyTKp4kN3stBhiI+0IaPjqicAbicXg7yQoJhmOjpp2h8RQG7/uwYUXo K7Cqt2lqj5DC15CdXOzOVzFPaM3Lcm4Zo8Jcmct984/IOX29vwyHphCvLW6afpGGriRx hn5qyypvrjvRGAPajwKgXP3ibFXDFsx33bsVo= MIME-Version: 1.0 Received: by 10.142.118.9 with SMTP id q9mr746095wfc.49.1256237628515; Thu, 22 Oct 2009 11:53:48 -0700 (PDT) Date: Fri, 23 Oct 2009 00:23:48 +0530 Message-ID: <8939cf0d0910221153n3bc41341y41744594778f1b84@mail.gmail.com> From: manohar kallutla To: freeipmi-users@gnu.org X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 2) X-Mailman-Approved-At: Thu, 22 Oct 2009 15:53:34 -0400 Content-Type: text/plain; charset=ISO-8859-1 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Cc: freeipmi-devel@gnu.org Subject: [Freeipmi-users] Need help for configure bmc-watchdog X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 18:54:01 -0000 Hi, Firstly thanks for providing the free ipmifreeware. I have downloaded the *freeipmi.0.7.2* version from the site. Actually I want to install the *bmc-watchdog. * ** While I am configuring, the following error was occured (*shown in red color below*). Please let me know ,to resolve this issue. ./configure ........................................................................................................... checking dynamic linker characteristics... GNU/Linux ld.so checking how to hardcode library paths into programs... immediate checking for cpp... /usr/bin/cpp checking whether make sets $(MAKE)... (cached) yes checking for gcry_md_open in -lgcrypt... yes checking gcrypt.h usability... yes checking gcrypt.h presence... yes checking for gcrypt.h... yes checking whether GCRYCTL_SET_THREAD_CBS is declared... no *configure: error: libgcrypt with threads support required for libfreeipmi* ........................................................................................................................... In order to configure the bmc-watchdog, do we need to configure all the tools. eg:- /home/xxxxx/freeipmi-0.7.2 eg:- ./configure Is it possible to configure only bmc-watchdog like this eg:-/freeipmi-0.7.2/bmc-watchdog eg:- ./configure Appreciate your earliest response. Thanks and Regards, Manohar.K ** ** * * From MAILER-DAEMON Thu Oct 22 17:09:06 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N14uA-0005tn-MG for mharc-freeipmi-users@gnu.org; Thu, 22 Oct 2009 17:09:06 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N14u8-0005sp-4o for freeipmi-users@gnu.org; Thu, 22 Oct 2009 17:09:04 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N14u2-0005qk-VL for freeipmi-users@gnu.org; Thu, 22 Oct 2009 17:09:03 -0400 Received: from [199.232.76.173] (port=54759 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N14u2-0005qV-Ft; Thu, 22 Oct 2009 17:08:58 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:48237) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N14u2-0002Wx-2f; Thu, 22 Oct 2009 17:08:58 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 22 Oct 2009 14:08:57 -0700 Subject: Re: [Freeipmi-users] Need help for configure bmc-watchdog From: Al Chu To: manohar kallutla In-Reply-To: <8939cf0d0910221153n3bc41341y41744594778f1b84@mail.gmail.com> References: <8939cf0d0910221153n3bc41341y41744594778f1b84@mail.gmail.com> Content-Type: text/plain Date: Thu, 22 Oct 2009 14:08:56 -0700 Message-Id: <1256245736.4819.45.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-devel@gnu.org, freeipmi-users@gnu.org X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 21:09:04 -0000 Hi Manohar, On Fri, 2009-10-23 at 00:23 +0530, manohar kallutla wrote: > Hi, > > Firstly thanks for providing the free ipmifreeware. > > I have downloaded the *freeipmi.0.7.2* version from the site. Actually I > want to install the *bmc-watchdog. * > ** > While I am configuring, the following error was occured (*shown in red color > below*). Please let me know ,to resolve this issue. > > ./configure > > ........................................................................................................... > checking dynamic linker characteristics... GNU/Linux ld.so > checking how to hardcode library paths into programs... immediate > checking for cpp... /usr/bin/cpp > checking whether make sets $(MAKE)... (cached) yes > checking for gcry_md_open in -lgcrypt... yes > checking gcrypt.h usability... yes > checking gcrypt.h presence... yes > checking for gcrypt.h... yes > checking whether GCRYCTL_SET_THREAD_CBS is declared... no > *configure: error: libgcrypt with threads support required for libfreeipmi* > ........................................................................................................................... FreeIPMI needs the gcrypt library to be built. You'll need to install it. > In order to configure the bmc-watchdog, do we need to configure all the > tools. > > eg:- /home/xxxxx/freeipmi-0.7.2 > eg:- ./configure > > Is it possible to configure only bmc-watchdog like this > eg:-/freeipmi-0.7.2/bmc-watchdog > eg:- ./configure I'm a little confused with the question. You need to run ./configure in order to compile. After running configure successfully, you run 'make' to compile the program. Then you'll be able to use bmc-watchdog. Al > Appreciate your earliest response. > > Thanks and Regards, > Manohar.K > > ** > ** > * > > * > _______________________________________________ > Freeipmi-users mailing list > Freeipmi-users@gnu.org > http://*lists.gnu.org/mailman/listinfo/freeipmi-users > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Thu Oct 22 18:25:25 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N1661-0007l2-QF for mharc-freeipmi-users@gnu.org; Thu, 22 Oct 2009 18:25:25 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N165z-0007gd-Ti for freeipmi-users@gnu.org; Thu, 22 Oct 2009 18:25:23 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N165v-0007cZ-8s for freeipmi-users@gnu.org; Thu, 22 Oct 2009 18:25:23 -0400 Received: from [199.232.76.173] (port=38081 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N165v-0007cL-04 for freeipmi-users@gnu.org; Thu, 22 Oct 2009 18:25:19 -0400 Received: from nspiron-3.llnl.gov ([128.115.41.83]:27516 helo=smtp.llnl.gov) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N165u-0004oT-NA for freeipmi-users@gnu.org; Thu, 22 Oct 2009 18:25:18 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by smtp.llnl.gov with ESMTP; 22 Oct 2009 15:25:02 -0700 From: Al Chu To: freeipmi-users@gnu.org Content-Type: text/plain Date: Thu, 22 Oct 2009 15:25:02 -0700 Message-Id: <1256250302.4819.56.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Subject: [Freeipmi-users] FreeIPMI 0.7.14 Released X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 22 Oct 2009 22:25:24 -0000 http://ftp.gluster.com/pub/freeipmi/0.7.14/ 0.7.14 - 10/16/09 ----------------- o Fix consolidated-output corner cases. Al -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Fri Oct 23 13:08:56 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N1NdI-0007NH-Q7 for mharc-freeipmi-users@gnu.org; Fri, 23 Oct 2009 13:08:56 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N1NdG-0007MG-IC for freeipmi-users@gnu.org; Fri, 23 Oct 2009 13:08:54 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N1NdB-0007ID-OG for freeipmi-users@gnu.org; Fri, 23 Oct 2009 13:08:54 -0400 Received: from [199.232.76.173] (port=38833 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N1Nd6-0007FH-20; Fri, 23 Oct 2009 13:08:44 -0400 Received: from nspiron-1.llnl.gov ([128.115.41.81]:35221) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N1Nd5-00005W-LS; Fri, 23 Oct 2009 13:08:43 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-1.llnl.gov with ESMTP; 23 Oct 2009 10:06:35 -0700 From: Al Chu To: freeipmi-devel@gnu.org In-Reply-To: <1255470243.3074.140.camel@auk31.llnl.gov> References: <1254774950.20077.168.camel@auk31.llnl.gov> <1255470243.3074.140.camel@auk31.llnl.gov> Content-Type: text/plain Date: Fri, 23 Oct 2009 10:06:34 -0700 Message-Id: <1256317594.4819.74.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 7bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org Subject: [Freeipmi-users] Re: [Freeipmi-devel] FreeIPMI 0.8.0 Beta3 - Feedback Request X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 23 Oct 2009 17:08:54 -0000 I've put up a beta3 release. http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta3.tar.gz Changes from beta 2: Fixed portability issues for netbsd. Fixed some config file bugs. Fixed some OEM-isms. Al On Tue, 2009-10-13 at 14:44 -0700, Al Chu wrote: > Hi everyone, > > I've put up a beta2 release here: > > http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta2.tar.gz > > Changes from beta 1: > > I've modified the ipmi-sel output so there are only 2 levels of > verbosity (former level 1 verbosity is now default). > > Fixed some output corner cases. > > Added --tail to ipmi-sel. > > Fixed a shared sensors corner case. > > Al > > On Mon, 2009-10-05 at 13:35 -0700, Al Chu wrote: > > Hi everyone, > > > > I've put up a beta release of FreeIPMI 0.8.1.beta1 here: > > > > http://ftp.gluster.com/pub/freeipmi/qa-release/freeipmi-0.8.0.beta1.tar.gz > > > > I'd appreciate any testing, input, etc. from people. There are a few > > feature changes that I would like to get some input on. I am open to > > changing, reverting, or adjusting based on user input. Attached to the > > e-mail is the official NEWS release that lists all the changes in > > glorious detail. > > > > New ipmi-sensors/ipmi-sel/ipmimonitoring default output: > > -------------------------------------------------------- > > > > The default output of ipmi-sensors, ipmi-sel, and ipmimonitoring has > > been modified for easier readability and consistency to each other. > > Some information is not output but by default anymore and is available > > through new options or increased verbosity. A variety of new options > > are available for alternate outputs too. > > > > A) Do people like the new output format? Is it easier to read (which is > > my primary goal)? > > > > B) Are there any options like --entity-sensor-names, > > --no-sensor-type-output, --non-abbreviated-units, etc. that people think > > should be default rather than an option? > > > > C) Is there an output that should be default instead, or have an option > > to give an alternate output? > > > > D) Does the --legacy-output option not fully maintain backwards > > compatability and break anybody's scripts?? > > > > Things I would appreciate testing on > > ------------------------------------ > > > > I'd appreciate people trying them out on their systems to make sure > > everything still outputs fine and I make any new corner cases. I'm > > particularly interested in ensuring I didn't break: > > > > A) The --bridge-sensors options on ipmi-sensors and ipmimonitoring > > > > B) Multirecords outputs on ipmi-fru. > > > > C) Workarounds, most notably the Intel workarounds > > > > D) The new ipmi-dcmi tool, which I have not been able to fully vet due > > to lack of a system. > > > > Any feedback would be appreciated before I release. > > > > Thanks, > > Al > > > > > > _______________________________________________ > > Freeipmi-devel mailing list > > Freeipmi-devel@gnu.org > > http://*lists.gnu.org/mailman/listinfo/freeipmi-devel > -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory From MAILER-DAEMON Thu Oct 29 12:44:55 2009 Received: from mailman by lists.gnu.org with archive (Exim 4.43) id 1N3Y7L-0000PB-ME for mharc-freeipmi-users@gnu.org; Thu, 29 Oct 2009 12:44:55 -0400 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N3Y7J-0000O1-Eo for freeipmi-users@gnu.org; Thu, 29 Oct 2009 12:44:53 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N3Y7E-0000Kx-Kh for freeipmi-users@gnu.org; Thu, 29 Oct 2009 12:44:52 -0400 Received: from [199.232.76.173] (port=47436 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N3Y7E-0000Ko-E1 for freeipmi-users@gnu.org; Thu, 29 Oct 2009 12:44:48 -0400 Received: from nspiron-2.llnl.gov ([128.115.41.82]:4500) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1N3Y7D-0004jk-R7 for freeipmi-users@gnu.org; Thu, 29 Oct 2009 12:44:48 -0400 X-Attachments: None Received: from auk31.llnl.gov (HELO [134.9.93.159]) ([134.9.93.159]) by nspiron-2.llnl.gov with ESMTP; 29 Oct 2009 09:44:45 -0700 From: Al Chu To: Moerman Nicolas In-Reply-To: <66F68487BF0EED4BA7D767E2410F30B38C6C648665@FRSPX100.fr01.awl.atosorigin.net> References: <66F68487BF0EED4BA7D767E2410F30B38C6C648665@FRSPX100.fr01.awl.atosorigin.net> Content-Type: text/plain; charset=UTF-8 Date: Thu, 29 Oct 2009 09:44:45 -0700 Message-Id: <1256834685.4819.209.camel@auk31.llnl.gov> Mime-Version: 1.0 X-Mailer: Evolution 2.12.3 (2.12.3-19.el5) Content-Transfer-Encoding: 8bit X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. Cc: freeipmi-users@gnu.org Subject: [Freeipmi-users] Re: [FREEIPMI] trouble to commit pef policy X-BeenThere: freeipmi-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: chu11@llnl.gov List-Id: GNU FreeIPMI User's Mailing List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 29 Oct 2009 16:44:53 -0000 Hey Nicolas, Entering section `Alert_Policy_2' Comment on line 2 Parsed `Alert_Policy_2:Policy_Type=Always_Send_To_This_Destination' Comment on line 4 Parsed `Alert_Policy_2:Policy_Enabled=Yes' Comment on line 6 Parsed `Alert_Policy_2:Policy_Number=2' Comment on line 8 Parsed `Alert_Policy_2:Destination_Selector=1' Comment on line 10 Parsed `Alert_Policy_2:Channel_Number=2' Comment on line 12 Parsed `Alert_Policy_2:Alert_String_Set_Selector=1' Comment on line 14 Parsed `Alert_Policy_2:Event_Specific_Alert_String=No' Leaving section `Alert_Policy_2' ===================================================== Set PEF Configuration Parameters Request ===================================================== [ 12h] = cmd[ 8b] [ 9h] = parameter_selector[ 7b] [ 0h] = reserved1[ 1b] [ 2h] = alert_policy_entry_number[ 7b] [ 0h] = reserved2[ 1b] [ 0h] = policy_number.policy_type[ 3b] [ 0h] = policy_number.enabled[ 1b] [ 0h] = policy_number.policy_number[ 4b] [ 0h] = channel_destination.destination_selector[ 4b] [ 0h] = channel_destination.channel_number[ 4b] [ 0h] = alert_string_key.alert_string_set_selector[ 7b] [ 0h] = alert_string_key.event_specific_alert_string[ 1b] ===================================================== Set PEF Configuration Parameters Response ===================================================== [ 12h] = cmd[ 8b] [ CCh] = comp_code[ 8b] ipmi_cmd_set_pef_configuration_parameters_alert_policy_table: bad completion code: request data/parameter invalid ERROR: Failed to commit `Alert_Policy_2:Policy_Type' Hmmmm ... I'm wondering if it's complaining that the channel number is 0. Lets try a trick. Can you reorder your alert_policy_2 config to list "channel number" first in the Alert_Policy_2 block? In general, try re-ordering them around and see if it helps (from your debug I assume you had tried to config only Alert_Policy_2 at the time). If that is the issue, I can add a workaround for your motherboard. The core issue (which I've hit with multiple vendors) is that it is possible for the default config on the motherboard to be an "illegal" config. So when the user tries to change only 1 sub-field for that area, how are they supposed to know that a part they aren't interested is configured illegally. Al P.S. If moving them fields around makes it work, PLMK what fields and then PLMK the vendor and motherboard, so I can document it. On Thu, 2009-10-29 at 14:07 +0100, Moerman Nicolas wrote: > Hello Al, > > > > I meet a problem to commit settings into the PEF, specialy a policy. > > The amazing thing is that it worked but now it isn't anymore. I've got > a "ERROR: Failed to commit". > > I think my syntax is OK, these problems appeared since my BMC reset > test , I think… > > > > Maybe an optin has been reset and i don't remmerber what and where. > > I join the debug output of my command and the conf file. > > I hope you will have an idea about what's happen. > > thanks > > > > > > ______________________________________________________________________________ > > Nicolas MOERMAN > > Technical Operations > > Tel : +33 (0)3 20 60 79 48 > > > ATOS WORLDLINE > Z.I A Rue dela Pointe 59113 SECLIN > > www.*atosworldline.com > > Atos Worldline is an Atos Origin Company: www.*atosorigin.com > > > > > > > > > > > ______________________________________________________________________ > > Ce message et les pièces jointes sont confidentiels et réservés à > l'usage exclusif de ses destinataires. Il peut également être protégé > par le secret professionnel. Si vous recevez ce message par erreur, > merci d'en avertir immédiatement l'expéditeur et de le détruire. > L'intégrité du message ne pouvant être assurée sur Internet, la > responsabilité du groupe Atos Origin ne pourra être recherchée quant > au contenu de ce message. Bien que les meilleurs efforts soient faits > pour maintenir cette transmission exempte de tout virus, l'expéditeur > ne donne aucune garantie à cet égard et sa responsabilité ne saurait > être recherchée pour tout dommage résultant d'un virus transmis. > > This e-mail and the documents attached are confidential and intended > solely for the addressee; it may also be privileged. If you receive > this e-mail in error, please notify the sender immediately and destroy > it. As its integrity cannot be secured on the Internet, the Atos > Origin group liability cannot be triggered for the message content. > Although the sender endeavours to maintain a computer virus-free > network, the sender does not warrant that this transmission is > virus-free and will not be liable for any damages resulting from any > virus transmitted. -- Albert Chu chu11@llnl.gov Computer Scientist High Performance Systems Division Lawrence Livermore National Laboratory