Data analysis method and device and electronic equipment

By automatically parsing the crash test dataset, the problem of low BMC fault analysis rate under large-scale stress tests is solved, and the rapid location and repair of BMC faults is achieved.

CN118938857AActive Publication Date: 2024-11-12NETTRIX INFORMATION IND CO LTD
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
CN202410994362.0
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-07-23
Publication Date
2024-11-12
Estimated Expiration
2044-07-23

AI Technical Summary

Technical Problem

In large-scale stress testing scenarios, the number of BMC failures is large and the amount of crashed memory information is large. The existing technology relies on manual analysis to lead to low analysis rate and waste of human resources, and a large amount of duplicate information.

Method used

Provide a data analysis method, by obtaining the crash test data set, automatically analyzing the crash test data based on the analysis rules, iteratively analyze to improve the analysis rate, and push the analysis results to the quality monitoring end or operation and maintenance personnel.

Benefits of technology

It realizes automated analysis of a large amount of crash test data caused by BMC failures, improves the analysis rate, and helps operation and maintenance personnel to locate and repair the faults in a timely manner.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118938857A_ABST
    Figure CN118938857A_ABST
Patent Text Reader

Abstract

The invention provides a data analysis method and device and electronic equipment, and relates to the technical field of data processing. The method comprises the following steps: firstly, acquiring a crash test data set for carrying out a pressure test on a plurality of tested BMCs (Baseboard Management Controller); then selecting a target analysis rule corresponding to a data level from the analysis rule set on the basis of the data level to which each piece of crash test data in the crash test data set belongs, and analyzing each piece of crash test data on the basis of the target analysis rule to obtain each piece of target analysis data; and finally, performing iterative analysis on each piece of target analysis data, and outputting an analysis result corresponding to each piece of target analysis data, by adopting the mode, a large amount of crash test data generated by the BMC fault can be automatically collected, and the analysis rate of the crash test data is improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application relates to the field of data processing technology, and in particular to a data analysis method, device and electronic equipment. Background Art

[0002] The baseboard management controller (BMC) is a dedicated controller used to monitor and manage servers. When the server's BMC fails (for example, the BMC's kernel code or application code is wrong), it provides maintenance personnel with alarm information and corresponding recovery measures.

[0003] Specifically, during the startup and operation of the BMC, when there is an error in the BMC kernel code or the kernel crashes, the kernel panic mechanism will be triggered to capture the crash memory information generated by the kernel failure and store the crash memory information of the kernel failure in the Kdump file; when there is an error in the code of the BMC application layer, the crash memory information generated by the application code error (such as memory layout, variable value, call stack information, and CPU register value, etc.) will be saved in the core dump file (coredump file). Maintenance personnel can analyze the cause of the application crash based on the coredump file and repair the corresponding fault.

[0004] At present, the crash memory information generated by BMC application code errors is usually analyzed manually. If there are many BMCs with faults in a large-scale stress test scenario, and the amount of crash memory information generated by BMC application code errors is large, the method of manually analyzing the crash memory information generated by application code errors will reduce the speed of analyzing the crash memory information generated by application code errors; in addition, since there is a large amount of repeated information in the crash memory information generated by application code errors, manual analysis one by one will also cause a waste of human resources. Summary of the invention

[0005] The present invention provides a data analysis method, device and electronic device to improve the speed of analyzing a large amount of crash memory information generated by BMC failure. The specific technical solution is as follows:

[0006] In a first aspect, the present application provides a data analysis method, comprising:

[0007] Obtain a crash test data set for stress testing multiple baseboard management controllers (BMCs) under test;

[0008] Based on the data level to which each crash test data in the crash test data set belongs, selecting a target parsing rule corresponding to the data level from a parsing rule set, and parsing each crash test data based on the target parsing rule to obtain each target parsed data;

[0009] Iteratively analyze each of the target parsed data, and output the analysis results corresponding to each of the target parsed data.

[0010] Based on the above method, a large amount of crash test data generated by the tested BMC fault in the stress test scenario can be collected, and a more detailed and automated analysis of the large amount of crash test data can be performed to improve the analysis rate of the crash test data.

[0011] In a possible implementation, the step of obtaining a crash test data set for performing stress tests on multiple BMCs under test includes:

[0012] Accessing any target BMC among the multiple tested BMCs;

[0013] Determine whether there is crash memory information generated by a kernel failure in the first preset directory of the target BMC;

[0014] If yes, transferring the crash memory information to the crash test data set;

[0015] If not, the core dump file in the second preset directory of the target BMC is transferred to the crash test data set.

[0016] Based on the above method, the crash memory information generated by the kernel failure of the target BMC can be collected.

[0017] In a possible implementation, transferring the core dump file in the second preset directory of the target BMC to the crash test data set includes:

[0018] Determine whether the core dump file exists in the second preset directory of the target BMC;

[0019] If yes, transferring the core dump file to the crash test data set;

[0020] If not, then access the next target BMC among the multiple tested BMCs until each BMC among the multiple tested BMCs is polled.

[0021] Based on the above method, the core dump files generated by the application code errors of the target BMC can be collected, and the crash memory information and the core dump files can be stored in the crash test data set.

[0022] In a possible implementation, if the data layer to which the crash test data belongs is the kernel layer, the crash test data is parsed using the following target parsing rule:

[0023] Determine a firmware version of a target BMC that generates the crash test data;

