JP2000112788A - Supporting method for fault recovery, device therefor and machine readable storage medium recording program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to present a user with an appropriate method coping with a fundamental fault cause when the fault occurs to a computer. SOLUTION: A program 1 stores an identifier allocated to processing unit in a state monitoring table 2 and stores resource information which indicates a resource used by the processing unit in a resource data base 3 every time it executes the processing unit (for example, a function or the like). When a fault detection part 5 detects a fault occurrence, a fault cause examination part 6 finds the processing unit that becomes a fundamental fault cause on the basis of the state monitoring table 2, the resource data base 3 and contents of a document data base 4 and, furthermore, acquires a coping method stored in the document data base 4 in accordance with the processing unit. A document edit display mechanism part 8 edits the coping method and a memory image which a resource sample mechanism part 7 samples and displays them to a display device 9.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for presenting an appropriate countermeasure to a user when a failure occurs in a computer. Technology for presenting appropriate countermeasures to the elderly.

[0002]

2. Description of the Related Art When a failure occurs during the operation of a program such as an operating system or an application program, conventionally, generally, a user compares a failure message output from the system with a document such as a manual to determine the type of the failure. I was trying to find the cause and get a solution. However, since this method is manually performed, there is a problem that much time is required to obtain a coping method, and there is a problem that a burden is imposed on a user.

In order to solve such a problem,
A table in which a failure message, a coping method, and a description are stored in association with each other is provided, and when a failure message is output, the table is searched using the failure message as a key, and a coping method corresponding to the failure message is provided. A technique has been proposed for presenting an explanation to a user (for example, Japanese Patent Application Laid-Open No. 3-75844). According to this conventional technique, when a failure occurs, a coping method is automatically presented, so that a coping method can be obtained in a short time without putting a burden on the user.

[0004]

However, the above-mentioned prior art has the following problems. That is,
Since only the coping method registered in the table in response to the failure message output by the system is presented to the user, there is a problem that an appropriate coping method may not be presented to the user.

[0005] For example, if a failure occurs when a certain program accesses a specific file, the system outputs a failure message indicating that the specific file is invalid. However, the root cause of the failure in this case is not that the specific file is fraudulent, but what caused the specific file to be fraudulent. For example, if another program has created an error in the specific file before the error message was output, or if a user's operation error has caused the error, these are the root causes of the error. Become. As described above, when the failure cause indicated by the failure message is different from the fundamental failure cause, the conventional technology does not provide a method of coping with the fundamental failure cause,
There was a problem that the presented coping method may not be appropriate.

An object of the present invention is to provide a method for coping with a fundamental cause of a failure.

[0007]

In order to achieve the above object, the failure recovery assisting method of the present invention associates an identifier of a processing unit of a program with the possibility that the processing unit may cause a fundamental failure. A document database is provided in which basic information indicating whether or not there is an error and a method for coping with the case where the processing unit is a fundamental cause of failure are provided. While storing the identifier of the processing unit in the status monitoring table in the order of execution,
Storing resource information indicating resources used in the processing unit in a resource database in association with the processing unit identifier stored in the status monitoring table;
Upon detecting a failure, a processing unit that causes a fundamental failure is obtained based on the contents of the status monitoring table, the contents of the resource database, and the contents of the document database, and the obtained processing unit that causes the fundamental failure is obtained. And outputting the coping method stored in the document database corresponding to the identifier of the document.

[0008] As a preferred apparatus for carrying out the above-mentioned failure recovery assistance method, the failure recovery assistance apparatus of the present invention associates an identifier of a processing unit of a program with the possibility that the processing unit may cause a fundamental failure. A document database storing basic information indicating whether or not there is a processing unit and a countermeasure in the case where the processing unit is considered to be a fundamental cause of failure. A status monitoring table in which unit identifiers are stored in the order of execution, and each time a program processing unit is executed, resource information indicating resources used in the processing unit is associated with the identifier stored in the status monitoring table. A resource database stored when the failure is detected, the contents of the status monitoring table, the contents of the resource database, and the document. A failure cause investigating unit for obtaining a processing unit that causes a fundamental failure based on the contents of the database, and the document corresponding to the identifier of the processing unit that causes a fundamental failure found by the failure cause investigating unit A document editing and displaying mechanism for outputting a coping method stored in the database.

