Fault diagnosis method and device, computer equipment and readable storage medium

Abstract

The invention relates to a fault diagnosis method and device, computer equipment and a readable storage medium. The method comprises the steps that a fault diagnosis request sent by a terminal is received, the fault diagnosis request is responded, basic conditions of the elastic file system are diagnosed according to related information, a fault diagnosis result is determined, and the fault diagnosis result is sent to the terminal. Wherein the fault diagnosis request comprises related information of the elastic file system, and the basic condition comprises at least one of a network link, a storage cluster state, a use process or virtual machine configuration. By adopting the method, manpower can be saved.

Description

Technical Field

[0001] The present application relates to the field of communication technology, and in particular to a fault diagnosis method, apparatus, computer equipment and readable storage medium. Background Art

[0002] With the rapid development of cloud computing technology and the increasing demand for file storage, more and more application scenarios will provide users with file storage services through the elastic file system under the new generation of cloud platform architecture.

[0003] Users may encounter various problems when using the elastic file system. In the related art, if a user encounters a problem when using the elastic file system, he will report it. The troubleshooting process from user reporting to fault identification is usually complicated and requires a lot of communication and positioning, which consumes a lot of manpower.

[0004] Therefore, how to propose a manpower-saving fault diagnosis method is a technical problem to be solved urgently in this field. Summary of the invention

[0005] Based on this, it is necessary to provide a fault diagnosis method, device, computer equipment and readable storage medium that can save manpower in order to solve the above technical problems.

[0006] In a first aspect, the present application provides a fault diagnosis method, comprising:

[0007] Receiving a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system;

[0008] In response to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information and determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration;

[0009] Send fault diagnosis results to the terminal.

[0010] In a second aspect, the present application also provides a fault diagnosis method, comprising:

[0011] Sending a fault diagnosis request to a controller corresponding to the elastic file system, the fault diagnosis request including relevant information of the elastic file system, the fault diagnosis request being used for the controller to respond to the fault diagnosis request, diagnose basic conditions of the elastic file system according to the relevant information, and determine a fault diagnosis result; the basic conditions including at least one of a network link, a storage cluster status, a usage process, or a virtual machine configuration;

[0012] Receive the fault diagnosis results sent by the controller.

[0013] In a third aspect, the present application also provides a fault diagnosis device, comprising:

[0014] A receiving module, used for receiving a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system;

[0015] A diagnosis module, configured to respond to a fault diagnosis request, diagnose a basic condition of the elastic file system according to relevant information, and determine a fault diagnosis result; the basic condition includes at least one of a network link, a storage cluster state, a usage process, or a virtual machine configuration;

[0016] The sending module is used to send the fault diagnosis result to the terminal.

[0017] In a fourth aspect, the present application further provides a fault diagnosis device, comprising:

[0018] A sending module, used to send a fault diagnosis request to a controller corresponding to the elastic file system, the fault diagnosis request including relevant information of the elastic file system, the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of a network link, a storage cluster state, a usage process or a virtual machine configuration;

[0019] The receiving module is used to receive the fault diagnosis result sent by the controller.

[0020] In a fifth aspect, the present application further provides a computer device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of any of the above methods when executing the computer program.

[0021] In a sixth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, wherein the computer program implements the steps of any of the above methods when executed by a processor.

[0022] In a seventh aspect, the present application also provides a computer program product, comprising a computer program, which implements the steps of any of the above methods when executed by a processor.

[0023] The above-mentioned fault diagnosis method, apparatus, computer equipment and readable storage medium can receive a fault diagnosis request sent by a terminal, and the fault diagnosis request includes relevant information of the elastic file system. Therefore, it can respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and automatically, efficiently and accurately determine the fault diagnosis result to send the fault diagnosis result to the terminal. In addition, the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. In the above process, human participation is reduced. Therefore, the fault diagnosis of the elastic file system can be achieved without a lot of communication and positioning, which reduces the consumption of manpower and saves manpower. BRIEF DESCRIPTION OF THE DRAWINGS

[0024] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0025] Figure 1 A schematic diagram of a fault diagnosis process in the related art;

[0026] Figure 2 An application environment diagram of a fault diagnosis method in an embodiment;

[0027] Figure 3 A schematic diagram of a flow chart of a fault diagnosis method in an embodiment;

[0028] Figure 4 A schematic diagram of a process for determining a fault diagnosis result in an embodiment;

[0029] Figure 5 is a schematic diagram of a network link in one embodiment;

[0030] Figure 6 A schematic diagram of a process for determining a fault diagnosis result in an embodiment;

[0031] Figure 7 A schematic diagram of the architecture of a storage cluster in one embodiment;

[0032] Figure 8 An example diagram of diagnosing the status of a storage cluster in one embodiment;

[0033] Fig. 9 An example diagram of diagnosing a use environment of a virtual machine in one embodiment;

[0034] Fig.10An example diagram of diagnosing a mount command in one embodiment;

[0035] Fig.11 A schematic diagram of a process for determining a fault diagnosis result in an embodiment;

[0036] Fig.12 is a schematic diagram of VPC information in one embodiment;

[0037] Fig.13 is a schematic diagram of a data packet in one embodiment;

[0038] Fig.14 An example diagram of diagnosing a virtual machine configuration in one embodiment;

[0039] Fig.15 is a flowchart of yet another fault diagnosis method in an embodiment;

[0040] Fig.16 is a schematic diagram of a diagnostic interface in one embodiment;

[0041] Fig.17 A schematic diagram of a process of a fault diagnosis method in an embodiment;

[0042] Fig.18 is a structural block diagram of a fault diagnosis device in one embodiment;

[0043] Fig.19 is a structural block diagram of yet another fault diagnosis device in an embodiment;