[0024] Determine whether there is a target kernel image version corresponding to the firmware version in a preset kernel image version set, wherein the kernel image version in the kernel image version set represents an uncompressed version after kernel compilation of the tested BMC;

[0025] If yes, then obtaining the image version time of the target kernel image version and the firmware version time of the crash test data, and when determining that the image version time is the same as the firmware version time, calling a kernel dump file analysis tool to parse the crash test data;

[0026] If not, the first prompt information is output.

[0027] Based on the above method, automatic parsing of kernel dump files can be achieved.

[0028] In a possible implementation, if the data layer to which the crash test data belongs is the application layer, the crash test data is parsed using the following target parsing rules:

[0029] The firmware version of the target BMC that generates the crash test data is determined.

[0030] Determine whether there is a target symbol table corresponding to the firmware version in the symbol table set, wherein the symbol table set is generated when compiling the firmware of the plurality of BMCs under test, and each firmware version of the BMC under test corresponds to a symbol table version;

[0031] If yes, then acquiring crash indication information in the crash test data, and parsing the crash test data based on the crash indication information;

[0032] If not, a prompt message is output.

[0033] Based on the above method, automatic parsing of core dump files can be achieved.

[0034] In a possible implementation, the crash indication information includes a crash process name or a crash thread name. If the crash thread name in the crash test data is obtained, parsing the crash test data based on the crash indication information includes:

[0035] Searching the crash process name associated with the crash thread name in the thread statistics table;

[0036] Based on the crash process name, a program debugging tool GDB is called to parse the crash test data.

[0037] Based on the above method, automatic parsing of core dump files can be achieved.

[0038] In a possible implementation, after outputting the analysis results corresponding to each of the target parsed data, the method further includes:

[0039] Pushing the analysis results corresponding to each of the target parsed data to the quality monitoring end; or

[0040] Based on the operation data of the tested BMC, a comprehensive analysis report is generated, and the comprehensive analysis report is pushed to the quality monitoring end or the operation and maintenance personnel, so that the operation and maintenance personnel can repair the abnormal BMC based on the comprehensive analysis report, wherein the operation data at least includes the memory information, CPU status information and restart information of the tested BMC.

[0041] By pushing crash test data to the quality monitoring end or operation and maintenance personnel, the operation and maintenance personnel can more intuitively determine whether it is a kernel failure or an application layer code failure, locate the fault problem in a timely manner, and repair the faulty server.

[0042] In a second aspect, the present application provides a data analysis device, comprising:

[0043] A data acquisition module is used to acquire a crash test data set for stress testing of multiple baseboard management controllers (BMCs) under test;

[0044] A data parsing module, configured to select a target parsing rule corresponding to the data level from a parsing rule set based on the data level to which each crash test data in the crash test data set belongs, and parse each crash test data based on the target parsing rule to obtain each target parsed data;

[0045] The data analysis module is used to iteratively analyze each of the target parsed data and output the analysis results corresponding to each of the target parsed data.

[0046] In a third aspect, the present application provides an electronic device, including:

[0047] Memory, used to store computer programs;

[0048] The processor is used to implement the steps of the above-mentioned data analysis method when executing the computer program stored in the memory.

[0049] In a fourth aspect, the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above-mentioned data analysis method are implemented.

[0050] For each aspect from the second to the fourth aspect and the technical effects that may be achieved by each aspect, please refer to the above description of the technical effects that can be achieved by the first aspect or various possible schemes in the first aspect, and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] Figure 1 A flowchart of a data analysis method provided in an embodiment of the present application;

[0052] Figure 2 A schematic diagram of the data analysis system architecture provided in an embodiment of the present application;

[0053] Figure 3 A flowchart for obtaining a crash test data set provided in an embodiment of the present application;

[0054] Figure 4 A schematic diagram of storage of crash test data provided by an embodiment of the present application;

[0055] Figure 5 A flowchart of parsing a kernel dump file provided in an embodiment of the present application;

[0056] Figure 6 A flowchart of parsing a core dump file provided in an embodiment of the present application;

[0057] Figure 7 A flowchart of analyzing target parsing data provided in an embodiment of the present application;

[0058] Figure 8 A schematic diagram of the analysis results pushed to the quality monitoring terminal provided in an embodiment of the present application;

[0059] Fig. 9 A schematic diagram of the structure of a data analysis device provided in an embodiment of the present application;

[0060] Fig.10 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the purpose, technical solutions and advantages of the present application clearer, the present application will be further described in detail below in conjunction with the accompanying drawings. The specific operating methods in the method embodiments can also be applied to device embodiments or system embodiments. It should be noted that in the description of the present application, "multiple" is understood as "at least two". "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. A is connected to B, which can represent: A is directly connected to B and A is connected to B through C. In addition, in the description of the present application, words such as "first" and "second" are only used to distinguish the purpose of description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0062] The embodiments of the present application are described in detail below in conjunction with the accompanying drawings.

[0063] The baseboard management controller is a dedicated controller used to monitor and manage the server. When the BMC of the server fails (for example, the kernel code or application code of the BMC is wrong), it provides alarm information and corresponding recovery measures to maintenance personnel.