In this configuration, when a failure is detected, the failure cause investigating unit performs a process for causing a fundamental failure based on the contents of the status monitoring table, the contents of the resource database and the contents of the document database. The unit is obtained, and the document editing and displaying mechanism outputs the coping method stored in the document database corresponding to the identifier of the processing unit which is the fundamental cause of the failure obtained by the failure cause investigating unit.

[0010]

Embodiments of the present invention will now be described in detail with reference to the drawings.

FIG. 1 is a block diagram showing a configuration example of an embodiment of the present invention. A program 1 such as an operating system or an application program, a state monitoring table 2, a resource database 3, a document database 4, a fault Detection unit 5 and failure cause investigation unit 6
, A resource collection mechanism unit 7, a document editing and display mechanism unit 8, and a display unit 9.

Different status identifiers are assigned to the processing units of the program 1 respectively. Here, the processing unit is a processing unit determined by a program creator. For example, a function can be a single processing unit, or a function is divided into a plurality of parts, and each part is set as a processing unit. You can also. At the time of execution, the program 1 has a function of storing the status identifier of the processing unit in the status monitoring table 2 in the order of execution each time the processing unit is executed, and also stores resource information indicating the resources used in the processing unit. It has a function of storing in the resource database 3 in association with the status identifier stored in the status monitoring table 2.

The document database 4 includes, in association with an identifier of a processing unit of a program, basic information indicating whether or not the processing unit is likely to cause a fundamental failure; And the countermeasures to be taken in the event of a serious failure.

When the fault detecting unit 5 detects a fault, the fault cause investigating unit 6 determines a processing unit which has caused a root fault based on the contents of the status monitoring table 2, the resource database 3 and the document database 4. It has a function to be sought and a function to retrieve a coping method corresponding to a fundamental cause of failure from the document database 4.

The resource collecting mechanism 7 has a function of collecting a memory image of a memory address accessed by a processing unit that has caused a fundamental failure.

The document editing and displaying mechanism unit 8 has a function of coping with the problem extracted from the document database 4 by the failure cause investigating unit 6 and a function of editing the memory image collected by the resource collecting mechanism unit 7 and displaying it on the display unit 9. .

Next, the operation of this embodiment will be described.

Each time a program 1 is executed, the program 1 writes a status identifier assigned to the process unit into the status monitoring table 2 in the order of execution, and stores information indicating resources used in the process unit in the status monitor table 2. Monitoring table 2
Is stored in the resource database 3 in association with the status identifier stored in the resource database 3.

When the failure detecting unit 5 detects the occurrence of a failure, the failure cause investigating unit 6 searches for a processing unit that has caused a fundamental failure based on the contents of the state monitoring table 2, the resource database 3, and the document database 4. (FIG. 2, S1).

The processing in S1 will be described in detail as follows.

When the failure detecting unit 5 detects a failure, the failure cause investigating unit 6 retrieves resource information from the last entry of the status monitoring table 2 (the entry in which the status identifier is stored last) and the relevant entry of the resource database 3. Is obtained and used as a key (FIG. 3, S11).

Thereafter, the failure cause investigating unit 6 goes back one entry in the status monitoring table 2 and refers to the contents of the entry of the resource database 3 related to the entry (S12, S14). Then, it is determined whether the resource indicated by the key resource information (related resource) exists in the resources indicated by the resource information stored in this entry (S15).

If there is no related resource (S15: NO), the process returns to S12. On the other hand, if there is a related resource (YES in S15), the document database 4 is searched using the status identifier stored in the entry of the status monitoring table 2 of interest as a key, and The root information corresponding to the identifier refers to. If the root information indicates that there is a possibility of causing a root failure, the processing unit corresponding to the state identifier is determined to be the root cause, and the state identifier is determined. Hold and S14
The resource information stored in the entry referred to in (1) is held (S16).

