Server troubleshooting method and device, storage medium and program product

Abstract

The invention provides a server troubleshooting method and device, a storage medium and a program product, and can be applied to the technical field of computers. The server troubleshooting method comprises the following steps: determining a troubleshooting step corresponding to a target server fault phenomenon input by a user based on a preset fault information set; determining a target to-be-checked node corresponding to the checking step, and displaying theoretical position information of the to-be-checked node in a target server to a user; according to the execution sequence of the troubleshooting steps, theoretical position information is sent to preset positioning equipment, so that the preset positioning equipment displays actual position information of the target node to be troubleshot in the target server to a user based on the received theoretical position information; in response to the obtained troubleshooting feedback information, a troubleshooting conclusion for the fault phenomenon of the target server is output based on the troubleshooting feedback information, and the troubleshooting feedback information is obtained by executing the troubleshooting step by the user based on the theoretical position information and the actual position information.

Description

Technical Field

[0001] The present application relates to the field of computers, and more specifically to a server fault troubleshooting method, device, storage medium, and program product. Background Art

[0002] When a server malfunctions, maintenance personnel need to combine board schematics, server link diagrams, and other information to determine the server's overall link status and, in turn, the fault location. For example, if a server discovers that its hard drive cannot be detected during testing, a comprehensive investigation of the entire hard drive link is necessary. However, manually troubleshooting the overall link status requires referencing numerous schematics and link diagrams, as well as searching for the physical location of the content to be investigated on the actual server. This reference and search process is time-consuming and prone to errors. Summary of the Invention

[0003] In view of the above problems, the present application provides a server fault troubleshooting method, device, storage medium and program product.

[0004] According to the first aspect of the present application, a server fault troubleshooting method is provided, comprising: determining a troubleshooting step corresponding to a target server fault phenomenon input by a user based on a preset fault information set; determining a target node to be troubleshooted corresponding to the troubleshooting step, and displaying theoretical position information of the target node to be troubleshooted in the target server to the user; sending theoretical position information to a preset positioning device according to the execution order of the troubleshooting steps, so that the preset positioning device displays actual position information of the target node to be troubleshooted in the target server to the user based on the received theoretical position information; in response to obtaining troubleshooting feedback information, outputting a troubleshooting conclusion for the target server fault phenomenon based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user executing the troubleshooting step based on the theoretical position information and the actual position information.

[0005] The second aspect of the present application provides an electronic device, comprising: one or more processors; a memory for storing one or more computer programs, wherein the one or more processors execute the one or more computer programs to implement the steps of the above method.

[0006] The third aspect of the present application further provides a computer-readable storage medium having a computer program or instructions stored thereon, which implements the steps of the above method when the computer program or instructions are executed by a processor.

[0007] The fourth aspect of the present application further provides a computer program product, comprising a computer program or instructions, which implement the steps of the above method when executed by a processor. BRIEF DESCRIPTION OF THE DRAWINGS

[0008] The above contents and other objects, features and advantages of the present application will become more apparent through the following description of the embodiments of the present application with reference to the accompanying drawings, in which:

[0009] Figure 1 The present invention provides an application scenario diagram of a server fault troubleshooting method, device, storage medium, and program product according to an embodiment of the present application.

[0010] Figure 2 A flow chart of a server fault troubleshooting method according to an embodiment of the present application is shown.

[0011] Figure 3 A flow chart of a server fault troubleshooting method according to another embodiment of the present application is shown.

[0012] Figure 4 A schematic diagram of a user display interface according to an embodiment of the present application is shown.

[0013] Figure 5 The figure shows a structural block diagram of a server fault troubleshooting device according to an embodiment of the present application.

[0014] Figure 6 A block diagram of an electronic device suitable for implementing a server fault troubleshooting method according to an embodiment of the present application is shown. DETAILED DESCRIPTION

[0015] Hereinafter, embodiments of the present application will be described with reference to the accompanying drawings. However, it should be understood that these descriptions are exemplary only and are not intended to limit the scope of the present application. In the detailed description below, for ease of explanation, many specific details are set forth to provide a comprehensive understanding of the embodiments of the present application. However, it is apparent that one or more embodiments may also be implemented without these specific details. In addition, in the following description, descriptions of known structures and technologies are omitted to avoid unnecessarily confusing the concepts of the present application.

[0016] The terms used herein are only for describing specific embodiments and are not intended to limit the present application. The terms "comprise," "include," etc. used herein indicate the presence of features, steps, operations, and / or components, but do not exclude the presence or addition of one or more other features, steps, operations, or components.

[0017] All terms used herein (including technical and scientific terms) have the meanings commonly understood by those skilled in the art unless otherwise defined. It should be noted that the terms used herein should be interpreted as having a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0018] When expressions such as "at least one of A, B, and C, etc." are used, they should generally be interpreted in accordance with the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include but is not limited to a system having A alone, B alone, C alone, A and B, A and C, B and C, and / or A, B, C, etc.).

[0019] In the server industry, during small-batch trial production, early shipments, or normal shipments of products, if problems such as poor internal circuit contact, damaged components, or bandwidth reduction in server links occur, maintenance personnel are usually required to use a multimeter to perform continuity tests on the cables and board ends of the server using server-related schematics, server link diagrams, and other information to locate the failure point or link.