[0064] Specifically, during the startup and operation of the BMC, when there is an error in the kernel code of the BMC, such as accessing a null pointer, deadlock, or accessing an illegal address, the kernel panic mechanism will be triggered to capture the crash memory information generated by the kernel failure and store the crash memory information of the kernel failure in the Kdump file; when an error occurs in an executing program in the BMC application layer, such as executing an invalid memory reference or a segmentation fault signal (SIGSEGV), the crash memory information generated by the application code error (such as memory layout, variable values, call stack information, and CPU register values) will be saved in the core dump file (coredump file). Maintenance personnel can analyze the cause of the application crash based on the coredump file, and then debug and repair the corresponding fault.

[0065] At present, the crash memory information generated by application code errors is usually analyzed manually. If there are many BMCs with faults in a large-scale stress test scenario, and the amount of crash memory information generated by BMC application code errors is large, the method of manually analyzing the crash memory information generated by application code errors will reduce the speed of analyzing the crash memory information generated by application code errors; in addition, since there is a large amount of repeated information in the crash memory information generated by application code errors, manual analysis one by one will also cause a waste of human resources.

[0066] In view of this, in order to comprehensively analyze a large amount of crash memory information generated by BMC failures in a stress testing scenario and to improve the analysis rate of the crash memory information, the present application provides a data analysis method, which specifically includes: first, obtaining a crash test data set for stress testing multiple baseboard management controllers BMC under test; then, based on the data level to which each crash test data in the crash test data set belongs, selecting a target parsing rule corresponding to the data level from a parsing rule set, and parsing each crash test data based on the target parsing rule to obtain each target parsing data; finally, iteratively analyzing each target parsing data, and outputting the analysis results corresponding to each target parsing data.

[0067] Through the method provided in the present application, a large amount of crash test data generated by BMC failures can be automatically collected, and the corresponding target parsing rules are selected according to the data level to which each crash test data belongs for parsing, so as to obtain corresponding analysis results, thereby improving the analysis rate of the crash test data and facilitating operation and maintenance personnel to locate fault problems.

[0068] Reference Figure 1 As shown, it is a flow chart of a data analysis method provided in an embodiment of the present application, the method comprising:

[0069] S1, obtaining a crash test data set for performing stress tests on multiple baseboard management controllers (BMCs) under test.

[0070] First of all, the method provided in this application can be applied to Figure 2 In the system architecture shown, the system architecture includes: a log analysis server, a BMC under test, a compilation server and a terminal device, and the method provided in the present application can be executed in the log analysis server.

[0071] This application does not impose any specific restrictions on the types and quantities of the above-mentioned servers. The functions of each server are briefly introduced below:

[0072] The log analysis server is used to collect crash memory information generated by stress testing the BMC under test, and parse the crash memory information according to the set parsing rules. After the parsing is completed, the analysis result corresponding to the crash memory information is sent to the terminal device.

[0073] The tested BMC is used to run the test version firmware compiled by the compilation server. When the tested BMC fails, the crash memory information generated is stored in a specified directory. In order to be able to test a large number of test version firmwares, the application can set multiple tested BMCs (such as tested BMC1-tested BMC3), and update a test version firmware in each tested BMC. In addition, the tested BMC can be deployed in the tested server, and the application does not specifically limit the deployment method of the tested BMC.

[0074] The compilation server is used to automatically compile and generate test version firmware, and when generating each test version firmware, it retains the symbol table information corresponding to the current test version firmware, wherein the symbol table information is the debugging information of the executable program collected by the compilation server when compiling the test version firmware, and the symbol table information can be used to parse crash memory information (dump file); in the present application, the compilation server can generate the test version firmware according to a set time period, and the time period can be set according to the actual test requirements, and the present application does not impose specific restrictions on this.

[0075] The terminal device can be a portable terminal such as a tablet computer or a mobile phone. The terminal device can receive the analysis results from the log analysis server and display the analysis results to the operation and maintenance personnel so that the operation and maintenance personnel can locate the fault problem based on the analysis results.

[0076] In the embodiments of the present application, as shown in the attached Figure 3 As shown, before obtaining a crash test data set for stress testing multiple baseboard management controllers (BMCs) under test, the log analysis server first compiles the corresponding test version firmware and retains the symbol table information of each test version firmware; then reads the configuration file of the BMC under test, and updates each test version firmware to the corresponding BMC under test. In specific implementation, a test version firmware can be updated for each BMC under test according to the device identification of the BMC under test, for example, BMC1 under test-firmware 1, BMC2 under test-firmware 2; finally, each BMC under test is stress tested. During the stress test, if the kernel of the BMC under test fails, the BMC under test will trigger the kernel panic mechanism and store the crash memory information of the kernel failure in the kernel dump file (Kdump file) of the specified directory of the BMC under test; if the application layer code of the BMC under test is wrong, the crash memory information generated by the application failure will be stored in the core dump file (coredump file) of the specified directory of the BMC under test. At this time, the crash memory information related to the test version firmware of the BMC under test is stored in the specified directory of each BMC under test that fails.

[0077] In the embodiment of the present application, after the stress test on the multiple BMCs under test is completed, the log analysis server may obtain a crash test data set of the stress test on the multiple BMCs under test.

[0078] Specifically, the log analysis server accesses any target BMC among multiple BMCs under test, for example, target BMC1. In the present application, the log analysis server can first determine the device identification of the BMC under test, for example, the IP address of the BMC under test, and then determine the target BMC to be accessed based on the IP address of the BMC under test; after successfully accessing the target BMC, the log analysis server can enter the directory of the target BMC, and then determine whether there is crash memory information caused by kernel failure in the first preset directory of the target BMC. If it exists, it means that the kernel code of the target BMC has failed. At this time, the log analysis server will transfer the crash memory information to the crash test data set; if it does not exist, the log analysis server will transfer the core dump file in the second preset directory of the target BMC to the crash test data set. In the present application, when determining whether there is crash memory information caused by kernel failure in the first preset directory of the target BMC, specifically, it can be first determined whether there is a directory named "_mem_" in the target directory, and whether there is crash memory information caused by kernel failure is determined based on the directory named "_mem_".