[0044] Fig. 20 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0045] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0046] Figure 1 FIG. 1 is a flow chart of a fault diagnosis process in the related technology, such as Figure 1As shown in the figure, after the user reports the problem of the elastic file system, the operation team will receive the user's work order problem report. Then, the operation team needs to identify the demand type of the user's work order problem report and confirm the scope of the problem. If it is found to be a problem related to the elastic file service, it will be reported to the corresponding elastic file operation and maintenance personnel. If the operation and maintenance personnel can find the root cause, such as a user usage problem, they can guide the user to use it correctly to complete the problem loop. However, if the operation and maintenance personnel cannot find the root cause, that is, they cannot solve the problem, then the operation and maintenance personnel need to report it to the R&D engineer, who will locate and solve it.

[0047] Due to the complexity of the overall architecture of Elastic Files, multiple teams are responsible for multiple components of Elastic Files. For example, the physical network team ensures network connectivity between nodes, the virtual network team ensures network connectivity between virtual machines and the Elastic File Gateway, and the cloud management platform ensures that user instructions can be issued correctly. Therefore, after the Elastic Files R&D engineer locates the problem to other component problems, the corresponding component team needs to locate and solve it. For example, if a problem is located in a cloud management platform component, it needs to be reported to the cloud management platform operation and maintenance and engineers until the problem is solved. In addition, the capabilities of R&D engineers vary. If the R&D engineer cannot solve the problem, it is necessary to continue to report to the Elastic Files expert for location and resolution.

[0048] It can be seen that in the fault diagnosis method in the related technology, a lot of positioning and communication are required from the time the work order is received. The fault diagnosis of the elastic file system involves different personnel including operation, maintenance, and R&D, and each person needs to master the basic knowledge of storage and network and have the ability to locate and analyze faults. The whole process is relatively complicated, time-consuming, and labor-intensive. Based on this, it is necessary to provide a fault diagnosis method for the above technical problems, which will be introduced below.

[0049] Figure 2 FIG. 1 is an application environment diagram of a fault diagnosis method in an embodiment, such as Figure 2 As shown, in an embodiment of the present application, the controller can communicate with the elastic file system 100, the database, the cloud management platform and the operation platform respectively.

[0050] Among them, the cloud management platform is used to manage the elastic file system 100. The database is used to store data related to the elastic file system 100, such as storing the configuration sent to the elastic file system 100 by the cloud management platform. The database includes but is not limited to the configuration management database (CMDB), and the operation platform is used to obtain and follow up on the problems reported by users. The controller includes but is not limited to a central processing unit (CPU), a digital signal processor (DSP), a field programmable gate array (FPGA) or other programmable logic devices. In some embodiments, the controller can also be implemented with an independent server or a server cluster consisting of multiple servers.

[0051] The elastic file system 100 can provide on-demand expansion, high-performance network-attached storage (NAS), and can provide large-scale shared access for multiple elastic cloud hosts, containers, physical machines and other computing services on the cloud, with high availability and high data persistence. In addition, it can provide a standard Portable Operating System Interface for UNIX (POSIX) file access interface, which can seamlessly integrate existing applications with file storage.

[0052] Please continue to refer to Figure 1 , the elastic file system 100 includes a host, a network address translation (NAT) gateway, an elastic file gateway, and a storage cluster. Further, the controller can communicate with the host, NAT gateway, elastic file gateway, and storage cluster in the elastic file system 100 respectively. It should be noted that, Figure 1 Only one elastic file system 100 is illustrated, and this embodiment does not limit the number of host machines, NAT gateways, and elastic file gateways.

[0053] Users can communicate with the storage cluster through the virtual machines in the host to store or read files. The data of the virtual machine is sent to the corresponding NAT gateway through the physical network of the host. The NAT gateway processes the received data and sends it to the corresponding elastic file gateway. For example, the NAT gateway can modify the source IP address of the data, and add the virtual private cloud (Virtual Private Cloud, VPC) information and virtual private Internet Protocol (Internet Protocol, IP) address of the virtual machine in the TCP option. After receiving the data sent by the NAT gateway, the elastic file gateway will verify the legitimacy of the received data, parse the Network File System (NFS) or Common Internet File System (CIFS) and other protocols, and split the received data and write it to the corresponding storage cluster.

[0054] It can be seen that in the process of interaction between the virtual machine and the storage cluster, each node and link, as well as unreasonable operations by users, may cause abnormalities.

[0055] Figure 3 FIG. 1 is a flow chart of a fault diagnosis method in an embodiment. In an exemplary embodiment, as shown in FIG. Figure 3 As shown, a fault diagnosis method is provided, which is applied to Figure 2 The controller in is taken as an example for explanation, including the following S301 to S303.

[0056] S301, receiving a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system.

[0057] In this embodiment, the terminal may be a terminal used by an operator, for example, a terminal corresponding to an operation platform. The fault diagnosis request may be a request sent by the terminal to the controller in response to a diagnostic operation. For example, an operator may click "Start Diagnosis" through the terminal to initiate a diagnostic operation, so that the terminal sends a fault diagnosis request to the controller.

[0058] Among them, the fault diagnosis request includes relevant information of the elastic file system. The relevant information includes but is not limited to the resource pool identifier, virtual machine identifier, NAT identifier, elastic file identifier, virtual machine password and mount command. The resource pool identifier is used to indicate the resource pool where the virtual machine and the elastic file are located. The resource pool identifier is, for example, the resource pool name. The virtual machine identifier is used to indicate the virtual machine used by the user. The virtual machine identifier is, for example, the virtual machine identity identifier (Identification, ID). The NAT identifier is used to indicate the NAT gateway passed by the virtual machine used by the user. The elastic file identifier is used to indicate the elastic file gateway passed by the virtual machine used by the user. The elastic file identifier is, for example, the elastic file ID. The virtual machine password indicates the user password for logging into the virtual machine, for example, it can be the password of the root user in the virtual machine. The mount command is the command used by the user to mount a file through a virtual machine.

