CN113193990A - Fault processing method and device - Google Patents
Fault processing method and device Download PDFInfo
- Publication number
- CN113193990A CN113193990A CN202110383175.5A CN202110383175A CN113193990A CN 113193990 A CN113193990 A CN 113193990A CN 202110383175 A CN202110383175 A CN 202110383175A CN 113193990 A CN113193990 A CN 113193990A
- Authority
- CN
- China
- Prior art keywords
- fault
- information
- fault type
- resource library
- processing resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
- 238000003672 processing method Methods 0.000 title abstract description 5
- 238000012545 processing Methods 0.000 claims abstract description 93
- 238000000034 method Methods 0.000 claims abstract description 50
- 238000010586 diagram Methods 0.000 description 9
- 238000012423 maintenance Methods 0.000 description 3
- 238000007726 management method Methods 0.000 description 2
- 238000007789 sealing Methods 0.000 description 2
- 230000006978 adaptation Effects 0.000 description 1
- 238000013459 approach Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 230000007812 deficiency Effects 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/0631—Management of faults, events, alarms or notifications using root cause analysis; using analysis of correlation between notifications, alarms or events based on decision criteria, e.g. hierarchy, tree or time analysis
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
- H04L41/06—Management of faults, events, alarms or notifications
- H04L41/069—Management of faults, events, alarms or notifications using logs of notifications; Post-processing of notifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/455—Emulation; Interpretation; Software simulation, e.g. virtualisation or emulation of application or operating system execution engines
- G06F9/45533—Hypervisors; Virtual machine monitors
- G06F9/45558—Hypervisor-specific management and integration aspects
- G06F2009/45595—Network integration; Enabling network access in virtual machine instances
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The disclosure provides a fault handling method and device. The method comprises the following steps: acquiring fault information, wherein the fault information carries fault prompt information; determining the current fault type according to the fault prompt information, and matching a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types; if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, calling the solution corresponding to the fault type from the problem processing resource library, and issuing an operation instruction to a zero terminal or a virtual machine according to the solution corresponding to the fault type. The fault processing method in the embodiment of the disclosure can solve the problems that all the problems encountered by a user in the process of using a cloud desktop cannot be automatically collected, and quick response and automatic processing are made in the prior art.
Description
Technical Field
The present disclosure relates to the field of fault handling technologies, and in particular, to a fault handling method and apparatus.
Background
VDI, in brief, virtualizes your desktop by running a Windows system on the cluster servers of the data center. Users are connected with a virtual desktop (generally referred to as a virtual machine) through a user computing protocol from user side equipment (zero terminal), the users can access the desktops of the users through the zero terminal just like accessing a traditional locally installed desktop, the users can be connected to the desktops which the users want to be connected at any time and any place as long as a network exists, IT personnel can manage desktop users and data more easily, and the data of the users are safer because all the data are in a service provider. As shown in fig. 1, a user may access a virtual machine allocated to the cluster server through a zero terminal, thereby obtaining a desktop image, and control the obtained virtual desktop in a reverse control manner.
In some cases, direct communication between the client and the server is not desirable. For example, for security reasons, a user may wish to place all servers in a corporate private network behind a firewall and only allow agents to access them. In this case, the user must have the proxy server forward all requests and responses between the server and the user side, rather than having them communicate directly with each other. The proxy server (proxy server) decouples the client and the server. The server side registers itself to the proxy, allows the user side to access the service by exposing the interface, the server side does not need to disclose any information and data, and adds the user side and the server proxy to process all transmission work of sending method calls and parameters thereof to the server through the network and then sending responses back to the user side. The agent will complete all data sealing and de-sealing, security control, transport channel configuration and any other additional work. The user side sends the request through the proxy server, and the proxy server forwards the request to the server side and sends back the result or the abnormity of the request to the user side. By using a proxy server, applications can access remote services by sending messages. When the user uses the cloud desktop, the proxy server is accessed through the zero terminal, the proxy server transfers the connection request and the server cluster information, and the virtual desktop is returned to the zero terminal for the user to use. This approach is more suitable for wide area networks.
Disclosure of Invention
The purpose of the present disclosure is to overcome the deficiencies of the prior art, and provide a fault handling method and apparatus, where the fault handling method can solve the problems that in the prior art, all the problems encountered by a user in a process of using a cloud desktop cannot be automatically collected, and a quick response and automatic handling are made.
According to a first aspect of the embodiments of the present disclosure, there is provided a fault handling method, including:
acquiring fault information, wherein the fault information carries fault prompt information;
determining the current fault type according to the fault prompt information, and matching a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types;
if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, calling the solution corresponding to the fault type from the problem processing resource library, and issuing an operation instruction to a zero terminal or a virtual machine according to the solution corresponding to the fault type.
In one embodiment, the method further comprises:
and if the solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type, compiling corresponding fault information into an unprocessed fault resource list, and issuing a processing instruction to a zero terminal or a cloud desktop.
In one embodiment, the method further comprises:
the determining the current fault type according to the fault prompt information and matching a corresponding solution in a problem processing resource library according to the fault type comprises the following steps:
if the current fault type is determined to be occupied by the database according to the fault prompt information, the corresponding solution matched in the problem processing resource library according to the fault type is to close an occupied process or restart the database;
and if the occupied process is selected to be closed, determining the pid parameter of the occupied process, and closing the occupied process according to the pid parameter of the occupied process.
In one embodiment, the determining a current fault type according to the fault prompting information and matching a corresponding solution in a problem processing resource library according to the fault type includes:
if the current fault type is determined to be thread jamming according to the fault prompt information, a corresponding solution matched in a problem processing resource library according to the fault type is a restarting zero terminal or a restarting virtual machine;
if the current fault type is determined to be permission rejection according to the fault prompt information, sending prompt check permission service information or reminding permission expiration information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
if the current fault type is determined to be heartbeat disconnection or network interruption according to the fault prompt information, sending prompt check network information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
and if the current fault type is determined to be the process crash according to the fault prompt information, analyzing the crash reason according to the corresponding solution matched by the fault type in the problem processing resource library and carrying out remote upgrading.
In one embodiment, the obtaining the fault information includes:
the zero terminal or the cloud desktop sends fault information to a fault processing platform on the proxy server;
and a fault processing platform on the proxy server receives fault information sent by the zero terminal or the cloud desktop.
In one embodiment, the fault information is log information that includes warning level information and error level information.
In one embodiment, the fault notification information includes at least one of an error code, a fault label, a keyword, or error information.
According to a second aspect of the embodiments of the present disclosure, there is provided a fault handling apparatus including:
the acquisition module acquires fault information, wherein the fault information carries fault prompt information;
the processing module is used for determining the current fault type according to the fault prompt information and matching a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types;
and the calling module is used for calling the solution corresponding to the fault type from the problem processing resource library if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, and issuing an operation instruction to the zero terminal or the virtual machine according to the solution corresponding to the fault type.
In one embodiment, the fault handling apparatus further comprises:
and the programming module is used for programming corresponding fault information into an unprocessed fault resource list and issuing a processing instruction to a zero terminal or a cloud desktop if a solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type.
In one embodiment, the processing module comprises:
the determining submodule determines the current fault type according to the fault prompt information;
and the matching sub-module is used for matching the corresponding solution in the problem processing resource library according to the fault type.
According to the fault processing method provided by the disclosure, all problems of a user in a cloud desktop using process can be automatically collected, a quick response is made, and various problems are automatically processed.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the present disclosure and together with the description, serve to explain the principles of the disclosure.
FIG. 1 is a schematic diagram of a prior art fault handling system.
Fig. 2 is a schematic diagram of a fault handling system according to an embodiment of the present disclosure.
Fig. 3 is a flowchart of a fault handling method according to an embodiment of the present disclosure.
Fig. 4 is an architecture diagram of a fault handling apparatus according to an embodiment of the present disclosure.
Fig. 5 is an architecture diagram of a fault handling device according to an embodiment of the present disclosure.
Fig. 6 is an architecture diagram of a fault handling device according to an embodiment of the present disclosure.
Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the exemplary embodiments below are not intended to represent all implementations consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.
Fig. 2 is a schematic diagram of a fault handling system according to an embodiment of the present disclosure. As shown in fig. 2, the system includes a proxy server 201, and at least one zero terminal 202 and at least one cluster server 203 connected to the proxy server 201.
A user uses the zero terminal 202 to inquire and connect a cloud desktop through the proxy server 201, namely the zero terminal 202 is a receiving end, and the cloud desktop is a sending end; in the using process, the zero terminal 202 and the cloud desktop simultaneously collect problem information encountered in the current environment, do not locally record the problem information, and directly upload the problem information to a fault processing platform in the proxy server 201; the fault processing platform is responsible for collecting all the problems of the zero terminal 202 and the cloud desktop, and automatically issuing commands to the zero terminal 202 or the cloud desktop according to the processing means of the corresponding problems so as to process the corresponding problems; meanwhile, the fault processing platform can also be used for sorting the problems without the solutions, and informing engineers of analyzing and processing and updating the problem processing resources.
Fig. 3 is a flowchart of a fault handling method according to an embodiment of the present disclosure. As shown in fig. 3, the method includes:
step 101, acquiring fault information, wherein the fault information carries fault prompt information;
in one embodiment, the fault notification information includes at least one of an error code, a fault label, a keyword, or error information.
In one embodiment, the obtaining the fault information includes:
the zero terminal or the cloud desktop sends fault information to a fault processing platform on the proxy server;
and a fault processing platform on the proxy server receives fault information sent by the zero terminal or the cloud desktop.
In this embodiment, in the using process of a user, when a zero terminal or a cloud desktop (virtual machine) encounters a problem, the fault information is automatically uploaded to a fault processing platform in a proxy server;
specifically, the zero terminal or the virtual machine submits the problem information to the fault processing platform through the connection with the proxy server.
in one embodiment, the fault information is log information, the log information including warning level information and error level information;
in this embodiment, the fault information is transferred to the fault handling platform in the form of a log, which includes warning level information and error level information. For example, an error level of 113 represents a heartbeat discontinuity; a warning level of 223 represents a kicked line. Therefore, the current error type can be identified according to the fault prompt information.
Therefore, the embodiment of the disclosure may set a fault handling resource library, which includes each fault prompting message and a solution corresponding to the fault. Therefore, when the fault processing platform receives the fault information sent by the zero terminal or the virtual machine, the fault prompt information contained in the fault processing platform can be identified, and then the corresponding solution is matched in the fault processing resource library according to the fault prompt information.
In one embodiment, the determining a current fault type according to the fault prompting information and matching a corresponding solution in a problem processing resource library according to the fault type includes:
if the current fault type is determined to be occupied by the database according to the fault prompt information, the corresponding solution matched in the problem processing resource library according to the fault type is to close an occupied process or restart the database;
and if the occupied process is selected to be closed, determining the pid parameter of the occupied process, and closing the occupied process according to the pid parameter of the occupied process.
In one embodiment, the determining a current fault type according to the fault prompting information and matching a corresponding solution in a problem processing resource library according to the fault type includes:
if the current fault type is determined to be thread jamming according to the fault prompt information, a corresponding solution matched in a problem processing resource library according to the fault type is a restarting zero terminal or a restarting virtual machine;
if the current fault type is determined to be permission rejection according to the fault prompt information, sending prompt check permission service information or reminding permission expiration information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
if the current fault type is determined to be heartbeat disconnection or network interruption according to the fault prompt information, sending prompt check network information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
and if the current fault type is determined to be the process crash according to the fault prompt information, analyzing the crash reason according to the corresponding solution matched by the fault type in the problem processing resource library and carrying out remote upgrading.
And 303, if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, calling the solution corresponding to the fault type from the problem processing resource library, and issuing an operation instruction to the zero terminal or the virtual machine according to the solution corresponding to the fault type.
Optionally, the method further comprises:
and if the solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type, compiling corresponding fault information into an unprocessed fault resource list, and issuing a processing instruction to a zero terminal or a cloud desktop.
In this embodiment, if the matching is unsuccessful, the corresponding fault information is compiled into an unprocessed fault resource list, and a general processing command, such as a restart service, is issued to the zero terminal or the cloud desktop, and meanwhile, a maintenance worker is notified, and the operation and maintenance worker analyzes the unprocessed fault and uploads the corresponding solution to the fault processing resource library for calling when a subsequent problem is encountered again. Therefore, the fault processing resource library in the embodiment of the disclosure has strong expandability, and the fault processing resource library can be continuously expanded by operation and maintenance personnel.
According to the fault processing method provided by the disclosure, all problems of a user in a cloud desktop using process can be automatically collected, a quick response is made, and various problems are automatically processed.
Based on the fault management method described in the embodiment corresponding to fig. 3, the following is an embodiment of the apparatus of the present disclosure, which may be used to execute an embodiment of the fault management method of the present disclosure.
Fig. 4 is an architecture diagram of a fault handling apparatus according to an embodiment of the present disclosure. As shown in fig. 4, the fault handling apparatus includes: an acquisition module 401, a processing module 402, and a calling module 403; the acquiring module 401 is configured to acquire fault information, where the fault information carries fault prompting information; the processing module 402 is configured to determine a current fault type according to the fault notification information, and match a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types; the invoking module 403 is configured to, when a solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, invoke the solution corresponding to the fault type from the problem processing resource library, and issue an operation instruction to the zero terminal or the virtual machine according to the solution corresponding to the fault type.
Fig. 5 is an architecture diagram of a fault handling device according to an embodiment of the present disclosure. As shown in fig. 5, the fault handling apparatus includes: the system comprises an acquisition module 501, a processing module 502, a calling module 503 and a programming module 504; the compiling module 504 is configured to, when a solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type, compile corresponding fault information into an unprocessed fault resource list, and issue a processing instruction to a zero terminal or a cloud desktop.
Fig. 6 is an architecture diagram of a fault handling device according to an embodiment of the present disclosure. As shown in fig. 6, the fault handling apparatus includes: the system comprises an acquisition module 601, a processing module 602, a calling module 603 and a programming module 604; wherein the processing module 602 includes a determination sub-module 6021 and a matching sub-module 6022; the determining submodule 6021 is configured to determine a current fault type according to the fault prompt information; matching sub-module 6022 is configured to match the corresponding solution in the problem processing resource pool according to the fault type.
Those of ordinary skill in the art will understand that: all or a portion of the steps of implementing the above-described method embodiments may be performed by hardware associated with program instructions. The aforementioned program may be preset in a computer-readable storage medium. When executed, the program performs steps comprising the method embodiments described above; and the aforementioned storage medium includes: various media that can store program codes, such as ROM, RAM, magnetic or optical disks.
Other embodiments of the disclosure will be apparent to those skilled in the art from consideration of the specification and practice of the disclosure disclosed herein. This disclosure is intended to cover any variations, uses, or adaptations of the disclosure following, in general, the principles of the disclosure and including such departures from the present disclosure as come within known or customary practice within the art to which the disclosure pertains. It is intended that the specification and examples be considered as exemplary only, with a true scope and spirit of the disclosure being indicated by the following claims.
It will be understood that the present disclosure is not limited to the precise arrangements described above and shown in the drawings and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.
Claims (10)
1. A fault handling method, characterized in that a fault handling platform on a proxy server, the method comprises:
acquiring fault information, wherein the fault information carries fault prompt information;
determining the current fault type according to the fault prompt information, and matching a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types;
if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, calling the solution corresponding to the fault type from the problem processing resource library, and issuing an operation instruction to a zero terminal or a virtual machine according to the solution corresponding to the fault type.
2. The method of claim 1, further comprising:
and if the solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type, compiling corresponding fault information into an unprocessed fault resource list, and issuing a processing instruction to a zero terminal or a cloud desktop.
3. The method of claim 1, wherein determining a current fault type according to the fault notification information and matching a corresponding solution in a problem handling repository according to the fault type comprises:
if the current fault type is determined to be occupied by the database according to the fault prompt information, the corresponding solution matched in the problem processing resource library according to the fault type is to close an occupied process or restart the database;
and if the occupied process is selected to be closed, determining the pid parameter of the occupied process, and closing the occupied process according to the pid parameter of the occupied process.
4. The method of claim 1, wherein determining a current fault type according to the fault notification information and matching a corresponding solution in a problem handling repository according to the fault type comprises:
if the current fault type is determined to be thread jamming according to the fault prompt information, a corresponding solution matched in a problem processing resource library according to the fault type is a restarting zero terminal or a restarting virtual machine;
if the current fault type is determined to be permission rejection according to the fault prompt information, sending prompt check permission service information or reminding permission expiration information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
if the current fault type is determined to be heartbeat disconnection or network interruption according to the fault prompt information, sending prompt check network information to a user according to a corresponding solution matched by the fault type in a problem processing resource library;
and if the current fault type is determined to be the process crash according to the fault prompt information, analyzing the crash reason according to the corresponding solution matched by the fault type in the problem processing resource library and carrying out remote upgrading.
5. The method according to any one of claims 1 to 4, wherein the obtaining fault information comprises:
the zero terminal or the cloud desktop sends fault information to a fault processing platform on the proxy server;
and a fault processing platform on the proxy server receives fault information sent by the zero terminal or the cloud desktop.
6. The method according to any one of claims 1 to 4,
the fault information is log information, and the log information comprises warning level information and error level information.
7. The method according to any one of claims 1 to 4,
the fault notification information includes at least one of an error code, a fault label, a keyword, or error information.
8. A fault handling apparatus, characterized in that the fault handling apparatus comprises:
the acquisition module acquires fault information, wherein the fault information carries fault prompt information;
the processing module is used for determining the current fault type according to the fault prompt information and matching a corresponding solution in a problem processing resource library according to the fault type; the problem processing resource library is preset with a plurality of fault types and solutions corresponding to the fault types;
and the calling module is used for calling the solution corresponding to the fault type from the problem processing resource library if the solution corresponding to the fault type is matched in the problem processing resource library according to the fault type, and issuing an operation instruction to the zero terminal or the virtual machine according to the solution corresponding to the fault type.
9. The fault handling device of claim 8, further comprising:
and the programming module is used for programming corresponding fault information into an unprocessed fault resource list and issuing a processing instruction to a zero terminal or a cloud desktop if a solution corresponding to the fault type is not matched in the problem processing resource library according to the fault type.
10. The fault handling device according to claim 8 or 9, wherein the processing module comprises:
the determining submodule determines the current fault type according to the fault prompt information;
and the matching sub-module is used for matching the corresponding solution in the problem processing resource library according to the fault type.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110383175.5A CN113193990A (en) | 2021-04-09 | 2021-04-09 | Fault processing method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202110383175.5A CN113193990A (en) | 2021-04-09 | 2021-04-09 | Fault processing method and device |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113193990A true CN113193990A (en) | 2021-07-30 |
Family
ID=76975322
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202110383175.5A Pending CN113193990A (en) | 2021-04-09 | 2021-04-09 | Fault processing method and device |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113193990A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118577A (en) * | 2022-06-24 | 2022-09-27 | 重庆长安汽车股份有限公司 | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium |
| CN115408112A (en) * | 2022-11-02 | 2022-11-29 | 确信信息股份有限公司 | Bug processing method, system, medium and equipment for intranet production environment |
-
2021
- 2021-04-09 CN CN202110383175.5A patent/CN113193990A/en active Pending
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115118577A (en) * | 2022-06-24 | 2022-09-27 | 重庆长安汽车股份有限公司 | Method and device for determining remote upgrade abnormal reason, electronic equipment and storage medium |
| CN115118577B (en) * | 2022-06-24 | 2023-08-18 | 重庆长安汽车股份有限公司 | Remote upgrade abnormality cause determination method, device, electronic equipment and storage medium |
| CN115408112A (en) * | 2022-11-02 | 2022-11-29 | 确信信息股份有限公司 | Bug processing method, system, medium and equipment for intranet production environment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111861140A (en) | Service processing method, device, storage medium and electronic device | |
| US20080098109A1 (en) | Incident resolution | |
| US11392873B2 (en) | Systems and methods for simulating orders and workflows in an order entry and management system to test order scenarios | |
| US20050262075A1 (en) | Systems and methods for collaboration shared state management | |
| CN106210099B (en) | Data processing system and method | |
| CN111193602B (en) | Automatic operation and maintenance management system and method | |
| CN107292117B (en) | Processing method and device for quality guarantee of mass shared medical images | |
| CN111309550A (en) | Data acquisition method, system, equipment and storage medium of application program | |
| CN113193990A (en) | Fault processing method and device | |
| US20050273714A1 (en) | Systems and methods for an embedded collaboration client | |
| CN113055421A (en) | Service grid management method and system | |
| KR101416280B1 (en) | Event handling system and method | |
| CN114666407A (en) | RPA cross-terminal communication method and equipment | |
| CN111865868B (en) | Cross-network regional service calling method and system | |
| US20060123387A1 (en) | Apparatus and method for producing application software for streaming service and system and method for providing software streaming service with network fault tolerance | |
| CN112765246B (en) | Task processing method, device, electronic equipment and storage medium | |
| CN113411209A (en) | Distributed password service full-link detection system and method | |
| CN116957764A (en) | Account data processing method and device, electronic equipment and storage medium | |
| CN113778709B (en) | Interface calling method, device, server and storage medium | |
| US7805733B2 (en) | Software implementation of hardware platform interface | |
| CN105763365A (en) | Method and device for processing anomaly | |
| CN114338584A (en) | Message withdrawing method and message transmission system | |
| CN113079055A (en) | Method and device for dynamically acquiring AGV (automatic guided vehicle) running data | |
| CN115102854B (en) | Remote procedure call route management control method, system and equipment for micro-service | |
| CN114465766B (en) | SSH-based remote access method and device, electronic equipment and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |