JPH0944380A - Module management device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To quickly collect and process the log data in a device including plural modules which generate log data respectively. SOLUTION: Log file information including storage destination information in a storage means 10 of log files where log data are stored is set to a storage means 20. Based on information set to this storage means 20, modules 41 to 43 individually write the log data in corresponding log files in the storage means 10 independently of one another by write means 41a to 43a. In response to a read request from a user, a read means 50 acquires storage destination information corresponding to the requested module from the storage means 20 and reads out log data from the log file where the write means of this module writes log data.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to log data collection management, and more particularly to a module management device for managing a plurality of modules by log data.

[0002]

2. Description of the Related Art In a device including a plurality of modules such as a filing server, a module management device that manages log data from these modules and a module based on the log data processes a large amount of log data at high speed. Is required. As an example of such a module management device, there is a logging / data collection control device disclosed in Japanese Patent Publication No. 3-53655.

In this logging / data collection control device,
In order for multiple programs to write the logging data to the log file at high speed, a logging buffer is provided, the logging data is stored once in the queue stack, and the logging data is stored according to the stacking order in the queue stack.
Writing data to log file. Also, the log file is configured as one shared file.

On the other hand, in a filing server or the like, when a failure occurs in the filing server or the like, an operator intervenes to perform processing. However, when the operator processes, an operator who has sufficient experience is required, and there is a difference in the ability of each operator, and sufficient reliability cannot be obtained. As an example of solving such a problem, there is an operation management system of an information processing apparatus disclosed in Japanese Patent Laid-Open No. 6-149623. In this example, an operator's empirical rule is used as a processing condition file and a knowledge base file to collect information regarding the operational management state of the information processing apparatus, and operational management is performed based on that information.

[0005]

[Problems to be Solved by the Invention] However, Japanese Patent Publication No. 3-5
In the logging data collection control device disclosed in Japanese Patent No. 3655, when writing the logging data from the logging buffer to the log file, the logging data is serially written to the log file, which requires a large writing time. Moreover, it is difficult to write logging data at high speed.

Further, since the log file is configured as a shared file, when the client acquires the logging data, it is necessary to acquire all the log data and acquire the necessary logging data from it. Yes, it takes a lot of time for processing and acquisition.

On the other hand, the operation management system of the information processing apparatus disclosed in the above-mentioned Japanese Patent Laid-Open No. 6-149623 uses a processing condition file and a knowledge base file, so that the configuration is complicated, and the module management apparatus and the like have a complicated structure. It is difficult to apply as it is.

The present invention has been made in view of the above points, and an object thereof is to provide a module management device capable of collecting and processing log data at high speed in a device including a plurality of modules each generating log data. And

Another object of the present invention is to provide a module management device which can collect necessary log data from a necessary log file in a short time. Still another object of the present invention is to provide a module management device capable of managing a module based on log data.

[0010]

FIG. 1 is a block diagram showing the principle of the present invention for achieving the above object. In order to solve the above problems, in a module management device of a device including a plurality of modules according to the first aspect of the invention, a storage unit 10 that stores a plurality of log files 11 to 16 and a plurality of modules 41 to 43 are provided. Log file 1 in which log data is stored individually
Storage means 20 for storing log file information including storage destination information in the storage means 10 of 1 to 16, setting means 30 for setting log file information in this storage means, and corresponding to a plurality of modules 41 to 43 A plurality of writing means 41a to 43 for independently writing the log data of the respectively assigned modules to the log file indicated by the storage destination information of the log file information set by the setting means 30.
a and.

According to the second aspect of the invention, the plurality of modules are processes that operate independently of each other, and the plurality of writing means are realized by the same corresponding process, and the read request is made. In response to the request, the storage unit information corresponding to the requested modules 41 to 43 is acquired from the storage unit 20, and the reading unit 50 for reading the log data of the log file corresponding to the acquired storage destination information is further read from the storage unit 10. Have

