CN113961387A - Server error reporting evaluation and processing method, system and storage medium - Google Patents

Server error reporting evaluation and processing method, system and storage medium Download PDF

Info

Publication number
CN113961387A
CN113961387A CN202111273872.1A CN202111273872A CN113961387A CN 113961387 A CN113961387 A CN 113961387A CN 202111273872 A CN202111273872 A CN 202111273872A CN 113961387 A CN113961387 A CN 113961387A
Authority
CN
China
Prior art keywords
server
firmware
fault
defect
information
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.)
Withdrawn
Application number
CN202111273872.1A
Other languages
Chinese (zh)
Inventor
李征梅
付丽莉
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Suzhou Inspur Intelligent Technology Co Ltd
Original Assignee
Suzhou Inspur Intelligent Technology Co Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Suzhou Inspur Intelligent Technology Co Ltd filed Critical Suzhou Inspur Intelligent Technology Co Ltd
Priority to CN202111273872.1A priority Critical patent/CN113961387A/en
Publication of CN113961387A publication Critical patent/CN113961387A/en
Withdrawn legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/079—Root cause analysis, i.e. error or fault diagnosis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F11/00—Error detection; Error correction; Monitoring
    • G06F11/07—Responding to the occurrence of a fault, e.g. fault tolerance
    • G06F11/0703—Error or fault processing not based on redundancy, i.e. by taking additional measures to deal with the error or fault not making use of redundancy in operation, in hardware, or in data representation
    • G06F11/0766—Error or fault reporting or storing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/60—Software deployment
    • G06F8/65—Updates
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F8/00—Arrangements for software engineering
    • G06F8/70—Software maintenance or management
    • G06F8/71—Version control; Configuration management

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Computer Security & Cryptography (AREA)
  • Quality & Reliability (AREA)
  • Health & Medical Sciences (AREA)
  • Biomedical Technology (AREA)
  • Debugging And Monitoring (AREA)

Abstract

The application relates to a method, a system and a storage medium for evaluating and processing error report of a server. In the application, when a server fails and reports errors, the server acquires failure and error reporting information of the server; matching fault reporting information of the server with firmware defect cases in a firmware defect database; counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold value; otherwise, feeding back the first manual processing information; if yes, feeding back upgrading decision information; the upgrading decision information content comprises a firmware version for solving the server fault and a fault risk; and under the condition of meeting the preset upgrading condition, acquiring firmware according to the firmware version for solving the server fault in the upgrading decision information to upgrade the server. According to the method and the device, whether the fault report error of the server can be automatically distinguished through firmware upgrading or not is judged, and the fault report error which can be solved through firmware upgrading is solved through firmware upgrading.

Description

