Fault analysis method and device, electronic equipment and storage medium

Abstract

The invention provides a fault analysis method and device, electronic equipment and a storage medium, and belongs to the technical field of computers.The method comprises the steps that running state information of first equipment is monitored, and if the running state information represents that the first equipment breaks down, target fault data corresponding to the first equipment are obtained through second equipment, the fault reason of the first device is determined based on the target fault data, the first device and the second device are interconnected through the target connection, the second device obtains and stores device operation data of the first device through the target connection, and the device operation data comprises the target fault data; the device operation data is stored in a specified storage area of a target storage space corresponding to the target connection in the second device, and the specified storage area is smaller than the target storage space. The target fault data is the data synchronously collected by the second equipment when the first equipment breaks down, and the fault state of the first equipment can be accurately reflected, so that the fault analysis efficiency and accuracy are improved by adopting the method.

Description

Technical Field

[0001] The present application relates to the field of chip technology, and in particular to a fault analysis method, device, electronic device and storage medium. Background Art

[0002] The stable operation of the server is the basis for ensuring business continuity and data security. Therefore, it is very important to obtain fault data in time to determine the cause of the failure when the server fails. Server failures usually include motherboard hardware failures, system failures, CPU failures, and component failures. Among them, CPU failure data and system failure data are crucial for analyzing the cause of server failures.

[0003] At present, the method of server fault troubleshooting is mainly to develop machines to simulate the server environment to reproduce the phenomenon of server failure, obtain fault data, and analyze the cause of the failure based on the fault data. However, this method is not only time-consuming and inefficient, but also because it is difficult to completely restore the reproduced fault, resulting in inaccurate fault data, which in turn affects the accuracy of server fault troubleshooting. Summary of the invention

[0004] The present application provides a fault analysis method, device, electronic device and storage medium.

[0005] According to a first aspect of the present application, a fault analysis method is provided, the method comprising: Monitoring the operation status information of the first device; If the operation status information indicates that the first device has a fault, target fault data corresponding to the first device is obtained through a second device, wherein the first device and the second device are interconnected through a target connection, the second device obtains and stores device operation data of the first device through the target connection, the device operation data includes the target fault data, and the device operation data is stored in a designated storage area of ​​a target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space; A failure cause of the first device is determined based on the target failure data.

[0006] In one possible implementation, the target connection is a graphic data transmission interface; the device operation data includes system operation data of the first device; the operating system of the first device collects system operation data at a first preset period, and sends the collected system operation data to the second device through the graphic data transmission interface, and the second device stores the received system operation data to the designated storage area.

[0007] In one possible implementation, when there is no free storage space in the designated storage area, the second device clears data in the designated storage area that has been stored for longer than a preset time period, and stores newly received system operation data in the designated storage area.

[0008] In one possible implementation, the target connection is a communication interface; the device operation data includes CPU fault data of the first device; the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data to the designated storage area.

[0009] In one possible implementation manner, the second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device.

[0010] In one possible implementation manner, obtaining target fault data corresponding to the first device through the second device includes: sending a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, wherein the device log data includes the device operation data stored in the designated storage area; receiving the device log data sent by the second device through the preset communication connection; The device operation data corresponding to the fault time period of the first device is determined as target fault data through the device log data.

[0011] In one possible implementation manner, the second device is a baseboard management controller, and the baseboard management controller is deployed in the first device.

[0012] According to a second aspect of the present application, a fault analysis device is provided, the device comprising: A status monitoring module, used to monitor the operating status information of the first device; a fault data acquisition module, configured to acquire target fault data corresponding to the first device through a second device if the operation status information indicates that the first device has a fault, wherein the first device and the second device are interconnected through a target connection, the second device acquires and stores device operation data of the first device through the target connection, the device operation data includes the target fault data, and the device operation data is stored in a designated storage area of ​​a target storage space corresponding to the target connection in the second device, the designated storage area being smaller than the target storage space; A fault analysis module is used to determine a fault cause of the first device based on the target fault data.

[0013] In one possible implementation, the target connection is a graphic data transmission interface; the device operation data includes system operation data of the first device; the operating system of the first device collects system operation data at a first preset period, and sends the collected system operation data to the second device through the graphic data transmission interface, and the second device stores the received system operation data to the designated storage area.

[0014] In one possible implementation, when there is no free storage space in the designated storage area, the second device clears data in the designated storage area that has been stored for longer than a preset time period, and stores newly received system operation data in the designated storage area.

[0015] In one possible implementation, the target connection is a communication interface; the device operation data includes CPU fault data of the first device; the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data to the designated storage area.

[0016] In one possible implementation manner, the second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device.

[0017] In one possible implementation mode, the fault data acquisition module is specifically used to send a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, and the device log data includes the device operation data stored in the designated storage area; receive the device log data sent by the second device through the preset communication connection; and determine the device operation data corresponding to the fault time period of the first device as the target fault data through the device log data.