After that, if the resource information in the entry of the resource database 3 referred to in S14 includes resource information that is not included in the resource information currently set as a key, the failure cause investigating unit 6 checks the resource information. Is added to the key (S17), and the process returns to S12.
If no such resource information exists, the process returns to S12 without performing the key addition process. When the above-described processing is performed on all entries of the state monitoring table 2 (YES in S13), the failure cause investigation unit 6 sets
Is performed.

In S2, the failure cause investigating unit 6 searches the document database 4 based on the state identifier of the processing unit which has become the fundamental cause of failure found in S1 to obtain a coping method. Fault information combining the coping method and the resource information of the processing unit is generated and passed to the document editing and displaying mechanism unit 8. In the process of S2, the failure cause investigation unit 6 also performs a process of passing the resource information of the processing unit to the resource collection mechanism unit 7.

When the resource information is passed, the resource collection mechanism section 7 collects a memory image based on the resource information, and
The collected memory image is transferred to the document editing and displaying mechanism 8 (S3).

The document editing and displaying mechanism 8 edits the fault information from the fault cause investigating unit 6 and the memory image from the resource collecting mechanism 7 and displays them on the display unit 9 (S4, S5).

As described above, according to the present embodiment, it is possible to present a user with a method of coping with a fundamental cause of a failure, so that appropriate measures can be taken.

FIG. 4 is a block diagram of a first example of the present embodiment, which comprises a computer 10, a magnetic disk device 20, a display unit 30, and a recording medium 40.

The computer 10 includes an application program 11, an operating system 12, a status monitoring table 13, a resource database 14,
It includes a failure cause investigation unit 15, a resource collection mechanism unit 16, and a document editing and displaying function unit 17.

The magnetic disk device 20 includes a document database 21 and a resource storage area 22.

Different state identifiers are assigned to the respective processing units of the application program 11 and the operating system 12. Here, the processing unit is a processing unit determined by a program creator. For example, a function can be a single processing unit, or a function is divided into a plurality of parts, and each part is set as a processing unit. You can also. The application program 11 and the operating system 12 have a function of storing the status identifier of the processing unit in the status monitoring table 13 in the order of execution each time the processing unit is executed at the time of execution. Resource information
It has a function of storing in the resource database 14 in association with the status identifier stored in the status monitoring table 13.

As shown in FIG. 5, the state monitoring table 13 registers a state identifier, a first pointer indicating the storage order of the state identifier, and a second pointer indicating related resource information.

As shown in FIG. 5, the resource database 14 stores a state identifier and resource information. The resource information indicates the used resources, such as the file names of the used files (environment setting files, temporary files, etc.), input / output values exchanged with other processing units and users, and addresses of used memories. And so on.

The document database 21 stores state identifiers of processing units of all programs executed on the computer 10 and stores the following information in association with each state identifier.

Basic information: information indicating whether there is a possibility of causing a fundamental failure.・ Response method: This is set only when the basic information indicates that there is a possibility of causing a fundamental failure. “Check that the input value of variable a is correct.”, “ Please check the following information, which indicates a solution such as “α, β”. Component type: Information indicating the type of component, such as the z function of the application program and the y function in the kernel. Outline of operation contents: This shows an outline of operation contents such as "input variable a and output to file x" and "execute zzz by input from user".

The fault cause investigating unit 15 is provided with a fault detecting unit 12a.
When a failure is detected, a function for searching for a processing unit that has caused a fundamental failure based on the contents of the state monitoring table 13, the resource database 14, and the document database 21 and a state identifier of the searched processing unit are provided. It has a function of acquiring a coping method stored in the document database 21 and the like.

The resource collecting mechanism 16 has a function of collecting a memory image of a memory address accessed by a processing unit that has caused a fundamental failure.

The document editing and displaying mechanism 17 has a function of coping with the problem extracted from the document database 21 by the fault cause investigating unit 15 and a function of editing the memory image collected by the resource collecting mechanism 16 and displaying the edited image on the display 30. .