FIG. 7 is a block diagram showing the principle of the third invention. In the illustrated module management device that manages a plurality of modules based on these log data, a storage unit 100 that stores a plurality of log files and a plurality of modules 131.
Storage means 110 for storing log file information including storage destination information in the storage means 100 for the log files in which log data is individually stored corresponding to Nos. To 133, and setting means for setting the log file information in the storage means 110. 12
0 and a plurality of modules that are provided corresponding to the plurality of modules 131 to 133 and independently write the log data of the respectively assigned modules to the log file indicated by the storage destination information of the log file information set by the setting unit 120. Writing means 131a to 133a, a monitoring means 140 that monitors the content of the log file in the storage means 100 to detect specific condition information, and a processing content corresponding to the condition information corresponding to the plurality of modules 131 to 133. And a processing condition storage unit 160 that stores the following, and a processing unit 150 that refers to the processing condition storage unit 160 and executes the processing content corresponding to the condition information detected by the monitoring unit 140 to the module indicated by the processing content. have.

[0013]

According to the module management apparatus of the first invention, the setting means 30 sets the log file information in the storage means 20 according to the designation from the user. In the log file information, the module name of the module that manages the log data,
The log file name to be stored and the storage destination information of the log file in the storage unit 10 are included. Each of the modules 41 to 43 manages the log files by grouping them according to the log file information preset in the storage means 20, for example, the module 41 manages the log files 11 and 12, and manages the log data. Are independently written in the corresponding log files by the writing means 41a to 43a. Modules 41-43
Log data is written independently to the log file, so parallel processing is possible and log data can be written at high speed.

In the module management device of the second invention, when the reading means 50 reads the log data from the storage means 10, the log files 11 to 16 of the storage means 10 are managed for each module. Log data can be acquired with.

According to the module management apparatus of the third invention, the storage means 110 stores the module name of the module for managing the log data, the log file name to be stored, and the storage location information of the log file in the log file storage means 100. The log file information that includes is set. Each of the modules 131, 132, 133 has writing means 131a, 132a, 133a, respectively, and writes log data in the corresponding log file according to the log file information set in the storage means 110. If a module writes, in its log file, condition information that causes other modules including its own module to perform some processing as log data, the monitoring unit 140 stores the log files 101 to 106 in the storage unit 100. By monitoring the contents, the log file in which the latest condition information is written is detected. At this time, the monitoring unit 140 checks the module managing the log file from the log file information set in the storage unit 110. The processing unit 150 refers to the processing condition storage unit 160, checks the processing condition corresponding to the condition information, and instructs the corresponding module to execute each.

[0016]

DESCRIPTION OF THE PREFERRED EMBODIMENTS First, the outline of the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing the principle configuration of a module management device according to the present invention.

The module management device of the present invention corresponds to the storage means 10 for storing a plurality of log files 11 to 16 in which the log data of the modules 41 to 43 are written and to which log file the log data of the module is written. A storage unit 20 that manages the relationship, a setting unit 30 that sets the corresponding relationship in advance, and a writing unit 41a that writes the log data of the modules 41 to 43 to a log file that has the preset corresponding relationship. ~
43a, and a reading means 50 for reading only log data relating to the module designated by the user. Here, the management module 40 including the storage unit 20, the setting unit 30, and the reading unit 50 includes each module 41.
It constitutes the main module for managing ~ 43.

In the above arrangement, the setting means 30 stores the log file information in accordance with the designation from the user.
Set to. The log file information includes the module name of the module that manages the log data, the log file name of the log file that should store the log data, and the log file indicating which directory of the storage means 10 the log file is in, for example. Contains storage location information. When storing the log data, each of the modules 41 to 43 refers to the log file information set in the storage unit 20, and writes the log data in a predetermined log file by the writing units 41a to 43a according to this information. . Since each module 41, 42, 43 independently writes log data in parallel to the log file managed by each module, the log data can be written at high speed.

Further, when reading the log data, the reading means 50 obtains the storage destination information of the log file managed by the module from the storage means 20 from the module name designated by the user, and the log is stored with the storage destination information. Access the file and read the log data.