[0018] In one possible implementation manner, the second device is a baseboard management controller, and the baseboard management controller is deployed in the first device.

[0019] According to a third aspect of the present application, an electronic device is provided, including: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the electronic device communicates with a second device via a preset communication connection, and the processor implements the method described in the present application when executing the computer program.

[0020] According to a fourth aspect of the present application, a storage medium containing computer executable instructions is provided, and when the computer executable instructions are executed by a computer processor, they are used to execute the method described in the present application.

[0021] The fault analysis method provided in the embodiment of the present application is adopted to monitor the operation status information of the first device. If the operation status information indicates that the first device has a fault, the target fault data corresponding to the first device is obtained through the second device, and the fault cause of the first device is determined based on the target fault data, wherein the first device and the second device are interconnected through the target connection, and the second device obtains and stores the device operation data of the first device through the target connection, and the device operation data includes the target fault data. The device operation data is stored in the designated storage area of ​​the target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space. That is, in the embodiment of the present application, the device operation data of the first device can be collected by the second device. When the first device fails, the device operation data collected by the second device may include the fault data of the first device. Therefore, the target fault data related to the fault of the first device can be obtained by the operation data of the first device collected by the second device, and then the fault cause of the first device can be determined. In the embodiment of the present application, the target fault data is the data synchronously collected by the second device when the first device fails, which can accurately reflect the fault state of the first device. Therefore, analyzing the cause of the fault by analyzing the target fault data can not only improve the efficiency of fault analysis, but also improve the accuracy of fault analysis.

[0022] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present application, nor is it intended to limit the scope of the present application. Other features of the present application will become easily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] By reading the detailed description below with reference to the accompanying drawings, the above and other purposes, features and advantages of the exemplary embodiments of the present application will become readily understood. In the accompanying drawings, several embodiments of the present application are shown in an exemplary and non-limiting manner, wherein: In the drawings, the same or corresponding reference numerals represent the same or corresponding parts.

[0024] Figure 1 A schematic diagram of an implementation flow of a fault analysis method provided in an embodiment of the present application is shown; Figure 2 Another implementation flow diagram of the fault analysis method provided in the embodiment of the present application is shown; Figure 3 A schematic diagram of the structure of a fault analysis device provided in an embodiment of the present application is shown; Figure 4 A schematic diagram of the structure of an electronic device according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0025] In order to make the purpose, features, and advantages of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.

[0026] Since the current server fault troubleshooting methods are inefficient and inaccurate, in order to improve the efficiency and accuracy of server fault troubleshooting, the present application provides a fault analysis method, device, electronic device and storage medium. The electronic device provided in the present application can be a mobile phone, computer, tablet computer, server management device and other devices.

[0027] The technical solution of the embodiment of the present application will be described below in conjunction with the drawings in the embodiment of the present application.

[0028] Figure 1 A schematic diagram of an implementation flow of the fault analysis method provided in an embodiment of the present application is shown. Figure 1 As shown, the method includes: S101, monitoring operating status information of a first device.

[0029] In the embodiment of the present application, the first device may be a server. The first device may also be a computer, a mobile phone, or other device. The running status information of the first device includes the running status information of the first device, which may include the CPU status data, memory status data, disk status data, device load status data, device hardware status data, device running services and process status data, and device log data of the first device. For example, the CPU status data may include the CPU usage rate and load balancing data, the memory status data may include the memory usage rate and cache usage, the disk status data may include the disk available space and the disk read and write status, the device load status data may include the total system load and the system load average, the device hardware status data may include the CPU temperature and the power-on status, the device running services and process status data may include the number of normally running processes and services and the number of crashed processes and services, and the device log data may include the error log of the operating system and the log data of each application deployed on the first device.

[0030] In an embodiment of the present application, if the electronic device is a server management device, the first device is a server. The server can generally be deployed on a rack in a computer room far away from the office area. If a server fails, the manager may not be able to debug the server on site due to the long distance. For this scenario, the manager can remotely monitor the running status of the server through the server management device. In a possible implementation, the server may include a baseboard management controller (BMC, Baseboard Management Controller), and the baseboard management controller can monitor the status of each hardware component of the server. For example, the baseboard management controller can monitor the power-on status of the server, the CPU temperature and fan speed of the server, etc. The server management device can access the baseboard management controller through the baseboard management controller interface, and then obtain the monitoring data of the baseboard management controller as the running status information of the server. The BMC can also determine whether the various hardware components of the server are abnormal based on the status of the various hardware components of the server obtained by monitoring. For example, if the CPU temperature is monitored to be higher than the preset temperature threshold, the baseboard management controller can generate a message that the CPU temperature of the server is abnormal. The server management device can also obtain information on whether the various hardware components of the server are abnormal through the baseboard management controller interface as the running status information of the server. The preset temperature threshold can be set according to the actual application scenario.