[0020] Among them, the schematic diagram is also called the electrical schematic diagram, which includes various circuit component symbols and the connection methods between them. By identifying the various circuit component symbols and connection methods in the schematic diagram, you can understand the actual working principle of the circuit. The server link diagram can also be called the server structure topology diagram, which can show the hardware composition inside the server, such as the central processing unit (CPU), memory, hard disk, network interface, etc. The server link diagram can be used to understand the server architecture and hardware configuration, and because the server link diagram shows the connection status and network layout of network devices, it helps to analyze and optimize network performance. You can use the topology diagram template to customize the creation of the topology diagram and modify and adjust the topology diagram as needed.

[0021] Related methods usually determine the overall link status of the server by cross-checking the schematic diagram with the server link diagram. For example, if a server finds that the hard drive cannot be detected during the test phase, it is necessary to conduct a comprehensive investigation of the entire hard drive link, which includes, for example: hard drive-backplane-backplane cable-motherboard-CPU-power supply. Among them, the "power supply-CPU-motherboard" in the entire hard drive link needs to be troubleshooted based on the motherboard schematic diagram, the "motherboard-backplane cable-backplane" needs to be troubleshooted based on the server link diagram, and the "backplane-hard drive" needs to be troubleshooted based on the backplane schematic diagram. The troubleshooting process needs to be verified based on a large number of schematic diagrams and link diagrams, and the troubleshooting steps need to be manually determined. It also needs to be converted to physical objects to find the specific point information of each component in order to troubleshoot the components. Therefore, the entire round of troubleshooting process takes a lot of time, resulting in low troubleshooting efficiency, and the troubleshooting process is prone to errors. In the case of troubleshooting errors at some points, it may cause errors in the entire troubleshooting link. Therefore, the technical level of the troubleshooters is required to be high, and the operational accuracy of the troubleshooters is required to be high. The manual troubleshooting process is more prone to misdiagnosis due to errors.

[0022] Furthermore, the method for troubleshooting circuit breaker failures in related servers is generally to check individual components. For example, if a server finds that its hard drive cannot be detected during the test phase, the method for troubleshooting the entire hard drive link is generally to replace the hard drive, backplane, backplane cable, CPU, memory, power supply, and motherboard one by one for cross-verification to locate the faulty component. However, replacement cross-verification takes a lot of time, and the operation of disassembling and assembling the entire server also consumes a lot of time. In addition, replacement cross-verification is prone to component damage due to disassembly and assembly operations, resulting in damage to the on-site server environment. If the cause of the fault is not determined during the troubleshooting process, and the fault phenomenon has disappeared, it will be difficult for the troubleshooter to further analyze the fault phenomenon because the on-site server environment has been destroyed.

[0023] In view of this, an embodiment of the present application provides a server fault troubleshooting method, including: determining a troubleshooting step corresponding to a target server fault phenomenon input by a user based on a preset fault information set; determining a target node to be troubleshooted corresponding to the troubleshooting step, and displaying the theoretical position information of the target node to be troubleshooted in the target server to the user; sending the theoretical position information to a preset positioning device according to the execution order of the troubleshooting steps, so that the preset positioning device displays the actual position information of the target node to be troubleshooted in the target server to the user based on the received theoretical position information; in response to obtaining troubleshooting feedback information, outputting a troubleshooting conclusion for the target server fault phenomenon based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user executing the troubleshooting step based on the theoretical position information and the actual position information.

[0024] Figure 1 The present invention provides an application scenario diagram of a server fault troubleshooting method, device, storage medium, and program product according to an embodiment of the present application.

[0025] like Figure 1 As shown, the application scenario according to this embodiment may include a digital process system 101 and a preset positioning device 102. The digital process system 101 may display the theoretical location information of the target node to be checked in the target server. For example, if the target nodes to be checked include node 1, node 2, ..., node n, the digital process system 101 may display the theoretical location information of each of nodes 1, node 2, ..., node n, such as displaying theoretical location information 1, theoretical location information 2, ..., theoretical location information n. The digital process system 101 may also send the theoretical location information to the preset positioning device 102. Based on the received theoretical location information, the preset positioning device 102 may determine and display the actual location information of the target node to be checked in the target server to the user. The actual location information may include, for example, actual location information 1, actual location information 2, ..., actual location information n.

[0026] For example, in the event of a target server failure, the user can input the target server failure phenomenon into the digital process system 101, and the troubleshooting steps corresponding to the target server failure phenomenon input by the user can be determined based on a preset fault information set; the target node to be troubleshooted corresponding to the troubleshooting step is determined, and the theoretical position information of the target node to be troubleshooted in the target server is displayed to the user; according to the execution order of the troubleshooting steps, the theoretical position information is sent to the preset positioning device 102, so that the preset positioning device 102 displays the actual position information of the target node to be troubleshooted in the target server to the user based on the received theoretical position information; in response to obtaining troubleshooting feedback information, a troubleshooting conclusion for the target server failure phenomenon is output based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user executing the troubleshooting steps based on the theoretical position information and the actual position information.

[0027] The following will be passed Figures 2 to 4 The server fault troubleshooting method of the embodiment of the present application is described in detail.

[0028] Figure 2 FIG. 1 shows a flow chart of a server fault troubleshooting method according to an embodiment of the present application. Figure 2 As shown, the server fault troubleshooting method of this embodiment includes operations S210 to S240.

[0029] In operation S210 , a troubleshooting step corresponding to a target server fault phenomenon input by a user is determined based on a preset fault information set.

[0030] Because different fault phenomena may correspond to different troubleshooting steps, it is possible to pre-acquire multiple historical fault phenomena for the server and obtain historical troubleshooting steps for the multiple historical fault phenomena. For example, this may be multiple historical fault phenomena for different types of servers and historical troubleshooting steps for each of the multiple historical fault phenomena. Based on a preset fault information set, the historical fault phenomena and historical troubleshooting steps corresponding to different types of servers can be determined. For example, when a user inputs a target server fault phenomenon for a target server, the troubleshooting steps corresponding to the target server fault phenomenon for the target server can be determined from the preset fault information set based on the target server type and the target server fault phenomenon.

[0031] In operation S220 , the target node to be checked corresponding to the checking step is determined, and theoretical location information of the target node to be checked in the target server is displayed to the user.

[0032] The preset fault information set may also include nodes to be troubleshooted corresponding to the troubleshooting steps. For example, the nodes to be troubleshooted may include server components. Different troubleshooting steps may correspond to corresponding nodes to be troubleshooted. For example, troubleshooting step 1 may correspond to nodes to be troubleshooted 1 and 2, and troubleshooting step 2 may correspond to node to be troubleshooted 3. Troubleshooting is required for the nodes to be troubleshooted to determine whether the fault is caused by a fault in the node to be troubleshooted.

[0033] For example, a preset fault information set can be imported into the digital process system in advance. After the user inputs the target server fault phenomenon into the digital process system, the system can automatically match the troubleshooting steps corresponding to the target server fault phenomenon based on the type of the target server and the target server fault phenomenon, and automatically determine the target node to be troubleshooted through the preset fault information set.

[0034] A 3D model corresponding to the target server can be displayed, such as a 3D model of a component. The 3D model can be generated using 3D rendering software built into the digital process system. Displaying the theoretical location information of the target node to be troubleshooted on the target server can include presenting the 3D model of the target node to be troubleshooted with a flashing animation. Furthermore, displaying the theoretical location information of the target node to be troubleshooted on the target server can also include annotating information related to the target node to be troubleshooted, such as pin numbers.

[0035] For example, when it is determined that the target nodes to be troubleshooted corresponding to troubleshooting step 1 include components 1 and component 2, the three-dimensional models of components 1 and 2 in the server can be displayed to the user, and the above three-dimensional models can be highlighted. The pin numbers of the above components can also be marked, for example, "test points: Pin 1 and Pin 2" can be marked.

[0036] For example, the theoretical location information of the target node to be troubleshooted in the target server can be displayed to the user in sequence according to the execution order of the troubleshooting steps. For example, in troubleshooting step 1, the 3D model of the target node to be troubleshooted corresponding to troubleshooting step 1 is highlighted, and in troubleshooting step 2, the 3D model of the target node to be troubleshooted corresponding to troubleshooting step 2 is highlighted. Specifically, in troubleshooting step 2, the highlighting of the 3D model of the target node to be troubleshooted in troubleshooting step 1 can be stopped, or the highlighting of the 3D model of the target node to be troubleshooted in troubleshooting step 1 can continue.

[0037] In operation S230, according to the execution order of the troubleshooting steps, the theoretical location information is sent to the preset positioning device, so that the preset positioning device displays the actual location information of the target node to be checked in the target server to the user based on the received theoretical location information.

[0038] For example, theoretical location information can be sent to the preset positioning device in sequence according to the execution order of the troubleshooting steps, so that the preset positioning device can display the actual location information of the target node to be checked in the target server to the user in sequence based on the theoretical location information received in sequence.

[0039] For example, in troubleshooting step 1, after determining theoretical location information 1 corresponding to troubleshooting step 1, theoretical location information 1 is sent to the preset positioning device. Based on the received theoretical location information 1, the preset positioning device determines actual location information 1 corresponding to the target node to be troubleshooted in troubleshooting step 1 and displays actual location information 1 to the user. Then, in troubleshooting step 2, theoretical location information 2 corresponding to troubleshooting step 2 is sent to the preset positioning device. Based on the received theoretical location information 2, the preset positioning device determines and displays actual location information 2 to the user.

[0040] Showing the actual location information of the target node to be checked in the target server to the user may include: shining a laser light on a physical component of the server corresponding to the target node to be checked.

[0041] For example, a robotic arm system can use the edge of the server chassis as a coordinate to accurately locate the overall structure of the server, and then use a laser light to illuminate the actual components of the server. The user can know the actual location of the target node to be checked in the target server by the lighting position.

[0042] After the theoretical position information and actual position information of the target node to be checked in the target server are displayed to the user, the user can quickly and accurately locate the position of the target node to be checked in the server entity based on the theoretical position information and the actual position information, and perform the check. For example, when the target node to be checked corresponding to step 1 includes component 1, the user can directly determine the shape, position and other information of component 1 based on the 3D model of component 1 seen and the lighting of the actual component 1 on the server, and check it.

[0043] In operation S240 , in response to obtaining troubleshooting feedback information, a troubleshooting conclusion for the target server fault phenomenon is output based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user performing troubleshooting steps based on the theoretical location information and the actual location information.

[0044] After the user performs troubleshooting steps on the target node to be troubleshooted based on the theoretical position information and the actual position information, the user will obtain troubleshooting feedback information corresponding to the target node to be troubleshooted. For example, after the user uses a multimeter to troubleshoot the target node to be troubleshooted, the user will obtain troubleshooting feedback information such as the current value and voltage value corresponding to the target node to be troubleshooted. After obtaining the troubleshooting feedback information, the user can input the troubleshooting feedback information into the digital process system so that the system can generate a fault troubleshooting conclusion based on the troubleshooting feedback information. The fault troubleshooting conclusion may include the name of the faulty node, the component number, the cause of the fault, etc.