FIG. 2 is a block diagram showing a concrete configuration example of the module management device of the present invention. In this figure,
The module management device can be applied to, for example, a filing server system, a print server system, etc. Here, an example of application to the filing server system 60 is shown. The filing server system 60 is connected to a user operation unit 80 that allows the user to make various settings and instruct reading of log data.

The user operation unit 80 corresponds to a client of the server / client model, and the user interface control unit 6 that accepts various processes from now on.
Connected to 1. The user interface control unit 61 is connected to the module management information storage unit 63 and the activation unit 64 via the module management unit 62, and the module management information storage unit 63 and the activation unit 64 include a plurality of functional modules 6.
5a, 65b, ..., 65n. The functional modules 65a, 65b, ..., 65n are respectively write units 66a, 66b, for writing log data.
, 66n, and is connected to the storage medium 70 to write the log data. Also, the user interface control unit 61 and the module management information storage unit 63.
Is connected to a log management unit 67, and the log management unit 67 is connected to the storage medium 70 so as to read log data. The management module 65 including the user interface control 61, the module management unit 62, the module management information storage unit 63, the activation unit 64, and the log management unit 67 is a main module that manages each functional module 65a, 65b ,. Make up the module.

The user interface control unit 61 sets log file information or controls acquisition of log data in accordance with a request from the user operation unit 80. The setting of log file information is stored in the module management information via the module management unit 62. The log management unit 67 acquires the log data. The activation unit 64 is configured to activate the functional modules 65a, 65b, ..., 6 when the system is activated.
Process 5n is activated. The module management unit 62 transfers the data of the module management information storage unit 63 to the user interface control unit 61 or each functional module 65a, 65.
The module information is passed to b, ..., 65n. Each functional module 65a, 65b, ..., 65n
Acquires the log file information of its own storage destination from the module management information storage unit 63, and writes in the write units 66a, 66b,
The log data is written to the log files 71, 72, 73, 74, 75, 76 of the storage medium 70 by the operation system library for each process by 66n. Then, the log management unit 67 responds to the log data acquisition request from the user operation unit 80 to specify the designated functional modules 65a, 65b, ..., 65.
The log data corresponding to n is acquired from the storage medium 70.

FIG. 3 is a diagram showing an example of the data structure of the log file information. As shown, log file information 90
Is the module name 9 of the module that manages the log data.
0a, a log file name 90b of the log file in which the log data should be stored, and a log file storage destination directory 90c indicating a path name of where the log file is stored in the log file storage means 10. There is.

The log file information 90 is for knowing which log file 71 to 76 of the storage medium 70 each functional module 65a, 65b, ... Part 8
A request for setting the log file information 90 is made from 0 to the user interface control unit 61, and the log file information 90 is temporarily set and registered in the module management information storage unit 63 via the module management unit 62. This allows
The log files 71 to 76 are managed in module units,
For example, the log files 71, 72 are grouped into a functional module 65a, and the log files 73, 74, 75
Are also grouped into a functional module 65b and the log file 76 is managed by a functional module 65c.

FIG. 4 is a flowchart showing the contents of the log file information setting process. Upon receiving the log file information setting request from the user operation unit 80, the user interface control unit 61 registers the log file storage destination information in the module management information storage unit 63 through the module management unit 62 for the functional module designated by the user. Yes (step S1). Here, it is checked whether or not the registration is normally performed (step S2), and if the registration is normally performed, the designated functional module is activated (step S3), and the process ends. If the registration is not normally performed in the determination in step S2, the designated function module is not started and the process ends.

FIG. 5 is a flowchart showing the contents of the log data writing process. When the functional modules 65a, 65b, ..., 65n perform log data write processing during system operation, first, the functional modules 65a, 65b ,. The storage destination log file information corresponding to the function module of its own is acquired from (step S11).
The corresponding log file of the storage medium 70 is opened from the acquired storage destination log file information (step S12),
The log data is written to the opened log file (step S13), and when the writing is completed, the corresponding log file is closed (step S14). Each of the functional modules 65a, 65b, ..., 65n can independently read / write the storage destination log file from / to the file by the operation system library. Therefore, the functional modules 65a, 65b ,.
.., 65n can perform log data write processing concurrently in parallel.