[0031] In the embodiment of the present application, the electronic device may also collect and analyze the system log file of the first device through a log monitoring tool, and the analysis result of the log file may include the operating status information of the server.

[0032] S102, if the operating status information indicates that the first device has a fault, target fault data corresponding to the first device is obtained through the second device, wherein the first device and the second device are interconnected through a target connection, and the second device obtains and stores device operating data of the first device through the target connection, and the device operating data includes the target fault data, and the device operating data is stored in a designated storage area of ​​the target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space.

[0033] In the embodiment of the present application, the second device may be a baseboard management controller or an integrated management controller, etc. The target connection may include a graphics data transmission interface and / or a communication interface, etc. The target fault data may include operating system fault data and / or CPU fault data of the first device, etc.

[0034] S103: Determine a fault cause of the first device based on the target fault data.

[0035] In the embodiment of the present application, the fault type of the first device included in the target fault data can be analyzed. For example, it can be queried whether the target fault data includes power fault data, disk fault data and / or CPU fault data of the first device. If power fault data, disk fault data and / or CPU fault data are queried, it can be determined that the first device has a hardware fault. For example, if the query target fault data includes data such as program errors and / or virus infections, it can be determined that the first device has a software fault; if the query target fault data includes data such as network connection interruption, it can be determined that the first device has a network connection fault.

[0036] In an embodiment of the present application, if the electronic device is a server management device, the first device is a server. If the server is down, the target fault data includes data characterizing that the server temperature is too high, such as data such as a high temperature alarm or a high temperature warning instruction. The server management device can determine that there is a hardware fault in the server based on the data characterizing that the server temperature is too high. The server management device can query the temperature-related data in the target fault data and analyze the causes of the high temperature of the server. For example, if the CPU temperature data is found to be higher than the preset temperature threshold, it can be determined that the cause of the fault is that the server is down due to the high CPU temperature. The server management device can also determine the corresponding fault solution based on the cause of the fault. For example, if the cause of the fault is that the server is down due to the high CPU temperature, the server management device can determine that the corresponding fault solution is: restart the server after the server temperature drops. For example, if the cause of the fault is that the CPU temperature is too high due to abnormal fan speed, causing the server to crash, the server management device can determine that the corresponding fault solution is: restart the server after replacing the fan.

[0037] The fault analysis method provided in the embodiment of the present application is adopted to monitor the operation status information of the first device. If the operation status information indicates that the first device has a fault, the target fault data corresponding to the first device is obtained through the second device, and the fault cause of the first device is determined based on the target fault data, wherein the first device and the second device are interconnected through the target connection, and the second device obtains and stores the device operation data of the first device through the target connection, and the device operation data includes the target fault data. The device operation data is stored in the designated storage area of ​​the target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space. That is, in the embodiment of the present application, the device operation data of the first device can be collected by the second device. When the first device fails, the device operation data collected by the second device may include the fault data of the first device. Therefore, the target fault data related to the fault of the first device can be obtained by the operation data of the first device collected by the second device, and then the fault cause of the first device can be determined. In the embodiment of the present application, the target fault data is the data synchronously collected by the second device when the first device fails, which can accurately reflect the fault state of the first device. Therefore, analyzing the cause of the fault by analyzing the target fault data can not only improve the efficiency of fault analysis, but also improve the accuracy of fault analysis.

[0038] In an embodiment of the present application, the second device may be a baseboard management controller, and the baseboard management controller may be deployed in the first device. For example, if the first device is a server, the baseboard management controller may be deployed on the server motherboard. The baseboard management controller may be interconnected with the operating system (OS) of the server through a video graphics array (VGA) interface, and the baseboard management controller may communicate with the CPU of the server through a serial communication (I2C) bus.

[0039] In an embodiment of the present application, the baseboard management controller can be used to monitor and manage the first device. For example, the baseboard management controller can manage the device attribute information of the first device. The device attribute information may include the model, manufacturer, production date and production attribute information of each component of the first device. The baseboard management controller can also record information such as the baseboard management controller's own server host name, IP address and baseboard management controller firmware version.

[0040] The baseboard management controller can manage the device status of the first device. For example, the baseboard management controller can monitor the temperature and voltage status of each hardware component of the server, such as the CPU, memory, hard disk and fan. The baseboard management controller can collect the temperature of each hardware component and adjust the fan speed to prevent the first device from overheating. The baseboard management controller can also control the power consumption of the first device to prevent the first device from consuming too much power. If an abnormality occurs in the hardware component of the first device, the baseboard management controller can send information about the abnormality of the hardware component of the first device to the second device through a communication connection with the second device. The communication connection may include an I2C communication connection or a network management protocol (SNMP, Simple Network Management Protocol) connection, etc.