[0079] In an embodiment of the present application, when the log analysis server transfers the core dump file in the second preset directory of the target BMC to the crash test data set, the log analysis server will first determine whether there is a core dump file in the second preset directory of the target BMC. If so, it means that a failure has occurred in the application code of the target BMC. At this time, the log analysis server will transfer the core dump file to the crash test data set; if not, the log analysis server will access the next target BMC among the multiple BMCs under test according to the device identifier of the BMC under test, until the kernel dump files and core dump files generated by each BMC in the multiple BMCs under test are collected to obtain the crash test data set.

[0080] Through the above manner, each BMC under test can be accessed according to the device identifier of the BMC under test, and the kernel dump file and the core dump file generated by each BMC under test can be transferred to the crash test data set.

[0081] In an embodiment of the present application, in a possible implementation manner, after obtaining the crash test data set Daily Test_202x_x, the log analysis server may classify and store the crash test data. Figure 4As shown, the log analysis server can first classify the crash test data according to the test time, and store the crash test data with the same test time in the storage unit of the log analysis server or the log storage server, for example, the crash test data with the same test time is stored in the log storage server directory 202x_xx_xx; then the crash test data is classified according to the IP address of the BMC under test, and the crash test data belonging to the same IP address (BMC under test) is stored in the directory BMC_IP; finally, according to the data level to which the crash test data belongs or (the data type of the crash test data), the crash test data (kernel dump file) belonging to the kernel layer is stored in the log storage server directory kdump, and the crash test data (core dump file) belonging to the application layer is stored in the log storage server directory corefiles, so as to obtain the classified crash test data set.

[0082] S2, based on the data level to which each crash test data in the crash test data set belongs, select a target parsing rule corresponding to the data level from the parsing rule set, and parse each crash test data based on the target parsing rule to obtain each target parsing data.

[0083] In an embodiment of the present application, after the log analysis server obtains the crash test data set, each crash test data in the crash test data set has its own corresponding IP address, test firmware version and data level (kernel layer, application layer); in order to be able to parse crash test data of different data levels, the log analysis server can select a target parsing rule corresponding to the data level of each crash test data from the parsing rule set, and use the target parsing rule to parse each crash test data to obtain each target parsed data.

[0084] In the embodiment of the present application, when the log analysis server determines that the data layer to which the crash test data belongs is the kernel layer (that is, the crash test data is a kernel dump file), the kernel dump file is parsed in the following manner:

[0085] The log analysis server first determines the firmware version of the target BMC that generates the crash test data; then determines whether there is a target kernel image version corresponding to the firmware version in the preset kernel image version set; if so, obtains the image version time of the target kernel image version and the firmware version time of the crash test data, and when it is determined that the image version time is the same as the firmware version time, calls the kernel dump file analysis tool to parse the crash test data; if not, outputs the first prompt information.

[0086] Specifically, see Figure 5As shown, after obtaining the crash test data set, the log analysis server can filter out multiple directories named "BMC_IP" in which kernel dump files exist in the crash test data set, wherein each directory named "BMC_IP" corresponds to an IP address of a BMC under test; if no directory named "BMC_IP" and containing a kernel dump file is found, a prompt message is sent to the terminal device, and the kernel dump file parsing process is exited; for any target directory among the multiple directories named "BMC_IP", the crash test data in the target directory is parsed as follows:

[0087] The log analysis server first determines the firmware version of the target BMC that generates the crash test data or determines the firmware version of the current IP (target directory); then determines whether there is a target kernel image version corresponding to the firmware version of the target BMC in a preset kernel image version set, wherein the kernel image version in the kernel image version set represents an uncompressed version after the kernel of the tested BMC is compiled; when the log analysis server matches the target kernel image version, the log analysis server can extract a specific field from the firmware version of the tested BMC, and the specific field can be a firmware identification number NH, and match the target kernel image version according to the firmware identification number.

[0088] When the log analysis server determines that there is a target kernel image version corresponding to the firmware version of the target BMC in the kernel image version set, the log analysis server can obtain the image version time of the target kernel image version, enter the target directory, and obtain the crash test data in the target directory and the firmware version time of the crash test data. In addition, after entering the target directory, the log analysis server can also determine whether the file in the directory is empty. When the file is empty, traverse the next directory named "BMC_IP" and where the kernel dump file exists; finally, determine whether the image version time of the target kernel image version is the same as the firmware version time of the crash test data. When the log analysis server determines that the image version time is the same as the firmware version time, the kernel dump file analysis tool is called to parse the crash test data.

[0089] In an embodiment of the present application, after the log analysis server enters the target directory and obtains the crash test data in the target directory, it also needs to determine whether the crash test data is compressed. If so, the crash test data is decompressed to obtain the firmware version time of the crash test data; if not, the firmware version time of the crash test data can be directly obtained.

[0090] In an embodiment of the present application, when the log analysis server determines that the image version time is different from the firmware version time, it sends an indication message to the terminal device to prompt that the image version time is inconsistent with the firmware version time and the current crash test data parsing fails.