Server error reporting evaluation and processing method, system and storage medium
Technical Field
The present disclosure relates to the field of server operation and maintenance, and in particular, to a method, a system, and a storage medium for evaluating and processing server error reporting.
Background
The data center has a large number of servers which are operated on line at different times, and the hardware, firmware, software, configuration information and the like of the servers are different. Inconvenience is caused to the maintenance management of the server.
At the server manufacturer side, iteration is fast for server product firmware versions such as BIOS, BMC, RMC, and the like, and a developer usually performs iteration upgrade to the next version after solving a part of bugs. Customers often purchase maintenance services for 3 to 5 years, server manufacturers regularly provide the new firmware versions to the customers, but the servers which are already on the shelf often cannot upgrade the firmware in time because of the operation of the business, so that some faults are repaired in the latest firmware version, but the old firmware version in the online server still exists. When the server of the data center has errors, more time is spent for screening the error information, part of the problems in the error information need to be solved by upgrading the firmware, and part of the problems need to be maintained by technical personnel. The existing method for screening and processing error information of the server mainly depends on a manual method, and if technicians have unclear updating effect on subsequent firmware, the technicians try various methods to solve the problem which can be solved by firmware upgrading. This may result in waste of manpower and material resources, and even in cases where the problem cannot be solved due to "no drug is symptomatic".
Disclosure of Invention
In order to solve the technical problem or at least partially solve the technical problem, the present application provides a server error evaluation and processing method, system and storage medium.
In a first aspect, the present application provides a method for evaluating and processing an error report of a server, including:
when a server fails and reports errors, acquiring failure and error reporting information of the server;
matching fault reporting information of the server with firmware defect cases in a firmware defect database;
counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold value;
otherwise, feeding back the first manual processing information;
if yes, feeding back upgrading decision information; the upgrading decision information content comprises a firmware version for solving the server fault and a fault risk;
and under the condition of meeting the preset upgrading condition, acquiring firmware according to the firmware version for solving the server fault in the upgrading decision information to upgrade the server.
Further, the fault error information includes server information, fault components, error codes, and fault log contents.
Furthermore, the firmware defect database stores firmware defect cases, and the content of the firmware defect cases comprises firmware versions, defect information of the firmware, defect risk levels and corresponding versions of firmware for solving defects;
the defect information of the firmware comprises: defective parts, error codes, and defect descriptions.
Further, the matching the fault reporting information of the server with the firmware defect cases in the firmware defect database includes:
and matching the firmware defect case corresponding to the fault error reporting information in the firmware defect database according to the fault component and the error code in the fault error reporting information.
Furthermore, the matching degree between the fault reporting information of the statistical server and the matched firmware defect case comprises:
analyzing the fault log content in the fault error reporting information and collecting fault keywords describing the fault from the fault log content;
collecting defect keywords for describing defects from the defect description of the firmware defect cases matched with the fault error reporting information;
and comparing the fault keywords with the defect keywords to obtain the matching degree of the fault keywords and the defect keywords as the matching degree of the server fault and the firmware defect case.
Further, the fault risk level in the firmware fault case matched with the fault reporting information of the server fault is used as the fault risk of the server fault, and the fault risk level comprises a high level, a middle level and a low level.
Further, the obtaining the firmware according to the firmware version for solving the server fault in the upgrade decision information to perform the server upgrade when the preset upgrade condition is met includes:
judging whether a target server sending out fault error reporting information is idle and obtaining upgrading permission, if so, obtaining a firmware version for solving the fault of the target server in upgrading decision information as a target firmware;
inquiring whether target firmware exists in a cloud firmware library;
if yes, downloading the target firmware into the target server and upgrading;
and otherwise, recording the missing target firmware and sending the target firmware to a server administrator and a cloud firmware library administrator through a preset contact way.
Furthermore, after the server firmware is upgraded according to the server fault reporting information, whether the server still generates the same server fault reporting error is verified, and if so, the server feeds back the second manual processing information.
In a second aspect, the present application provides a server firmware risk assessment and upgrade system, including: the fault uploading module uploads fault reporting information to the fault matching module when the server has fault reporting;
the fault matching module matches the firmware defect cases in the firmware defect database according to the fault reporting information of the server;
the judging module is used for counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold value or not;
the feedback module generates upgrading decision information when the judging module judges that the matching degree is greater than the set threshold value, and feeds back first manual processing information when the judging module judges that the matching degree is less than the set threshold value;
the decision module is used for providing upgrading permission for the server by an administrator;
and the upgrading module is used for acquiring the target firmware from the cloud firmware library according to the upgrading decision information to upgrade the target server when the server acquires the upgrading permission and is idle.
In a third aspect, the present application provides a storage medium for implementing the server error reporting evaluation and processing method, where the storage medium for implementing the server error reporting evaluation and processing method stores at least one instruction, and reads and executes the instruction to implement the server error reporting evaluation and processing method.
Compared with the prior art, the technical scheme provided by the embodiment of the application has the following advantages:
according to the method and the device, the fault error report which can be solved through firmware upgrading is determined in a mode of matching the server fault error report with the firmware defect cases in the firmware defect database, for the server fault error report which is caused by the existing firmware defects of the server, the firmware defect cases matched with the fault error report can provide target firmware for solving the fault error report, and the target firmware can be obtained through the cloud firmware library to upgrade and solve the fault error report which is caused by the firmware defects of the server. And the first manual processing information is provided for the fault reporting errors which cannot be solved through firmware upgrading, so that the server fault reporting errors which can be solved by non-firmware upgrading can be timely processed by technicians, and the automatic evaluation and discrimination processing of the server fault reporting errors is realized.
According to the method and the device, after the server firmware is upgraded according to the server fault reporting information, whether the same server fault reporting is generated by the server is verified, if yes, the second manual processing information is fed back, and the situation that the problem is not solved due to fault reporting error judgment is avoided.
Drawings
The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate embodiments consistent with the invention and together with the description, serve to explain the principles of the invention.
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without inventive exercise.
Fig. 1 is a flowchart of a method for evaluating and processing error reported by a server according to an embodiment of the present disclosure;
fig. 2 is a schematic content diagram of a firmware defect case stored in a firmware defect database according to an embodiment of the present application;
FIG. 3 is a flowchart illustrating matching of fault reporting information of a server with firmware defect cases in a firmware defect database according to an embodiment of the present disclosure;
fig. 4 is a flowchart illustrating a matching degree between fault reporting information of a statistical server and a matched firmware defect case according to an embodiment of the present disclosure;
fig. 5 is a flowchart illustrating that, when a preset upgrade condition is satisfied, a firmware is obtained according to a firmware version for solving a server fault in upgrade decision information to perform server upgrade according to an embodiment of the present application;
fig. 6 is a schematic diagram of a server firmware risk assessment and upgrade system according to an embodiment of the present disclosure.
Detailed Description
In order to make the objects, technical solutions and advantages of the embodiments of the present application clearer, the technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application, and it is obvious that the described embodiments are some embodiments of the present application, but not all embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
Example 1
Referring to fig. 1, an embodiment of the present application provides a method for evaluating and processing an error report of a server, including:
s100, when a server fails and reports errors, acquiring failure and error reporting information of the server; specifically, the fault error information includes server information, a fault component, an error code, and fault log content, where one possible type of the server information includes a server product number, and the source of the fault log content includes, but is not limited to, a black box log and a SEL log. In the specific implementation process, an operation and maintenance server connected with the server is configured, and when the server fails and reports errors, the server sends failure and error reporting information to the operation and maintenance server.
S200, matching the fault error reporting information of the server with the firmware defect cases in the firmware defect database.
In a specific implementation process, the firmware defect database is configured in the operation and maintenance server, and referring to fig. 2, a firmware defect case is stored in the firmware defect database, and the content of the firmware defect case includes a firmware version, defect information of the firmware, a defect risk level, and a corresponding version of firmware for solving a defect; the defect information of the firmware comprises: defective parts, error codes, and defect descriptions.
In a specific implementation process, matching a firmware defect case corresponding to fault error reporting information in a firmware defect database according to a fault component and an error code in the fault error reporting information, as shown in fig. 3, the matching of the fault error reporting information of the server with the firmware defect case in the firmware defect database includes:
s201, acquiring a fault component and an error code in fault error reporting information;
s202, searching and screening firmware defect cases which are the same as the defect parts in the fault error reporting information in a firmware defect database through the acquired fault parts, and finding out the firmware defect cases matched with the fault parts in the fault error reporting information;
s203, further query the firmware defect cases screened in the screening step S202 through the error codes in the fault error reporting information, and find out the firmware defect cases in which all the faulty components and the error codes are the same as those in the fault error reporting information.
S300, counting and judging whether the matching degree between the fault error-reporting information of the server and the matched firmware defect case is greater than a set threshold value or not; otherwise, jumping to S400, if yes, jumping to S500.
In the specific implementation process, referring to fig. 4, the matching degree between the failure error reporting information of the statistical server and the matched firmware defect case includes:
s301, analyzing fault log contents in the fault error reporting information and collecting fault keywords describing the fault from the fault log contents;
s302, collecting defect keywords for describing defects from the defect description of the firmware defect case matched with the fault error reporting information;
s303, comparing the fault keyword with the defect keyword to obtain the matching degree of the fault keyword and the defect keyword as the matching degree of the server fault and the firmware defect case.
S400, feeding back first manual processing information; in the specific implementation process, the contact information of the administrator and the server information of the server maintained by the administrator are bound and stored in the operation and maintenance server. And when judging whether the matching degree between the fault reporting information of the server and the matched firmware defect case is smaller than a set threshold value, determining that the fault reporting of the server cannot be solved by updating the firmware. And feeding back first manual processing information to the administrator according to the contact way of the administrator corresponding to the server, wherein the first manual processing information comprises fault error reporting information with the matching degree not reaching a set threshold value, and arranging technicians to process corresponding fault error reporting according to the first manual processing information.
S500, feeding back upgrading decision information; the upgrading decision information content comprises a firmware version for solving the server fault and a fault risk; and when judging whether the matching degree between the fault reporting information of the server and the matched firmware defect case is greater than a set threshold value, considering that the updated firmware can solve the fault reporting of the server. And acquiring the firmware of the corresponding version and the defect risk level for solving the defect in the firmware defect case with the fault error reporting matching degree of the server, further generating the upgrading decision information, and feeding back the upgrading decision information to an administrator according to the contact way of the administrator corresponding to the server. And when the upgrading decision information is generated, taking the defect risk level in the firmware defect case as the fault risk of the server fault, wherein the defect risk level comprises a high level, a medium level and a low level. One possible way is: the defect risk level of the alarm type defects which do not influence the server function is configured to be low level, so that the fault risk of the alarm type faults which do not influence the server function and report errors is low level.
S600, under the condition that the preset upgrading condition is met, obtaining firmware according to the firmware version which solves the server fault in the upgrading decision information, and upgrading the server. Specifically, the preset upgrade condition includes that the server acquires upgrade permission given by an administrator and the server is in an idle state.
In a specific implementation process, referring to fig. 5, when a preset upgrade condition is satisfied, obtaining a firmware according to a firmware version that solves a server fault in the upgrade decision information to perform server upgrade includes:
s601, judging whether the target server sending the fault error reporting information obtains the upgrading permission, if so, executing S602, otherwise, giving up the upgrading and updating of the server firmware. In a specific implementation process, an administrator determines whether to give upgrading permission to the target server according to the fault risk in the upgrading decision information. One possible way is: and if the fault risk of fault error reporting is not low level, the administrator gives the target server upgrading permission.
And S602, judging whether the target server sending the fault error reporting information is in an idle state, if so, executing S603, otherwise, periodically acquiring the state of the target server and circularly executing S602.
S603, acquiring the firmware version for solving the target server fault in the upgrading decision information as the target firmware.
S604, inquiring whether a target firmware exists in the cloud firmware library; if yes, executing S605; otherwise, S606 is performed.
S605, downloading the target firmware to the target server and upgrading.
And S606, recording the missing target firmware and sending the target firmware to a server administrator and a cloud firmware library administrator through a preset contact mode.
In the specific implementation process, after the server firmware is upgraded according to the server fault reporting information, whether the server still generates the same server fault reporting error is verified, and if so, the server feeds back second manual processing information to an administrator.
Example 2
Referring to fig. 6, an embodiment of the present application provides a server firmware risk assessment and upgrade system, including: and the fault uploading module uploads fault reporting information to the fault matching module when the server has fault reporting. And the fault matching module is used for matching the firmware defect cases in the firmware defect database according to the fault reporting information of the server. And the judging module is used for counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold, and the set threshold is configured by the configuration module in the specific implementation process.
The feedback module generates and sends upgrading decision information to an administrator when the judging module judges that the matching degree is greater than the set threshold value, and generates and sends first manual processing information to the administrator when the judging module judges that the matching degree is less than the set threshold value;
the decision module is used for providing upgrading permission for the server by an administrator;
the upgrading module is used for acquiring the target firmware from the cloud firmware library according to the upgrading decision information to upgrade the target server when the server acquires the upgrading permission and is idle;
and the verification module is used for verifying whether the server still generates the same server fault report error or not after the server firmware is upgraded aiming at the server fault report error information, and if so, generating and feeding back second manual processing information.
Example 3
The embodiment of the application provides a storage medium for realizing the server error reporting evaluation and processing method, the storage medium for realizing the server error reporting evaluation and processing method stores at least one instruction, and the instruction is read and executed to realize the server error reporting evaluation and processing method.
In the embodiments provided in the present invention, it should be understood that the disclosed apparatus and method may be implemented in other ways. For example, the above-described apparatus embodiments are merely illustrative, and for example, the division of the units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed. In addition, the shown or discussed mutual coupling or direct coupling or communication connection may be an indirect coupling or communication connection through some interfaces, devices or units, and may be in an electrical, mechanical or other form.
The units described as separate parts may or may not be physically separate, and parts displayed as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiment.
In addition, functional units in the embodiments of the present invention may be integrated into one processing unit, or each unit may exist alone physically, or two or more units are integrated into one unit. The integrated unit can be realized in a form of hardware, and can also be realized in a form of a software functional unit.
The foregoing are merely exemplary embodiments of the present invention, which enable those skilled in the art to understand or practice the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims (10)

