Server debugging method and device, storage medium and electronic equipment
By deploying transmitters of multiple wireless communication protocols on the server debugging equipment, the problem of low server debugging efficiency in the prior art is solved, efficient fault information collection and debugging instruction execution in different network environments is realized, and the flexibility and speed of debugging are improved.
Patent Information
- Application Number
- CN202411620656.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-11-13
- Publication Date
- 2025-03-04
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
In the prior art, server debugging efficiency is low, especially in the R&D stage or network restriction environment, traditional debugging methods have problems of insufficient flexibility and timeliness.
A server debugging method is provided, by deploying a connector, a controller, a first transmitter and a second transmitter on a debugging device, and using the first wireless communication protocol and the second wireless communication protocol, the collection, transmission and generation and execution of server fault information in different network environments.
This method improves the efficiency and flexibility of server debugging, and can debug without accessing the server's corresponding LAN or mobile communication network, reduces geographical restrictions, and improves the speed and accuracy of fault response and repair.
Smart Images

Figure CN119557132A_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of computers, and in particular, to a server debugging method and device, a storage medium, and an electronic device. Background Art
[0002] As the core equipment of the data center, the stability and reliability of the server are of vital importance. Server failure will not only bring the risk of data loss, but also cause business interruption and cause great losses. The server's BIOS (Basic Input / Output System) debugging and fault analysis are key links to ensure its normal operation. Therefore, quickly and accurately locating and repairing faults in server BIOS debugging is an important link in server R&D and operation and maintenance.
[0003] In the prior art, the efficiency of server debugging is low, mainly limited by two traditional debugging methods. One method is to communicate through the BMC (baseboard management controller). Although it can achieve remote monitoring, it requires the server to be connected to the network, which is difficult to meet in the R&D stage or in a network-restricted usage environment. Another method is to use a serial port line to directly connect to the server for debugging. Although this method can ensure direct data transmission, it requires BIOS engineers to operate on-site, which greatly limits the flexibility and timeliness of debugging.
[0004] With regard to the problems in related technologies such as low efficiency of server debugging, no effective solution has been proposed yet. Summary of the invention
[0005] The embodiments of the present application provide a server debugging method and device, a storage medium, and an electronic device to at least solve the problem of low efficiency of server debugging in the related art.
[0006] According to an embodiment of the present application, a server debugging method is provided, wherein a connector, a controller, a first transmitter and a second transmitter are deployed on a debugging device, the connector is connected to the first transmitter and the second transmitter respectively through the controller, the connector is used to connect to the server to be debugged, the first transmitter is configured to allow data to be transmitted using a first wireless communication protocol, the first wireless communication protocol is a protocol that allows data to be transmitted using a mobile communication network without accessing a local area network corresponding to the server to be debugged, the second transmitter is configured to allow data to be transmitted using a second wireless communication protocol, the second wireless communication protocol is a protocol that allows data to be transmitted within a target distance of the second transmitter without accessing a mobile communication network, and the method is applied to the controller, comprising:
[0007] Collecting target server fault information generated during the fault operation from the server to be debugged;
[0008] Filtering out a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment currently located by the server to be debugged;
[0009] Controlling the target transmitter to transmit the target server fault information to the target terminal, wherein the target terminal is used to send a target debugging instruction generated according to the target server fault information to the target transmitter, wherein the target debugging instruction is used to indicate a debugging operation that allows the fault operation of the server to be debugged to be repaired;
[0010] The debugging operation indicated by the target debugging instruction is executed on the server to be debugged.
[0011] Optionally, the step of selecting a target transmitter that matches a target network state currently located by the server to be debugged from the first transmitter and the second transmitter includes:
[0012] Detecting the current network status of the server to be debugged;
[0013] In a case where the network state of the server to be debugged is currently a first network state, determining the first transmitter as the target transmitter, wherein the first network state is used to indicate that data can be transmitted between a device and an external terminal in a network environment where the server to be debugged is currently located without accessing a local area network corresponding to the server to be debugged using a mobile communication network;
[0014] When the network state of the server to be debugged is currently a second network state, the second transmitter is determined as the target transmitter, wherein the second network state is used to indicate that data transmission within the target distance is allowed between the device and the external terminal in the network environment where the server to be debugged is currently located without accessing the mobile communication network.
[0015] Optionally, controlling the target transmitter to transmit the target server fault information to the target terminal includes:
[0016] In the case where the target transmitter is the first transmitter, the first transmitter is controlled to transmit the target server fault information to a first terminal, wherein the first terminal and the first transmitter transmit data using the first wireless communication protocol, and the first terminal is used to: extract candidate fault keywords from the target server fault information, match candidate fault operation types corresponding to the candidate fault keywords from fault keywords and fault operation types with corresponding relationships, match candidate debugging instructions corresponding to the candidate fault operation types from fault operation types and debugging instructions with corresponding relationships, and send the candidate debugging instructions to the target transmitter, wherein the candidate debugging instructions are used to indicate a debugging operation that allows repairing the fault of the candidate fault operation type, the target debugging instructions include the candidate debugging instructions, and the target terminal includes the first terminal;
[0017] In the case that the target transmitter is the second transmitter, the second transmitter is controlled to transmit the target server fault information to the second terminal, wherein the second wireless communication protocol is used to transmit data between the second terminal and the second transmitter, and the second terminal is used to: extract alternative fault keywords from the target server fault information, match alternative fault operation types corresponding to the alternative fault keywords from fault keywords and fault operation types with corresponding relationships, match alternative debugging instructions corresponding to the alternative fault operation types from fault operation types and debugging instructions with corresponding relationships, send the alternative debugging instructions to the target transmitter, the alternative debugging instructions are used to indicate debugging operations that allow repairing the faults of the alternative fault operation types, the target debugging instructions include the alternative debugging instructions, and the second terminal is an external terminal located within the target distance of the second transmitter, and the target terminal includes the second terminal.
[0018] Optionally, a power supply is further deployed on the debugging device, the controller, the first transmitter, and the second transmitter are respectively connected to the power supply, and the controlling the target transmitter to transmit the target server fault information to the target terminal includes:
[0019] When the target transmitter is the first transmitter, controlling the power supply to turn on the power supply of the first transmitter, and controlling the power supply to turn off the power supply of the second transmitter, wherein the first transmitter is configured to transmit data using the first wireless communication protocol when powered, and the second transmitter is configured to prohibit the use of the second wireless communication protocol to transmit data when not powered;
[0020] When the target transmitter is the second transmitter, the power supply is controlled to turn on the power supply of the second transmitter, and the power supply is controlled to turn off the power supply of the first transmitter, wherein the second transmitter is configured to transmit data using the first wireless communication protocol when powered, and the first transmitter is configured to prohibit the use of the first wireless communication protocol to transmit data when not powered.
[0021] Optionally, collecting target server fault information generated during fault operation from the server to be debugged includes:
[0022] Detecting the connection status between the connector and the server to be debugged;
[0023] In the case where the connection state is a normal connection state, generating a target acquisition instruction, wherein the target acquisition instruction is used to instruct the server to be debugged to transmit server fault information to the controller;
[0024] Calling the connector to send the target acquisition instruction to the server to be debugged;
[0025] Receive the target server failure information transmitted by the server to be debugged.
[0026] Optionally, after collecting target server fault information generated during fault operation from the server to be debugged, the method further includes:
[0027] Identify the reference fault operation type of the server to be debugged according to the target server fault information;
[0028] A reference debugging instruction matching the reference fault operation type is generated, wherein the reference debugging instruction is used to indicate a debugging operation that allows repairing a fault of the reference fault operation type.
[0029] Optionally, a first memory and a second memory are further deployed on the debugging device, the first memory and the second memory are respectively connected to the controller, the first memory stores fault keywords and fault operation types with corresponding relationships, the second memory stores fault operation types and debugging instructions with corresponding relationships, and the identifying the reference fault operation type of the server to be debugged according to the target server fault information includes:
[0030] Extracting reference fault keywords from the target server fault information;
[0031] Matching the reference fault operation type corresponding to the reference fault keyword from the fault keywords and fault operation types having a corresponding relationship;
[0032] The generating a reference debugging instruction matching the reference fault operation type comprises:
[0033] The reference debugging instruction corresponding to the reference fault operation type is matched from the fault operation types and debugging instructions having a corresponding relationship.
[0034] According to another embodiment of the embodiment of the present application, a debugging device for a server is further provided, wherein a connector, a controller, a first transmitter and a second transmitter are deployed on the debugging device, wherein the connector is connected to the first transmitter and the second transmitter respectively through the controller, wherein the connector is used to connect to the server to be debugged, wherein the first transmitter is configured to allow data to be transmitted using a first wireless communication protocol, wherein the first wireless communication protocol is a protocol that allows data to be transmitted using a mobile communication network without accessing a local area network corresponding to the server to be debugged, wherein the second transmitter is configured to allow data to be transmitted using a second wireless communication protocol, wherein the second wireless communication protocol is a protocol that allows data to be transmitted within a target distance of the second transmitter without accessing a mobile communication network, wherein the device is applied to the controller and includes:
[0035] A collection module, used for collecting target server fault information generated during the fault operation from the server to be debugged;
[0036] a screening module, used to screen out a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment currently located by the server to be debugged;
[0037] a control module, configured to control the target transmitter to transmit the target server fault information to a target terminal, wherein the target terminal is configured to send a target debugging instruction generated according to the target server fault information to the target transmitter, wherein the target debugging instruction is configured to indicate a debugging operation that allows the fault operation of the server to be debugged to be repaired;
[0038] The execution module is used to execute the debugging operation indicated by the target debugging instruction on the server to be debugged.
[0039] According to another embodiment of the present application, a computer program product is provided, including a computer program, wherein the computer program is executed by a processor to perform the steps in any of the above method embodiments.
[0040] According to another embodiment of the present application, a computer-readable storage medium is provided, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when run.
[0041] According to another embodiment of the present application, an electronic device is provided, including a memory and a processor, wherein the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0042] In an embodiment of the present application, a server debugging method is proposed. A connector, a controller, a first transmitter and a second transmitter are deployed on the debugging device. The connector is connected to the first transmitter and the second transmitter respectively through the controller. The connector can be connected to the server to be debugged. The first transmitter is configured to allow the use of a first wireless communication protocol to transmit data. The first wireless communication protocol is a protocol that allows the use of a mobile communication network to transmit data without accessing a local area network corresponding to the server to be debugged. The second transmitter is configured to allow the use of a second wireless communication protocol to transmit data. The second wireless communication protocol is a protocol that allows the use of a mobile communication network to transmit data within a target distance of the second transmitter without accessing a mobile communication network. The controller first collects target server fault information generated during fault operation from the server to be debugged; then, a target transmitter that matches the target network state currently located in the server to be debugged is selected from the first transmitter and the second transmitter. The target network state can indicate the data transmission method allowed to be used between the device and the external terminal in the network environment currently located in the server to be debugged. Afterwards, the target transmitter is controlled to transmit the target server fault information to the target terminal. The target terminal can send a target debugging instruction generated according to the target server fault information to the target transmitter. The target debugging instruction can indicate a debugging operation that allows the repair of the faulty operation of the server to be debugged. Finally, the debugging operation indicated by the target debugging instruction is executed on the server to be debugged. By deploying a transmitter supporting the first wireless communication protocol and the second wireless communication protocol in the debugging device, the server can be debugged in a variety of environments, including a situation where access to the local area network corresponding to the server to be debugged is not allowed or access to the mobile communication network is not allowed. At the same time, the server fault information is directly transmitted to the target terminal through wireless transmission, and then the target debugging instruction corresponding to the fault information is sent back to the controller in the same wireless transmission mode. No thread wiring debugging is required, which makes up for the deficiency of the prior art in the dependence on a specific network environment and geographical restrictions in the server debugging process. The above technical solution is adopted to solve the problems of low efficiency of server debugging in related technologies, and achieves the technical effect of improving the efficiency of server debugging. BRIEF DESCRIPTION OF THE DRAWINGS
[0043] Figure 1 It is a hardware structure block diagram of a computer device of a server debugging method according to an embodiment of the present application;
[0044] Figure 2 is a flow chart of a server debugging method according to an embodiment of the present application;
[0045] Figure 3 is a schematic diagram of a system module diagram of a server debugging method according to an embodiment of the present application;
[0046] Figure 4 is a schematic diagram of a server fault diagnosis rule structure in a server debugging method according to an embodiment of the present application;
[0047] Figure 5 is a schematic diagram of a server fault debugging rule structure in a server debugging method according to an embodiment of the present application;
[0048] Figure 6 It is a schematic diagram of a system module diagram of a debugging extension method for a server according to an embodiment of the present application;
[0049] Figure 7 It is a schematic diagram of a server debugging method process according to an embodiment of the present application;
[0050] Figure 8 is a structural block diagram of a server debugging device according to an embodiment of the present application;
[0051] Fig. 9 is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION
[0052] The embodiments of the present application will be described in detail below with reference to the accompanying drawings and in combination with the embodiments.
[0053] It should be noted that the terms "first", "second", etc. in the specification and claims of this application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.
[0054] The method embodiments provided in the embodiments of the present application can be executed in a server device or a similar computing device. Taking running on a server device as an example, Figure 1 1 is a hardware structure block diagram of a computer device of a server debugging method according to an embodiment of the present application. Figure 1 As shown, the server device may include one or more ( Figure 1Only one is shown in the figure) a processor 102 (the processor 102 may include but is not limited to a processing device such as a microprocessor MCU or a programmable logic device FPGA) and a memory 104 for storing data, wherein the server device may also include a transmission device 106 and an input / output device 108 for communication functions. It can be understood by those skilled in the art that Figure 1 The structure shown is only for illustration and does not limit the structure of the above server device. Figure 1 More or fewer components as shown, or with Figure 1 Different configurations shown.
[0055] The memory 104 can be used to store computer programs, for example, software programs and modules of application software, such as the computer program corresponding to the debugging method of the server in the embodiment of the present application. The processor 102 executes various functional applications and data processing by running the computer program stored in the memory 104, that is, to implement the above method. The memory 104 may include a high-speed random access memory, and may also include a non-volatile memory, such as one or more magnetic storage devices, flash memory, or other non-volatile solid-state memory. In some instances, the memory 104 may further include a memory remotely arranged relative to the processor 102, and these remote memories may be connected to the server device via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0056] The transmission device 106 is used to receive or send data via a network. The specific example of the above network may include a wireless network provided by a communication provider of the server device. In one example, the transmission device 106 includes a network adapter (Network Interface Controller, referred to as NIC), which can be connected to other network devices through a base station so as to communicate with the Internet. In one example, the transmission device 106 can be a radio frequency (RF) module, which is used to communicate with the Internet wirelessly.
[0057] In this embodiment, a server debugging method is provided. A connector, a controller, a first transmitter and a second transmitter are deployed on a debugging device. The connector is connected to the first transmitter and the second transmitter respectively through the controller. The connector is used to connect to the server to be debugged. The first transmitter is configured to allow data to be transmitted using a first wireless communication protocol, which is a protocol that allows data to be transmitted using a mobile communication network without accessing a local area network corresponding to the server to be debugged. The second transmitter is configured to allow data to be transmitted using a second wireless communication protocol, which is a protocol that allows data to be transmitted within a target distance of the second transmitter without accessing a mobile communication network. The method is applied to the controller. Figure 2 is a flow chart of a server debugging method according to an embodiment of the present application, such as Figure 2 As shown, the process includes the following steps:
[0058] Step S12, collecting target server fault information generated during the fault operation from the server to be debugged;
[0059] Step S14, selecting a target transmitter that matches the target network state in which the server to be debugged is currently located from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment in which the server to be debugged is currently located;
[0060] Step S16, controlling the target transmitter to transmit the target server fault information to the target terminal, wherein the target terminal is used to send a target debugging instruction generated according to the target server fault information to the target transmitter, wherein the target debugging instruction is used to indicate a debugging operation that allows repairing the fault operation of the server to be debugged;
[0061] Step S18: executing the debugging operation indicated by the target debugging instruction on the server to be debugged.
[0062] Optionally, in this embodiment, Figure 3 is a schematic diagram of a system module diagram of a server debugging method according to an embodiment of the present application, such as Figure 3As shown, the debugging device can be, but is not limited to, a server BIOS wireless debugging device composed of multiple modules; the connector can be, but is not limited to, a serial port communication module in the server BIOS wireless debugging device; the controller can be, but is not limited to, a component that can complete tasks such as data processing and data exchange, such as MCU (Microcontroller Unit), which can be implemented by single-chip microcomputers such as STM32 and MSP430; the first transmitter can be, but is not limited to, a module that allows data to be transmitted using a mobile communication network without accessing the local area network corresponding to the server to be tested, such as a 4G / 5G transmission module, which can be implemented using a DTU (Data Transfer Unit), and the corresponding first wireless communication protocol can be, but is not limited to, including: the fourth generation mobile communication protocol (4G) and the fifth generation mobile communication protocol (5G); the second transmitter can be, but is not limited to, a module that allows data to be transmitted within its target distance without accessing the mobile communication network, such as a Bluetooth transmission module, which can be implemented using a Bluetooth chip and module. The corresponding second wireless communication protocol can be, but is not limited to, including: Bluetooth communication protocol (Bluetooth) and ZigBee communication protocol.
[0063] Optionally, in this embodiment, if Figure 3 As shown, the serial communication module is connected to the 4G transmission module (first transmitter) and the Bluetooth transmission module (second transmitter) respectively through the control module MCU, and is connected to the server to be debugged by serial communication through the serial communication module. The serial communication module is used to interact with the server to be debugged for serial information. The functions of the serial communication module may include but are not limited to: collecting target server fault information (logs, BIOS debug information or other information that can indicate fault information) generated when the server to be debugged fails to run, and may also transmit information sent by the controller (including information on debugging operations indicated by target debugging instructions).
[0064] Optionally, in this embodiment, if Figure 3 As shown, the target transmitter can be selected from the first transmitter and the second transmitter in the following ways, but not limited to: button triggering selection, selecting a suitable transmitter according to the current network environment of the server to be debugged, and controlling the selection switch button of the wireless transmission module (the first transmitter or the second transmitter) in the server BIOS wireless debugging device to determine the corresponding transmitter as the target transmitter; the controller autonomously selects, and the controller automatically matches the suitable transmitter according to the current network environment of the server to be debugged.
[0065] Optionally, in this embodiment, the target terminal may include but is not limited to any device that can receive and process data from the debugging device, display data, analyze results, and send control commands, including a first terminal and a second terminal, wherein the first terminal may be but is not limited to an application deployed on a server or a PC-side host computer, which is used for BIOS R&D personnel to remotely debug server failures; the second terminal may be but is not limited to an application installed on a mobile device-side host computer (a portable device such as a smart phone or a tablet computer), which can be used to debug the server in a close distance or without a serial line environment.
[0066] Optionally, in this embodiment, if Figure 3 As shown, the 4G transmission module uses the mobile communication network to transmit data with the target terminal when the server to be debugged is not allowed to connect to the corresponding local area network, and the Bluetooth transmission module uses Bluetooth transmission to transmit data with the target terminal when the server to be debugged is not allowed to use the mobile communication network. After determining the target transmitter, the target transmitter can transmit the target server fault information processed by the controller to the target terminal through wireless transmission, or receive the target debugging instruction generated by the target terminal according to the target server fault information processed by the controller, and then send it to the server to be debugged through the controller to execute the operation indicated by the target debugging instruction, wherein the target debugging instruction can be a control command that can repair the faulty operation of the server to be debugged.
[0067] As an optional solution, the step of selecting a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter includes:
[0068] S21, detecting the current network status of the server to be debugged;
[0069] S22, when the network state of the server to be debugged is currently a first network state, determining the first transmitter as the target transmitter, wherein the first network state is used to indicate that in the network environment where the server to be debugged is currently located, it is allowed to use a mobile communication network to transmit data between a device and an external terminal without accessing a local area network corresponding to the server to be debugged;
[0070] S23, when the network state of the server to be debugged is currently a second network state, determining the second transmitter as the target transmitter, wherein the second network state is used to indicate that data transmission within the target distance is allowed between the device and the external terminal in the network environment where the server to be debugged is currently located without accessing the mobile communication network.
[0071] Optionally, in this embodiment, the first network state may include but is not limited to a network state in which the local area network corresponding to the server to be debugged cannot be connected but the mobile communication network can be used to transmit data. For example, when the server to be debugged is in an environment where it can be connected to an external network, the target terminal can transmit data with the server to be debugged through a 4G or 5G network even if it is not in the same local area network as the server to be debugged. This state is determined as the first network state, and the first transmitter is selected as the destination transmitter.
[0072] Optionally, in this embodiment, the second network state may include but is not limited to a network state in which the mobile communication network cannot be used but data can be transmitted within the target instance. For example, when the server to be debugged is in an environment where it cannot be connected to the external network, the target terminal can choose to transmit data with it via Bluetooth within the effective range of Bluetooth, determine this state as the second network state, and select the second transmitter as the destination transmitter.
[0073] Optionally, in this embodiment, the target transmitter can be determined by, but is not limited to, the following methods: a BIOS engineer detects the current network environment of the server to be debugged and selects a suitable target transmitter; the controller autonomously selects, the controller detects the current network environment of the server to be debugged and selects a matching target transmitter, the controller first performs a network connection test, and automatically selects the first transmitter as the target transmitter if the network connection is successful, and automatically selects the second transmitter as the target transmitter if the network connection fails.
[0074] As an optional solution, controlling the target transmitter to transmit the target server fault information to the target terminal includes:
[0075] S31, when the target transmitter is the first transmitter, control the first transmitter to transmit the target server fault information to the first terminal, wherein the first wireless communication protocol is used to transmit data between the first terminal and the first transmitter, and the first terminal is used to: extract candidate fault keywords from the target server fault information, match candidate fault operation types corresponding to the candidate fault keywords from fault keywords and fault operation types with corresponding relationships, match candidate debugging instructions corresponding to the candidate fault operation types from fault operation types and debugging instructions with corresponding relationships, send the candidate debugging instructions to the target transmitter, the candidate debugging instructions are used to indicate a debugging operation that allows repairing the fault of the candidate fault operation type, the target debugging instructions include the candidate debugging instructions, and the target terminal includes the first terminal;
[0076] S32, when the target transmitter is the second transmitter, control the second transmitter to transmit the target server fault information to the second terminal, wherein the second wireless communication protocol is used to transmit data between the second terminal and the second transmitter, and the second terminal is used to: extract alternative fault keywords from the target server fault information, match alternative fault operation types corresponding to the alternative fault keywords from fault keywords and fault operation types with corresponding relationships, match alternative debugging instructions corresponding to the alternative fault operation types from fault operation types and debugging instructions with corresponding relationships, and send the alternative debugging instructions to the target transmitter, the alternative debugging instructions are used to indicate debugging operations that allow repairing the fault of the alternative fault operation type, the target debugging instructions include the alternative debugging instructions, and the second terminal is an external terminal located within the target distance of the second transmitter, and the target terminal includes the second terminal.
[0077] Optionally, in this embodiment, Figure 4 is a schematic diagram of a server fault diagnosis rule structure in a server debugging method according to an embodiment of the present application, such as Figure 4 As shown, the fault diagnosis rules may be, but are not limited to, a data set including n known fault keywords and corresponding m fault operation types, where n and m are integers greater than 0 and satisfy n greater than or equal to m, that is, one or more fault keywords may belong to the same fault operation type, and the fault types may include, but are not limited to, downtime, memory failure, CPU failure, PCIE failure, etc.
[0078] Optionally, in this embodiment, Figure 5 is a schematic diagram of a server fault debugging rule structure in a server debugging method according to an embodiment of the present application, such as Figure 5 As shown, the fault debugging rule may be, but is not limited to, a data set including m known operation types and corresponding x debugging instructions, where x is an integer greater than 0 and satisfies x less than or equal to m, that is, one or more fault operation types can be repaired by one debugging instruction.
[0079] Optionally, in this embodiment, both fault diagnosis rules and fault debugging rules can be pre-embedded by R&D personnel during the debugging equipment production stage, or can be dynamically sent to the controller by BIOS debugging engineers at the target terminal to adapt to changing fault diagnosis needs.
[0080] Optionally, in this embodiment, if Figure 3As shown, in the case where it is determined that the target transmitter is the first transmitter, the control module MCU in the debugging device controls the 4G transmission module to transmit the BIOS debug information to the PC-side host computer. After receiving the BIOS debug information, the PC-side host computer first extracts candidate fault keywords from it. The candidate fault keywords can be but are not limited to key sentences in the BIOS debug information that can indicate a certain fault type of the server. Then, fault operation type matching is performed. According to the known fault keywords and the corresponding fault operation types, candidate fault operation types matching the candidate fault key sentences are obtained. Then, according to the known fault operation types and the corresponding debugging instructions, candidate debugging instructions matching the candidate fault operation types are obtained. Finally, the candidate debugging instructions are sent to the target transmitter, wherein the candidate debugging instructions can be debugging operations that allow repairing server faults of the candidate fault operation types.
[0081] Optionally, in this embodiment, if Figure 3 As shown, when it is determined that the target transmitter is the second transmitter, the control module MCU in the debugging device controls the Bluetooth transmission module to transmit the BIOS debug information to the mobile device host computer. The operation process of the mobile device host computer after receiving the BIOS debug information is similar to that of the PC host computer, which will not be repeated here.
[0082] Optionally, in this embodiment, due to differences between the PC-side host computer and the mobile device-side host computer in terms of user interface, performance, usage scenarios, user roles and data display, the extracted fault keywords may be different, and the corresponding fault operation types and subsequent debugging instructions may also be different.
[0083] As an optional solution, a power supply is also deployed on the debugging device, and the controller, the first transmitter and the second transmitter are respectively connected to the power supply, and the controlling the target transmitter to transmit the target server fault information to the target terminal includes:
[0084] S41, when the target transmitter is the first transmitter, controlling the power supply to turn on the power supply of the first transmitter, and controlling the power supply to turn off the power supply of the second transmitter, wherein the first transmitter is configured to transmit data using the first wireless communication protocol when powered, and the second transmitter is configured to prohibit the use of the second wireless communication protocol to transmit data when not powered;
[0085] S42, when the target transmitter is the second transmitter, controlling the power supply to turn on the power supply of the second transmitter, and controlling the power supply to turn off the power supply of the first transmitter, wherein the second transmitter is configured to transmit data using the first wireless communication protocol when powered, and the first transmitter is configured to prohibit the use of the first wireless communication protocol to transmit data when not powered.
[0086] Optionally, in this embodiment, the power supply may be, but is not limited to, a power supply module that can supply power to each functional module on the debugging device, such as Figure 3 As shown, the server BIOS wireless debugging device also includes a power module for controlling the power supply of other modules in the debugging device. The voltage can be converted into different voltages such as 3.3V and 5V through different voltage conversion chips to meet the power requirements of different modules.
[0087] Optionally, in this embodiment, if Figure 3 As shown, both the 4G transmission module and the Bluetooth transmission module can use the corresponding wireless communication protocol (the first wireless communication protocol or the second wireless communication protocol) to transmit data only when they are powered. Specifically, when it is determined that the target transmitter is the 4G transmission module, the control module MCU controls the power module to power the 4G transmission module and stops powering the Bluetooth transmission module; when it is determined that the target transmitter is the Bluetooth transmission module, the control module MCU controls the power module to power the Bluetooth transmission module and stops powering the 4G transmission module.
[0088] As an optional solution, the collecting of target server fault information generated during the fault operation of the server to be debugged includes:
[0089] S51, detecting the connection status between the connector and the server to be debugged;
[0090] S52, when the connection state is a normal connection state, generating a target acquisition instruction, wherein the target acquisition instruction is used to instruct the server to be debugged to transmit server fault information to the controller;
[0091] S53, calling the connector to send the target acquisition instruction to the server to be debugged;
[0092] S54: Receive the target server failure information transmitted by the server to be debugged.
[0093] Optionally, in this embodiment, if Figure 3As shown, before the control module MCU collects the BIOS debug information generated during the fault operation from the server to be debugged, it is necessary to first detect the connection status between the serial port communication module and the serial port of the server to be debugged. The detection method can be but is not limited to judging the connection status through the indicator light 1 on the debugging device indicating the connection status with the serial port of the server to be debugged. For example, if the indicator light 1 flashes green, it means that the connector is connected to the server to be debugged normally, wherein the indicator light can be an LED light. When the detection result shows that the connection is normal, the control module MCU generates a target collection instruction, and calls the serial port communication module to send the target collection instruction to the server to be debugged. After the server to be debugged responds to the target collection instruction, the BIOS debug information is transmitted to the control module MCU, thereby realizing the collection of the BIOS debug information of the server to be debugged.
[0094] As an optional solution, after collecting the target server fault information generated during the fault operation from the server to be debugged, the method further includes:
[0095] S61, identifying a reference fault operation type of the server to be debugged according to the target server fault information;
[0096] S62: Generate a reference debugging instruction matching the reference fault operation type, wherein the reference debugging instruction is used to indicate a debugging operation that allows repairing a fault of the reference fault operation type.
[0097] Optionally, in this embodiment, after collecting the target server fault information of the server to be debugged, the controller can further match the target server fault information with the fault operation type according to the fault diagnosis rule, determine the matching result as the reference fault operation type of the server to be debugged, and then match the target server fault operation type with the debugging instruction according to the fault debugging rule, determine the matching result as the reference debugging instruction of the server to be debugged, and then automatically send the reference debugging instruction to the server to be debugged for fault repair. In this way, the debugging device can automatically diagnose and repair the server to be tested, reduce the need for manual intervention, shorten the fault response and repair time, and improve the speed and accuracy of server fault processing.
[0098] As an optional solution, the debugging device is further deployed with a first memory and a second memory, the first memory and the second memory are respectively connected to the controller, the first memory stores fault keywords and fault operation types with corresponding relationships, the second memory stores fault operation types and debugging instructions with corresponding relationships, and the identifying of the reference fault operation type of the server to be debugged according to the target server fault information includes:
[0099] S71, extracting reference fault keywords from the target server fault information;
[0100] S72, matching the reference fault operation type corresponding to the reference fault keyword from the fault keywords and fault operation types having a corresponding relationship;
[0101] The generating a reference debugging instruction matching the reference fault operation type comprises:
[0102] S73: Match the reference debugging instruction corresponding to the reference fault operation type from the fault operation types and debugging instructions having a corresponding relationship.
[0103] Optionally, in this embodiment, Figure 6 is a schematic diagram of a system module diagram of a server debugging extension method according to an embodiment of the present application, such as Figure 6 As shown, the server BIOS unlimited debugging device (debugging device) also includes a first memory and a second memory, and the memory 1 and the memory 2 are respectively connected to the control module MCU (controller), wherein the first memory can be the memory 1, which stores the fault diagnosis rules; the second memory can be the memory 2, which stores the fault debugging rules. Optionally, the memory 1 and the memory 2 can also be one memory, which is connected to the control module MCU and stores the fault diagnosis rules and the fault debugging rules.
[0104] Optionally, in this embodiment, after receiving BIOS debug information, the controller first extracts reference fault keywords therefrom, where the reference fault keywords may be but are not limited to key statements in the BIOS debug information that may indicate a certain fault type of the server, and then performs fault operation type matching, obtains a reference fault operation type that matches the reference fault key statement according to fault diagnosis rules, and then obtains a reference debugging instruction that matches the reference fault operation type according to fault debugging rules, and finally, sends a reference debugging instruction to the server to be debugged, where the reference debugging instruction may be a debugging operation that allows repairing a server fault of the reference fault operation type.
[0105] In addition, when the controller detects that there is no fault operation type matching the reference fault keyword in the first memory, it generates an add request and sends the add request to the corresponding target account, wherein after receiving the add request, the target account adds the newly added fault operation type corresponding to the reference fault keyword to the first memory, and adds a new debugging instruction to the second memory; in this way, the fault debugging rules and fault diagnosis rules can be continuously updated to adapt to various fault debugging.
[0106] Furthermore, the first memory and the second memory can be deployed inside the debugging device, but are not limited to being deployed in the debugging device, and can also be deployed in the cloud corresponding to the debugging device, that is, the first memory is the first cloud storage space, and the second memory is the second cloud storage space. The controller can access the first cloud storage space to obtain the corresponding fault keywords and fault operation types, and access the second cloud storage space to obtain the corresponding fault operation types and debugging instructions. In this way, the internal structure of the debugging device can be further simplified, and the flexibility of storage deployment can be increased.
[0107] Optionally, in this embodiment, in order to better understand the process of the debugging method of the above-mentioned server, the debugging method process of the above-mentioned server is described below in combination with an optional embodiment, but it is not used to limit the technical solution of the embodiment of the present application.
[0108] In this embodiment, a server debugging method is provided. Figure 7 is a schematic diagram of a server debugging method process according to an embodiment of the present application, such as Figure 7As shown, it mainly includes the following steps: after the server BIOS wireless debugging device (hereinafter referred to as the wireless debugging device) is powered on, the indicator light representing the serial port connection status of the server to be debugged and the connection status of the wireless transmission module turns green and flashes, indicating the connection status. The serial communication module of the wireless debugging device is connected to the BIOS serial port of the server to be debugged, and the system will match the serial port configuration according to the preset configuration to connect, and then the communication between the server to be debugged and the wireless debugging system can be realized, and the corresponding indicator light turns green and always on; at the same time, the wireless debugging device will initialize different wireless transmission modules according to the selection switch of the wireless transmission module, such as the 4G transmission module or the Bluetooth transmission module. When the wireless transmission module is successfully connected, the indicator light representing the remote connection status turns green and always on. After the serial communication module and the wireless communication module are successfully connected, they work in the transparent transmission mode by default, that is, the instructions of the host computer can be forwarded to the serial port of the server to be debugged through the wireless debugging device, and the information printed in the serial port of the server to be debugged will also be transmitted to the host computer. By pressing the button switch on the wireless debugging device, the control system can be switched to the fault analysis mode, and the indicator light of the corresponding mode selection switch will also be always on green. In the fault analysis mode, the control system will send a command to open the BIOSDebug mode (target acquisition instruction) to the server, so that the serial port of the server to be debugged will print out the BIOS debug information during the boot process. The BIOS debug information will be saved and processed in the control system, and the server fault operation types such as downtime, memory failure, CPU failure, PCIE failure, etc. will be matched according to the preset fault diagnosis rules or those sent by the host computer. After identifying the fault operation type, the analysis result will be uploaded to the host computer. At this time, the BIOS engineer can use the preset or custom-added processing rules (fault debugging rules) on the host computer software to repair the fault or further locate the fault.
[0109] Through the description of the above implementation methods, those skilled in the art can clearly understand that the method according to the above embodiment can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, magnetic disk, optical disk), and includes a number of instructions for a terminal device (which can be a mobile phone, computer, server, or network device, etc.) to execute the methods described in each embodiment of the present application.
[0110] In this embodiment, a debugging device for a server is also provided, which is used to implement the above-mentioned embodiments and preferred implementation modes, and the descriptions that have been made will not be repeated. As used below, the term "module" can be a combination of software and / or hardware that implements a predetermined function. Although the devices described in the following embodiments are preferably implemented in software, the implementation of hardware, or a combination of software and hardware, is also possible and conceivable.
[0111] Figure 8 is a structural block diagram of a server debugging device according to an embodiment of the present application; Figure 8 As shown, a connector, a controller, a first transmitter and a second transmitter are deployed on the debugging device, the connector is connected to the first transmitter and the second transmitter respectively through the controller, the connector is used to connect to the server to be debugged, the first transmitter is configured to allow the use of a first wireless communication protocol to transmit data, the first wireless communication protocol is a protocol that allows the use of a mobile communication network to transmit data without accessing a local area network corresponding to the server to be debugged, the second transmitter is configured to allow the use of a second wireless communication protocol to transmit data, the second wireless communication protocol is a protocol that allows the use of a target distance of the second transmitter without accessing a mobile communication network, and the device is applied to the controller, including:
[0112] A collection module 802 is used to collect target server fault information generated during the fault operation from the server to be debugged;
[0113] A screening module 804 is used to screen out a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment currently located by the server to be debugged;
[0114] A control module 806 is used to control the target transmitter to transmit the target server fault information to the target terminal, wherein the target terminal is used to send a target debugging instruction generated according to the target server fault information to the target transmitter, and the target debugging instruction is used to indicate a debugging operation that allows the fault operation of the server to be debugged to be repaired;
[0115] The execution module 808 is used to execute the debugging operation indicated by the target debugging instruction on the server to be debugged.
[0116] In an exemplary embodiment, the screening module comprises:
[0117] A first detection unit, used to detect the current network status of the server to be debugged;
[0118] A first determining unit is used to determine the first transmitter as the target transmitter when the network state of the server to be debugged is currently a first network state, wherein the first network state is used to indicate that data can be transmitted between a device and an external terminal in the network environment where the server to be debugged is currently located without accessing a local area network corresponding to the server to be debugged using a mobile communication network;
[0119] A second determination unit is used to determine the second transmitter as the target transmitter when the network state of the server to be debugged is currently a second network state, wherein the second network state is used to indicate that data transmission within the target distance is allowed between the device and the external terminal in the network environment where the server to be debugged is currently located without accessing the mobile communication network.
[0120] In an exemplary embodiment, the control module comprises:
[0121] a first control unit, configured to, when the target transmitter is the first transmitter, control the first transmitter to transmit the target server fault information to a first terminal, wherein the first terminal and the first transmitter transmit data using the first wireless communication protocol, and the first terminal is configured to: extract candidate fault keywords from the target server fault information, match candidate fault operation types corresponding to the candidate fault keywords from fault keywords and fault operation types having a corresponding relationship, match candidate debugging instructions corresponding to the candidate fault operation types from fault operation types and debugging instructions having a corresponding relationship, and send the candidate debugging instructions to the target transmitter, wherein the candidate debugging instructions are used to indicate a debugging operation that allows repairing the fault of the candidate fault operation type, the target debugging instructions include the candidate debugging instructions, and the target terminal includes the first terminal;
[0122] a second control unit, configured to, when the target transmitter is the second transmitter, control the second transmitter to transmit the target server fault information to a second terminal, wherein the second wireless communication protocol is used to transmit data between the second terminal and the second transmitter, and the second terminal is configured to: extract alternative fault keywords from the target server fault information, match alternative fault operation types corresponding to the alternative fault keywords from fault keywords and fault operation types having a corresponding relationship, match alternative debugging instructions corresponding to the alternative fault operation types from fault operation types and debugging instructions having a corresponding relationship, and send the alternative debugging instructions to the target transmitter, wherein the alternative debugging instructions are used to indicate a debugging operation that allows repair of the fault of the alternative fault operation type, and the target debugging instructions include the alternative debugging instructions; the second terminal is an external terminal located within the target distance of the second transmitter, and the target terminal includes the second terminal.
[0123] In an exemplary embodiment, a power supply is further deployed on the debugging device, the controller, the first transmitter and the second transmitter are respectively connected to the power supply, and the control module includes:
[0124] a third control unit, configured to control the power supply to turn on the power supply of the first transmitter and to control the power supply to turn off the power supply of the second transmitter when the target transmitter is the first transmitter, wherein the first transmitter is configured to transmit data using the first wireless communication protocol when powered, and the second transmitter is configured to prohibit the use of the second wireless communication protocol to transmit data when not powered;
[0125] and a fourth control unit, for controlling the power supply to turn on power to the second transmitter and controlling the power supply to turn off power to the first transmitter when the target transmitter is the second transmitter, wherein the second transmitter is configured to transmit data using the first wireless communication protocol when powered, and the first transmitter is configured to prohibit data transmission using the first wireless communication protocol when not powered.
[0126] In an exemplary embodiment, the acquisition module includes:
[0127] A second detection unit, used to detect the connection status between the connector and the server to be debugged;
[0128] a generating unit, configured to generate a target acquisition instruction when the connection state is a normal connection state, wherein the target acquisition instruction is used to instruct the server to be debugged to transmit server fault information to the controller;
[0129] A calling unit, used for calling the connector to send the target acquisition instruction to the server to be debugged;
[0130] The receiving unit is used to receive the target server fault information transmitted by the server to be debugged.
[0131] In an exemplary embodiment, the apparatus further comprises:
[0132] An identification module, configured to identify a reference fault operation type of the server to be debugged according to the target server fault information after the target server fault information generated during the fault operation is collected from the server to be debugged;
[0133] A generating module is used to generate a reference debugging instruction matching the reference fault operation type, wherein the reference debugging instruction is used to indicate a debugging operation that allows repairing the fault of the reference fault operation type.
[0134] In an exemplary embodiment, the debugging device further comprises a first memory and a second memory, the first memory and the second memory are respectively connected to the controller, the first memory stores fault keywords and fault operation types having a corresponding relationship, the second memory stores fault operation types and debugging instructions having a corresponding relationship, and the identification module comprises:
[0135] An extraction unit, configured to extract reference fault keywords from the target server fault information;
[0136] A first matching unit, configured to match the reference fault operation type corresponding to the reference fault keyword from fault keywords and fault operation types having a corresponding relationship;
[0137] The generating module comprises:
[0138] The second matching unit is used to match the reference debugging instruction corresponding to the reference fault operation type from the fault operation types and debugging instructions having a corresponding relationship.
[0139] It should be noted that the above modules can be implemented by software or hardware. For the latter, it can be implemented in the following ways, but not limited to: the above modules are all located in the same processor; or the above modules are located in different processors in any combination.
[0140] An embodiment of the present application also provides a computer program product, including a computer program, which, when executed by a processor, implements the steps of the method described in each embodiment of the present application; the computer program product also includes a non-volatile computer-readable storage medium, which stores the computer program, and when executed by a processor, implements the steps of the method described in each embodiment of the present application.
[0141] An embodiment of the present application further provides a computer-readable storage medium, in which a computer program is stored, wherein the computer program is configured to execute the steps of any of the above method embodiments when running.
[0142] In an exemplary embodiment, the computer-readable storage medium may include, but is not limited to, various media that can store computer programs, such as a USB flash drive, a read-only memory (ROM), a random access memory (RAM), a mobile hard disk, a magnetic disk or an optical disk.
[0143] An embodiment of the present application further provides an electronic device, Fig. 9 is a schematic diagram of an electronic device according to an embodiment of the present application, such as Fig. 9 As shown, the electronic device includes a memory and a processor, the memory stores a computer program, and the processor is configured to run the computer program to execute the steps in any one of the above method embodiments.
[0144] In an exemplary embodiment, the electronic device may further include a transmission device and an input / output device, wherein the transmission device is connected to the processor, and the input / output device is connected to the processor.
[0145] For specific examples in this embodiment, reference may be made to the examples described in the above embodiments and exemplary implementation modes, and this embodiment will not be described in detail herein.
[0146] Obviously, those skilled in the art should understand that the above modules or steps of the present application can be implemented by a general computing device, they can be concentrated on a single computing device, or distributed on a network composed of multiple computing devices, they can be implemented by a program code executable by a computing device, so that they can be stored in a storage device and executed by the computing device, and in some cases, the steps shown or described can be executed in a different order from that herein, or they can be made into individual integrated circuit modules, or multiple modules or steps therein can be made into a single integrated circuit module for implementation. Thus, the present application is not limited to any specific combination of hardware and software.
[0147] The above description is only the preferred embodiment of the present application and is not intended to limit the present application. For those skilled in the art, the present application may have various modifications and variations. Any modification, equivalent replacement, improvement, etc. made within the principles of the present application shall be included in the protection scope of the present application.
Claims
1. A server debugging method, characterized in that: A connector, a controller, a first transmitter and a second transmitter are deployed on the debugging device. The connector is connected to the first transmitter and the second transmitter respectively through the controller. The connector is used to connect to the server to be debugged. The first transmitter is configured to allow data to be transmitted using a first wireless communication protocol, which is a protocol that allows data to be transmitted using a mobile communication network without accessing a local area network corresponding to the server to be debugged. The second transmitter is configured to allow data to be transmitted using a second wireless communication protocol, which is a protocol that allows data to be transmitted within a target distance of the second transmitter without accessing a mobile communication network. The method is applied to the controller and includes: Collecting target server fault information generated during the fault operation from the server to be debugged; Filtering out a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment currently located by the server to be debugged; Controlling the target transmitter to transmit the target server fault information to the target terminal, wherein the target terminal is used to send a target debugging instruction generated according to the target server fault information to the target transmitter, wherein the target debugging instruction is used to indicate a debugging operation that allows the fault operation of the server to be debugged to be repaired; The debugging operation indicated by the target debugging instruction is executed on the server to be debugged.
2. The method according to claim 1, characterized in that The step of selecting a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter includes: Detecting the current network status of the server to be debugged; In a case where the network state of the server to be debugged is currently a first network state, determining the first transmitter as the target transmitter, wherein the first network state is used to indicate that data can be transmitted between a device and an external terminal in a network environment where the server to be debugged is currently located without accessing a local area network corresponding to the server to be debugged using a mobile communication network; When the network state of the server to be debugged is currently a second network state, the second transmitter is determined as the target transmitter, wherein the second network state is used to indicate that data transmission within the target distance is allowed between the device and the external terminal in the network environment where the server to be debugged is currently located without accessing the mobile communication network.
3. The method according to claim 2, characterized in that The controlling the target transmitter to transmit the target server fault information to the target terminal includes: In the case where the target transmitter is the first transmitter, the first transmitter is controlled to transmit the target server fault information to a first terminal, wherein the first terminal and the first transmitter transmit data using the first wireless communication protocol, and the first terminal is used to: extract candidate fault keywords from the target server fault information, match candidate fault operation types corresponding to the candidate fault keywords from fault keywords and fault operation types with corresponding relationships, match candidate debugging instructions corresponding to the candidate fault operation types from fault operation types and debugging instructions with corresponding relationships, and send the candidate debugging instructions to the target transmitter, wherein the candidate debugging instructions are used to indicate a debugging operation that allows repairing the fault of the candidate fault operation type, the target debugging instructions include the candidate debugging instructions, and the target terminal includes the first terminal; In the case that the target transmitter is the second transmitter, the second transmitter is controlled to transmit the target server fault information to the second terminal, wherein the second wireless communication protocol is used to transmit data between the second terminal and the second transmitter, and the second terminal is used to: extract alternative fault keywords from the target server fault information, match alternative fault operation types corresponding to the alternative fault keywords from fault keywords and fault operation types with corresponding relationships, match alternative debugging instructions corresponding to the alternative fault operation types from fault operation types and debugging instructions with corresponding relationships, send the alternative debugging instructions to the target transmitter, the alternative debugging instructions are used to indicate debugging operations that allow repairing the faults of the alternative fault operation types, the target debugging instructions include the alternative debugging instructions, and the second terminal is an external terminal located within the target distance of the second transmitter, and the target terminal includes the second terminal.
4. The method according to claim 2, characterized in that: The debugging device is also equipped with a power supply, the controller, the first transmitter and the second transmitter are respectively connected to the power supply, and the control of the target transmitter to transmit the target server fault information to the target terminal includes: When the target transmitter is the first transmitter, controlling the power supply to turn on the power supply of the first transmitter, and controlling the power supply to turn off the power supply of the second transmitter, wherein the first transmitter is configured to transmit data using the first wireless communication protocol when powered, and the second transmitter is configured to prohibit the use of the second wireless communication protocol to transmit data when not powered; When the target transmitter is the second transmitter, the power supply is controlled to turn on the power supply of the second transmitter, and the power supply is controlled to turn off the power supply of the first transmitter, wherein the second transmitter is configured to transmit data using the first wireless communication protocol when powered, and the first transmitter is configured to prohibit the use of the first wireless communication protocol to transmit data when not powered.
5. The method according to claim 1, characterized in that The collecting of target server fault information generated during the fault operation from the server to be debugged includes: Detecting the connection status between the connector and the server to be debugged; In the case where the connection state is a normal connection state, generating a target acquisition instruction, wherein the target acquisition instruction is used to instruct the server to be debugged to transmit server fault information to the controller; Calling the connector to send the target acquisition instruction to the server to be debugged; Receive the target server failure information transmitted by the server to be debugged.
6. The method according to claim 1, characterized in that After collecting the target server fault information generated during the fault operation from the server to be debugged, the method further includes: Identify the reference fault operation type of the server to be debugged according to the target server fault information; A reference debugging instruction matching the reference fault operation type is generated, wherein the reference debugging instruction is used to indicate a debugging operation that allows repairing a fault of the reference fault operation type.
7. The method according to claim 6, characterized in that The debugging device is further provided with a first memory and a second memory, the first memory and the second memory are respectively connected to the controller, the first memory stores fault keywords and fault operation types having a corresponding relationship, the second memory stores fault operation types and debugging instructions having a corresponding relationship, and the step of identifying the reference fault operation type of the server to be debugged according to the target server fault information includes: Extracting reference fault keywords from the target server fault information; Matching the reference fault operation type corresponding to the reference fault keyword from the fault keywords and fault operation types having a corresponding relationship; The generating a reference debugging instruction matching the reference fault operation type comprises: The reference debugging instruction corresponding to the reference fault operation type is matched from the fault operation types and debugging instructions having a corresponding relationship.
8. A server debugging device, characterized in that: A connector, a controller, a first transmitter and a second transmitter are deployed on the debugging device. The connector is connected to the first transmitter and the second transmitter respectively through the controller. The connector is used to connect to the server to be debugged. The first transmitter is configured to allow data to be transmitted using a first wireless communication protocol. The first wireless communication protocol is a protocol that allows data to be transmitted using a mobile communication network without accessing a local area network corresponding to the server to be debugged. The second transmitter is configured to allow data to be transmitted using a second wireless communication protocol. The second wireless communication protocol is a protocol that allows data to be transmitted within a target distance of the second transmitter without accessing a mobile communication network. The device is applied to the controller and includes: A collection module, used for collecting target server fault information generated during the fault operation from the server to be debugged; a screening module, used to screen out a target transmitter that matches the target network state currently located by the server to be debugged from the first transmitter and the second transmitter, wherein the target network state is used to indicate a data transmission mode allowed to be used between a device and an external terminal in the network environment currently located by the server to be debugged; a control module, configured to control the target transmitter to transmit the target server fault information to a target terminal, wherein the target terminal is configured to send a target debugging instruction generated according to the target server fault information to the target transmitter, wherein the target debugging instruction is configured to indicate a debugging operation that allows the fault operation of the server to be debugged to be repaired; The execution module is used to execute the debugging operation indicated by the target debugging instruction on the server to be debugged.
9. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, wherein the computer program implements the steps of the method described in any one of claims 1 to 7 when executed by a processor.
10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method described in any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Switch debugging method and device, server and computer readable storage medium
CN113821390A
Data center equipment debugging method and system
CN117785583A
Edge server monitoring method, device and system, electronic equipment and storage medium
CN118119038A
Cited By
Electronic device
CN120469545A