[0045] According to the embodiments of the present application, the theoretical position information of the target node to be troubleshooted in the target server is displayed to the user by highlighting and flashing the three-dimensional model corresponding to the target node to be troubleshooted, and the actual position information of the target node to be troubleshooted in the target server is displayed to the user by shining light on the actual components of the server. On the one hand, more accurate fault location can be achieved, avoiding blind troubleshooting and cross-replacement verification of components one by one, effectively reducing hardware loss and troubleshooting time; on the other hand, abstract circuit principles and fault locations can be converted into intuitive visual information, so that non-professionals can easily understand and determine the location of the node to be troubleshooted, without having to manually interpret professional drawings such as schematics and circuit diagrams to find the actual location of the node to be troubleshooted for troubleshooting, simplifying the complex troubleshooting process, thereby reducing the professional threshold and manual workload, and improving troubleshooting efficiency and accuracy. In addition, by combining the functions of determining the troubleshooting steps corresponding to the target server fault phenomenon input by the user based on a preset fault information set and displaying the theoretical location information and actual location information of the target node to be troubleshooted in the target server to the user, and integrating the above functions into the same system, a complete server fault troubleshooting system can be formed, thereby improving the automation and intelligence level of fault diagnosis.

[0046] According to an embodiment of the present application, the preset fault information set includes a correspondence between a server fault phenomenon and a troubleshooting path, and the troubleshooting path includes at least one troubleshooting step node and a connection sequence between at least one troubleshooting step node.

[0047] For example, based on the acquired multiple historical fault phenomena and corresponding historical troubleshooting steps, the corresponding relationship between the server fault phenomenon and the troubleshooting steps can be determined, and the execution order of the troubleshooting steps can be determined. For a server fault phenomenon, at least one troubleshooting step node corresponding to the server fault phenomenon can be generated, and each troubleshooting step node can be associated with a troubleshooting step. For example, the troubleshooting step associated with troubleshooting step node 1 is "confirming the on / off status of the hard disk to the motherboard", and the troubleshooting step associated with troubleshooting step node 2 connected to troubleshooting step node 1 is "confirming the on / off status of the motherboard to the power supply". According to the connection order, it can be determined that after executing troubleshooting step 1, troubleshooting step 2 can be executed.

[0048] The troubleshooting steps corresponding to the target server failure phenomenon input by the user may include an initial troubleshooting step and subsequent troubleshooting steps. Determining the troubleshooting steps corresponding to the target server failure phenomenon input by the user based on a preset fault information set may include: determining a target troubleshooting path corresponding to the target server failure phenomenon from the preset fault information set; determining the initial troubleshooting step corresponding to the initial troubleshooting step node in the target troubleshooting path; and determining subsequent troubleshooting steps based on the initial feedback data corresponding to the initial troubleshooting step.

[0049] Figure 3 FIG. 1 shows a flow chart of a server fault troubleshooting method according to another embodiment of the present application. Figure 3 As shown, the server fault troubleshooting method of this embodiment includes operations S310 to S360.

[0050] In operation S310 , a starting troubleshooting step is determined.

[0051] For example, because the preset fault information set includes a correspondence between server fault symptoms and troubleshooting paths, the target server fault symptom can be determined from the preset fault information set to determine the troubleshooting path corresponding to the target server fault symptom, thereby obtaining a target troubleshooting path. The target troubleshooting path can include multiple troubleshooting step nodes, and the troubleshooting step node that is ranked first in the connection order can be used as the starting troubleshooting step node, and the troubleshooting step corresponding to the starting troubleshooting step node can be used as the starting troubleshooting step.

[0052] In operation S320 , the theoretical location information and the actual location information of the target node to be checked corresponding to the initial checking step are displayed.

[0053] For example, the three-dimensional model of the target node to be checked corresponding to the initial troubleshooting step can be highlighted and flashed to display the theoretical location information, and the laser light can be used to illuminate the physical components of the server corresponding to the target node to be checked to display the actual location information.

[0054] In operation S330 , initial feedback data input by a user is received.

[0055] The initial feedback data may include troubleshooting data obtained by the user performing the initial troubleshooting steps. For example, based on the theoretical location information and the actual location information, the user may perform the initial troubleshooting steps on the target node to be troubleshooted, such as confirming the on / off status of the circuit from the hard drive to the motherboard, to obtain corresponding troubleshooting data. The troubleshooting data may include, for example, the resistance and voltage values of the components corresponding to the initial troubleshooting steps. Furthermore, the digital process system may receive the initial feedback data input by the user.

[0056] In operation S340 , subsequent troubleshooting steps are determined.

[0057] According to an embodiment of the present application, the troubleshooting path further includes a feedback data numerical condition associated with at least one troubleshooting step node. Determining a subsequent troubleshooting step based on the initial feedback data corresponding to the initial troubleshooting step includes: matching the initial feedback data with the feedback data numerical condition associated with the initial troubleshooting step node, and determining the subsequent troubleshooting step based on the matching result.

[0058] For example, a feedback data value condition can represent the standard range that the feedback data obtained when the user executes the troubleshooting step corresponding to the troubleshooting step node should meet, assuming that the node to be troubleshooted corresponding to the troubleshooting step node is not faulty. For example, if the troubleshooting step corresponding to troubleshooting step node 1 is "Confirm the on / off status of the hard drive to the motherboard," the feedback data value condition associated with troubleshooting step node 1 is 0.477Ω to 1.3Ω. This indicates that if the node to be troubleshooted corresponding to this step is not faulty, the feedback data obtained when troubleshooting with a multimeter should be between 0.477Ω and 1.3Ω.