FIG. 6 is a flowchart showing the contents of the log data reading process. When it is desired to acquire the log data of each functional module 65a, 65b, ..., 65n from the user operation unit 80, the user interface control unit 61 is requested to acquire the log data. At that time, the module name of the functional module to be acquired is specified. The user interface control unit 61 passes the module name designated by the user to the log management unit 67, and the log management unit 67
Then, the storage location information of the log file corresponding to the specified module name, that is, the storage location directory is searched and acquired from the module management information storage unit 63 (step S21). Next, from the storage destination log file information, a file is opened in the operation system library for the corresponding file (step S22), and it is determined whether or not there is log data in the corresponding file (step S23). If there is log data in the opened log file, the log data is read from the log file (step S24), and the read log data is transferred to the user operation unit 80 (step S25). Then, the corresponding log file is closed (step S2
6). If there is no log data in the corresponding file in the determination of step S23, the process proceeds to step S26 and the corresponding log file is immediately closed.

In this embodiment, each functional module 65a,
Since 65b, ..., 65n are all operated by independent processes, log data can be efficiently written individually to the log file. Even when the user acquires log data, the log file is managed in module units, so internal processing can also acquire log data for each functional module, and log data can be acquired efficiently. be able to.

Next, an outline of a module management device according to another invention will be described. FIG. 7 is a block diagram showing the basic configuration of another module management device according to the present invention.

The module management device of the present invention stores the storage means 100 for storing a plurality of log files 101 to 106 in which the log data is written and which log file the log data is stored in the storage means 100. A storage unit 110 that stores information about the correspondence and a setting unit 120 that presets the correspondence.
And writing means 131a, 132a, 133 for writing the log data in the modules 131, 132, 133 to the log files having a preset correspondence relationship.
a and the log file 1 stored in the storage unit 100
When the contents 01 to 106 are monitored and log data representing condition information that causes another module including the own module to perform some processing is detected, the storage unit 1
A monitoring unit 140 for checking the module using the log file in which the condition information is written from the log file information set to 10, and executing processing corresponding to the condition of the module checked according to the condition information. A processing unit 150 that defines the processing unit 150 and a processing condition corresponding to the condition information, and refers to the processing of the module corresponding to the condition information when the processing unit 150 executes the processing corresponding to the condition information. Condition storage means 160. Here, the management module 130 including the storage unit 110, the setting unit 120, the monitoring unit 140, the processing unit 150, and the processing condition storage unit 160 is a main module that manages each module 131, 132, 133 by log data. .

In the module management device of this configuration, the module name of the module that manages the log data in the storage means 110, the log file name to be stored, and the storage means 1
The log file information including the storage destination information of the log files 101 to 106 in 00 is set. Each of the modules 131, 132 and 133 has a writing means 131.
The log data is written in the corresponding log file according to the log file information set in the storage unit 110 by a, 132a, and 133a.

Here, it is assumed that a module writes, for example, log data of its own failure information in its own log file. The monitoring unit 140 detects the log file in which the latest failure information is written by monitoring the contents of the log files 101 to 106 of the storage unit 100.
At this time, the monitoring unit 140 checks the module managing the log file from the log file information in the storage unit 110, makes an inquiry to the processing condition storage unit 160, and acquires the processing condition corresponding to the failure information regarding the module. Then, the processing unit 150 causes the module to execute the process corresponding to the failure defined in the acquired processing condition.

FIG. 8 is a block diagram showing a concrete configuration example of another module management device. In this figure, the module management device manages log data for each module in a filing server system 170 that provides a filing function, obtains a failure occurrence of the module from the log data, and takes appropriate measures. is there.