[0041] The baseboard management controller can be connected to the server management device so that the server management device can remotely manage the first device through the baseboard management controller. For example, the server management device can remotely control the first device to start, shut down, restart, maintain, update firmware, and install the system through the baseboard management controller. The baseboard management controller can also manage the log files, user information, BIOS management, and alarm management of the first device to ensure the stable operation of the first device.

[0042] In an embodiment of the present application, the target connection may be a graphics data transmission interface; the device operation data may include system operation data of the first device; the operating system of the first device collects system operation data every first preset period, and sends the collected system operation data to the second device through the graphics data transmission interface, and the second device stores the received system operation data to the designated storage area.

[0043] The first preset period can be set to 30 seconds or 1 minute, etc. The first device can transmit image data and system operation data to the second device through the graphic data transmission interface. The second device can store the image data and system operation data transmitted by the first device through the second device in the target storage space. Specifically, the system operation data can be stored in a designated storage area of ​​the target storage space. The designated storage area can be a designated storage unit in a preset target storage space. In a possible implementation, the target storage space can be a storage space corresponding to the graphic data transmission interface in the memory of the second device. For example, the size of the storage space corresponding to the graphic data transmission interface in the memory of the second device is 64Mb. Any 1Mb or any 2Mb storage unit of the storage space corresponding to the graphic data transmission interface in the memory of the second device can be designated as the designated storage area, and the second device can store the system operation data sent by the first device to the designated storage area.

[0044] In a possible implementation, when the first device sends system operation data of the first device to the second device through a graphic data transmission interface, if an image data transmission instruction is received, the first device may suspend sending the system operation data and wait for the image data transmission to be completed. The first device may continue to send the system operation data of the first device to the second device through the graphic data transmission interface.

[0045] In a possible implementation, if the first device is a server and the second device is a baseboard management controller, the baseboard management controller and the operating system of the server can be interconnected through a physical VGA interface. The storage address size of the VGA interface mapped in the memory of the baseboard management controller is 64Mb. Any 1Mb of the 64Mb storage address mapped by the VGA interface in the memory of the baseboard management controller can be preset as a designated storage area. The operating system of the server can send system operation data to the baseboard management controller through the VGA interface every 1 minute or 30 seconds, and the baseboard management controller stores it in the designated storage area.

[0046] For example, if the interface name of the VGA interface in the baseboard management controller is / dev / vgasharedmem, and the interface name of the VGA interface in the server is / dev / vgamem, the script get_os_error.sh can be configured in the server. The script get_os_error.sh can be set to automatically copy the system fault file of the operating system as system operation data every 1 minute when the server is powered on and enters the operating system, and locate the VGA interface according to the interface name / dev / vgasharedmem and the interface name / dev / vgamem, and send the copied system operation data to the baseboard management controller through the VGA interface. The baseboard management controller can store the received system operation data in the designated storage area.

[0047] In a possible implementation, when there is no free storage space in the designated storage area, the second device clears the data in the designated storage area that has been stored for longer than a preset time period, and stores the newly received system operation data in the designated storage area. The preset time period may be set to be longer than or equal to the first preset period or the second preset period.

[0048] In the embodiment of the present application, the size of the designated storage area is fixed. When there is no free storage space in the designated storage area, if the second device receives new system operation data, the second device can clear the data stored in the designated storage area for the longest time, and then store the new system operation data in the free area of ​​the designated storage area. The storage space occupied by the cleared data must be greater than or equal to the storage space required by the new system operation data.

[0049] In an embodiment of the present application, when the size of the designated storage area is fixed, the second device can write new system operation data by clearing some data that has been stored in the designated storage area for a long time, which not only saves the storage space of the second device but also realizes the function of collecting the system operation data of the first device.

[0050] In an embodiment of the present application, the target connection may be a communication interface; the device operation data includes CPU fault data of the first device; the second device collects CPU fault data of the first device through the communication interface at a second preset period, and stores the collected CPU fault data in the designated storage area. The second preset period may be set according to actual application requirements, for example, to 5 minutes or 10 minutes, etc. For example, the target connection may be an I2C communication interface.

[0051] In an embodiment of the present application, a service process may be added to the second device, and the service process is used to collect the CPU fault data of the first device through the I2C communication interface every second preset period, and store the collected CPU fault data of the first device in a designated storage area. Alternatively, the second device may be controlled by a remote management device to collect the CPU fault data of the first device, and store the collected CPU fault data of the first device in a designated storage area. For example, a service process may be added to the remote management device, and the service process is used to control the second device to collect the CPU fault data of the first device through the I2C communication interface every second preset period after the second device is started, and store the collected CPU fault data of the first device in a designated storage area.