The recording medium 40 is a disk, a semiconductor memory, or another recording medium, in which a program for causing the computer 10 to function as a failure recovery auxiliary device is recorded. The program stored in the recording medium 40 is read by the computer 10, and by controlling the operation of the computer 10, the failure cause investigation unit 15 and the resource collection mechanism unit 1 are stored on the computer 10.
6. Implement the document editing and displaying mechanism 17.

Next, the operation of this embodiment will be described by taking as an example a case where two application programs AP01 and AP02 are operating. The application program AP01 searches the database DB01 at the request of the user and outputs the result to a file F01.
It is assumed that the contents of the database DB01 are updated by the user's input.

Now, the application program AP01
It is assumed that the failure detection unit 12a detects a failure during the execution of.
At this time, the last entry of the state monitoring table 13 includes
As shown in FIG. 5, the application program AP0
The status identifier “AP01: 002” of the processing unit being executed in one processing unit is stored. In the resource database 14, resource information “file name; DB0” indicating the resource used by the processing unit is stored.
1, entry; XXX "is stored in association with the last entry of the status monitoring table 13.

The failure cause investigating unit 15 includes a failure detecting unit 12a.
Detects the failure, as shown in the flowchart of FIG. 3, the resource information “file name; DB01, entry; X” stored in the entry of the resource database 14 associated with the last entry of the status monitoring table 13
XX "as a key (S11).

Thereafter, the failure cause investigating unit 15 goes up one entry of the status monitoring table 13 and refers to the entry of the resource database 14 related to the entry (S12, S14). Now, for example, in the entry of the resource database 14 referred to, "file name; DB01, entry; XXX, input value;
If "YYY" is stored, the result of the determination in S15 is YES, and the failure cause investigating unit 15 performs the processing in S16.

In S16, the failure cause investigating unit 15
The document database 21 is searched using the status identifier “AP02: 006” stored in the entry (the second entry from the end) of the status monitoring table 13 that is currently focused on, and the status identifier “AP02: 006”
Get the basic information corresponding to. Now, assuming that the root information indicates that there is a possibility of causing a root failure, the failure cause investigating unit 15 sets the state identifier “AP02:
006 "as the status identifier of the processing unit causing the fundamental failure, and the resource information" file name; DB01, entry; X "in the entry referred to in S14.
XX, input value; YYY "is held in combination with the above-mentioned state identifier.

Thereafter, the failure cause investigating unit 15 adds the resource information “file name; DB01, entry; currently used as a key to the resource information“ file name; DB01, entry; XXX, input value; YYY ”held in S16. XX
Resource information "input value; YYY" not included in "X"
Exists, so that “file name; DB01, entry; XXX, input value; YYY” obtained by adding “input value; YYY” to the current key is used as a new key (S17), and then the entry in the state monitoring table 13 is made. One up, 3 from the end
Attention is paid to the third entry (S12). Thereafter, the failure cause investigating unit 15 refers to the entry of the resource database 14 corresponding to the third entry from the end (S14).

Now, for example, in the entry of the resource database 14 referred to, “output value: Y
Assuming that “YY, input value 000” is stored, S1
Since the determination result of step 5 is YES, the failure cause investigation unit 15
Performs the processing of S16.

The failure cause investigating unit 15 stores the status identifier “AP01: 00” stored in the entry (the third entry from the end) of the status monitoring table 13 that is currently focused on.
The document database 21 is searched using “1” as a key, and the basic information corresponding to the state identifier “AP01: 001” is obtained. Now, assuming that the root information does not indicate that there is a possibility of causing a root failure, the failure cause investigating unit 15 performs the processing of S17 without holding the state identifier “AP01: 001”. . When the above processing is performed up to the last entry of the status monitoring table 13, the failure cause investigating unit 15 performs the processing of S2 shown in the flowchart of FIG.