1. A method for evaluating and processing server error report is characterized by comprising the following steps:
when a server fails and reports errors, acquiring failure and error reporting information of the server;
matching fault reporting information of the server with firmware defect cases in a firmware defect database;
counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold value;
otherwise, feeding back the first manual processing information;
if yes, feeding back upgrading decision information; the upgrading decision information content comprises a firmware version for solving the server fault and a fault risk;
and under the condition of meeting the preset upgrading condition, acquiring firmware according to the firmware version for solving the server fault in the upgrading decision information to upgrade the server.
2. The method for evaluating and processing the error report of the server as claimed in claim 1, wherein the fault report information includes server information, fault component, error code, and fault log content.
3. The method for evaluating and processing the error report of the server as claimed in claim 1, wherein the firmware defect database stores firmware defect cases, and the content of the firmware defect cases includes firmware version, defect information of firmware, defect risk level and corresponding version firmware for solving the defect;
the defect information of the firmware comprises: defective parts, error codes, and defect descriptions.
4. The method as claimed in claim 1, wherein the matching of the fault reporting information of the server with the firmware defect cases in the firmware defect database comprises:
and matching the firmware defect case corresponding to the fault error reporting information in the firmware defect database according to the fault component and the error code in the fault error reporting information.
5. The method as claimed in claim 1, wherein the step of counting the matching degree between the fault reporting information of the server and the matched firmware defect cases comprises:
analyzing the fault log content in the fault error reporting information and collecting fault keywords describing the fault from the fault log content;
collecting defect keywords for describing defects from the defect description of the firmware defect cases matched with the fault error reporting information;
and comparing the fault keywords with the defect keywords to obtain the matching degree of the fault keywords and the defect keywords as the matching degree of the server fault and the firmware defect case.
6. The method for evaluating and processing the fault report of the server as claimed in claim 3, wherein the fault risk level in the firmware fault case matched with the fault report information of the server is used as the fault risk of the server fault, and the fault risk level includes a high level, a middle level and a low level.
7. The method for evaluating and processing the error report of the server according to claim 1, wherein the obtaining the firmware according to the firmware version for solving the server failure in the upgrade decision information to perform the server upgrade when the preset upgrade condition is satisfied comprises:
judging whether a target server sending out fault error reporting information is idle and obtaining upgrading permission, if so, obtaining a firmware version for solving the fault of the target server in upgrading decision information as a target firmware;
inquiring whether target firmware exists in a cloud firmware library;
if yes, downloading the target firmware into the target server and upgrading;
and otherwise, recording the missing target firmware and sending the target firmware to a server administrator and a cloud firmware library administrator through a preset contact way.
8. The method as claimed in claim 1, wherein after upgrading the firmware of the server according to the failure reporting information of the server, it is verified whether the server still generates the same failure reporting error of the server, and if so, the server feeds back the second manual processing information.
9. A server firmware risk assessment and upgrade system, comprising: the fault uploading module uploads fault reporting information to the fault matching module when the server has fault reporting;
the fault matching module matches the firmware defect cases in the firmware defect database according to the fault reporting information of the server;
the judging module is used for counting and judging whether the matching degree between the fault error reporting information of the server and the matched firmware defect case is greater than a set threshold value or not;
the feedback module generates upgrading decision information when the judging module judges that the matching degree is greater than the set threshold value, and feeds back first manual processing information when the judging module judges that the matching degree is less than the set threshold value;
the decision module is used for providing upgrading permission for the server by an administrator;
and the upgrading module is used for acquiring the target firmware from the cloud firmware library according to the upgrading decision information to upgrade the target server when the server acquires the upgrading permission and is idle.
10. A storage medium for implementing the method for evaluating and processing the error report of the server, wherein the storage medium for implementing the method for evaluating and processing the error report of the server stores at least one instruction, reads and executes the instruction to implement the method for evaluating and processing the error report of the server according to any one of claims 1 to 8.
CN202111273872.1A 2021-10-29 2021-10-29 Server error reporting evaluation and processing method, system and storage medium Withdrawn CN113961387A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202111273872.1A CN113961387A (en) 2021-10-29 2021-10-29 Server error reporting evaluation and processing method, system and storage medium

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202111273872.1A CN113961387A (en) 2021-10-29 2021-10-29 Server error reporting evaluation and processing method, system and storage medium