[0059] By matching the starting feedback data with the feedback data numerical condition associated with the starting troubleshooting step node, it can be determined whether the starting feedback data falls within the feedback data numerical condition. If it is determined that it falls within the feedback data numerical condition, it means that the node to be troubleshooted corresponding to the starting troubleshooting step has not failed. Therefore, the troubleshooting step corresponding to the troubleshooting step node directly connected to the starting troubleshooting step node can be executed next, that is, the subsequent troubleshooting steps include: the troubleshooting step corresponding to the troubleshooting step node directly connected to the starting troubleshooting step node.

[0060] If the matching result determines that the initial feedback data does not fall within the feedback data value conditions, it indicates that a fault has occurred in the node to be checked corresponding to the initial troubleshooting step. Furthermore, a subsequent troubleshooting step can further troubleshoot the node to be checked corresponding to the initial troubleshooting step to determine the cause of the fault in the node to be checked.

[0061] By determining the target troubleshooting path corresponding to the target server fault phenomenon from a preset fault information set, and determining the starting troubleshooting step corresponding to the starting troubleshooting step node in the target troubleshooting path, and then matching the starting feedback data with the feedback data numerical conditions associated with the starting troubleshooting step node, and determining subsequent troubleshooting steps based on the matching results, the troubleshooting steps can be determined automatically and accurately. Compared with manual troubleshooting of individual devices and cross-verification of replacements for components one by one, the probability of troubleshooting errors is reduced, and the troubleshooting accuracy and efficiency are improved.

[0062] In operation S350, the theoretical location information and actual location information of the target node to be checked corresponding to the subsequent troubleshooting step are displayed. For example, a three-dimensional model of the target node to be checked corresponding to the subsequent troubleshooting step can be highlighted and flashed to display the theoretical location information, and a laser light can be shined on the physical server component corresponding to the target node to display the actual location information.

[0063] In operation S360 , a troubleshooting conclusion is output.

[0064] Based on the user's feedback information for the initial troubleshooting steps and subsequent troubleshooting steps, troubleshooting feedback information corresponding to the target server's fault symptoms can be obtained. Based on the troubleshooting feedback information, the cause of the fault can be determined, and a solution to the cause can also be determined, resulting in a troubleshooting conclusion. For example, if the target server's fault symptoms entered by the user include the inability to detect the hard drive at location NO2, based on the user's feedback information for the initial troubleshooting steps and subsequent troubleshooting steps, the cause of the fault can be determined to be a single hard drive backplane failure, and the solution is to replace the hard drive backplane.

[0065] According to an embodiment of the present application, the server fault troubleshooting method may further include the following operations.

[0066] Target identification information of the target node to be checked is determined, wherein the target identification information may include, for example, a component number of the target node to be checked.

[0067] The target coordinate information and the target rendering rule corresponding to the target node to be checked are read from the pre-built node mapping relationship set according to the target identification information.

[0068] For example, the pre-built node mapping relationship set may include coordinate information corresponding to at least one node to be checked, wherein at least one node to be checked includes a target node to be checked, and the coordinate information may represent the location of the node to be checked in the server. The node mapping relationship set may also include rendering rules corresponding to at least one node to be checked, wherein the rendering rules may include target rendering rules, and the target rendering rules may represent the visual marking method corresponding to the node to be checked, such as highlighting the node to be checked, or flashing it, or marking it using the above methods together. The rendering rules of at least one node to be checked may be the same or different, and may be set according to actual conditions.

[0069] A target model component corresponding to the target node to be checked in a pre-built server model is determined based on the target coordinate information.

[0070] The server model can include models of multiple components corresponding to the server, for example, including 3D models of each of the multiple components. Based on the target coordinate information, the target model component corresponding to the target node to be checked can be accurately located from the server model. For example, if the target coordinate information includes (x1, y1, z1), the model component at the position (x1, y1, z1) can be located from the server model, thereby determining the target model component corresponding to the target node to be checked.

[0071] Visually mark the target model components based on the target rendering rules.

[0072] For example, the visual mark includes a highlight flashing mark, and the theoretical location information of the target node to be checked in the target server can be displayed to the user through the visual mark.

[0073] By determining the target model device corresponding to the target node to be checked in the pre-built server model based on the target coordinate information, and visually marking the target model device based on the target rendering rules, the theoretical position of the target node to be checked can be intuitively displayed to the user, thereby facilitating the user to accurately locate the target node to be checked.

[0074] According to an embodiment of the present application, the server fault troubleshooting method also includes: determining and displaying to the user the troubleshooting step execution information corresponding to the troubleshooting step, the troubleshooting step execution information including at least one of the following: troubleshooting equipment usage information, and material information of the node to be troubleshooted.

[0075] Relevant schematic diagrams (such as board schematics) and related link diagrams (such as link diagrams between components) corresponding to the server can be obtained in advance. Based on the relevant schematic diagrams and related link diagrams, server component information, such as component information for the main card, backplane, power board, fan board, power supply, memory, CPU, cables, and other components, can be determined, as well as server component operating information. Server component operating information can include, for example, pin power supply information, serial general-purpose input / output information, inter-integrated circuit bus signal information, and data transmission link information. For example, a staff member can pre-determine the component information and server component operating information based on the relevant schematic diagrams and related link diagrams. By combing through this component information and server component operating information, the overall status of the server can be more accurately determined, such as the component number, component model, and connection relationship of the node to be investigated. For example, it can be determined that the power supply link for a hard drive at a certain location includes: hard drive - hard drive backplane numbered NO1 - hard drive backplane sub-component numbered NO1 - backplane power cable - motherboard connector - motherboard bus - motherboard power interface - power supply.