[0059] Optionally, the relevant information of the elastic file system may be information specified by an operator, or information sent to the terminal by other devices, or information determined by the terminal according to a user work order problem report, but this embodiment is not limited thereto.

[0060] S302, in response to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration.

[0061] In this embodiment, the fault diagnosis result is the result obtained after diagnosing the basic situation of the elastic file system, which may include whether the elastic file system has a fault, and the cause and location of the fault in the event of a fault. In some embodiments, the fault diagnosis result may also include the severity of the fault and / or the fault handling measures.

[0062] When using the elastic file system, users may encounter various problems. For example, in the process of using the elastic file system, users need to execute the mount command. Different operating systems and different operating system versions have different configuration methods. For example, when users use elastic files in Windows systems, CIFS protocol is generally used, and when using elastic files in Linux systems, NFS protocol is generally used. The methods of installing clients in different operating systems are also different, and users need to be able to choose the correct usage method in the corresponding system. Taking configuration problems as an example, the elastic file system has powerful authentication capabilities and rich authentication methods. Different permissions can be configured based on different combinations of IP, network segment, VPC, permission group, and priority. Once the configuration is wrong, the user will not be able to use the file system. Taking system failure as an example, the use of the elastic file system involves three key parts: client, network, and server. If any part fails, the file system will be unavailable.

[0063] Therefore, this embodiment will diagnose the basic situation of the elastic file system based on the relevant information. Among them, the basic situation of the elastic file system includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. The network link includes a communication link between at least two nodes in the elastic file system, for example, it can be a communication link between a virtual machine and a corresponding NAT gateway. The storage cluster status indicates the usage status of the storage cluster, for example, it can be the status of the hard disk in the storage cluster, the read-write status, etc. The usage process refers to the usage process of the user communicating between the virtual machine and the storage cluster. The virtual machine configuration refers to the configuration of the virtual machine used by the user, which includes but is not limited to the VPC information of the virtual machine.

[0064] Optionally, the controller may send a data packet to a host machine corresponding to the relevant information, start a packet capture program on each node in the elastic file system, and monitor the packet capture results of the packet capture program to obtain the packet capture results, and then analyze the packet capture results to obtain the fault diagnosis results.

[0065] Optionally, the controller may also send a diagnostic program to the elastic file gateway corresponding to the relevant information, and the elastic file gateway returns the fault diagnosis result to the controller based on the diagnostic program.

[0066] S303: Send the fault diagnosis result to the terminal.

[0067] In this embodiment, after the controller determines the fault diagnosis result, it can send the fault diagnosis result to the terminal. This embodiment does not limit the form of sending the fault diagnosis result.

[0068] Further optionally, after receiving the fault diagnosis result sent by the controller, the terminal can display the fault diagnosis result. For example, if the fault diagnosis result indicates that the communication link between the NAT gateway and the elastic file gateway is abnormal, the terminal can display "NAT gateway and elastic file gateway network abnormality is detected, please contact XXX immediately".

[0069] In the above fault diagnosis method, it is possible to receive a fault diagnosis request sent by a terminal, and the fault diagnosis request includes relevant information of the elastic file system. Therefore, it is possible to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and automatically, efficiently and accurately determine the fault diagnosis result to send the fault diagnosis result to the terminal. In addition, the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. In the above process, manual participation is reduced. Therefore, the fault diagnosis of the elastic file system can be achieved without a lot of communication and positioning, which reduces the consumption of manpower and saves manpower.

[0070] Figure 4 FIG. 1 is a flow chart of determining a fault diagnosis result in an embodiment. In an exemplary embodiment, the fault diagnosis result includes a first diagnosis result and / or a second diagnosis result; Figure 4 As shown, S302 includes S401 to S402.

[0071] S401, sending a data packet to a host machine corresponding to the relevant information.

[0072] In this embodiment, the controller can determine the host machine used by the user based on the relevant information. Optionally, the relevant information includes a resource pool identifier and a virtual machine identifier, and the controller can determine the host machine corresponding to the relevant information based on the resource pool identifier and the virtual machine identifier. Exemplarily, the controller can query the host machine information and file gateway information from the cloud management platform based on the resource pool identifier and the virtual machine identifier to determine the entire link device from the virtual machine to the storage cluster, that is, to determine the host machine used by the user.

[0073] Then, the controller can send a data packet to the host corresponding to the relevant information. This embodiment does not limit the form of the data packet, nor does it limit the form of sending the data packet. Further optionally, the controller can periodically send at least one data packet to the host corresponding to the relevant information.

[0074] S402, according to the first packet capture result of the network address translation gateway corresponding to the relevant information, diagnose the first network link to obtain a first diagnostic result; the first network link is the network link between the host machine and the network address translation gateway; and / or, according to the second packet capture result of the elastic file gateway corresponding to the relevant information, diagnose the second network link to obtain a second diagnostic result; the second network link is the network link between the network address translation gateway and the elastic file gateway.

[0075] In this embodiment, the corresponding NAT gateway and / or elastic file gateway can be determined according to the relevant information. For example, the controller can determine the NAT gateway corresponding to the relevant information according to the resource pool identifier and the NAT identifier in the relevant information, and determine the elastic file gateway corresponding to the relevant information according to the resource pool identifier and the elastic file identifier in the relevant information.

[0076] Furthermore, the controller may determine the first packet capture result and / or the second packet capture result. The first packet capture result is the packet capture result corresponding to the NAT gateway, and the controller may obtain the first packet capture result through a packet capture tool or a packet capture program. It should be noted that the first packet capture result may be obtained by directly capturing packets on the controller side, or by capturing packets on the NAT gateway side, and the controller receives the first packet capture result. The second packet capture result is the packet capture result corresponding to the elastic file gateway, and the process of obtaining the second packet capture result may refer to the first packet capture result, which will not be described in detail here.