[0052] In a possible implementation, the second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device. If the first device is a server, the second device is a baseboard management controller. The CPU is one of the core components of the server. The performance of the CPU is related to the processing power and response speed of the server. Therefore, collecting CPU fault data is crucial for server fault analysis. The baseboard management controller and the CPU of the server can communicate through the I2C communication interface. A process get_cpuRegs can be added to the baseboard management controller, and the process get_cpuRegs is used to obtain CPU register information once every ten minutes through the I2C communication interface. The CPU register information may include CPU operating status data and CPU fault data. For example, the baseboard management controller can read the CPU's MSRO000_0179_MCG_CAP and obtain the number of register groups related to the machine check architecture (MCA) of the CPU. The baseboard management controller can read the starting address of the CPU's MCA register as: MSR_c000_2000, and the reading end address is: MSR_cO00_2000+( The MCA register address range is obtained by reading the start address and end address of the MCA register. The baseboard management controller can also obtain the definition information of the MCA register group by reading the Platform Power Register (PPR) document. The register information can also include data such as CPU usage and CPU load.

[0053] The baseboard management controller can write the acquired CPU register information into the CPU fault log file cpu_mcaregs.log, and store the fault log file cpu_mcaregs.log into a designated storage area in the memory of the baseboard management controller. The designated storage area can be any 1Mb of the 64Mb storage address mapped by the VGA interface in the memory of the baseboard management controller.

[0054] In a possible implementation, when there is no free storage space in the designated storage area, the second device clears data in the designated storage area that has been stored for longer than a preset time period, and stores newly received CPU fault data in the designated storage area.

[0055] In the embodiment of the present application, the size of the designated storage area is fixed. When there is no free storage space in the designated storage area, if new CPU fault data is received, the second device can clear the portion of data that has been stored in the designated storage area for the longest time, and then store the new CPU fault data in the empty area in the designated storage area. The size of the storage space occupied by the cleared data must be greater than or equal to the size of the storage space required for the new system operation data. In the embodiment of the present application, the second device can continuously write new system operation data by clearing part of the data in the designated storage area, which not only saves the storage space of the second device, but also can continuously collect the CPU fault data of the first device for fault analysis and processing of the first device.

[0056] In the embodiment of the present application, the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data in a designated storage area, which can be used to evaluate the performance of the first device and analyze the failure of the first device. By collecting the CPU fault data, the management personnel can understand the performance status of the first device, and help the management personnel determine whether the first device is in normal working condition or whether a performance upgrade is required. When the first device fails, the CPU fault data collected by the second device can reflect the CPU fault of the first device, so that the management personnel can locate the source of the failure of the first device and formulate a reasonable fault handling plan.

[0057] In an embodiment of the present application, the electronic device can visualize the system operation data and / or CPU fault data collected by the second device, so that the management personnel can intuitively obtain the fault status of the first device. For example, the system operation data of the first device may include the number of threads, thread status, system memory usage, disk usage, I / O request queue, network connection status and system configuration data of the first device. The number of threads, thread status, system memory usage, disk usage, I / O request queue, network connection status and system configuration data can be displayed on the display in the form of a table for the management personnel to view.

[0058] The CPU fault data may include CPU usage, CPU load, the number of MCA registers of the CPU, and configuration information of the MCA registers, etc. The electronic device may also display the data such as CPU usage, CPU load, the number of MCA registers of the CPU, and configuration information of the MCA registers on the display in a table form for easy viewing by management personnel.

[0059] In one possible implementation, Figure 2 FIG. 2 shows another implementation flow diagram of the fault analysis method provided in the embodiment of the present application. Figure 2As shown, the acquiring target fault data corresponding to the first device through the second device includes: S201, sending a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, and the device log data includes the device operation data stored in the designated storage area.

[0060] The preset communication connection may include an I2C communication connection.

[0061] In the embodiment of the present application, when the operating status information of the first device is monitored to indicate that the first device has a fault, for example, the first device is detected to be down, the electronic device can generate a target fault data acquisition instruction and send it to the second device. The target fault data acquisition instruction may include information such as the time when the first device has a fault.

[0062] In the embodiment of the present application, the device operation data also includes a time mark, which is used to characterize the time when the first device generated the device operation data. The second device can generate device log data from all device operation data and device log files stored in the designated storage area according to the target fault data acquisition instruction, or can generate device log data from the device operation data and device log files in the data stored in the designated storage area whose time mark is after the time when the first device fails according to the time when the first device fails. The second device can generate device log data from the device operation data and device log files through the HTTP protocol.

[0063] S202: Receive the device log data sent by the second device through the preset communication connection.

[0064] S203: Determine, through the device log data, device operation data corresponding to the fault time period of the first device as target fault data.

[0065] In the embodiment of the present application, the electronic device can obtain the device operation data with a time stamp within the fault time period of the first device as the target fault data according to the time stamp of the device operation data. Alternatively, all device operation data stored in the designated storage area can be used as the target fault data to compare and analyze the state of the first device before and after the fault occurs to determine the cause of the fault.

[0066] In the embodiment of the present application, the second device can actively collect the system operation data and CPU fault data of the first device, and support exporting the system operation data and CPU fault data by generating logs and sending them to the electronic device for analyzing the cause of the fault. Since the second device can store the collected system operation data and CPU fault data in the designated storage area in a circular overlay manner, that is, the data stored in the designated storage area is the latest data of the operation of the first device, including the complete system fault information and CPU register information of the first device, the system operation data and CPU fault data of the first device collected by the second device are used to analyze the cause of the fault, which can help managers quickly locate the fault problem and the cause of the fault. By adopting the fault analysis method provided in the embodiment of the present application, the server system fault data and CPU fault data can be exported through the baseboard management controller, which not only speeds up the efficiency of fault analysis, but also improves the accuracy of fault analysis.

[0067] Based on the same inventive concept, according to the fault analysis method provided in the above embodiment of the present application, correspondingly, another embodiment of the present application also provides a fault analysis device, whose structural schematic diagram is shown in FIG. Figure 3 As shown, specifically including: The status monitoring module 301 is used to monitor the operation status information of the first device; a fault data acquisition module 302, configured to acquire target fault data corresponding to the first device through a second device if the operation status information indicates that the first device has a fault, wherein the first device and the second device are interconnected through a target connection, the second device acquires and stores device operation data of the first device through the target connection, the device operation data includes the target fault data, and the device operation data is stored in a designated storage area of ​​a target storage space corresponding to the target connection in the second device, the designated storage area being smaller than the target storage space; The fault analysis module 303 is used to determine the fault cause of the first device based on the target fault data.

[0068] The fault analysis device provided in the embodiment of the present application is used to monitor the operation status information of the first device. If the operation status information indicates that the first device has a fault, the target fault data corresponding to the first device is obtained through the second device, and the fault cause of the first device is determined based on the target fault data, wherein the first device and the second device are interconnected through the target connection, and the second device obtains and stores the device operation data of the first device through the target connection, and the device operation data includes the target fault data. The device operation data is stored in the designated storage area of ​​the target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space. That is, in the embodiment of the present application, the device operation data of the first device can be collected by the second device. When the first device fails, the device operation data collected by the second device may include the fault data of the first device. Therefore, the target fault data related to the fault of the first device can be obtained by the operation data of the first device collected by the second device, and then the fault cause of the first device can be determined. In the embodiment of the present application, the target fault data is the data synchronously collected by the second device when the first device fails, which can accurately reflect the fault state of the first device. Therefore, analyzing the cause of the fault by analyzing the target fault data can not only improve the efficiency of fault analysis, but also improve the accuracy of fault analysis.

[0069] In one possible implementation, the target connection is a graphic data transmission interface; the device operation data includes system operation data of the first device; the operating system of the first device collects system operation data at a first preset period, and sends the collected system operation data to the second device through the graphic data transmission interface, and the second device stores the received system operation data to the designated storage area.

[0070] In one possible implementation, when there is no free storage space in the designated storage area, the second device clears data in the designated storage area that has been stored for longer than a preset time period, and stores newly received system operation data in the designated storage area.

[0071] In one possible implementation, the target connection is a communication interface; the device operation data includes CPU fault data of the first device; the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data to the designated storage area.

[0072] In one possible implementation manner, the second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device.

[0073] In one possible implementation, the fault data acquisition module 302 is specifically used to send a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, and the device log data includes the device operation data stored in the designated storage area; receive the device log data sent by the second device through the preset communication connection; and determine the device operation data corresponding to the fault time period of the first device as the target fault data through the device log data.

[0074] In one possible implementation manner, the second device is a baseboard management controller, and the baseboard management controller is deployed in the first device.

[0075] The fault analysis device provided in the embodiment of the present application is used to monitor the operation status information of the first device. If the operation status information indicates that the first device has a fault, the target fault data corresponding to the first device is obtained through the second device, and the fault cause of the first device is determined based on the target fault data, wherein the first device and the second device are interconnected through the target connection, and the second device obtains and stores the device operation data of the first device through the target connection, and the device operation data includes the target fault data. The device operation data is stored in the designated storage area of ​​the target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space. That is, in the embodiment of the present application, the device operation data of the first device can be collected by the second device. When the first device fails, the device operation data collected by the second device may include the fault data of the first device. Therefore, the target fault data related to the fault of the first device can be obtained by the operation data of the first device collected by the second device, and then the fault cause of the first device can be determined. In the embodiment of the present application, the target fault data is the data synchronously collected by the second device when the first device fails, which can accurately reflect the fault state of the first device. Therefore, analyzing the cause of the fault by analyzing the target fault data can not only improve the efficiency of fault analysis, but also improve the accuracy of fault analysis.

[0076] According to an embodiment of the present application, another embodiment of the present application further provides a server, wherein the server and the baseboard management controller are interconnected via a graphic data transmission interface. The server sends the system operation data to the baseboard management controller via the graphic data transmission interface, and the baseboard management controller stores the received system operation data in a designated storage area of ​​the corresponding target storage space in the memory of the baseboard management controller, wherein the designated storage area is smaller than the target storage space. The operating system of the server can collect the system operation data at every first preset period, and send the collected system operation data to the baseboard management controller via the graphic data transmission interface.

[0077] According to an embodiment of the present application, another embodiment of the present application further provides a baseboard management controller, wherein the baseboard management controller and the first device are interconnected through a graphic data transmission interface; the baseboard management controller can obtain and store system operation data of the first device through the graphic data transmission interface, and the system operation data is stored in a designated storage area of ​​the target storage space corresponding to the memory of the baseboard management controller, and the designated storage area is smaller than the target storage space.

[0078] In one possible implementation, the baseboard management controller obtains the system operation data from the operating system of the first device every first preset period.

[0079] In one possible implementation, when there is no free storage space in the designated storage area, the baseboard management controller clears data in the designated storage area that has been stored for longer than a preset time period, and stores newly received system operation data in the designated storage area.

[0080] In one possible implementation, the baseboard management controller and the first device communicate via a communication interface; the baseboard management controller collects CPU fault data of the first device via the communication interface every second preset period, and stores the collected CPU fault data in a designated storage area.

[0081] In one possible implementation, the baseboard management controller reads CPU register information of the first device through the communication interface as the CPU fault data of the first device.

[0082] In one possible implementation mode, the baseboard management controller sends a target fault data acquisition instruction to a receiving electronic device via a preset communication connection, and generates device log data based on the target fault data acquisition instruction, the device log data includes device operation data stored in a designated storage area, and sends the device log data to the electronic device via a preset communication connection, so that the electronic device determines the device operation data corresponding to the fault time period of the first device as the target fault data through the device log data.

[0083] In the embodiment of the present application, the device operation data of the first device can be collected by the baseboard management controller. When the first device fails, the device operation data collected by the baseboard management controller may include the fault data of the first device. Therefore, the target fault data related to the fault of the first device can be obtained by the first device operation data collected by the baseboard management controller, and then the fault cause of the first device can be determined. In the embodiment of the present application, the target fault data is the data synchronously collected by the baseboard management controller when the first device fails, which can accurately reflect the fault state of the first device. Therefore, analyzing the cause of the fault by analyzing the target fault data can not only improve the efficiency of fault analysis, but also improve the accuracy of fault analysis.

[0084] According to an embodiment of the present application, the present application also provides an electronic device and a readable storage medium.

[0085] Figure 4 A schematic block diagram of an example electronic electronic device 400 that can be used to implement an embodiment of the present application is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workbenches, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device can also represent various forms of mobile devices, such as personal digital processing, cellular phones, smart phones, wearable devices, and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present application described and / or required herein.

[0086] like Figure 4 As shown, the electronic device 400 includes a computing unit 401, which can perform various appropriate actions and processes according to a computer program stored in a read-only memory (ROM) 402 or a computer program loaded from a storage unit 408 into a random access memory (RAM) 403. In the RAM 403, various programs and data required for the operation of the electronic device 400 can also be stored. The computing unit 401, the ROM 402, and the RAM 403 are connected to each other via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0087] Multiple components in the electronic device 400 are connected to the I / O interface 405, including: an input unit 406, such as a keyboard, a mouse, etc.; an output unit 407, such as various types of displays, speakers, etc.; a storage unit 408, such as a disk, an optical disk, etc.; and a communication unit 409, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 409 allows the electronic device 400 to exchange information / data with other devices through a computer network such as the Internet and / or various telecommunication networks.