[0076] For example, troubleshooting equipment usage information can include multimeter usage requirements, such as the meter's usage modes, including on / off, resistance, and other settings. Troubleshooting equipment usage information can also include automatically generated images of the multimeter and the multimeter's theoretical reference values corresponding to the troubleshooting steps. Material information for the node to be troubleshooted can include, for example, the part number (PN).

[0077] Figure 4 A schematic diagram of a user display interface according to an embodiment of the present application is shown.

[0078] The user can enter a fault symptom, such as a target server fault symptom, which can include "The hard drive with location number NO2 cannot be detected, and the link power supply is abnormal." After determining the troubleshooting steps, the troubleshooting steps and the corresponding troubleshooting step execution information can be displayed to the user. For example, the user can be shown: Troubleshooting Step 1 specifically includes "Confirming the on / off status of the hard drive to the motherboard," Troubleshooting Step 2 specifically includes "Confirming the on / off status of the motherboard to the power supply," Troubleshooting Step 3 specifically includes "The first round of troubleshooting to confirm whether the hard drive backplane has a single abnormality," and Troubleshooting Step 4 specifically includes "The second round of troubleshooting to confirm whether the hard drive backplane has a single abnormality." For troubleshooting Steps 1 to 4, the corresponding multimeter theoretical reference values can all be 0.477Ω-1.3Ω. The multimeter theoretical reference values can, for example, represent the range of resistance measured using the on / off setting of the multimeter when the node to be troubleshooted is not faulty. The multimeter settings corresponding to the above four troubleshooting steps can all be on / off, with the red test lead corresponding to the voltage and resistance measurement holes and the black test lead corresponding to the common terminal jack. In addition, the part numbers of the nodes to be checked corresponding to each of the troubleshooting steps 1 to 4 can also be displayed, such as part numbers XXX1 to XXX6. Furthermore, the component information of the nodes to be checked corresponding to each of the troubleshooting steps 1 to 4 can also be displayed, such as component models, etc. Furthermore, the troubleshooting conclusions corresponding to each of the troubleshooting steps 1 to 4 can also be displayed. The troubleshooting conclusions can be obtained by the user executing the troubleshooting steps based on the theoretical location information and the actual location information. For troubleshooting steps 1 to 3, the troubleshooting conclusions can be "empty", for example, it can indicate that no abnormality has been found in the troubleshooting step. In troubleshooting step 4, the troubleshooting conclusion can be determined and displayed as "hard disk backplane single unit failure, replace the hard disk backplane."

[0079] According to an embodiment of the present application, the server fault troubleshooting method further includes: in response to obtaining conclusion feedback information of the user on the fault troubleshooting conclusion, performing an update operation on the preset fault information set based on the conclusion feedback information.

[0080] Conclusion feedback information may include user feedback on the troubleshooting conclusion. For example, when the user reports that the troubleshooting conclusion does not correspond to the target server fault phenomenon, and if the target server fault phenomenon still exists after repairs based on the troubleshooting conclusion, an update operation on the troubleshooting information set may be performed. The update operation may include, for example, adjusting or updating the information in the preset fault information set. The troubleshooting conclusion does not correspond to the target server fault phenomenon, which may be because the troubleshooting step nodes, feedback data numerical conditions, and other contents in the preset fault information set may not be accurate enough, so they can be adjusted. Alternatively, it may be because the preset fault information set lacks information corresponding to the target server fault phenomenon, so new information corresponding to the target server fault phenomenon can be added.

[0081] By performing an update operation on the preset fault information set based on conclusion feedback information, the preset fault information set can be dynamically adjusted based on user feedback, so that a fault troubleshooting conclusion can be output more accurately subsequently.

[0082] Based on the above server fault troubleshooting method, this application also provides a server fault troubleshooting device. Figure 5 The device is described in detail.

[0083] Figure 5 The figure shows a structural block diagram of a server fault troubleshooting device according to an embodiment of the present application.

[0084] like Figure 5 As shown, the server fault troubleshooting device 500 of this embodiment includes a first determination module 510 , a second determination module 520 , a sending module 530 and an output module 540 .

[0085] The first determining module 510 is used to determine the troubleshooting steps corresponding to the target server fault phenomenon input by the user based on the preset fault information set. In one embodiment, the first determining module 510 can be used to perform the operation S210 described above, which will not be repeated here.

[0086] The second determining module 520 is used to determine the target node to be checked corresponding to the troubleshooting step and display the theoretical location information of the target node to be checked in the target server to the user. In one embodiment, the second determining module 520 can be used to perform the operation S220 described above, which will not be repeated here.

[0087] The sending module 530 is configured to send the theoretical location information to the preset positioning device according to the execution order of the troubleshooting steps, so that the preset positioning device can display the actual location information of the target node to be checked on the target server to the user based on the received theoretical location information. In one embodiment, the sending module 530 can be used to perform the operation S230 described above, and will not be repeated here.

[0088] Output module 540 is configured to, in response to obtaining troubleshooting feedback information, output a troubleshooting conclusion regarding the target server fault phenomenon based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user performing troubleshooting steps based on the theoretical location information and the actual location information. In one embodiment, output module 540 may be configured to perform operation S240 described above, which will not be further described here.

[0089] According to an embodiment of the present application, the first determination module 510 includes a first determination submodule, a second determination submodule, and a third determination submodule.