[0077] Further, since the controller has sent a data packet to the host machine, if the first network link between the host machine and the NAT gateway communicates normally, the NAT gateway can receive the first data corresponding to the data packet, and therefore, the controller can diagnose the first network link according to the first packet capture result to obtain a first diagnostic result. For example, the controller can analyze the first packet capture result to determine whether there is the first data corresponding to the data packet, and if there is the first data corresponding to the data packet, determine the first diagnostic result that the first network link communicates normally, and if there is no first data corresponding to the data packet, determine the first diagnostic result that the first network link communicates abnormally.

[0078] Similarly, on the basis that the first network link between the host machine and the NAT gateway communicates normally, if the second network link between the NAT gateway and the elastic file gateway communicates normally, then the elastic file gateway can also receive the second data corresponding to the data packet, so the controller can diagnose the second network link according to the second packet capture result to obtain the second diagnostic result. For example, the controller can analyze the second packet capture result to determine whether there is the second data corresponding to the data packet, and if there is the second data corresponding to the data packet, then determine the second diagnostic result that the second network link communicates normally, and if there is no second data corresponding to the data packet, then determine the second diagnostic result that the second network link communicates abnormally.

[0079] If any one of the first network link and the second network link is abnormal, the virtual machine and the storage cluster cannot communicate normally. Figure 5 FIG. 1 is a schematic diagram of a network link in an embodiment, Figure 5 As shown, the first network link communicates normally, while the second network link communicates abnormally. Therefore, the first packet capture result contains the first data corresponding to the data packet, while the second packet capture result does not contain the second data corresponding to the data packet.

[0080] In one embodiment, the controller may first diagnose the first network link according to the first packet capture result to obtain a first diagnostic result, and if the first diagnostic result indicates that the communication of the first network link is normal, the controller may then diagnose the second network link according to the second packet capture result to obtain a second diagnostic result. If the first diagnostic result indicates that the communication of the first network link is abnormal, there is no need to diagnose the second network link.

[0081] Of course, the controller can also diagnose the second network link according to the second packet capture result to obtain a second diagnostic result. If the second diagnostic result indicates that the second network link is communicating normally, the controller can diagnose the first network link according to the first packet capture result to obtain a first diagnostic result. If the second diagnostic result indicates that the second network link is communicating abnormally, there is no need to diagnose the first network link.

[0082] In some embodiments, the controller may also diagnose the first network link in series or in parallel according to the first packet capture result to obtain a first diagnostic result, and diagnose the second network link in series or in parallel according to the second packet capture result to obtain a second diagnostic result, which is not limited in this embodiment.

[0083] In the above embodiment, a data packet can be sent to the host machine corresponding to the relevant information, and the first network link can be diagnosed to obtain a first diagnostic result according to the first packet capture result of the network address translation gateway corresponding to the relevant information; and / or, the second network link can be diagnosed to obtain a second diagnostic result according to the second packet capture result of the elastic file gateway corresponding to the relevant information. Since the first network link is the network link between the host machine and the network address translation gateway, and the second network link is the network link between the network address translation gateway and the elastic file gateway, the automatic diagnosis of the network link in the elastic file system is realized.

[0084] Figure 6 FIG. 1 is a flowchart of another method for determining a fault diagnosis result in an embodiment. In an exemplary embodiment, the fault diagnosis result includes a third diagnosis result; Figure 6 As shown, S302 includes S601 to S602.

[0085] S601, sending a call request to the elastic file gateway corresponding to the relevant information; the call request is used for the elastic file gateway to diagnose according to the status of the storage cluster connected to the elastic file gateway and determine the third diagnosis result.

[0086] In this embodiment, the determination of the elastic file gateway corresponding to the relevant information can refer to S402, which is not repeated here. After determining the elastic file gateway corresponding to the relevant information, the controller sends a call request to the elastic file gateway. Exemplarily, the call request can be a remote procedure call (RPC) request.

[0087] After receiving the call request, the elastic file gateway will diagnose according to the state of the storage cluster to which it is connected, and determine the third diagnosis result. Optionally, the elastic file gateway can execute a detection program, which can obtain the state of the storage cluster, and diagnose according to the state of the storage cluster to determine the third diagnosis result.

[0088] Optionally, the controller may determine the third diagnostic result based on the service status and / or number of processes of the storage cluster. The number of processes may be the number of processes of the Network File System Daemon in the storage cluster. For example, the controller may determine that the third diagnostic result is that the service status of the storage cluster is abnormal when the service status of the storage cluster is not running. For another example, the controller may determine that the third diagnostic result is that the number of processes of the storage cluster is abnormal when the number of processes of the storage cluster is less than a preset number of processes.

[0089] Optionally, the controller may also determine the third diagnosis result according to the input / output wait (iowait) ratio. For example, when the input / output wait ratio is greater than a preset ratio, the controller may determine that the third diagnosis result is that the read / write pressure of the storage cluster is high.

[0090] Optionally, the controller may also obtain the recovery flow in the storage cluster and determine the third diagnosis result according to the recovery flow. For example, the controller may determine that the third diagnosis result is abnormal storage recovery flow of the storage cluster when there is recovery flow or the recovery flow is greater than a preset flow size.

[0091] Optionally, the controller may also obtain the status of each hard disk in the storage cluster, and determine the third diagnosis result according to the status of each hard disk in the storage cluster. For example, if there is an abnormal hard disk, the third diagnosis result is that there is an abnormal hard disk.

[0092] Figure 7 FIG. 1 is a schematic diagram of the architecture of a storage cluster in an embodiment. Figure 7 As shown, each elastic file gateway corresponds to multiple cluster nodes, for example, corresponding to cluster node 1 to cluster node n. Each cluster node includes multiple solid-state drives (SSDs). For example, each cluster node includes n hard drives, which are recorded as SSD1 to SSDn, where n is an integer greater than 1. The status of the storage cluster includes, but is not limited to, the service status of the storage cluster, the status of the SSD in the storage cluster, etc.

