<div class="socmaildefaultfont" dir="ltr" style="font-family:Arial, Helvetica, sans-serif;font-size:10.5pt" ><div dir="ltr" ><div>Goal : Collect BMC failure analysis and Debug data within size limit 1MB ( Max size per entry 500K).<br> <br>Evaluation Scope:<br> • Identify industry standard open Source tool that can be used for BMC Debug Data monitoring, packaging and reporting.<br> <br>Tools considered for this evaluation :<br> • SOSREPORT: Failure Debug data Packaging<br> • ABRT: Failure Monitoring and Debug Data Packaging and reporting</div>
<div>Packaging: SOSREPORT<br><a href="http://github.com/sosreport/sos" >http://github.com/sosreport/sos</a><br> <br>What is sosreport ?<br> • It generates a compressed tar archive of diagnostic information from the running system. The archive may be stored locally or centrally for recording or tracking purposes or may be sent to technical support representatives, developers or system administrators to assist with technical fault-finding and debugging.<br> <br>Technologies used:<br> • Python<br> <br>Pros:<br> • Sos is modular in design and is able to collect data from a wide range of subsystems and packages that may be installed.<br> • XML or HTML report summary support.<br> • Provides easy way to control the contents.<br> • Widely used in Linux community which has active support forums<br> • Used in Open Power.<br>Cons:<br> • Package size is not suitable for Storage constrained embedded platforms.<br> <br>Base SOS Package with minimal plugin size: 360K (based on Fedora distribution)<br> <br> <br>Reporting: ABRT (Automatic Bug Reporting Tool)<br><a href="https://github.com/abrt/abrt" >https://github.com/abrt/abrt</a><br> <br>What is abrt?<br> • A set of tools to help users detect and report application crashes.<br> • Its main purpose is to ease the process of reporting an issue and finding a solution.<br> <br>Technologies:<br> • libreport - Problem data format, reporting<br> • satyr backtrace processing, microreports.<br> • Python3<br> • Glib2<br> • Gtk3<br> • D-Bus<br> • SELinux<br> • systemd<br> <br>Pros:<br> • Modular, with plugin for different languages (C, C++,Python),different reporters, databases for crash reports.<br> • Provide detailed information about kernel, package, machine environment.<br> • Nice cli and GUI for report management.<br> • Provide Automatic reporting option.<br> <br>Cons:<br> • Needs separate packages for C/C++/Python problem analyzer.<br> • Heavy Executable's code size footprint<br> • ~2.65MB Disk space required for Base application.<br> <br>Base Package size: 2.65MB (based on Fedora distribution)<br> Bytes.<br>abrt 2519822 -- The ABRT daemon which runs under the root user as a background service.<br>abrt-cli 0<br>abrt-addon-pstoreoops 14497 -- Collecting Kernel oopses from pstore storage.<br>abrt-addon-python3 18386 -- Python hook and anlyzer for handling uncaught exception in python program.<br>abrt-tui 24928 -- abrt command line interface.<br>abrt-addon-coredump-helper 35098 -- Hook for C/C++ crashed programs.<br>abrt-addon-vmcore 44498 -- Extracts oops message from the kernel core and install Kernel debuginfo if needed.<br>abrt-addon-xorg 51445 -- (NA) Extract Xorg crashes from systemd-journal.<br>abrt-libs 71026 --<br>abrt-addon-kerneloops 73981 -- Collecting Kernel Crash and reporter plugin<br>abrt-python3 85040 -- High level API for querying,creating and manipulating problems handled in Python3</div>
<div> </div>
<div> </div>
<div> </div>
<div>Overall Conclusion: Preferably not to use these tools( ABRT,SOSREPORT) for BMC debug data collection features mainly due to Flash size limitation.<br><br>Note: I will be sending separate note on BMC Dump design which provides more details on the current approach.</div></div>
<div dir="ltr" > </div>
<div dir="ltr" > </div>
<div dir="ltr" >Thanks & Regards<br><br>Jayanth Othayoth<br>mailto:ojayanth@in.ibm.com</div></div><BR>