[0090] The first determination submodule is used to determine the target troubleshooting path corresponding to the target server fault phenomenon from the preset fault information set; the second determination submodule is used to determine the starting troubleshooting step corresponding to the starting troubleshooting step node in the target troubleshooting path; the third determination submodule is used to determine the subsequent troubleshooting steps based on the starting feedback data corresponding to the starting troubleshooting step.

[0091] According to an embodiment of the present application, the third determination submodule includes a matching unit configured to match the initial feedback data with the feedback data value condition associated with the initial troubleshooting step node, and determine subsequent troubleshooting steps based on the matching result.

[0092] According to an embodiment of the present application, the server fault troubleshooting device 500 further includes a third determination module, a reading module, a fourth determination module and a visual marking module.

[0093] The third determination module is used to determine the target identification information of the target node to be checked; the reading module is used to read the target coordinate information and target rendering rules corresponding to the target node to be checked from a pre-built node mapping relationship set according to the target identification information; the fourth determination module is used to determine the target model device corresponding to the target node to be checked in the pre-built server model based on the target coordinate information; the visual marking module is used to visually mark the target model device based on the target rendering rule.

[0094] According to an embodiment of the present application, the server fault troubleshooting device 500 further includes a fifth determination module.

[0095] The fifth determination module is used to determine and display to the user the troubleshooting step execution information corresponding to the troubleshooting step, and the troubleshooting step execution information includes at least one of the following: troubleshooting equipment usage information and node material information to be checked.

[0096] According to an embodiment of the present application, the server fault troubleshooting device 500 further includes an execution module.

[0097] The execution module is used for executing an update operation on a preset fault information set based on the conclusion feedback information obtained from the user in response to the conclusion feedback information.

[0098] According to embodiments of the present application, any multiple modules among the first determination module 510, the second determination module 520, the sending module 530, and the output module 540 may be combined into a single module, or any one of these modules may be split into multiple modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of other modules and implemented in a single module. According to embodiments of the present application, at least one of the first determination module 510, the second determination module 520, the sending module 530, and the output module 540 may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FPGA), a programmable logic array (PLA), a system on a chip, a system on a substrate, a system on a package, an application-specific integrated circuit (ASIC), or may be implemented in hardware or firmware through any other reasonable means of circuit integration or packaging, or may be implemented in any one of the three implementation methods of software, hardware, and firmware, or any appropriate combination of any of these. Alternatively, at least one of the first determination module 510 , the second determination module 520 , the sending module 530 and the output module 540 may be at least partially implemented as a computer program module, which may perform corresponding functions when executed.

[0099] Figure 6 A block diagram of an electronic device suitable for implementing a server fault troubleshooting method according to an embodiment of the present application is shown.

[0100] like Figure 6 As shown, an electronic device 600 according to an embodiment of the present application includes a processor 601, which can perform various appropriate actions and processes based on a program stored in a read-only memory (ROM) 602 or a program loaded from a storage unit 608 into a random access memory (RAM) 603. The processor 601 may include, for example, a general-purpose microprocessor (e.g., a CPU), an instruction set processor and / or a related chipset and / or a dedicated microprocessor (e.g., an application-specific integrated circuit (ASIC)), etc. The processor 601 may also include onboard memory for caching purposes. The processor 601 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present application.

[0101] Various programs and data required for the operation of the electronic device 600 are stored in the RAM 603. The processor 601, ROM 602, and RAM 603 are connected to each other via a bus 604. The processor 601 performs various operations of the method flow according to the embodiment of the present application by executing the programs in the ROM 602 and / or RAM 603. It should be noted that the programs may also be stored in one or more memories other than the ROM 602 and RAM 603. The processor 601 may also perform various operations of the method flow according to the embodiment of the present application by executing the programs stored in one or more memories.

[0102] According to an embodiment of the present application, electronic device 600 may further include an input / output (I / O) interface 605, which is also connected to bus 604. Electronic device 600 may also include one or more of the following components connected to I / O interface 605: an input section 606 including a keyboard, mouse, etc.; an output section 607 including devices such as a cathode ray tube (CRT), liquid crystal display (LCD), and speakers; a storage section 608 including a hard disk; and a communication section 609 including a network interface card such as a LAN card or modem. Communication section 609 performs communication processing via a network such as the Internet. A drive 610 is also connected to I / O interface 605 as needed. Removable media 611, such as a magnetic disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed in drive 610 as needed, so that computer programs read from the removable media can be installed into storage section 608 as needed.

[0103] This application also provides a computer-readable storage medium, which may be included in the device / apparatus / system described in the above embodiments, or may exist independently and not be incorporated into the device / apparatus / system. The computer-readable storage medium carries one or more programs, and when the one or more programs are executed, the method according to the embodiments of this application is implemented.

[0104] According to an embodiment of the present application, a computer-readable storage medium may be a non-volatile computer-readable storage medium, and may include, for example, but not limited to: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present application, a computer-readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. For example, according to an embodiment of the present application, a computer-readable storage medium may include the ROM 602 and / or RAM 603 described above and / or one or more memories other than ROM 602 and RAM 603.

[0105] The embodiments of the present application also include a computer program product, which includes a computer program containing program code for executing the method shown in the flowchart. When the computer program product is run in a computer system, the program code is used to enable the computer system to implement the method provided in the embodiments of the present application.

[0106] The computer program executes the above functions defined in the system / device of the embodiment of the present application when the computer program is executed by the processor 601. According to the embodiment of the present application, the system, device, module, unit, etc. described above can be implemented by a computer program module.