To the filing server system 170 is connected a user operation unit 180 for the user to make various settings relating to the management of log data. The user operation unit 180 corresponds to a client of the server / client model, and in the filing server system 170, it is connected to a user interface control unit 171 that receives various processes from the user operation unit 180. The user interface control unit 171 includes a module management information storage unit 173 and a process execution unit 1 via the module management unit 172.
74, and the module management information storage unit 173 and the process execution unit 174 include a plurality of functional modules 175a,
It is connected to 175b and 175c. These functional modules 175a, 175b, 175c have write units 175aa, 175ba, 175ca, respectively, through which the storage medium 19 is written so as to write log data individually.
Connected to 0. A log management unit 176 is connected to the user interface control unit 171 and the module management information storage unit 173, and the log management unit 176 is connected to the storage medium 190 so as to read the log data. Further, the log monitoring unit 177 causes the log files 191, 192, 193, 194, 195, 1 of the storage medium 190 to be recorded.
96 is connected to the storage medium 190 so as to monitor log data at regular intervals, for example. The log monitoring unit 177 is connected to the module management information storage unit 173 so as to refer to the log file information, and is also connected to a process determination unit 178 that notifies the failure information of the module as log data. The processing determination unit 178 provides a processing condition file 179 that acquires a processing condition when notified from the log monitoring unit 177 and a module management unit 172 that notifies what processing is to be performed based on the processing condition. It is connected. The processing condition file 179 is also connected to the module management unit 172 in order to set or change processing conditions. Here, a management module 175 including a user interface control unit 171, a log monitoring unit 177, a processing determination unit 178, a processing condition file 179, a module management unit 172, a module management information storage unit 173, a processing execution unit 174, and a log management unit 176. Shows each functional module 175a according to the log data,
It is a main module that manages 175b and 175c.

Functional modules 175a, 175b, 17
In the filing server system 170, the filing server system 170 includes, for example, a session reception module for receiving a user request from a client and sending a processing command from the content of the request to an attribute and content management unit, and a storage location of a stored object. It can be an attribute and content management module whose main functions are cooperation and file operation, a database module which handles only the attributes of stored objects, and the like. here,
The functional module 175a is a session reception unit, the functional module 175b is an attribute and content management unit, and the functional module 175c is a database unit.

The user interface control unit 171 controls log file information setting or log data acquisition control in accordance with a request from the user operation unit 180. The log file information setting is performed via the module management unit 172 to store module management information. The log management unit 176 acquires the log data. The setting of log file information is performed by each function module 175a, 175b,
This is to set a dedicated log file that the 175c independently manages.

The process execution unit 174 is the module management unit 17
Each functional module 175a, 175 by the instruction from 2
b, 175c start / stop / handling of processing code. The module management unit 172 manages each functional module designated through the user interface control unit 171 or the process determination unit 178. At this time, the module management unit 172 inquires or rewrites the module information in the module management information storage unit 173, or issues an execution command to the process execution unit 174.

Each functional module 175a, 175b, 1
75c is a module management information storage unit 1 when writing log data to a log file managed by itself.
73 to obtain log file information of its own storage destination, and log data is stored in the log file 19 of the storage medium 190.
A file is read / written for each process by the operation system library for 1,192,193,194,195,196. Then, the log management unit 176 acquires log data corresponding to the functional modules 175a, 175b, and 175c specified by the log data acquisition request from the user operation unit 180 from the storage medium 190, and transmits the log data to the user operation unit 180 via the interface control unit 171. Forward.

FIG. 9 is a diagram showing an example of the format of the processing condition file. In this example, the format of the processing condition file 179 is as follows: "module name" of the module that has written the failure information as log data, "error code" that represents the failure information, and a "processing" field that describes the processing target module and processing code. have. The functional modules 175a, 175b, 175
c is "module1", "module"
2 ”and“ module 3 ”. At the time of creating a file, the operator must be previously and which modules can use what processing code and description to know the meaning of the processing code.

According to the illustrated example, at first, a database crash occurs in the function module 175c of the database section (error code is "DB_CR").
USH ") is described.
In this case, the functional modules 175a, 175b, 17
5c is set to the "offline state" to cut processing requests from other clients. Then, to the functional module 175c (module 3), a processing code (scavenge) for instructing restoration work is sent, and after restoration, all the functional modules 175a, 175.
b, 175c are set to the "online state", and the processing for returning to the normal state is described.

