CN107179959A - A kind of method, device and a kind of storage medium for predicting computer operation troubles - Google Patents
A kind of method, device and a kind of storage medium for predicting computer operation troubles Download PDFInfo
- Publication number
- CN107179959A CN107179959A CN201710358828.8A CN201710358828A CN107179959A CN 107179959 A CN107179959 A CN 107179959A CN 201710358828 A CN201710358828 A CN 201710358828A CN 107179959 A CN107179959 A CN 107179959A
- Authority
- CN
- China
- Prior art keywords
- log
- problem log
- subset
- logs
- fault
- 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
- 238000000034 method Methods 0.000 title claims abstract description 49
- 238000012423 maintenance Methods 0.000 claims abstract description 22
- 238000000605 extraction Methods 0.000 claims description 11
- 230000010354 integration Effects 0.000 claims description 7
- 238000013507 mapping Methods 0.000 claims description 5
- 238000012163 sequencing technique Methods 0.000 claims 1
- 239000000284 extract Substances 0.000 abstract description 2
- 238000010586 diagram Methods 0.000 description 12
- 238000013024 troubleshooting Methods 0.000 description 3
- YTPUIQCGRWDPTM-UHFFFAOYSA-N 2-acetyloxybenzoic acid;5-(2-methylpropyl)-5-prop-2-enyl-1,3-diazinane-2,4,6-trione;1,3,7-trimethylpurine-2,6-dione Chemical compound CC(=O)OC1=CC=CC=C1C(O)=O.CN1C(=O)N(C)C(=O)C2=C1N=CN2C.CC(C)CC1(CC=C)C(=O)NC(=O)NC1=O YTPUIQCGRWDPTM-UHFFFAOYSA-N 0.000 description 1
- 206010033799 Paralysis Diseases 0.000 description 1
- 238000009825 accumulation Methods 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 238000007726 management method Methods 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 238000012544 monitoring process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000013021 overheating Methods 0.000 description 1
- 238000012805 post-processing Methods 0.000 description 1
- 238000010187 selection method Methods 0.000 description 1
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/0751—Error or fault detection not based on redundancy
-
- 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/0793—Remedial or corrective actions
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Quality & Reliability (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application discloses a kind of method, device and a kind of storage medium for predicting computer operation troubles in fact, and methods described includes：Extract daily record collection the problem of in running log, form problem log subset；The failure table of comparisons is searched according to problem log subset；If storage problem daily record subset and corresponding operation troubles problem log subset in look-up table, operation troubles is exported, or export the corresponding relation of problem log subset and operation troubles.The failure that computer is likely to occur can quickly be determined using the method, point out staff to safeguard computer interdependent node, it is to avoid the problem of computer utilization ratio that posterior maintenance is caused is not high.Meanwhile, it is not high to the skill requirement of field personnel using the method, reduce the cost of computer maintenance.
Description
Technical Field
The application relates to the technical field of computer management, in particular to a method for predicting computer operation faults; the present invention also relates to an apparatus for predicting an operational failure of a computer and a storage medium storing program code for implementing the foregoing method.
Background
When the computer runs, the log recording system can record the operation information and the corresponding occurrence time information to form a running log of the computer, thereby realizing the monitoring and recording of the running state of the system. When a hardware fault or a software fault occurs in the computer, technicians can reversely determine fault nodes and fault time of the computer according to own experience by reversely reading the running logs.
However, the manual reading of the operation log of the system for fault judgment requires a large amount of manual investment, and the efficiency is low; the computer is already in a paralyzed or low-efficiency running state, and the working efficiency of the computer is influenced. Moreover, analyzing computer failures through the running logs requires a significant amount of experience accumulation by the technicians; especially, some system faults can be obtained only by analyzing the logical relationship and the recording sequence among a plurality of running logs, and under the condition that a technician is not familiar with the system architecture of the computer, the running fault of the computer is difficult to analyze through the running logs.
Therefore, how to avoid manually reading the operation log of the computer system and perform troubleshooting is a problem to be considered by those skilled in the art.
Disclosure of Invention
The application provides a method and a device for predicting computer operation faults and a storage medium, and aims to solve the problems that the working efficiency of a computer is influenced and the requirements on the experience of technical personnel are high due to the fact that the existing post-processing mode of manually reading system operation logs is adopted.
The embodiment of the invention provides a method for predicting computer operation faults, which comprises the following steps:
extracting problem logs in the running logs to form a problem log subset;
searching a fault comparison table according to the problem log subset;
and if the problem log subsets and the corresponding operation fault log subsets are stored in the fault comparison table, outputting the operation fault, or outputting the corresponding relation between the problem log subsets and the operation fault.
Optionally, the problem log in the running log is extracted to form a problem log subset according to the following steps:
determining the priority of each problem log;
and selecting the problem logs with the priority greater than or equal to the first set priority to form a problem log subset.
Optionally, arranging the problem logs according to the generation time to form a problem log subset; or,
and arranging the problem logs according to the priority size to form a problem log subset.
Optionally, extracting the problem logs in the running log and forming the problem log subset includes:
determining the priority of each problem log;
selecting the problem log with the highest priority as a main problem log;
selecting a secondary problem log from the rest problem logs according to the main problem log;
and forming the main problem log and the secondary problem log into a problem log subset.
Optionally, according to the following steps, selecting a secondary problem log from the remaining problem logs according to the primary problem log:
selecting a predetermined number of problem logs before and/or after the generation of the main problem log as secondary problem logs, or selecting the problem logs before and/or within a predetermined time after the generation of the main problem log as secondary problem logs;
forming a problem log subset by the main problem log and the secondary problem log according to the following steps;
optionally, before selecting the secondary problem log from the remaining problem logs, the method further includes:
deleting the problem logs with the priority lower than the second preset priority;
selecting a secondary problem log from the remaining problem logs according to the following steps:
selecting a secondary issue log among the remaining issue logs having priority levels greater than and equal to the second preset priority level.
Optionally, the method further includes:
if the fault comparison table does not comprise the operation fault corresponding to the problem log subset, temporarily storing the problem log subset;
and after the operation fault corresponding to the problem log subset appears and is solved, inputting the operation fault into a fault comparison table, and establishing and storing a corresponding relation between the problem log subset and the operation fault.
Optionally, the method further includes:
if the fault comparison table does not comprise the operation fault corresponding to the problem log subset, the problem log subset is sent to the remote maintenance platform;
receiving a problem log subset returned by the remote maintenance platform and a corresponding relation of a corresponding operation fault, and storing the corresponding relation to a fault comparison table;
and/or, an output operational failure.
The embodiment of the invention also provides a device for predicting the computer operation fault, which comprises the following steps:
the storage module is used for storing a fault comparison table;
the problem log extraction module is used for extracting the problem logs in the running logs and forming a problem log subset;
the fault searching module is used for searching a fault comparison table according to the problem log subset;
and the output module is used for outputting the operation fault or outputting the corresponding relation between the problem log subset and the operation fault sum when the fault comparison table comprises the operation fault corresponding to the problem log subset.
Optionally, the problem log extracting module includes:
the priority determining unit is used for determining the priority of each problem log;
and the problem log selection unit is used for selecting the problem log sub-integrated problem log subset with the priority greater than or equal to the first set priority.
Optionally, the problem log selecting unit arranges and extracts the problem logs according to the generation time to form a problem log subset; or,
and arranging the problem logs according to the priority size to form a problem log subset.
Optionally, the problem log extracting module includes:
the priority determining unit is used for determining the priority of each problem log;
the main problem log selection unit is used for selecting the problem log with the highest priority as the main problem log;
a secondary problem log selecting unit for selecting a secondary problem log from the remaining problem logs;
and the problem log subset integration unit is used for forming the main problem log and the secondary problem log into a problem log subset.
Optionally, the secondary problem log selecting unit selects the secondary problem log according to the following steps:
selecting a predetermined number of problem logs before and/or after the generation of the main problem log as secondary problem logs, or selecting the problem logs before and/or within a predetermined time after the generation of the main problem log as secondary problem logs;
and the problem log subset integration unit sorts the main problem log and the secondary problem log according to the generation time to form a problem log subset.
Optionally, the apparatus further comprises:
the problem log deleting unit is used for deleting the problem logs with the priority lower than or equal to a second preset priority;
the sub-problem log selecting unit selects a sub-problem log among remaining problem logs having priorities higher than and equal to a second preset priority.
Optionally, the apparatus further comprises:
the temporary storage module is used for temporarily storing the problem log subsets without corresponding operation faults into a fault comparison table;
the input module is used for receiving operation faults corresponding to the problem temporary storage problem log subset;
and the mapping establishing module is used for establishing the corresponding relation between the temporary storage problem log subset and the operation fault and storing the temporary storage problem log subset and the operation fault into the fault comparison table.
Optionally, the apparatus further comprises:
the sending module is used for sending the problem log subset to the remote maintenance platform when the fault comparison table does not comprise the operation fault corresponding to the problem log subset;
and the receiving module is used for receiving the corresponding relation between the problem log subset fed back by the remote maintenance platform and the corresponding operation fault and storing the corresponding relation to the fault comparison table.
An embodiment of the present invention further provides a storage medium, in which a program code implementing the method for predicting an operational failure of a computer is stored.
According to the method for predicting the computer operation fault, provided by the embodiment of the invention, the operation fault comparison table is searched according to the selected problem log subset, so that the possible fault of the computer can be quickly determined, then, the staff is prompted to maintain the computer relative node, and the problem of low utilization efficiency of the computer caused by post-maintenance is avoided. Meanwhile, by adopting the method, the experience requirement on field workers is not high, and the maintenance cost of the computer is reduced.
Drawings
To more clearly illustrate the background art or the technical solutions of the present invention, the following brief description of the drawings incorporated in the prior art or the detailed description of the present invention; it should be apparent that the following drawings in conjunction with the detailed description are only for the convenience of understanding the embodiments of the present invention, and other drawings can be obtained by those skilled in the art without creative efforts;
FIG. 1 is a flow chart of a method of predicting an operational failure of a computer;
FIG. 2 is a flow chart of forming a subset of a problem log;
FIG. 3 is another flow chart for forming a subset of the issue log; (ii) a
FIG. 4 is a flow chart of another method of predicting an operational failure of a computer;
FIG. 5 is a flow chart of another method of predicting an operational failure of a computer;
FIG. 6 is a block diagram of an apparatus for predicting an operational failure of a computer;
FIG. 7 is a block diagram of an issue log extraction module;
FIG. 8 is a block diagram of another problem log extraction module;
FIG. 9 is a block diagram of another apparatus for predicting an operational failure of a computer;
FIG. 10 is a block diagram of another apparatus for predicting an operational failure of a computer;
in fig. 6-10: 11-storage module, 12-problem log extraction module, 121-priority determination unit, 122-problem log selection unit, 123-main problem log selection unit, 124-secondary problem log selection unit, 125-problem log subset integration unit, 13-fault finding module, 14-output module, 15-temporary storage module, 16-input module, 17-mapping establishment module, 18-sending module and 19-receiving module.
Detailed Description
In order to make those skilled in the art better understand the technical solution of the present invention, the technical solution in the embodiment of the present invention will be clearly and completely described below with reference to the drawings in the embodiment of the present invention, and it is obvious that the described embodiment is only a part of the embodiment of the present invention, and 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 invention.
The invention provides a method for predicting the operation failure of a computer, which can be applied to a commercial server system or a household computer, and is particularly suitable for the commercial server system requiring a large amount of daily maintenance.
FIG. 1 is a flowchart of a method for predicting an operational failure of a computer according to an embodiment. As shown in fig. 1, a method for predicting an operational failure of a computer according to an embodiment of the present invention includes the following steps.
S101, extracting problem logs in the running logs to form a problem log subset;
when the computer runs, the log recording system can record various user operations generated in the running process, various events generated in the system, hardware, software and other problems of the computer and generate the running log. The problem logs comprise event logs and problem logs generated in the running process, and all the logs comprise attribute information such as occurrence time and priority.
In order to realize the detection of the computer operation fault, the computer firstly obtains the operation logs output by the log recording system, screens problem logs according to the attribute information of each log in the operation logs, and screens at least one problem log according to a preset rule to form a problem log subset.
S102: and searching a fault comparison table according to the problem log subset, and judging whether an operation fault corresponding to the problem log subset exists or not.
The fault comparison table is a lookup table for recording the corresponding relation between the problem log subset and the operation fault; before the method is implemented, a user or an equipment provider can input the corresponding relation between the problem logs accumulated by using experience and the operation faults into a fault comparison table to be used as a reference for automatically judging the possible operation faults by a computer.
Of course, the selection method of the problem log subset in the failure lookup table should be the same as the method of forming the problem log subset in S101.
S103: and if the operation fault corresponding to the problem log subset exists, outputting the operation fault or outputting the corresponding relation between the problem log subset and the operation fault.
If the operation fault table comprises the problem log subsets and the problem log subsets have corresponding operation fault problems, the computer outputs corresponding operation faults or outputs the corresponding relation between the problem log subsets and the operation faults so that operating personnel can know the possible operation faults and maintain the corresponding nodes of the computer, and the problem of downtime or reduced operation performance caused by the operation faults is avoided.
In practical application, the corresponding relationship between the operation fault, the problem log subset and the operation fault may be soft copy output or hard copy output. In a larger server system, the operation fault can be sent to the mobile device in data communication with the server system, so that a worker carries the mobile device to correspondingly search for a corresponding operation fault node.
There are several possible methods for forming the problem log subset in S101 according to the operating characteristics of the computer.
First method
FIG. 2 is a flow diagram of an embodiment to form a subset of an issue log; as shown in fig. 2, the first method includes the following steps.
S201, determining the priority of each problem log.
As previously stated, when the logging system generates logs, the logging system may give different priorities to different problem logs; the problem logs with higher priority indicate that the computer has higher probability of failure, and the problem logs with lower priority indicate that the computer has lower probability of failure.
For example, in A practical storage system, the logging system would generate S, A, B, C four problem logs of different priorities, and the priority of the problem logs would be S-A-B-C in descending order.
S202: and selecting the problem logs with the priority greater than or equal to the first set priority to form a problem log subset.
In practical application, the low priority of the problem log represents that the corresponding problem log feedback computer has low possibility of generating operation faults, and the corresponding operation faults can be regular faults generated by frequent maintenance nodes of workers. In order to avoid the running fault corresponding to the problem logs with lower priority output by the computer and the redundancy of generated data, the problem logs with lower priority can be deleted according to a preset rule, and only the problem logs with higher priority are selected from the problem logs. For example, in the aforementioned application, only the problem log sub-integrated problem log subsets with priorities S and a may be selected.
In addition, possible composition scenarios for the problem log subsets are described herein. The problem log subset is a set selected from the problem logs according to a preset rule. The number of the problem logs in the problem log subset is determined according to a preset rule, the number of the problem logs can be one or more, and the number of the problem logs can be determined according to experience of users and equipment suppliers. For example, some problem logs with priority S can reflect the problems of insufficient storage space, overheating of a CPU, or insufficient memory space of a computer, and the like, individually, so that the number of problem logs in the problem log subset may be only one; in other cases, the computer may be determined to have an operational failure based on a plurality of subsets of the problem logs, so that the number of problem logs in the subset of the problem logs may be set to be a plurality.
In the case that there are a plurality of problem logs in the problem log subset, the problem logs may be arranged in different ways to represent different operation faults, and therefore, the arrangement order of the problem logs in the problem log subset needs to be determined.
In practical application, the problem logs in the problem log subset can be sorted according to the generation time or the priority; in the case of multiple problem logs of equal priority, the problem logs in the problem log subset may also be sorted first according to priority and then according to generation time, or sorted first according to generation time and then according to priority.
Second method
FIG. 3 is a flow diagram of an embodiment to provide for forming a subset of an issue log; as shown in fig. 3, the first method includes the following steps.
S301: the priority of each problem log is determined.
This step is similar to the step S201, and reference may be made to the step S201, which will not be described herein.
S302: selecting the problem log with the highest priority as a main problem log;
s303: selecting a secondary problem log from the rest problem logs according to the main problem log;
s304: and forming the main problem log and the secondary problem log into a problem log subset.
When a problem occurs in a certain node of the computer, the problem log with higher priority is more likely to be generated. Thus, in some cases, the problem log with the highest priority may be selected as the representative for determining that the computer may have an operational failure, and the problem log with the highest secondary priority may be used as the primary problem log.
The node problem represented by the primary problem log may be caused by a node failure represented by another secondary priority problem log, or the node problem represented by the primary problem log may cause a node failure represented by another secondary priority problem log to occur, and then cause an actual failure. Therefore, the main problem log can be used as a basic node to select the secondary problem log, and the main problem log and the secondary problem log are sub-integrated into the problem log subset.
In actual operation, the secondary problem log may be a problem log already generated before the generation of the main problem log, or may be a problem log after the generation of the main problem log; in some cases, the secondary issue log may also include both issue logs that have been generated prior to the generation of the primary issue log and issue logs that were generated after the occurrence of the primary issue log.
Specifically, the selection strategy of the secondary problem log may be several: (1) the preset number of the secondary problem logs can be set, and the secondary problem logs before the generation of the main problem log or the secondary problem logs after the generation of the main problem log are selected according to the time sequence; (2) a time zone may be set, and a problem log within a preset time before or after the generation of the main problem log may be selected as the sub problem log.
Similar to the first method, the primary issue log and the secondary issue log may be arranged in order of priority to form a subset of issue logs, or may be arranged in order of generation time to form a subset of issue logs.
Similarly, in the second method, some problem logs with lower priorities may enter the problem log subset to cause information redundancy, and therefore, when selecting a secondary problem log according to the primary problem log, the problem log with a priority lower than a second preset priority, for example, the problem log with the priority C, may be deleted.
For ease of understanding, a specific method of forming the problem log is illustrated here.
(1) Suppose there are S, A, B, C problem logs in the problem log set, the problem logs are arranged in the order of A-B-A-C-S-B-C.
Firstly, the computer determines and selects the problem log with the priority S as the main problem log according to the priority of each problem log.
Secondly, the computer selects the first three problem logs as secondary problem logs according to the S problem log. In one case, three problem logs B-A-C arranged in sequence before S can be selected according to the time sequence; in another case, the problem log with the priority of C may be deleted, and the three problem logs A-B-A arranged in sequence before S may be selected as the secondary problem log. Similarly, the selection of the post-S problem log may follow the steps described above.
(2) Suppose that the problem log set includes only A, B problem logs, the problem logs are arranged in the order B-B-B-A-A-B-B.
Firstly, the computer considers the priority of each problem log and determines and selects the problem log with the priority of A as the main problem log.
Because the problem log set comprises two problem logs with the priority of A, two problem log subsets are generated, and if the number of the preset secondary problem logs is 6 and the main problem log occurs three before and after, the problem log subsets are B-B-B-A-A-B-B and B-B-A-A-B-B-B.
In practical application, some operation faults which do not correspond to the problem log subsets in the fault comparison table may occur in the system, and the problem logs are only manually analyzed when the operation faults actually occur in the column, so that the fault occurrence position is determined.
In order to avoid that a large amount of time is consumed to analyze the problem logs when the faults occur again, when the operation faults corresponding to the problem log subsets do not exist in the fault comparison table, the method for predicting the operation faults of the computer provided by the embodiment of the invention can be further expanded.
FIG. 4 is a flowchart of another method for predicting an operational failure of a computer according to an embodiment. In another embodiment, as shown in FIG. 4, the method further comprises steps S104 and S105 in addition to steps S101-S103.
S104: and temporarily storing the problem log subset.
S105: and after the operation fault corresponding to the problem log subset appears and is solved, inputting the operation fault into a fault comparison table, and storing the corresponding relation between the problem log subset and the operation fault.
After the working personnel read the reverse-push working log and determine and solve the system operation fault, the corresponding relation between the problem log subset and the operation fault can be input into a fault comparison table for subsequent automatic check.
FIG. 4 is a flowchart of another method for predicting an operational failure of a computer according to an embodiment. In the computer with remote maintenance function, the troubleshooting of rare faults can also be carried out by the remote maintenance platform, so that the method comprises steps S106-S108 in addition to steps S101-S103.
S106: sending the problem log subset to a remote maintenance platform;
s107: receiving a corresponding relation between a problem log subset returned by the remote maintenance platform and a corresponding operation fault, and storing the corresponding relation to a fault comparison table;
s108: and outputting the operation fault.
When the running fault corresponding to the problem log subset does not exist in the running fault comparison table stored in the body computer, the computer sends the problem log subset to the remote maintenance platform;
similar problems with other computers may already be stored in the remote maintenance platform, or a professional may reason about a subset of the rare problem logs to determine operational failure.
After the remote maintenance platform determines the operation fault corresponding to the rare problem log subset, the corresponding relation between the rare problem log subset and the operation fault is fed back to the computer, and the computer stores the corresponding relation to the operation fault comparison table; and if the corresponding operation fault does not occur, the computer can also output the operation fault and prompt the staff to perform corresponding maintenance.
Besides providing the device for predicting the computer operation failure, the embodiment of the invention also provides a device for realizing the method. Fig. 6 is a block diagram of an apparatus for predicting an operational failure of a computer according to an embodiment, and as shown in fig. 6, the apparatus for predicting an operational failure of a computer includes a storage module 11, a problem log extraction module 12, a troubleshooting module 13, and an output module 14.
Wherein: the storage module 11 is used for storing a fault comparison table; the problem log extracting module 12 is configured to extract a problem log in the running log to form a problem log subset; the fault searching module 13 is used for searching a fault comparison table according to the problem log subset; and the output module 14 is configured to output the operation fault or output a corresponding relationship between the subset of the problem logs and the sum of the operation faults when the fault comparison table includes the operation faults corresponding to the subset of the problem logs.
Fig. 7 is a block diagram of the problem log extraction module 12 according to an embodiment. As shown in fig. 7, in one implementation, the issue log extraction module 12 may include a priority determination unit 121 and an issue log selection unit 122. The priority determining unit 121 is configured to determine the priority of each problem log; the problem log selection unit 122 is configured to select a problem log subset of which the priority is greater than or equal to a first set priority.
The problem log selecting unit 122 may arrange the problem logs according to the generation time and form the problem log subsets, or may arrange the problem logs according to the priority and form the problem log subsets.
Fig. 8 is a block diagram of another problem log extraction module 12 according to an embodiment. In another implementation, as shown in FIG. 8, the issue log extraction module 12 may include a priority determination unit 121, a primary issue log selection unit 123, a secondary issue log selection unit 124, and an issue log subset integration unit 125. Wherein: the priority determining unit 121 is configured to determine the priority of each problem log; the main issue log selecting unit 123 is configured to select an issue log with the highest priority as a main issue log; the secondary problem log selecting unit 124 is configured to select a secondary problem log among the remaining problem logs; the issue log subset integration unit 125 is configured to sub-integrate the primary issue log and the secondary issue log into an issue log subset.
Specifically, the secondary problem log selecting unit 124 may select the secondary problem log according to the following steps: a predetermined number of problem logs before and/or after the generation of the main problem log are selected as the sub problem logs, or problem logs before and/or within a predetermined time after the generation of the main problem log are selected as the sub problem logs.
In correspondence thereto, the problem log subset integrating unit 125 may sort the primary problem logs and the secondary problem logs into the problem log subsets by the generation time.
In addition, the device provided by the embodiment of the invention also comprises a problem log deleting unit; the problem log deleting unit is used for deleting the problem logs with the priority lower than or equal to a second preset priority; accordingly, the sub problem log selecting unit 124 selects a sub problem log among the remaining problem logs having priorities higher than and equal to the second preset priority.
FIG. 9 is a block diagram of another apparatus for predicting an operational failure of a computer according to an embodiment. As shown in fig. 9, in a specific application of the present invention, the apparatus for predicting computer operation failure further includes a temporary storage module 15, an input module 16, and a mapping establishing module 17. Wherein: the temporary storage module 15 is configured to temporarily store the problem log subsets that do not have corresponding operation faults into the fault comparison table; the input module 16 is used for receiving operation faults corresponding to the problem temporary storage problem log subset;
the mapping establishing module 17 is configured to establish a correspondence between the temporary storage problem log subset and the operation fault, and store the correspondence into the fault comparison table.
Fig. 10 is a block diagram of another apparatus for predicting an operational failure of a computer. In another embodiment of the present invention, as shown in fig. 10, the apparatus for predicting computer operation failure further comprises a sending module 18 and a receiving module 19. The sending module 18 is configured to send the problem log subset to the remote maintenance platform when the fault comparison table does not include the operation fault corresponding to the problem log subset; and the receiving module 19 is configured to receive a corresponding relationship between the problem log subset fed back by the remote maintenance platform and the corresponding operation fault, and store the corresponding relationship in a fault comparison table.
In addition to providing the foregoing method and apparatus, an embodiment of the present invention further provides a storage medium, where a code implementing the foregoing method for predicting an operating failure of a computer is stored in the storage medium. In a specific application, the storage medium includes but is not limited to an optical disc, a removable hard disk, a flash disk and other bulk storage media, and the package may also be a storage medium such as a cloud storage server and capable of distributing program codes or program fragments.
The method, the apparatus and a storage medium for predicting computer operation failure in the embodiments of the present invention are described in detail above. The principle and the implementation manner of the present invention are explained in this section by using specific embodiments, and the above description of the embodiments is only used to help understanding the core idea of the present invention, and all other embodiments obtained by those skilled in the art without creative efforts will fall within the protection scope of the present invention without departing from the principle of the present invention.
Claims (10)
1. A method of predicting an operational failure of a computer, comprising:
extracting problem logs in the running logs and forming a problem log subset;
searching a fault comparison table according to the problem log subset;
and if the problem log subsets and the corresponding operation faults are stored in the fault comparison table, outputting the operation faults or outputting the corresponding relation between the problem log subsets and the operation faults.
2. The method of predicting an operational failure of a computer according to claim 1,
extracting the problem logs in the running log and forming the problem log subset comprise:
determining the priority of each problem log;
selecting the problem log with the highest priority as a main problem log;
selecting a secondary problem log from the rest problem logs according to the main problem log;
and forming the main problem log and the secondary problem log into a problem log subset.
3. The method of predicting an operational failure of a computer according to claim 2,
selecting a secondary problem log from the remaining problem logs according to the primary problem log according to the following steps:
a predetermined number of problem logs before and/or after the generation of the primary problem log are selected as the secondary problem logs, or,
selecting the problem logs before and/or within a preset time after the generation of the main problem log as secondary problem logs;
forming a problem log subset by the main problem log and the secondary problem log according to the following steps;
and sequencing the main problem log and the secondary problem log according to the generation time to form a problem log subset.
4. A method of predicting an operational failure of a computer according to any one of claims 1-3, further comprising:
if the fault comparison table does not comprise the operation fault corresponding to the problem log subset, temporarily storing the problem log subset;
and after the operation fault corresponding to the problem log subset appears and is solved, inputting the operation fault into a fault comparison table, and storing the corresponding relation between the problem log subset and the operation fault.
5. A method of predicting an operational failure of a computer according to any one of claims 1-3, further comprising:
if the fault comparison table does not comprise the operation fault corresponding to the problem log subset, the problem log subset is sent to the remote maintenance platform;
receiving a problem log subset returned by the remote maintenance platform and a corresponding relation of a corresponding operation fault, and storing the corresponding relation to a fault comparison table;
and/or, an output operational failure.
6. An apparatus for predicting operational failure of a computer, comprising:
the storage module (11) is used for storing a fault comparison table;
the problem log extraction module (12) is used for extracting the problem logs in the running logs and forming a problem log subset;
the fault searching module (13) is used for searching a fault comparison table according to the problem log subset;
and the output module (14) is used for outputting the operation fault or outputting the corresponding relation between the problem log subset and the operation fault sum when the fault comparison table comprises the operation fault corresponding to the problem log subset.
7. The apparatus of claim 6, wherein the problem log extraction module (12) comprises:
a priority determination unit (121) for determining the priority of each problem log;
a main issue log selection unit (123) for selecting an issue log with the highest priority as a main issue log;
a secondary problem log selecting unit (124) for selecting a secondary problem log among the remaining problem logs;
and the problem log subset integration unit (125) is used for forming the main problem log and the secondary problem log into a problem log subset.
8. The apparatus of claim 7,
a sub-problem log selection unit (124) selects a sub-problem log according to the following steps:
a predetermined number of problem logs before and/or after the generation of the primary problem log are selected as the secondary problem logs, or,
selecting the problem logs before and/or within a preset time after the generation of the main problem log as secondary problem logs;
the problem log subset integration unit (125) sorts the main problem log and the sub problem log according to the generation time to form a problem log subset.
9. The apparatus of any of claims 6-8, further comprising:
the temporary storage module (15) is used for temporarily storing the problem log subsets which do not have corresponding operation faults into the fault comparison table;
the input module (16) is used for receiving the operation fault corresponding to the temporary stored problem log subset;
and the mapping establishing module (17) is used for storing the corresponding relation between the temporary stored problem log subset and the operation fault into the fault comparison table.
10. A storage medium, characterized by: comprising program code for implementing a method for predicting an operational failure of a computer according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710358828.8A CN107179959A (en) | 2017-05-19 | 2017-05-19 | A kind of method, device and a kind of storage medium for predicting computer operation troubles |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201710358828.8A CN107179959A (en) | 2017-05-19 | 2017-05-19 | A kind of method, device and a kind of storage medium for predicting computer operation troubles |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN107179959A true CN107179959A (en) | 2017-09-19 |
Family
ID=59832243
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201710358828.8A Pending CN107179959A (en) | 2017-05-19 | 2017-05-19 | A kind of method, device and a kind of storage medium for predicting computer operation troubles |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107179959A (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485860A (en) * | 2021-06-28 | 2021-10-08 | 北京达佳互联信息技术有限公司 | Data processing method, data processing equipment, storage medium and fault positioning system |
| CN115509797A (en) * | 2022-11-22 | 2022-12-23 | 北京优特捷信息技术有限公司 | Method, device, equipment and medium for determining fault category |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060010352A1 (en) * | 2004-07-06 | 2006-01-12 | Intel Corporation | System and method to detect errors and predict potential failures |
| CN101833497A (en) * | 2010-03-30 | 2010-09-15 | 山东高效能服务器和存储研究院 | Computer fault management system based on expert system method |
| CN102129397A (en) * | 2010-12-29 | 2011-07-20 | 深圳市永达电子股份有限公司 | Method and system for predicating self-adaptive disk array failure |
| CN103596208A (en) * | 2013-11-15 | 2014-02-19 | 大唐移动通信设备有限公司 | Method and system for judging fault of network element |
| CN103778044A (en) * | 2012-10-23 | 2014-05-07 | 伊姆西公司 | Method and device for diagnosing system faults |
-
2017
- 2017-05-19 CN CN201710358828.8A patent/CN107179959A/en active Pending
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20060010352A1 (en) * | 2004-07-06 | 2006-01-12 | Intel Corporation | System and method to detect errors and predict potential failures |
| CN101833497A (en) * | 2010-03-30 | 2010-09-15 | 山东高效能服务器和存储研究院 | Computer fault management system based on expert system method |
| CN102129397A (en) * | 2010-12-29 | 2011-07-20 | 深圳市永达电子股份有限公司 | Method and system for predicating self-adaptive disk array failure |
| CN103778044A (en) * | 2012-10-23 | 2014-05-07 | 伊姆西公司 | Method and device for diagnosing system faults |
| CN103596208A (en) * | 2013-11-15 | 2014-02-19 | 大唐移动通信设备有限公司 | Method and system for judging fault of network element |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113485860A (en) * | 2021-06-28 | 2021-10-08 | 北京达佳互联信息技术有限公司 | Data processing method, data processing equipment, storage medium and fault positioning system |
| CN113485860B (en) * | 2021-06-28 | 2024-03-01 | 北京达佳互联信息技术有限公司 | Data processing method, device, storage medium and fault positioning system |
| CN115509797A (en) * | 2022-11-22 | 2022-12-23 | 北京优特捷信息技术有限公司 | Method, device, equipment and medium for determining fault category |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US11275641B2 (en) | Automatic correlation of dynamic system events within computing devices | |
| CN1669001B (en) | Method and device for business continuation policy for server consolidation environment | |
| CN109669844B (en) | Equipment fault processing method, device, equipment and storage medium | |
| CN104137085A (en) | Method for controlling access of clients to a service in a cluster environment | |
| WO2020000817A1 (en) | Method, system, and apparatus for allocating hard disks belonging to placement group, and storage medium | |
| CN103646104A (en) | Hard real-time fault diagnosis method and system | |
| CN111262822B (en) | File storage method, device, block link point and system | |
| CN102799485A (en) | Historical data migration method and device | |
| CN114746843A (en) | Memory health tracking for differentiated data recovery configurations | |
| US8090994B2 (en) | System, method, and computer readable media for identifying a log file record in a log file | |
| CN107179959A (en) | A kind of method, device and a kind of storage medium for predicting computer operation troubles | |
| CN112311902A (en) | File sending method and device based on micro-service | |
| CN115756955A (en) | Data backup and data recovery method and device and computer equipment | |
| CN105550071A (en) | System file upgrading and detecting method and communication device | |
| CN105573872A (en) | Hardware maintenance method and device of data storage system | |
| CN107729182B (en) | Data storage and access method and device | |
| CN109271270A (en) | The troubleshooting methodology, system and relevant apparatus of bottom hardware in storage system | |
| CN108173711A (en) | Enterprises system data exchange monitoring method | |
| CN106708445A (en) | Link selection method and device | |
| CN115130130B (en) | Network disk file unlocking method and device, network disk and storage medium | |
| CN116760745A (en) | Network exception handling method, apparatus, device, storage medium and program product | |
| CN107196799B (en) | Data processing platform redundant server backup and switching operation control method | |
| CN111324513B (en) | Monitoring management method and system for artificial intelligence development platform | |
| CN105790975A (en) | Service processing operation execution method and device | |
| CN114356051A (en) | Research on electronic information storage technology based on cloud computing and cloud server |
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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20170919 |
|
| RJ01 | Rejection of invention patent application after publication |