[0107] In one embodiment, the computer program may be stored on a tangible storage medium such as an optical storage device or a magnetic storage device. In another embodiment, the computer program may be transmitted and distributed in the form of a signal on a network medium, downloaded and installed via the communication portion 609, and / or installed from a removable medium 611. The program code contained in the computer program may be transmitted using any appropriate network medium, including but not limited to wireless, wired, or any suitable combination thereof.

[0108] In such an embodiment, the computer program can be downloaded and installed from a network via the communication section 609, and / or installed from a removable medium 611. When the computer program is executed by the processor 601, the above-mentioned functions defined in the system of the embodiment of the present application are performed. According to the embodiment of the present application, the systems, devices, means, modules, units, etc. described above can be implemented by computer program modules.

[0109] According to an embodiment of the present application, the program code for executing the computer program provided by the embodiment of the present application can be written in any combination of one or more programming languages. Specifically, these computer programs can be implemented using high-level procedural and / or object-oriented programming languages, and / or assembly / machine languages. Programming languages include, but are not limited to, languages such as Java, C++, Python, "C" or similar programming languages. The program code can be executed entirely on the user computing device, partially on the user device, partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device can be connected to the user computing device through any type of network, including a local area network (LAN) or a wide area network (WAN), or can be connected to an external computing device (for example, using an Internet service provider to connect via the Internet).

[0110] The flowcharts and block diagrams in the accompanying drawings illustrate the possible implementation architecture, functions and operations of the systems, methods and computer program products according to various embodiments of the present application. In this regard, each box in the flowchart or block diagram can represent a module, program segment, or a part of code, and the above-mentioned module, program segment, or a part of code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some alternative implementations, the functions marked in the box can also occur in an order different from that marked in the accompanying drawings. For example, two boxes represented in succession can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flowchart, and the combination of the boxes in the block diagram or flowchart, can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0111] Those skilled in the art will appreciate that the features described in the various embodiments of this application may be combined and / or coupled in various ways, even if such combinations or couplings are not explicitly described in this application. In particular, the features described in the various embodiments of this application may be combined and / or coupled in various ways without departing from the spirit and teachings of this application. All such combinations and / or couplings fall within the scope of this application.

[0112] The embodiments of the present application have been described above. However, these embodiments are for illustrative purposes only and are not intended to limit the scope of the present application. Although each embodiment has been described separately above, this does not mean that the measures in each embodiment cannot be advantageously used in combination. Without departing from the scope of the present application, those skilled in the art may make various substitutions and modifications, and these substitutions and modifications should all fall within the scope of the present application.

Claims

1. A server fault troubleshooting method, characterized in that: The method comprises: Determine, based on a preset fault information set, the troubleshooting steps corresponding to the target server fault phenomenon input by the user; Determine the target node to be checked corresponding to the troubleshooting step, and display theoretical location information of the target node to be checked in the target server to the user; According to the execution order of the troubleshooting steps, the theoretical location information is sent to a preset positioning device, so that the preset positioning device displays the actual location information of the target node to be checked in the target server to the user based on the received theoretical location information; In response to obtaining troubleshooting feedback information, a troubleshooting conclusion for the target server fault phenomenon is output based on the troubleshooting feedback information, wherein the troubleshooting feedback information is obtained by the user performing the troubleshooting steps based on the theoretical location information and the actual location information.

2. The method according to claim 1, characterized in that The preset fault information set includes a correspondence between a server fault phenomenon and a troubleshooting path, and the troubleshooting path includes at least one troubleshooting step node and a connection sequence between at least one of the troubleshooting step nodes.

3. The method according to claim 2, characterized in that The step of determining, based on the preset fault information set, the fault phenomenon of the target server input by the user and corresponding to the fault includes: Determining a target troubleshooting path corresponding to the target server fault phenomenon from the preset fault information set; Determining a starting troubleshooting step corresponding to a starting troubleshooting step node in the target troubleshooting path; Determine subsequent troubleshooting steps based on initial feedback data corresponding to the initial troubleshooting step.

4. The method according to claim 3, characterized in that The troubleshooting path further includes a feedback data value condition associated with the at least one troubleshooting step node; The determining of subsequent troubleshooting steps based on the initial feedback data corresponding to the initial troubleshooting step includes: The initial feedback data is matched with the feedback data value condition associated with the initial troubleshooting step node, and the subsequent troubleshooting step is determined according to the matching result.

5. The method according to claim 1, wherein The method further comprises: Determine the target identification information of the target node to be checked; Reading target coordinate information and target rendering rules corresponding to the target node to be checked from a pre-built node mapping relationship set according to the target identification information; Determining a target model component corresponding to the target node to be checked in a pre-built server model based on the target coordinate information; The target model device is visually marked based on the target rendering rule.

6. The method according to claim 1, characterized in that The method further comprises: Determine and display to the user the troubleshooting step execution information corresponding to the troubleshooting step, wherein the troubleshooting step execution information includes at least one of the following: troubleshooting equipment usage information and node material information to be troubleshooted.

7. The method according to claim 1, characterized in that The method further comprises: In response to obtaining conclusion feedback information of the user on the fault troubleshooting conclusion, an update operation of the preset fault information set is performed based on the conclusion feedback information.

8. A computer program product comprising a computer program or instructions, characterized in that When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

9. An electronic device comprising: one or more processors; a memory for storing one or more computer programs, It is characterized in that the one or more processors execute the one or more computer programs to implement the steps of the method according to any one of claims 1 to 7.

10. A computer-readable storage medium having a computer program or instruction stored thereon, characterized in that: When the computer program or instruction is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.

Images