Next, regarding the function module 175a of the session reception unit, the processing procedure when an abnormality occurs in the table for managing the session in this function module 175a is described. That is, if an error occurs in the table that manages the session and the failure information is the error code “SESSION_TABLE_CRUSH”, the security state cannot be maintained.
All functional modules 175a, 175b, 175c
Is stopped and the management module 175 is notified to that effect.

Next, the processing procedure of the management module 175 will be described. FIG. 10 is a flowchart showing the processing contents of the management module. In the management module 175, first, the log monitoring unit 177 acquires log file information of each functional module from the module management information storage unit 173, and knows the log file used by each functional module (step S31). Then, the log files are polled in order to monitor these log files, and it is confirmed whether the latest error code is output to each log file (step S32). Here, it is judged whether or not an error code exists (step S33), and if the error code does not exist, the log file is continuously monitored. For example, if the function module 175c outputs a log of the error code, In that case, the log monitoring unit 177 notifies the process determination unit 178 of that fact. Here, the processing determination unit 178 reads the processing condition file 179 and obtains the processing target module and the processing code sent to the module (step S34). The processing determination unit 178 notifies the module management unit 172 of the target module and the processing code (step S35). The module management unit 172 knows the current states of the filing server system 170 and the functional module from the module management information storage unit 173, and instructs the process execution unit 174. The process execution unit 174 communicates the process code to the target module (step S36). Since the received functional module knows the content of the processing code, the processing corresponding to the processing code is performed.

Although the processing is performed in the above-described flow, the management module 175 has no knowledge of the contents of the processing condition file 179, such as the error code and the processing code, and wonders what the functional module is. Do not know. In other words, error codes, processing codes, and managing modules can be added and deleted freely.

Next, an example of setting the processing condition file 179 by the module management unit 172 will be described.
Here, as an example, a setting procedure of the processing condition file 179 at the time of upgrading the function module 175b of the attribute and content management unit will be described.

FIG. 11 is a flow chart illustrating the procedure for setting the processing condition file. First, the function module 175a of the session reception unit is taken offline (step S41), and the function module 17 of the attribute and content management unit is set.
5b is stopped (step S42). Next, the upgraded functional module is installed (step S43), and the module management unit 172 sets the required processing code in the processing condition file 179 (step S43).
44). Then, all the functional modules are brought online (step S45), and this processing ends.

According to the above embodiment, the processing condition file 1
By creating 79 in advance by the operator, necessary processing can be automatically performed when an error occurs. There are various settings for the processing method and level depending on the user who uses the server, and these can be set for each user. There is no need to replace the module to be managed when upgrading the version of the management module 175 because it is independent of the management module 175. In addition, the server can be flexibly constructed even if the type and number of functional modules and processing codes are changed. By monitoring the module by polling the log file, communication for transmitting an error code does not occur between the monitored module and the monitoring module. That is, the present invention can be applied not only to the filing server but also to an application system that functions with a plurality of modules. And, there is an advantage that the platform on which the management module is mounted is not selected.

In the above description, the filing server system is taken as an example, but the present invention is not limited to this. For example, it can be applied to any device having a plurality of functional modules. Also, as an example of the execution of the function module corresponding to the error code as the value to be set in the processing condition file, setting a certain condition code causes the log data output by a certain function module to be different. It can also be a trigger for causing the functional module to execute some function. This makes it possible to transmit some execution instruction to another function module through the management module including the log monitoring unit in a configuration in which there is no communication means between the function modules.

[0048]

As described above, according to the present invention, the log file name and the storage destination information for each module can be set and managed in the server system from the user side, and each module in the server system can be managed in the server system. Acquires the storage location information of the log file corresponding to the request module to the storage means, and enables the writing means to write the log data to the storage location log file. Each module operates in an independent process and is specified in advance. Efficiently write the log data to each log file created, and when the user requests to get the log data, the data can be acquired in module units.
As a result, each module in the server can access the log file for each module, so there is no need to wait in the log data writing process, and writing can be performed efficiently, and the log file is managed for each module. Therefore, the acquisition processing speed of log data can be improved.