Publications (1)

Publication Number Publication Date
CN113961387A true CN113961387A (en) 2022-01-21

Family

ID=79468404

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202111273872.1A Withdrawn CN113961387A (en) 2021-10-29 2021-10-29 Server error reporting evaluation and processing method, system and storage medium

Country Status (1)

Country Link
CN (1) CN113961387A (en)

Similar Documents

Publication Publication Date Title
US9871815B2 (en) Method and system for automated computer vulnerability tracking
US8291382B2 (en) Maintenance assessment management
US20220138041A1 (en) Techniques for identifying and remediating operational vulnerabilities
CN107533504A (en) Anomaly analysis for software distribution
CN107678936B (en) Business system pre-inspection method, server and computer readable storage medium
CN105580032A (en) Method and system for reducing instability when upgrading software
CN109165170B (en) Method and system for automatic request test
US20190087179A1 (en) System and method for predicting defects in a computer program
US11544052B2 (en) Tenant declarative deployments with release staggering
US8086909B1 (en) Automatic core file upload
CN108776643A (en) A kind of object code merging control method and system based on Version Control flow
US8327189B1 (en) Diagnosing an incident on a computer system using a diagnostics analyzer database
WO2020091592A1 (en) A self-learning method and system for automatically performing application packaging and deployment for a hosting environment
CN111273932B (en) Component refreshing method, system and computer readable storage medium
CN113238864A (en) Python-based MongoDB cluster deployment method and system
US7716137B2 (en) System and method for automatically tracking and enabling the operation of a product
CN113806160B (en) Method, device, equipment and storage medium for monitoring configuration file
US20050033866A1 (en) Managed support service for electronic devices
CN113961387A (en) Server error reporting evaluation and processing method, system and storage medium
CN116383090A (en) Automatic testing method and platform for kylin system migration tool
US10310840B2 (en) Computer system, method of managing transmission of software with computer system, program therefor, and recording medium
US8423831B2 (en) System and method for performing auditing and correction
CN116028077A (en) Application installation method based on mobile terminal, ecological service system and electronic equipment
CN115269424A (en) Automatic regression testing method, device, equipment and storage medium for production flow
CN106992873B (en) Protection group processing method and device

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
WW01 Invention patent application withdrawn after publication

Application publication date: 20220121

WW01 Invention patent application withdrawn after publication