[0091] When the log analysis server determines that the target kernel image version corresponding to the target firmware version does not exist in the kernel image version set, the log analysis server can send a first prompt information to the terminal device that the target kernel image version corresponding to the target firmware version does not exist in the kernel image version set.

[0092] Based on the above-mentioned parsing method for the kernel dump files in the target directory, the log analysis server parses the kernel dump files in each target directory in multiple directories named "BMC_IP", and can obtain the parsing result corresponding to each (crash test data) kernel dump file.

[0093] By means of the above method, a large number of kernel dump files generated by multiple BMC kernel failures under test in the crash test data set can be automatically parsed, thereby improving the parsing rate of a large number of kernel dump files.

[0094] In the embodiment of the present application, when the log analysis server determines that the data layer to which the crash test data belongs is the application layer (that is, the crash test data is a core dump file), the core dump file is parsed in the following manner:

[0095] The log analysis server first determines the firmware version of the target BMC that generates the crash test data; then determines whether there is a target symbol table corresponding to the firmware version in a pre-acquired symbol table set, wherein the symbol table set is generated when compiling the firmware of multiple BMCs under test, and each firmware version of the BMC under test corresponds to a symbol table version; if so, obtains crash indication information in the crash test data, and parses the crash test data based on the crash indication information; if not, outputs a second prompt message.

[0096] Specifically, see Figure 6 As shown, after obtaining the crash test data set, the log analysis server can filter out multiple directories named "BMC_IP" in the crash test data set where core dump files (corefiles directories) exist, wherein each directory named "BMC_IP" corresponds to an IP address of a tested BMC; if no directory named "BMC_IP" and containing core dump files is found, a prompt message is sent to the terminal device to exit the core dump file parsing process; for any target directory among the multiple directories named "BMC_IP", the crash test data in the target directory is parsed as follows:

[0097] The log analysis server first determines the firmware version of the target BMC that generates the crash test data or determines the firmware version of the current IP (target directory); then determines whether there is a target symbol table corresponding to the firmware version of the target BMC in the pre-acquired symbol table set, wherein the symbol table set is generated when compiling the firmware of multiple BMCs under test, and each firmware version of the BMC under test corresponds to a symbol table version; when the log analysis server matches the target symbol table, the log analysis server can also extract a specific field from the firmware version of the BMC under test, and the specific field can be a firmware identification number NH, and match the target symbol table according to the firmware identification number.

[0098] When the log analysis server determines that there is a target symbol table corresponding to (matching) the firmware version of the target BMC in the symbol table set, the log analysis server can enter the target directory (corefiles directory), obtain the crash test data and crash indication information of the crash test data in the target directory, and parse the crash test data according to the crash indication information.

[0099] In an embodiment of the present application, after entering the target directory, the log analysis server also needs to determine whether the files in the target directory are empty. If so, it parses the next target directory (next IP); if not, it determines whether the crash test data is compressed. If compressed, the log analysis server needs to decompress the crash test data to obtain the crash indication information of the crash test data, wherein the crash indication information can be the crash process name or crash thread name of the crash test data, and the present application does not impose specific restrictions on this; if it is not compressed, the log analysis server can directly obtain the crash indication information of the crash test data.

[0100] When the log analysis server determines that the target symbol table corresponding to the firmware version of the target BMC does not exist in the symbol table set, the log analysis server may send second prompt information to the terminal device indicating that the target symbol table corresponding to the firmware version of the target BMC does not exist in the symbol table set.

[0101] In an embodiment of the present application, after obtaining the crash indication information, if the log analysis server obtains the crash process name in the crash test data, then the log analysis server can parse the crash test data based on the crash process name and call the program debugging tool GNU Debugger (GDB); if the log analysis server obtains the crash thread name in the crash test data, then the log analysis server can first search the thread statistics table for the crash process name associated with the crash thread name; then, based on the crash process name, call the program debugging tool GNU Debugger (GDB) to parse the crash test data. It should be noted that due to the length limit of the process name, for processes with particularly duplicate names, the log analysis server can perform a secondary match, and after a successful match, call the GDB tool to parse the crash test data according to the configured command file.

[0102] Based on the above-mentioned parsing method for core dump files in the target directory, the log analysis server parses the core dump files in each target directory in multiple directories named "BMC_IP" to obtain the parsing result corresponding to each core dump file (crash test data).

[0103] By means of the above method, a large number of core dump files generated by multiple BMC application layer program code failures in the crash test data set can be automatically parsed, thereby improving the parsing rate of a large number of core dump files.

[0104] In an embodiment of the present application, after the log analysis server parses the kernel dump file and the core dump file in the crash test data set according to their respective corresponding target parsing rules, each target parsing data can be obtained.

[0105] S3, iteratively analyze each target parsing data, and output the analysis results corresponding to each target parsing data.

[0106] In the examples of this application, see Figure 7 As shown, when iteratively analyzing each target parsed data, the log analysis server can first set a relevant configuration set for the analysis tool, and the configuration parameters of the configuration set can be adjusted according to business needs. For example, when analyzing a core dump file, set the log dump path for dump file analysis, enable GDB tool output dump, import symbol table information, print stack information, etc.; when analyzing a kernel dump file, print stack information or fault logs, etc.

[0107] After the log analysis server uses the analysis tool to enter the analysis interface, it can execute the commands provided by the configuration set to obtain the execution results, and pre-process the execution results, for example, filter the execution results, such as sending log names, filtering other related information; then send the pre-processed execution results to the data handler, and continue to wait for the next analysis command. In addition, before sending the pre-processed execution results to the data handler, the pre-processed execution results can also be optimized, for example, generating structured information, so as to form analysis specifications later.

[0108] After obtaining the preprocessed execution result, the data processing end of the log analysis server can analyze the execution result and generate the next parsing command based on the analysis result. For example, when parsing a core dump file, the stack information result is output to the data processing end, and the file name and corresponding line number of the core dump file where the failure occurred are filtered out in the stack information, and the corresponding code is searched in the code library to obtain the variable information contained in the line of code, including the variable name and variable type, and the information is passed to the storage engine (cmd engine).

[0109] After receiving the information transmitted by the data processing end, the storage engine of the log analysis server generates a new analysis command based on the transmitted information, stores the command, and transmits it to the server for iterative analysis. For example, the variable type transmitted by the data processing end determines whether to use the print variable command or the print structure type command, and then splices the command with the variable information and transmits it to the server for the next round of analysis.

[0110] The log analysis server can output the analysis results corresponding to each target parsed data by iteratively analyzing each target parsed data.

[0111] In the embodiment of the present application, after the log analysis server generates the analysis results corresponding to each target parsed data, it can also push the analysis results corresponding to each target parsed data to the quality monitoring end. For the user, the user can access the analysis results through the browser, for example, by logging into the quality monitoring webpage, entering the file name of the dump file, and obtaining the analysis results of the dump file, wherein the analysis results include but are not limited to call stack information, current register usage and other related information. The specific content of the analysis results pushed to the quality monitoring end can be found in Figure 8 shown.

[0112] In a possible implementation, the log analysis server can also obtain the operating data of the BMC under test, such as memory information, CPU usage, and reboot reason information (Reboot info) of the BMC under test. Then, a comprehensive analysis report is generated based on the operating data of the BMC under test, and the comprehensive analysis report is pushed to the quality monitoring end or the operation and maintenance personnel. Specifically, the log analysis server can send the operation and maintenance personnel who have subscribed to the operating information of the BMC under test via email or text message, so that the operation and maintenance personnel can perform fault repair on the abnormal BMC based on the comprehensive analysis report.

[0113] In summary, the traditional dump file analysis method is usually performed manually, the analysis rate is low and there is no analysis method for kernel dump files; the present application performs stress tests on multiple tested baseboard management controllers BMCs, collects crash test data (kernel dump files and core dump files) generated by multiple tested BMC kernel or application layer code failures; and according to the data level to which the crash test data belongs, selects the target parsing rule corresponding to the data level of the crash test data for parsing, and obtains each target parsing data; then iteratively analyzes each target parsing data; in the stress test scenario, it is possible to perform a more detailed analysis of a large amount of crash test data generated by BMC failures, and improve the analysis rate of crash test data. By pushing the crash test data to the quality monitoring end or the operation and maintenance personnel, the operation and maintenance personnel can more intuitively determine whether it is a kernel failure or an application layer code failure, locate the fault problem in a timely manner, and repair the faulty BMC.

[0114] To facilitate understanding of this solution, the following briefly describes the overall process of analyzing crash memory information caused by kernel or application layer code errors:

[0115] Perform stress test on the BMC under test: The compile server compiles the test version firmware, retains the symbol table information of the test version firmware, reads the configuration file of the BMC under test, updates the test version firmware to the BMC under test, and performs stress test on the BMC under test.

[0116] Obtain crash test data sets generated by kernel or application layer code errors of multiple BMCs under test: after the stress test is completed, access the target BMC through the device identifier (IP) of the BMC under test. If the access is successful, enter the directory of the target BMC, and determine whether there is crash memory information of the kernel failure in the first preset directory of the target BMC. If so, forward the crash memory information to the crash test data set; if not, determine whether there is a core dump file in the second preset directory of the target BMC. When it is determined that there is a core dump file, transfer the core dump file to the crash test data set; when it is determined that there is no core dump file, access the next target BMC among the multiple BMCs under test, and obtain the crash test data set after polling each of the multiple BMCs under test.

[0117] The crash test data in the crash test data set are classified and stored: first, the crash test data are classified according to the test time, and the crash test data with the same test time are stored in the log storage server directory 202x_xx_xx; then, the crash test data are classified according to the IP address of the BMC under test, and the crash test data belonging to the same IP address (BMC under test) are stored in the directory BMC_IP; finally, according to the data layer to which the crash test data belongs, the crash test data (kernel dump file) belonging to the kernel layer is stored in the log storage server directory kdump, and the crash test data (core dump file) belonging to the application layer is stored in the log storage server directory corefiles, so as to obtain the classified crash test data set.

[0118] Parsing the kernel dump file: Filter out multiple directories named with BMC_IP where kernel dump files exist from the crash test data set, determine the firmware version of the target directory (determine the firmware version of the target BMC that generates the kernel dump file) for a target directory among the multiple directories named with BMC_IP where kernel dump files exist, determine whether there is a target kernel image version corresponding to the firmware version of the target BMC in the preset kernel image version set, if so, obtain the image version time of the target kernel image version, enter the target directory, obtain the firmware version time of the kernel dump file, and when it is determined that the image version time is the same as the firmware version time, call the kernel dump file analysis tool to parse the kernel dump file; if not, send a prompt message that the kernel dump file parsing fails to the terminal device.