In addition to the module group that constitutes the server, a management module for monitoring these is added,
If an error occurs in one of the modules that make up these servers, the log file set for each of these modules will log an error code indicating the nature of the failure, and the management module will log these log files. By always polling, it is possible to monitor whether a failure has occurred. Furthermore, processing condition storage means is provided which describes what kind of processing is to be performed at which error. As a result, the error code is read from the log record logged when a failure occurs from a certain module, the process that matches the error code is searched from the processing condition storage means, and the module group that manages this process is searched. Since it is possible to provide a recovery function that can be executed against it, it is possible to guarantee stable operation as a server system, reduce operator labor costs, shorten abnormal processing time, and force other modules to operate. Since it can be stopped, it is possible to suppress the occurrence of secondary abnormalities and reduce the overhead of error processing. Further, since the monitoring device has no concern about the contents of the error code written in the log file set for each module and the processing code corresponding to the error code, no overhead occurs when the modules to be configured are reinstalled.

[Brief description of drawings]

FIG. 1 is a block diagram showing a principle configuration of a module management device according to the present invention.

FIG. 2 is a block diagram showing a specific configuration example of a module management device of the present invention.

FIG. 3 is a diagram showing an example of a data structure of log file information.

FIG. 4 is a flowchart showing the contents of a log file information setting process.

FIG. 5 is a flowchart showing the contents of a log data write process.

FIG. 6 is a flowchart showing the contents of a log data read process.

FIG. 7 is a block diagram showing a principle configuration of another module management device according to the present invention.

FIG. 8 is a block diagram showing a specific configuration example of another module management device.

FIG. 9 is a diagram showing an example of a format of a processing condition file.

FIG. 10 is a flowchart showing the processing contents of a management module.

FIG. 11 is a flowchart illustrating a procedure for setting a processing condition file.

[Explanation of symbols]

 11-16 Log File 10 Storage Means 20 Storage Means 30 Setting Means 40 Management Modules 41-43 Modules 41a-43a Writing Means 50 Reading Means 101-106 Log Files 100 Storage Means 110 Storage Means 120 Setting Means 130 Management Modules 131, 132 , 133 modules 131a, 132a, 133a writing means 140 monitoring means 150 processing means 160 processing condition storage means

Claims (3)

[Claims] 1. A module management device for a device including a plurality of modules, comprising: a storage unit that stores a plurality of log files; and a log file that individually stores log data corresponding to the plurality of modules. Storage means for storing log file information including storage destination information in the storage means; setting means for setting the log file information in the storage means; and a module provided corresponding to the plurality of modules, each of the assigned modules. A module management device comprising: a plurality of writing units that independently write log data to a log file indicated by the storage location information of the log file information set by the setting unit. 2. The plurality of modules are processes that operate independently of each other, and the plurality of writing units are realized by the same corresponding process, and are requested in response to a read request. The storage device further includes a reading unit that acquires the storage destination information corresponding to the module from the storage unit and that reads log data of a log file corresponding to the storage destination information acquired from the storage unit. 1. The module management device according to 1. 3. A module management device that manages a plurality of modules based on these log data, and storage means for storing a plurality of log files, and log data individually stored corresponding to the plurality of modules. Storage means for storing log file information including storage destination information in the storage means of the log file, setting means for setting the log file information in the storage means, provided corresponding to the plurality of modules, A plurality of writing means for independently writing the log data of each assigned module to the log file indicated by the storage destination information of the log file information set by the setting means, and monitoring the contents of the log file in the storage means And a monitoring unit for detecting specific condition information, and a process corresponding to the condition information corresponding to the plurality of modules. A processing condition storage unit that stores the content, and a processing unit that refers to the processing condition storage unit and executes the processing content corresponding to the condition information detected by the monitoring unit to the module indicated by the processing content. A module management device having.