[0093] Figure 8 FIG. 1 is an example diagram of diagnosing the status of a storage cluster in one embodiment. Figure 8 As shown, in one embodiment, the controller can first determine whether the service status and the number of processes in the storage cluster are normal. If the service status and the number of processes are abnormal, the corresponding processing personnel are reported for processing. If the service status and the number of processes are normal, it is further determined whether the input and output waiting ratio is less than the first threshold (for example, 10%). If the input and output waiting ratio is less than the first threshold, it means that no fault is detected. If the input and output waiting ratio is not less than the first threshold, the controller further determines whether the input and output waiting ratio is less than the second threshold (for example, 60%). If the input and output waiting ratio is less than the second threshold, it means that the pressure on the storage cluster node is large, and the controller will trigger an alarm. If the input and output waiting ratio is not less than the second threshold, the controller will further detect whether there is recovery traffic. If there is recovery traffic, it means that the storage node is abnormal, and the controller will report the fault. If there is no recovery traffic, the controller will determine whether there is a faulty hard disk in the storage cluster. If there is a faulty hard disk, the fault will also be reported. If there is no faulty hard disk, the diagnosis of the state of the storage cluster is terminated. Among them, the second threshold is greater than the first threshold.

[0094] S602, receiving a third diagnosis result sent by the elastic file gateway.

[0095] In this embodiment, after the elastic file gateway determines the third diagnostic result, it returns the third diagnostic result to the controller, so that the controller receives the third diagnostic result.

[0096] In the above embodiment, since a call request can be sent to the elastic file gateway corresponding to the relevant information, and the call request is used for the elastic file gateway to diagnose according to the status of the storage cluster connected to the elastic file gateway and determine the third diagnostic result, after receiving the third diagnostic result sent by the elastic file gateway, the fault diagnosis result after diagnosing the storage cluster status is realized.

[0097] In an exemplary embodiment, optionally, the fault diagnosis result includes at least one of the fourth diagnosis result, the fifth diagnosis result, and the sixth diagnosis result; the above S302 may include at least one of the following:

[0098] (1) Determine the environment information of the virtual machine in the elastic file system according to the relevant information, and diagnose the use environment of the virtual machine according to the environment information of the virtual machine to determine a fourth diagnosis result.

[0099] In this embodiment, the controller can determine the environment information of the virtual machine in the elastic file system according to the relevant information. Optionally, the relevant information may include a virtual machine identifier, and the controller may determine the environment information of the virtual machine according to the virtual machine identifier. For example, the controller may obtain the environment information of the virtual machine from the cloud management platform according to the virtual machine identifier.

[0100] Among them, the environmental information refers to the relevant information of the environment in which the virtual machine runs, which includes but is not limited to at least one of the virtual machine's operating system, the image version of the operating system, the usage agreement, the protocol version of the usage agreement, and the client information. The operating system is, for example, a Windows system or a Linux system. The usage protocol is, for example, an NFS protocol or a CIFS protocol. The client information includes, for example, whether the client is installed, the version of the client, etc. Further, the controller can diagnose the usage environment of the virtual machine according to the environmental information of the virtual machine and determine the fourth diagnostic result.

[0101] Further optionally, the controller may diagnose the use environment of the virtual machine according to the environment information of the virtual machine and the preset environment requirements to determine a fourth diagnostic result. The preset environment requirements include, but are not limited to, at least one of the operating system requirements, image version requirements, usage protocol requirements, protocol version requirements, and preset client information. In some embodiments, the controller may also determine the fourth diagnostic result according to the environment information of the virtual machine and a preset correspondence, wherein the preset correspondence includes a correspondence between the environment information and the diagnostic result.

[0102] Fig. 9 FIG. 1 is an example diagram of diagnosing the use environment of a virtual machine in an embodiment. Fig. 9 As shown, if the operating system of the virtual machine is Windows, the protocol used is CIFS, and the image version is 2008, the image version is too low, and the fourth diagnostic result can be "Please use the 2012 image". If the operating system of the virtual machine is Windows, and the protocol used is NFS, the protocol used is not supported, and the fourth diagnostic result can be "Not supported yet, please use CIFS". If the operating system of the virtual machine is Linux, and the protocol used is CIFS, and the protocol version is lower than 2.0, the protocol version is too low, and the fourth diagnostic result can be "Please use protocol 2.1 or above". If the operating system of the virtual machine is Linux, and the protocol used is NFS, and the client information shows that the client is not installed, the fourth diagnostic result can be "Please install the client".

[0103] (2) When the relevant information includes a mount command, diagnose the mount command to obtain a fifth diagnosis result.

[0104] In this embodiment, if the relevant information includes a mount instruction, the controller can diagnose the mount command to obtain a fifth diagnosis result. Optionally, the controller can analyze the configuration of the local directory, mount parameters, mount path, etc. of the mount command to obtain the fifth diagnosis result.

[0105] Fig.10 FIG. 1 is an example diagram of diagnosing a mount command in an embodiment. Fig.10 As shown, when the controller determines the mount command and the protocol used is the NFS protocol, if the local directory does not exist after analyzing the mount command, the fifth diagnostic result may be "Please create a local directory". If the mount parameter is determined to be incorrect after analyzing the mount command, for example, "-t" is not used, the fifth diagnostic result may be "Please use -t to specify the NFS protocol". If the mount path is determined to be incorrect after analyzing the mount command, the fifth diagnostic result may be "Please copy the mount command from the console".

[0106] (3) When the relevant information includes a mount command and a virtual machine password, log in to the virtual machine according to the virtual machine password, and execute the mount command in the virtual machine to determine the sixth diagnostic result according to the execution result of the virtual machine.