[0088] The computing unit 401 may be a variety of general and / or special processing components with processing and computing capabilities. Some examples of the computing unit 401 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various dedicated artificial intelligence (AI) computing chips, various computing units running machine learning model algorithms, digital signal processors (DSPs), and any appropriate processors, controllers, microcontrollers, etc. The computing unit 401 performs the various methods and processes described above, such as the fault analysis method. For example, in some embodiments, the fault analysis method may be implemented as a computer software program, which is tangibly contained in a machine-readable medium, such as a storage unit 408. In some embodiments, part or all of the computer program may be loaded and / or installed on the electronic device 400 via the ROM 402 and / or the communication unit 409. When the computer program is loaded into the RAM 403 and executed by the computing unit 401, one or more steps of the fault analysis method described above may be performed. Alternatively, in other embodiments, the computing unit 401 may be configured to perform the fault analysis method in any other appropriate manner (e.g., by means of firmware).

[0089] Various embodiments of the technology described above herein may be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), integrated systems on chips (SOCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. The program code for implementing the method of the present application may be written in any combination of one or more programming languages. In the context of the present application, a machine-readable medium may be a tangible medium. A machine-readable medium may be a machine-readable signal medium or a machine-readable storage medium. A machine-readable medium may include, but is not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. A computer system may include a client and a server. The client and the server are generally remote from each other and typically interact through a communication network. The server may be a cloud server, a server of a distributed system, or a server incorporating a blockchain. In addition, the terms "first" and "second" are used for descriptive purposes only and cannot be understood as indicating or implying relative importance or implicitly indicating the number of technical features indicated. In the description of the present application, “plurality” means two or more than two, unless otherwise clearly and specifically defined.

[0090] The above is only a specific implementation of the present application, but the protection scope of the present application is not limited thereto. Any person skilled in the art who is familiar with the present technical field can easily think of changes or substitutions within the technical scope disclosed in the present application, which should be included in the protection scope of the present application. Therefore, the protection scope of the present application should be based on the protection scope of the claims.

Claims

1. A fault analysis method, characterized in that: The method comprises: Monitoring the operation status information of the first device; If the operation status information indicates that the first device has a fault, target fault data corresponding to the first device is obtained through a second device, wherein the first device and the second device are interconnected through a target connection, the second device obtains and stores device operation data of the first device through the target connection, the device operation data includes the target fault data, and the device operation data is stored in a designated storage area of ​​a target storage space corresponding to the target connection in the second device, and the designated storage area is smaller than the target storage space; A failure cause of the first device is determined based on the target failure data.

2. The method according to claim 1, characterized in that The target connection is a graphic data transmission interface; the device operation data includes system operation data of the first device; the operating system of the first device collects system operation data every first preset period, and sends the collected system operation data to the second device through the graphic data transmission interface, and the second device stores the received system operation data to the designated storage area.

3. The method according to claim 2, characterized in that When there is no free storage space in the designated storage area, the second device clears the data in the designated storage area that has been stored for longer than a preset time period, and stores the newly received system operation data in the designated storage area.

4. The method according to claim 1, characterized in that The target connection is a communication interface; the device operation data includes CPU fault data of the first device; the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data in the designated storage area.

5. The method according to claim 4, characterized in that The second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device.

6. The method according to claim 5, characterized in that The acquiring, by the second device, target fault data corresponding to the first device includes: sending a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, wherein the device log data includes the device operation data stored in the designated storage area; receiving the device log data sent by the second device through the preset communication connection; The device operation data corresponding to the fault time period of the first device is determined as target fault data through the device log data.

7. The method according to claim 1, characterized in that The second device is a baseboard management controller, and the baseboard management controller is deployed in the first device.

8. A fault analysis device, characterized in that: The device comprises: A status monitoring module, used to monitor the operating status information of the first device; a fault data acquisition module, configured to acquire target fault data corresponding to the first device through a second device if the operation status information indicates that the first device has a fault, wherein the first device and the second device are interconnected through a target connection, the second device acquires and stores device operation data of the first device through the target connection, the device operation data includes the target fault data, and the device operation data is stored in a designated storage area of ​​a target storage space corresponding to the target connection in the second device, the designated storage area being smaller than the target storage space; A fault analysis module is used to determine a fault cause of the first device based on the target fault data.

9. The device according to claim 8, characterized in that The target connection is a graphic data transmission interface; the device operation data includes system operation data of the first device; the operating system of the first device collects system operation data every first preset period, and sends the collected system operation data to the second device through the graphic data transmission interface, and the second device stores the received system operation data to the designated storage area.

10. The device according to claim 9, characterized in that When there is no free storage space in the designated storage area, the second device clears the data in the designated storage area that has been stored for longer than a preset time period, and stores the newly received system operation data in the designated storage area.

11. The device according to claim 8, characterized in that The target connection is a communication interface; the device operation data includes CPU fault data of the first device; the second device collects the CPU fault data of the first device through the communication interface every second preset period, and stores the collected CPU fault data in the designated storage area.

12. The device according to claim 11, characterized in that The second device reads the CPU register information of the first device through the communication interface as the CPU fault data of the first device.

13. The device according to claim 12, characterized in that The fault data acquisition module is specifically used to send a target fault data acquisition instruction to the second device through a preset communication connection, so that the second device generates device log data according to the target fault data acquisition instruction, and the device log data includes the device operation data stored in the designated storage area; receive the device log data sent by the second device through the preset communication connection; and determine the device operation data corresponding to the fault time period of the first device as the target fault data through the device log data.

14. The device according to claim 8, characterized in that The second device is a baseboard management controller, and the baseboard management controller is deployed in the first device.

15. An electronic device, characterized in that: include: A memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the electronic device communicates with a second device via a preset communication connection, and the processor implements the method as described in any one of claims 1 to 7 when executing the computer program.

16. A storage medium containing computer executable instructions, characterized in that: The computer executable instructions are used to perform the method of any one of claims 1-7 when executed by a computer processor.

Images