[0119] Parsing the core dump file: screening out multiple directories named with BMC_IP where core dump files exist from the crash test data set, determining the firmware version of the target directory (determining the firmware version of the target BMC that generates the core dump file) for a target directory among the multiple directories named with BMC_IP where core dump files exist, determining whether a target symbol table corresponding to the firmware version of the target BMC exists in a preset symbol table set, if so, entering the target directory, obtaining the core dump file in the directory and crash indication information of the core dump file, and when determining that the crash indication information is a crash process name, calling a GDB tool to parse the core dump file according to the crash process name, if not, sending a second prompt message indicating that the core dump file parsing fails to the terminal device.

[0120] Iterative analysis of kernel dump files and core dump files: set relevant configuration sets for the analysis tool, use the analysis tool to enter the analysis interface, execute the commands provided by the configuration set, obtain the execution results, preprocess the execution results, send the preprocessed execution results to the data handler, and continue to wait for the next analysis command; the data handler analyzes the execution results and generates the next parsing command based on the analysis results; after receiving the information transmitted by the data handler, the storage engine generates a new analysis command based on the transmitted information, stores the command, and transmits it to the server for iterative analysis.

[0121] Push the analysis result of the dump file to the quality monitoring end: Push the analysis result of the dump file to the quality monitoring end. For users, the users can obtain the analysis result through a browser, for example, by logging in to the quality monitoring webpage and entering the file name of the dump file to obtain the analysis result of the dump file; or generate a comprehensive analysis report based on the operation data of the tested BMC, for example, the memory information, CPU usage and restart reason information (Reboot info) of the tested BMC, and push the comprehensive analysis report to the quality monitoring end or operation and maintenance personnel, so that the operation and maintenance personnel can repair the abnormal BMC based on the comprehensive analysis report.

[0122] Based on the method provided in the above embodiment, the present application embodiment also provides a data analysis device, such as Fig. 9 The figure is a schematic diagram of the structure of a data analysis device in an embodiment of the present application, the device comprising:

[0123] The data acquisition module 901 is used to acquire a crash test data set for performing stress tests on multiple baseboard management controllers BMC under test;

[0124] The data parsing module 902 is used to select a target parsing rule corresponding to the data level from the parsing rule set based on the data level to which each crash test data in the crash test data set belongs, and parse each crash test data based on the target parsing rule to obtain each target parsed data;

[0125] The data analysis module 903 is used to perform iterative analysis on each of the target parsed data and output the analysis results corresponding to each of the target parsed data.

[0126] Based on the same inventive concept, an electronic device is also provided in the embodiment of the present application, and the electronic device can realize the functions of the aforementioned data analysis device, referring to Fig.10 , the electronic device comprises:

[0127] At least one processor 1001, and a memory 1002 connected to the at least one processor 1001. The specific connection medium between the processor 1001 and the memory 1002 is not limited in the embodiment of the present application. Fig.10 In the example, the processor 1001 and the memory 1002 are connected via the bus 1000. Fig.10 The connections between other components are shown in bold lines, and are not intended to be limiting. The bus 1000 can be divided into an address bus, a data bus, a control bus, etc. For ease of representation, Fig.10 Only one thick line is used in the figure, but it does not mean that there is only one bus or one type of bus. Alternatively, the processor 1001 can also be called a controller, and there is no limitation on the name.

[0128] In the embodiment of the present application, the memory 1002 stores instructions that can be executed by at least one processor 1001. The at least one processor 1001 can execute the data analysis method discussed above by executing the instructions stored in the memory 1002. The processor 1001 can implement Fig. 9 The functions of each module in the device shown.

[0129] Among them, processor 1001 is the control center of the device, and can use various interfaces and lines to connect various parts of the entire control device. By running or executing instructions stored in memory 1002 and calling data stored in memory 1002, various functions of the device and processing data, the device can be monitored as a whole.

[0130] In one possible design, the processor 1001 may include one or more processing units, and the processor 1001 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs, and the modem processor mainly processes wireless communications. It is understandable that the modem processor may not be integrated into the processor 1001. In some embodiments, the processor 1001 and the memory 1002 may be implemented on the same chip, and in some embodiments, they may also be implemented separately on separate chips.

[0131] Processor 1001 can be a general-purpose processor, such as a central processing unit (CPU), a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, and can implement or execute the various methods, steps and logic block diagrams disclosed in the embodiments of the present application. A general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the data analysis method disclosed in the embodiments of the present application can be directly embodied as a hardware processor to be executed, or a combination of hardware and software modules in the processor can be executed.

[0132] The memory 1002 is a non-volatile computer-readable storage medium that can be used to store non-volatile software programs, non-volatile computer executable programs and modules. The memory 1002 may include at least one type of storage medium, such as a flash memory, a hard disk, a multimedia card, a card-type memory, a random access memory (Random Access Memory, RAM), a static random access memory (Static Random Access Memory, SRAM), a programmable read-only memory (Programmable Read Only Memory, PROM), a read-only memory (Read Only Memory, ROM), an electrically erasable programmable read-only memory (Electrically Erasable Programmable Read-Only Memory, EEPROM), a magnetic memory, a disk, an optical disk, etc. The memory 1002 is any other medium that can be used to carry or store a desired program code in the form of an instruction or data structure and can be accessed by a computer, but is not limited thereto. The memory 1002 in the embodiment of the present application can also be a circuit or any other device that can realize a storage function, for storing program instructions and / or data.