[0107] In this embodiment, if the relevant information includes a mount command and a virtual machine password, the controller can log in to the virtual machine according to the virtual machine password by remote login, and execute the mount command in the virtual machine. Then, the virtual machine will run according to the mount command and obtain the execution result. The virtual machine can send the execution result to the controller, and the controller can also actively obtain the execution result. Further, the controller can determine the sixth diagnostic result according to the execution result of the virtual machine. Among them, the execution result can include execution success or execution failure. If the execution fails, the execution result can also include the reason for the execution failure, etc. This embodiment is not limited to this.

[0108] In the above embodiment, since the environmental information of the virtual machine in the elastic file system can be determined according to the relevant information, and the use environment of the virtual machine can be diagnosed according to the environmental information of the virtual machine to determine the fourth diagnostic result, when the relevant information includes the mount command, the mount command can be diagnosed to obtain the fifth diagnostic result, and when the relevant information includes the mount command and the virtual machine password, the virtual machine can be logged in according to the virtual machine password, and the mount command can be executed in the virtual machine to determine the sixth diagnostic result according to the execution result of the virtual machine. Therefore, through any one of the fourth diagnostic result, the fifth diagnostic result, and the sixth diagnostic result, the use process of the elastic file system can be diagnosed flexibly to reduce manpower consumption.

[0109] Fig.11 FIG. 1 is a flowchart of another method for determining a fault diagnosis result in an embodiment. In an exemplary embodiment, the fault diagnosis result includes a seventh diagnosis result, such as Fig.11 As shown, S302 includes S1101 to S1102.

[0110] S1101, determine virtual private cloud information of a virtual machine in an elastic file system according to relevant information.

[0111] In this embodiment, the relevant information may optionally include a virtual machine identifier, and the controller can determine the VPC information of the virtual machine in the elastic file system according to the virtual machine identifier. For example, the controller can obtain the VPC information of the virtual machine from the cloud management platform according to the virtual machine identifier. The VPC information may include an IP address corresponding to the VPC, and in some embodiments, the VPC information may also include the usage permissions of the VPC, such as read and write permissions.

[0112] Fig.12 FIG. 1 is a schematic diagram of VPC information in an embodiment. Fig.12As shown, users need to configure the VPC information of the virtual machine through the user interface. The VPC information of each virtual machine can be uniquely determined based on the NAT gateway and the virtual machine identifier. For example, virtual machine 1 needs to be configured with the VPC information of 1.1.1.1, VM2 needs to be configured with the VPC information of 1.1.1.2, and so on.

[0113] S1102: Diagnose the configuration of the elastic file gateway in the elastic file system according to the virtual private cloud information to determine a seventh diagnosis result.

[0114] In this embodiment, the controller can optionally determine whether the VPC has read and write permissions based on the VPC information to determine the seventh diagnosis result. For example, if there is no read and write permission, the seventh diagnosis result can indicate that there is no normal open permission and guide the user to perform correct permission configuration.

[0115] Optionally, the controller can obtain the configuration information of the virtual machine from the database according to the virtual machine identifier, and compare the VPC information with the obtained configuration information to determine the seventh diagnostic result. For example, if the VPC information and the configuration information are inconsistent, the seventh diagnostic result can indicate that the configuration is inconsistent, and report to the corresponding personnel to confirm the configuration. Among them, the configuration information of the virtual machine can be the configuration information sent to the database by the cloud management platform.

[0116] Optionally, the controller may obtain a data packet in the network link of the elastic file system, analyze the data packet in the network link, determine the authentication field of the data packet in the network link, and determine the seventh diagnostic result according to the authentication field and VPC information of the data packet in the network link. For example, in the case where the authentication field and VPC information of the data packet in the network link are inconsistent, the seventh diagnostic result may indicate a configuration inconsistency and report it to the corresponding personnel for processing.

[0117] Further optionally, the authentication field may be determined by a preset field in a Transmission Control Protocol (TCP) header in the data packet.

[0118] Fig.13 is a schematic diagram of a data packet in an embodiment, Fig.13 A schematic diagram of a data packet in a network link is shown. The data packet in the network link may be a TCP message, and the preset field may be an option field. Fig.13As shown, the data packet may include a link layer protocol, an IP header, a TCP header, and data to be transmitted. The TCP header may include fields for the source port, the destination port, a sequence number, a confirmation number, and an Option field. The Option field may include an authentication field. For example, the authentication field may be a VPC identifier and a virtual machine IP, where the virtual machine IP represents the virtual machine used by the user, and the VPC represents the VPC information corresponding to the virtual machine.

[0119] In some embodiments, the controller can first determine whether the VPC has read and write permissions based on the VPC information. If the VPC has read and write permissions, the controller can then obtain the configuration information of the virtual machine from the database based on the virtual machine identifier, and compare the VPC information with the obtained configuration information. Then, if the VPC information and the obtained configuration information are consistent, the data packets in the network link of the elastic file system are obtained, and the data packets in the network link are analyzed to determine the authentication field of the data packets in the network link, so as to determine the seventh diagnostic result based on the authentication field of the data packets in the network link and the VPC information.

[0120] Fig.14 For an example diagram of diagnosing a virtual machine configuration in an embodiment, please refer to Fig.14 , exemplarily, the controller can extract the VPC information of the virtual machine from the cloud management platform, and confirm whether the VPC information added by the file system has opened read and write permissions to the virtual machine. If the virtual machine does not have permissions, stop the fault diagnosis and directly inform the user to configure the correct permission group according to the instruction manual. If the read and write permissions are opened, then check the configuration of the elastic file gateway to confirm whether the actual configuration of the permissions is consistent with the management configuration. If the real permissions of the gateway are inconsistent with the management configuration, notify the cloud management attendant and the elastic file attendant to jointly confirm the configuration and change it. If the real permissions of the gateway are consistent with the management configuration, analyze the data packets in the link to analyze whether the authentication fields carried in the data packets are consistent with the user configuration. If they are inconsistent, contact the virtual network attendant for resolution.