In S2, the document database 21 is searched using the status identifier held in S16 as a key, and the coping method stored corresponding to the status identifier is obtained. Thereafter, fault information is generated by combining the acquired coping method and the resource information held in S16, and the fault information is passed to the document edit display function unit 17 and the resource information is passed to the resource collection mechanism unit 16. S16
When there are a plurality of sets of the state identifier and the resource information held in the above, the above-described processing may be performed on each of the sets, or the above-described processing may be performed only on the last held set. You may do it. In other words, since the processing unit of the state identifier included in the last held pair is highly likely to be a fundamental failure cause, the above-described processing is performed only on the last held pair. Is also good. When a plurality of sets are held, fault information is created for each set, and the priority of each fault information (the highest priority is given to the fault information for the last held set, (Lowest priority of the failure information for the held set) may be incorporated.

When the resource information is transferred, the resource collection mechanism 16 collects a memory image indicated by the memory address included in the resource information, stores the memory image in the resource storage area 22, and transfers the memory image to the document edit display function unit 17 ( S3).

Thus, the document editing and displaying function unit 17 edits the fault information from the fault cause investigating unit 15 and the memory image from the resource collecting mechanism unit 16 and displays them on the display unit 30 (S4, S5).

FIG. 6 is a block diagram of the second embodiment.
It includes a computer 10a, a magnetic disk device 20a, a display unit 30, and a recording medium 40a.

FIG. 4 shows that the computer 10a of this embodiment does not have the status monitoring table 13 and the resource database 14, and that it has the fault cause investigating unit 15a instead of the fault cause investigating unit 15. Computer 1
0.

The failure cause investigating unit 15 a
a if a failure is detected,
It has a function of performing the processing of S1 and S2 shown in FIG. 2 even when restarting a. The other components 11, 12, 12a, 16, 17 of the computer 10a have the same functions as the components denoted by the same reference numerals in the first embodiment.

Further, the magnetic disk drive 20a of this embodiment
Is different from the magnetic disk device 20 in the first embodiment shown in FIG. 4 in that a state monitoring table 13 and a resource database 14 are provided in addition to the document database 21 and the resource storage area 22. .

The recording medium 40a is a disk, a semiconductor memory, or another recording medium, and stores a program for causing the computer 10a to function as a failure recovery auxiliary device. The program recorded on the recording medium 40a is read by the computer 10a,
By controlling the operation of the computer 10a, a failure cause investigating unit 15a, a resource collecting mechanism unit 16, and a document editing and displaying mechanism unit 17 are realized on the computer 10a.

Next, the operation of this embodiment will be described.

The application program 11 and the operating system 12 store the status identifier in the status monitoring table 13 and execute the resource database 14 every time the processing unit is executed, similarly to the above-described embodiment.
To store resource information. Even if a failure that makes the operation impossible occurs in the computer 10a,
The status monitoring table 13 and the resource database 14
Since it is provided in the nonvolatile magnetic disk device 20a, its contents are preserved.

When the computer 10a is restarted, the failure cause investigating unit 15a performs the processing of S1 and S2 shown in the flowchart of FIG. 2, the resource collecting mechanism unit 16 performs the processing of S3, and the document editing and displaying unit 17 Perform the processing of S4 and S5. Thereby, the failure information including the coping method and the memory image are displayed on the display unit 30.

As described above, in the present embodiment, the status monitoring table 13 and the resource database 14 are provided on the nonvolatile magnetic disk device 20a. Even in the case of occurrence, when the computer 10a is restarted, it is possible to present a countermeasure for the fundamental cause of the failure. In the present embodiment, the status monitoring table 13 and the resource database 14 are provided on the magnetic disk device 20a, but they may be provided on another nonvolatile storage device.

[0061]

As described above, according to the present invention, when a failure is detected, a processing unit which causes a fundamental failure is obtained based on the contents of the status monitoring table, the resource database and the document database. Since the countermeasures stored in the document database are presented to the user in accordance with the identifier of the processing unit that causes the trouble, the user is basically required to provide the user with an appropriate countermeasure corresponding to the cause of the trouble. There is an effect that can be presented.

Further, according to the present invention, since the status monitoring table and the resource database are configured on a non-volatile storage device, even if a failure occurs that disables the operation of the computer, the status monitoring table and the resource database can be restarted. Thus, there is an effect that it is possible to present a method of coping with a fundamental failure cause.

[Brief description of the drawings]

FIG. 1 is a block diagram illustrating a configuration example of an embodiment of the present invention.

FIG. 2 is a flowchart showing a processing example of the embodiment and first and second examples.

FIG. 3 is a flowchart showing a detailed processing example of S1 shown in FIG. 2;

FIG. 4 is a block diagram of a first example of the embodiment of the present invention.

FIG. 5 is a diagram showing an example of contents of a state monitoring table 13 and a resource database 14.

FIG. 6 is a block diagram of a second example of the embodiment of the present invention.

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 ... Program 2 ... State monitoring table 3 ... Resource database 4 ... Document database 5 ... Failure detection part 6 ... Failure cause investigation part 7 ... Resource collection mechanism part 8 ... Document edit display mechanism part 9 ... Display part 10, 10a ... Computer 11 ... Application program 12 ... Operating system 12a ... Fault detection unit 13 ... Status monitoring table 14 ... Resource database 15, 15a ... Fault cause investigation unit 16 ... Resource collection mechanism unit 17 ... Document editing and display mechanism unit 20, 20a ... Magnetic disk unit 21 ... Document database 22 ... Resource storage area 30 ... Display unit 40,40a ... Recording medium

Claims (9)

[Claims] 1. Basic information indicating whether there is a possibility that a processing unit may be a fundamental cause of failure in association with an identifier of a processing unit of a program. A document database is provided in which a method for dealing with the processing is stored, and each time a processing unit of the program is executed, the identifier of the processing unit is stored in the state monitoring table in the order of execution, and the processing unit is stored in the processing unit. Resource information indicating the used resources in the resource database in association with the identifier of the processing unit stored in the status monitoring table, and when a failure is detected, the content of the status monitoring table, the content of the resource database, and the document Based on the contents of the database, a processing unit that causes a fundamental failure is determined, and the determined fundamental failure source is determined. A method for assisting recovery from a failure, comprising: outputting a countermeasure stored in the document database corresponding to an identifier of a processing unit that causes the failure. 2. A resource stored in the resource database starting from resource information of a processing unit executed at the time of detecting the failure among resource information stored in the resource database when the failure is detected. By tracing the information in the reverse order of the storage order, the basic information in the document database, which is a processing unit using the resource indicated by the resource information as the starting point, causes a fundamental failure By searching for a processing unit indicating that there is a possibility, and then tracing the resource information stored in the resource database in the reverse order to the storage order, using the resource information of the searched processing unit as a starting point, A processing unit using the resource indicated by the resource information as the starting point, and By repeatedly performing a process of searching for a processing unit indicating that the fundamental information in the document database is likely to be a fundamental cause of failure, and using the found processing unit as a processing unit of a fundamental failure cause The method according to claim 1, wherein 3. The state monitoring table and the resource database are provided on a non-volatile storage device, and are executed when the computer restarts and when the failure is detected in the resource information stored in the resource database. By tracing the resource information stored in the resource database in the order opposite to the storage order with the resource information of the processing unit as a starting point, the resource indicated by the resource information as the starting point is used. Search for a processing unit that indicates that the underlying information in the document database may be a fundamental cause of failure, and then using the resource information of the found processing unit as a starting point Trace the resource information stored in the resource database in the reverse order of the storage order This is a processing unit that uses the resource indicated by the resource information as the starting point, and indicates that the fundamental information in the document database may cause a fundamental failure 3. The failure recovery assisting method according to claim 2, wherein a process of searching for the error is repeatedly performed, and the searched processing unit is set as a processing unit of a fundamental failure cause. 4. The method according to claim 1, wherein the resource information includes a memory address accessed by the processing unit, and outputs a coping method stored in the document database corresponding to an identifier of the processing unit causing a fundamental failure. 3. The method according to claim 2, further comprising outputting a memory image indicated by a memory address included in the resource information of the processing unit that causes the fundamental failure.
Disaster recovery assistance method described. 5. Basic information indicating whether there is a possibility that the processing unit may cause a fundamental failure in association with an identifier of the processing unit of the program, and determining whether the processing unit is a fundamental failure cause. A document database in which a coping method in the event of being executed is stored, a status monitoring table in which an identifier of the processing unit is stored in an execution order each time a processing unit of the program is executed, and a processing unit of the program is executed. Each time the resource is detected, resource information indicating resources used in the processing unit is stored in association with the identifier stored in the status monitoring table. When a failure is detected, the content of the status monitoring table, Failure to find a processing unit that causes a fundamental failure based on the contents of the resource database and the contents of the document database A harm cause investigating unit; and a document editing and displaying mechanism unit for outputting a coping method stored in the document database in accordance with an identifier of a processing unit that is a fundamental cause of failure obtained by the trouble cause investigating unit. A failure recovery assist device characterized by the following. 6. The resource management system according to claim 1, wherein when the failure is detected, the resource information of the processing unit executed at the time of detecting the failure among the resource information stored in the resource database is used as a starting point. By tracing the resource information stored in the database in the reverse order of the storage order, the processing unit using the resource indicated by the resource information as the starting point and the basic information in the document database are A processing unit indicating that there is a possibility of causing a fundamental failure is searched for, and then, starting from the resource information of the searched processing unit, the resource information stored in the resource database is reversed in the storage order. By using the resource indicated by the resource information set as the starting point. Process of searching for a processing unit that indicates that the basic information in the document database may cause a fundamental failure is repeated. 6. The fault recovery assisting device according to claim 5, wherein the fault recovery assisting device has a configuration as a cause processing unit. 7. The state monitoring table and the resource database are configured on a non-volatile storage device, and the failure cause investigating unit, when the computer is restarted, selects one of the resource information stored in the resource database. Tracing the resource information stored in the resource database in the reverse order of the storage order with the resource information of the processing unit being executed at the time of detecting the failure as a starting point, A processing unit that uses the indicated resource and that indicates that the fundamental information in the document database may cause a fundamental failure is searched for, and then the processing unit of the searched processing unit is searched for. Starting from the resource information, the resource information stored in the resource database is By tracing in the reverse order to the delivery order, it is a processing unit using the resource indicated by the resource information as the starting point, and there is a possibility that the basic information in the document database may be a fundamental cause of failure. 7. The failure recovery assisting device according to claim 6, wherein a process of searching for a processing unit indicating that there is is performed repeatedly, and the searched processing unit is used as a processing unit of a fundamental failure cause. 8. The resource information includes a memory address accessed in a processing unit, and indicates a memory address included in the resource information of the processing unit that is a fundamental cause of failure by the failure cause investigation unit. A resource collection mechanism for collecting a memory image, wherein the document editing and display mechanism includes a coping method stored in the document database corresponding to an identifier of a processing unit that causes a fundamental failure; and the resource collection mechanism. 7. The fault recovery assist device according to claim 6, wherein the fault recovery assist device has a configuration for editing and outputting the memory image collected by the unit. 9. Basic information indicating whether or not the processing unit is likely to cause a fundamental failure in association with an identifier of the processing unit of the program; A document database in which a countermeasure in the case where the program is executed, a status monitoring table in which an identifier of the processing unit is stored in the execution order each time the processing unit of the program is executed, and Each time the computer is provided with a resource database in which resource information indicating resources used in the processing unit is stored in association with the identifier stored in the status monitoring table, as a failure recovery auxiliary device. A machine-readable recording medium on which a program is recorded, the computer comprising: A failure cause investigating unit that determines a processing unit that causes a fundamental failure based on the contents of the file, the contents of the resource database, and the contents of the document database. A machine-readable recording recording a program for recording a program for functioning as a document editing and displaying mechanism for outputting a coping method stored in the document database in accordance with an identifier of a processing unit. Medium.