[0133] By designing and programming the processor 1001, the code corresponding to the data analysis method described in the above embodiment can be fixed into the chip, so that the chip can execute the code when running. Figure 1The steps of the data analysis method of the embodiment shown are as follows: How to design and program the processor 1001 is a technique known to those skilled in the art and will not be described in detail here.

[0134] Based on the same inventive concept, an embodiment of the present application further provides a storage medium, which stores computer instructions. When the computer instructions are executed on a computer, the computer executes the data analysis method discussed above.

[0135] In some possible implementations, various aspects of the data analysis method provided by the present application may also be implemented in the form of a program product, which includes program code. When the program product is run on an apparatus, the program code is used to enable the control device to execute the steps of the data analysis method according to various exemplary implementations of the present application described above in this specification.

[0136] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented in one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) that include computer-usable program code.

[0137] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0138] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce an article of manufacture comprising an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0139] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for implementing the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0140] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A data analysis method, It is characterized in that include: Obtain a crash test data set for stress testing multiple baseboard management controllers (BMCs) under test; Based on the data level to which each crash test data in the crash test data set belongs, selecting a target parsing rule corresponding to the data level from a parsing rule set, and parsing each crash test data based on the target parsing rule to obtain each target parsed data; Iteratively analyze each of the target parsed data, and output the analysis results corresponding to each of the target parsed data.

2. The method according to claim 1, It is characterized in that The step of obtaining a crash test data set for performing stress tests on multiple BMCs under test includes: Accessing any target BMC among the multiple tested BMCs; Determine whether there is crash memory information generated by a kernel failure in the first preset directory of the target BMC; If yes, transferring the crash memory information to the crash test data set; If not, the core dump file in the second preset directory of the target BMC is transferred to the crash test data set.

3. The method according to claim 2, It is characterized in that The transferring the core dump file in the second preset directory of the target BMC to the crash test data set includes: Determine whether the core dump file exists in the second preset directory of the target BMC; If yes, transferring the core dump file to the crash test data set; If not, then access the next target BMC among the multiple tested BMCs until each BMC among the multiple tested BMCs is polled.

4. The method according to claim 1, It is characterized in that If the data layer to which the crash test data belongs is the kernel layer, the crash test data is parsed using the following target parsing rules: Determine a firmware version of a target BMC that generates the crash test data; Determine whether there is a target kernel image version corresponding to the firmware version in a preset kernel image version set, wherein the kernel image version in the kernel image version set represents an uncompressed version after kernel compilation of the tested BMC; If yes, then obtaining the image version time of the target kernel image version and the firmware version time of the crash test data, and when determining that the image version time is the same as the firmware version time, calling a kernel dump file analysis tool to parse the crash test data; If not, the first prompt information is output.

5. The method according to claim 1, It is characterized in that If the data layer to which the crash test data belongs is the application layer, the crash test data is parsed using the following target parsing rules: Determine a firmware version of a target BMC that generates the crash test data; Determine whether there is a target symbol table corresponding to the firmware version in the symbol table set, wherein the symbol table set is generated when compiling the firmware of the plurality of BMCs under test, and each firmware version of the BMC under test corresponds to a symbol table version; If yes, then acquiring crash indication information in the crash test data, and parsing the crash test data based on the crash indication information; If not, the second prompt message is output.

6. The method according to claim 5, It is characterized in that The crash indication information includes a crash process name or a crash thread name. If the crash thread name in the crash test data is obtained, parsing the crash test data based on the crash indication information includes: Searching the crash process name associated with the crash thread name in the thread statistics table; Based on the crash process name, a program debugging tool GDB is called to parse the crash test data.

7. The method according to claim 1, It is characterized in that After outputting the analysis results corresponding to each of the target parsed data, the method further includes: Pushing the analysis results corresponding to each of the target parsed data to the quality monitoring end; or Based on the operation data of the tested BMC, a comprehensive analysis report is generated, and the comprehensive analysis report is pushed to the quality monitoring end or the operation and maintenance personnel, so that the operation and maintenance personnel can repair the abnormal BMC based on the comprehensive analysis report, wherein the operation data at least includes the memory information, CPU status information and restart information of the tested BMC.

8. A data analysis device, It is characterized in that include: A data acquisition module is used to acquire a crash test data set for stress testing of multiple baseboard management controllers (BMCs) under test; A data parsing module, configured to select a target parsing rule corresponding to the data level from a parsing rule set based on the data level to which each crash test data in the crash test data set belongs, and parse each crash test data based on the target parsing rule to obtain each target parsed data; The data analysis module is used to iteratively analyze each of the target parsed data and output the analysis results corresponding to each of the target parsed data.

9. An electronic device, It is characterized in that include: Memory, used to store computer programs; A processor, configured to implement the steps of the method according to any one of claims 1 to 7 when executing the computer program stored in the memory.

10. A computer-readable storage medium, It is characterized in that The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Citation Information

Patent Citations

  • Fault analysis method and system for Linux operating system

    CN114706708A

  • Test method and system, test platform and test machine

    CN115756914A

  • Application crash analysis method and device

    CN115756934A

  • Processor information processing method and device, storage medium and electronic equipment

    CN117493065A

  • Kernel crash information capturing method and device, equipment and storage medium

    CN117931494A