[0121] In the above embodiment, since the virtual private cloud information of the virtual machine in the elastic file system can be determined based on the relevant information, and the configuration of the elastic file gateway in the elastic file system is diagnosed based on the virtual private cloud information to determine the seventh diagnostic result, the fault diagnosis result of the virtual machine configuration in the elastic file system can be efficiently and accurately known through the seventh diagnostic result.

[0122] The above description is based on the application of the fault diagnosis method to a controller. The fault diagnosis method can also be applied to a terminal. The following will introduce the process of applying the method to a terminal. Fig.15FIG. 1 is a flow chart of another fault diagnosis method in an embodiment. In an exemplary embodiment, as shown in FIG. Fig.15 As shown, a fault diagnosis method is also provided, which is applied to Figure 2 The terminal corresponding to the operation platform is taken as an example for explanation, including the following S1501 to S1502.

[0123] S1501, sending a fault diagnosis request to the controller corresponding to the elastic file system, the fault diagnosis request includes relevant information of the elastic file system, the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration.

[0124] Fig.16 is a schematic diagram of a diagnostic interface in an embodiment, such as Fig.16 As shown, in one embodiment, the operator can log in to the fault diagnosis program on the operation platform through the terminal to display the diagnosis interface on the terminal. Then, the operator can enter the resource pool name, virtual machine ID, elastic file ID, virtual machine root user password, user mount command and other related information in the diagnosis interface. Then, the operator clicks "Start Diagnosis", and the terminal will send a fault diagnosis request to the controller corresponding to the elastic file system, and the fault diagnosis request includes relevant information of the elastic file system.

[0125] Furthermore, the controller may diagnose the basic situation of the elastic file system according to the relevant information in response to the fault diagnosis request, and determine the fault diagnosis result. The process of the controller determining the fault diagnosis result can refer to the above embodiment, which will not be described in detail here.

[0126] S1502, receiving the fault diagnosis result sent by the controller.

[0127] Further, the controller sends the fault diagnosis result to the terminal so that the terminal receives the fault diagnosis result. Optionally, the terminal can display the fault diagnosis result, for example Fig.16 As shown in the figure, the operator is prompted that the user does not have the permission to mount the file system, and a relevant solution is given.

[0128] In the above fault diagnosis method, a fault diagnosis request can be sent to the controller corresponding to the elastic file system, and the fault diagnosis result sent by the controller can be received. Since the fault diagnosis request includes relevant information of the elastic file system, the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result, and the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. Therefore, the fault diagnosis of the elastic file system can be realized without a lot of communication and positioning, which reduces the consumption of manpower and saves manpower.

[0129] Fig.17 FIG. 1 is a process diagram of a fault diagnosis method in an embodiment. Fig.17 As shown, the fault diagnosis method of the present application can automate the manual troubleshooting method. After obtaining the user work order problem report, it is only necessary to extract the user work order problem report to determine the relevant information of the elastic file system, and the fault diagnosis result can be automatically determined based on the relevant information. After that, the operation personnel can guide the user to solve the problem based on the fault diagnosis results. In most cases, the fault diagnosis results can locate the root cause, and the problem can be solved by performing corresponding operations according to the fault diagnosis results. In some scenarios, if the fault diagnosis results still cannot locate the root cause, then report to the corresponding operation and maintenance or R&D engineer to solve the problem.

[0130] In this way, the fault handling efficiency can be improved and the labor cost can be reduced. It can be understood that the fault diagnosis method proposed in this application can also be applied to other public cloud and private cloud elastic file storage services.

[0131] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0132] Based on the same inventive concept, the embodiment of the present application also provides a fault diagnosis device for implementing the fault diagnosis method involved above. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above method, so the specific limitations in the fault diagnosis device embodiment provided below can refer to the limitations of the fault diagnosis method above, and will not be repeated here.

[0133] Fig.18 FIG. 1 is a structural block diagram of a fault diagnosis device in an embodiment. In an exemplary embodiment, as shown in FIG. Fig.18 As shown, a fault diagnosis device 1800 is provided, comprising: a receiving module 1801, a diagnosis module 1802 and a sending module 1803, wherein:

[0134] The receiving module 1801 is used to receive a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system.

[0135] The diagnosis module 1802 is used to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration.

[0136] The sending module 1803 is used to send the fault diagnosis result to the terminal.

[0137] The above-mentioned fault diagnosis device can receive a fault diagnosis request sent by a terminal, and the fault diagnosis request includes relevant information of the elastic file system. Therefore, it can respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and automatically, efficiently and accurately determine the fault diagnosis result to send the fault diagnosis result to the terminal. In addition, the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. In the above process, manual participation is reduced. Therefore, the fault diagnosis of the elastic file system can be achieved without a lot of communication and positioning, which reduces the consumption of manpower and saves manpower.

[0138] Optionally, the fault diagnosis result includes a first diagnostic result and / or a second diagnostic result; the diagnostic module 1802 is used to send a data packet to the host machine corresponding to the relevant information; according to the first packet capture result of the network address translation gateway corresponding to the relevant information, the first network link is diagnosed to obtain a first diagnostic result; the first network link is the network link between the host machine and the network address translation gateway; and / or, according to the second packet capture result of the elastic file gateway corresponding to the relevant information, the second network link is diagnosed to obtain a second diagnostic result; the second network link is the network link between the network address translation gateway and the elastic file gateway.

[0139] Optionally, the fault diagnosis result includes a third diagnosis result; the diagnostic module 1802 is used to send a call request to the elastic file gateway corresponding to the relevant information; the call request is used for the elastic file gateway to diagnose according to the status of the storage cluster connected to the elastic file gateway to determine the third diagnosis result; receive the third diagnosis result sent by the elastic file gateway.

[0140] Optionally, the fault diagnosis result includes at least one of the fourth diagnosis result, the fifth diagnosis result, and the sixth diagnosis result; the diagnosis module 1802 is further used for at least one of the following:

[0141] Determine the environment information of the virtual machine in the elastic file system according to the relevant information, and diagnose the use environment of the virtual machine according to the environment information of the virtual machine to determine a fourth diagnosis result;

[0142] In a case where the relevant information includes a mount command, diagnosing the mount command to obtain a fifth diagnosis result;

[0143] When the relevant information includes a mount command and a virtual machine password, the virtual machine is logged in according to the virtual machine password, and the mount command is executed in the virtual machine to determine the sixth diagnosis result according to the execution result of the virtual machine.

[0144] Optionally, the fault diagnosis result includes a seventh diagnostic result; a diagnostic module 1802 is used to determine the virtual private cloud information of the virtual machine in the elastic file system based on relevant information; based on the virtual private cloud information, the configuration of the elastic file gateway in the elastic file system is diagnosing to determine the seventh diagnostic result.

[0145] Fig.19 FIG. 1 is a structural block diagram of another fault diagnosis device in an embodiment. In an exemplary embodiment, as shown in FIG. Fig.19 As shown, a fault diagnosis device 1900 is provided, including: a sending module 1901 and a receiving module 1902, wherein:

[0146] The sending module 1901 is used to send a fault diagnosis request to the controller corresponding to the elastic file system, where the fault diagnosis request includes relevant information of the elastic file system, and the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, use process or virtual machine configuration;

[0147] The receiving module 1902 is used to receive the fault diagnosis result sent by the controller.

[0148] In the above fault diagnosis device, a fault diagnosis request can be sent to the controller corresponding to the elastic file system, and a fault diagnosis result sent by the controller can be received. Since the fault diagnosis request includes relevant information of the elastic file system, the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result. In addition, the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration. Therefore, the fault diagnosis of the elastic file system can be realized without a lot of communication and positioning, which reduces the consumption of manpower and saves manpower.

[0149] Each module in the above fault diagnosis device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0150] Fig. 20 FIG. 1 is an internal structure diagram of a computer device in an embodiment. In an exemplary embodiment, a computer device is provided. The computer device may be a server. The internal structure diagram thereof may be as shown in FIG. Fig. 20 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store relevant data. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a fault diagnosis method is implemented.

[0151] Those skilled in the art will understand that Fig. 20 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0152] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above-mentioned method embodiments when executing the computer program.

[0153] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0154] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0155] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0156] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0157] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A fault diagnosis method, characterized in that: The method comprises: Receiving a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system; In response to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration; The fault diagnosis result is sent to the terminal.

2. The method according to claim 1, characterized in that The fault diagnosis result includes a first diagnosis result and / or a second diagnosis result; and the diagnosing the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result includes: Sending a data packet to a host machine corresponding to the relevant information; According to the first packet capture result of the network address translation gateway corresponding to the relevant information, diagnose the first network link to obtain the first diagnosis result; the first network link is the network link between the host machine and the network address translation gateway; and / or, According to the second packet capture result of the elastic file gateway corresponding to the relevant information, the second network link is diagnosed to obtain the second diagnosis result; the second network link is the network link between the network address translation gateway and the elastic file gateway.

3. The method according to claim 1, characterized in that The fault diagnosis result includes a third diagnosis result; the diagnosing the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result includes: Sending a call request to the elastic file gateway corresponding to the relevant information; the call request is used for the elastic file gateway to diagnose according to the state of the storage cluster connected to the elastic file gateway, and determine the third diagnostic result; Receive the third diagnosis result sent by the elastic file gateway.

4. The method according to claim 1, characterized in that: The fault diagnosis result includes at least one of the fourth diagnosis result, the fifth diagnosis result, and the sixth diagnosis result; and the diagnosing the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result includes at least one of the following: Determine the environment information of the virtual machine in the elastic file system according to the relevant information, and diagnose the use environment of the virtual machine according to the environment information of the virtual machine to determine the fourth diagnosis result; In a case where the relevant information includes a mount command, diagnosing the mount command to obtain the fifth diagnosis result; In the case where the relevant information includes a mount command and a virtual machine password, the virtual machine is logged in according to the virtual machine password, and the mount command is executed in the virtual machine to determine the sixth diagnostic result according to the execution result of the virtual machine.

5. The method according to claim 1, characterized in that The fault diagnosis result includes a seventh diagnosis result; the diagnosing the basic situation of the elastic file system according to the relevant information to determine the fault diagnosis result includes: Determine virtual private cloud information of the virtual machine in the elastic file system according to the relevant information; According to the virtual private cloud information, the configuration of the elastic file gateway in the elastic file system is diagnosed to determine the seventh diagnosis result.

6. A fault diagnosis method, characterized in that: The method comprises: Sending a fault diagnosis request to a controller corresponding to the elastic file system, the fault diagnosis request including relevant information of the elastic file system, the fault diagnosis request being used for the controller to respond to the fault diagnosis request, diagnose basic conditions of the elastic file system according to the relevant information, and determine a fault diagnosis result; the basic conditions including at least one of a network link, a storage cluster status, a usage process, or a virtual machine configuration; Receive the fault diagnosis result sent by the controller.

7. A fault diagnosis device, characterized in that: The device comprises: A receiving module, configured to receive a fault diagnosis request sent by a terminal; the fault diagnosis request includes relevant information of the elastic file system; A diagnosis module, configured to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of the network link, storage cluster status, usage process or virtual machine configuration; A sending module is used to send the fault diagnosis result to the terminal.

8. A fault diagnosis device, characterized in that: The device comprises: A sending module, configured to send a fault diagnosis request to a controller corresponding to the elastic file system, wherein the fault diagnosis request includes relevant information of the elastic file system, and the fault diagnosis request is used for the controller to respond to the fault diagnosis request, diagnose the basic situation of the elastic file system according to the relevant information, and determine the fault diagnosis result; the basic situation includes at least one of a network link, a storage cluster state, a usage process, or a virtual machine configuration; The receiving module is used to receive the fault diagnosis result sent by the controller.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

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

Images