JP4918696B2 - Server monitoring system and program therefor - Google Patents

Description

  The present invention relates to a multi-server integrated monitoring technology for comprehensively monitoring a plurality of servers using e-mail, and particularly detects a failure of a plurality of servers connected via a network in real time using an existing infrastructure environment. The present invention relates to a comprehensive server monitoring system and a program therefor that can be discovered and recovered at an early stage, and the server self-recovery process associated therewith and remote control from e-mail are combined. .

  Previously, when operating multiple servers, contact with the administrator and failure recovery work when a failure occurred on a holiday or at night could only be handled by a manual operation by a human or a specific operating environment. In the absence of a specific operating environment, it was impossible to respond quickly.

  As a technique for monitoring a server at a remote location, for example, there is one described in Japanese Patent Laid-Open No. 2002-259310 “Server management system and server management method” (Patent Document 1).

  As described in Patent Document 1, it is possible to perform a remote operation from a mobile phone terminal to confirm a failure of a server in a remote location, repair a failure, or set a server, and there is no place or human restriction, The purpose is to provide an easy-to-use and convenient server monitoring system. For this reason, if a failure occurs on a managed server at a remote location, a failure message is sent to the mobile phone terminal by e-mail. The system administrator confirms the content of the failure message in the received e-mail, and enters the URL (Uniform Resource Locator) set for system operation to display the operation menu in HTML format and enter the failure state. The necessary functions are selected accordingly, and server failure recovery is performed.

  Further, as a technique for remotely operating an operation target apparatus in a remote place, there is one described in Japanese Patent Application Laid-Open No. 2004-15193 “Remote operation method and apparatus” (Patent Document 2).

  Patent Document 2 describes a remote operation method in which remote operation is performed by a simple operation, and the remote operation can be performed in a simpler environment without being constrained by an environment such as a computer connected to a network. For this purpose, the remote target device is operated remotely based on the subject of the email and / or the instruction content described in the text. Since e-mail can be sent and received by simple means such as a mobile phone, simple remote operation is possible using e-mail, and there is no need for an environment such as a computer connected to the network. Remote operation is also possible.

JP 2002-259310 A JP 2004-15193 A

  In the conventional server management system, since a failure recovery method based on remote operation is used, human operation is always performed.

  In Patent Document 1, failure messages received by e-mail are operated on an operation menu in HTML format using a portable terminal to recover the failure. However, this method is superior in operability, and more than one menu screen is used. Although it is possible to remotely control the server, it is not possible to remotely control multiple servers at the same time.

  In addition, in the case of the operation menu in the HTML format, it is conceivable that the browser software installed varies depending on the carrier of the mobile terminal, the specifications of the device manufacturer, and the like, so the problem remains whether it can be applied to all existing mobile terminals.

  In addition, what is described in Patent Document 2 is only related to remote operation of a measuring device (operation target device) such as an electron microscope, and is totally technical idea of remote operation for monitoring a failure of a server. As a matter of course, remote control of a plurality of servers is not considered at all.

  Therefore, the object of the present invention is to eliminate the above-mentioned problems of the prior art, reduce the number of human operations by using the existing infrastructure environment, and at the same time, the remote operation to a plurality of servers can be easily performed by mail. A server monitoring system and a program therefor are provided.

In order to achieve the above object, the present invention has the following configuration.
a) In the present invention, in a server monitoring system that monitors a plurality of servers connected to a network, a memory that holds a common table that stores information necessary for server monitoring that is accessible from all of the plurality of servers. Is provided. Further, all of the plurality of servers are provided with self-monitoring means for monitoring the own server with reference to the common table. In addition, one of the plurality of servers is set as a master server, and server monitoring means for monitoring all other servers with reference to the common table is provided in the master server. Then, all of the plurality of servers are comprehensively monitored by combining the monitoring functions of the self-monitoring means and the server monitoring means.

b) When a failure is detected by the self-monitoring means, each of the plurality of servers executes a self-recovery process in accordance with an instruction registered in advance in the common table, and then stores the situation and result in the common table in advance. Send an email to the administrator's email address of the registered administrator terminal, receive the email containing the command sent to each server from the administrator terminal that received the email, and decrypt the command contained in the email It has a mail check processing means for processing and enables remote operation from the administrator terminal.

c) In addition, the mail check processing means describes the monitoring processing contents, password, and one or more monitoring target servers and commands in the subject or text, and addresses one common mail address to the plurality of servers. When a sent mail is received, the contents described in the mail are extracted and decoded using keywords registered in the common table, and the execution or non-execution of the monitoring process is determined based on the decoding result. And means for executing the monitoring process in the case of execution.

d) Further, the plurality of servers have an interrupt function, and the interrupt function gives priority to the instruction from the mail.
e) One of the servers other than the master server is set as the sub-master server. The sub-master server monitors the master server, and if a failure occurs in the master server, the master server Instead, it has means for continuing the monitoring process of other servers.

f) Further, when a failure is detected as a result of monitoring by the self-monitoring means, the failure is made to correspond to a plurality of failure levels according to the failure status or the failure content, and processing is executed with priority assigned to the failure level.
g) In addition, a means for setting the mail transmission destination to which the monitoring result is sent according to the failure level is provided.
h) A program according to the present invention is a program for causing a computer to function as each means in the server monitoring system.

  In the present invention, as described above, self-monitoring means is incorporated in the server to be monitored, and when a failure occurs, self-repair processing can be automatically performed according to the registered settings according to the failure level. It is possible to reduce the operation.

  Also, since it is an operation by mail, the same operation can be performed from any device equipped with e-mail software that can send mail, and multiple instructions can be simultaneously written by writing instructions for each server in the mail text. It is also possible to perform different remote operations on one server.

  When the present invention is applied, a plurality of servers can be comprehensively monitored, and when a failure occurs in the server, the server itself performs self-recovery processing according to the failure level, thereby reducing the time for human operation. It is also possible to prevent operational mistakes.

  Further, when the server itself is in a state where it cannot be monitored by itself, the server monitoring unit of the master server can confirm the state of the server and notify the administrator of the failure to take early action.

  In addition, if the administrator receives a failure notification mail from the server, the server can be remotely operated by e-mail from any terminal as long as it has a function capable of sending mail, and the administrator can quickly As a result, a quick recovery can be achieved.

Hereinafter, an embodiment of the present invention will be described in detail with reference to the drawings.
FIG. 1 is a configuration diagram showing an embodiment of a multiple server integrated monitoring system (server monitoring system) that comprehensively monitors a plurality of servers according to the present invention. The server monitoring system according to the present embodiment has a configuration that can be remotely operated by electronic mail, and is provided in a mobile phone terminal (communication device) 101 capable of transmitting and receiving electronic mail and a network (communication line such as the Internet) 102. It is composed of a plurality of servers (master server 104, server A (submaster) 120, server B 121, server C 122) that are connected, that is, installed remotely.

  One of a plurality of servers is set as the master server 104, and server monitoring means (not shown) having a function of monitoring other servers is provided. One of the plurality of servers is set as the server A (submaster) 120 and has the same function as the master server 104. The server A (submaster) 120 has means (not shown) for confirming the state of the master server 104. When it is confirmed by the means that a failure has occurred in the master server 104, the master A Instead of the server 104, there is means (not shown) for continuously monitoring other servers.

  Each of the plurality of servers (master server 104, server A (submaster) 120, server B 121, server C 122) extracts a mail from the mail server 103 and performs various checks, 1 is provided with an internal monitoring processing unit 109 that performs self-recovery processing when a periodic process is executed and self-monitoring or failure is detected (in FIG. 1, these processing units in a server other than the master server 104 Is omitted). The master server 104 further includes a common table 111 as illustrated (may be provided outside the server as described later). The common table 111 is accessible from all servers.

  The mail check processing unit 105 is registered on the server side in accordance with the mail operation instruction, the processing authority check processing unit 106 that performs the authority check of the mail sender information, the server command check processing unit 107 that checks the corresponding server and the issued command. A processing unit such as a monitoring processing unit 108 that decodes the keyword and executes automatic processing on the server side is provided.

  Note that the monitoring processing unit 108 and the internal monitoring processing unit 109 include a mail transmission processing unit 110 for transmitting information such as a failure to a registered administrator or user.

  As will be described later, the common table 111 includes a mail confirmation table 112 (see FIG. 10), a mail processing status table 113 (see FIG. 12), an authority management table 114 (see FIG. 9), and a server management table 115 (see FIG. 8). The monitoring definition table 116 (see FIG. 11) is provided.

  Each server in the server monitoring system according to the present invention has a normal computer system configuration including a CPU, a memory, various registers, an external storage device, etc. (not shown), and each of the above-described processing units realizes the processing. The common table 111 is a table for storing common information that is accessed and used by each processing unit in each server, and is not shown in the figure. Stored in memory or external storage. As shown in FIG. 1, the common table 111 may be in the master server 104, but may be installed outside as long as it can be accessed from each server.

  Next, the registration contents of the common table 111 (the mail confirmation table 112, the mail processing status table 113, the authority management table 114, the server management table 115, and the monitoring definition table 116) will be described.

As shown in FIG. 10 (a), the mail confirmation table 112 includes a “subject” for setting a server subject to be monitored by the system for each automatically assigned number “No.” And so on.
FIG. 4B shows a specific example of the data.

In the mail processing status table 113, as shown in FIG. 12A, for each number “No.” that is numbered, “mail subject” (registered read mail information) for setting the information of the mail subject. "Password" for setting the password described in the mail subject, "Server identification number" for setting the server identification number to be monitored (server identification number 1 is server A, server identification number 2 is server (Identification number corresponding to B,...), “Email body” for setting the information of the mail body, “sender” for setting the mail address information of the sender name, and for setting the mail reception date and time “Reception date and time”, “update FLG (0: not processed, 1: processed)” for setting the processing status of the read mail, and processing result information in the processing authority check processing are set. “Processing result 1 (0: unmatch, 1: match)”, “processing result 2 (0: unmatch, 1: match)” for setting the processing result in the server command check processing, etc. Has an item name.
FIG. 4B shows a specific example of the data.

In the authority management table 114, as shown in FIG. 9A, for each automatically assigned number “No.”, a “mail address” and a password for setting a mail address for giving processing authority in this system are set. Field name such as “password”,.
FIG. 4B shows a specific example of the data.

As shown in FIG. 8A, the server management table 115 includes a “server” for setting server name information to be monitored in this system for each automatically assigned number “No.”. “Command name” for setting a command issuable command, “Process execution name” for setting a process name for executing the process, “Server management FLG (1: Master server, 2: Submaster server), “Administrator email address 1” for setting the administrator 1 email address, “Administrator email address 2” for setting the administrator 2 email address,... "Destination mail address 1" for setting the mail address 1 to be sent, "Destination mail address 2" for setting the mail address 2 to be sent, etc. With an eye name.
FIG. 4B shows a specific example of the data.

As shown in FIG. 11A, the monitoring definition table 116 includes a “server” for setting server name information to be monitored in this system for each automatically assigned number “No.”, and the IP of the server. “IP address” for setting an address, “interrupt FLG” for setting an interrupt FLG (FLG0: automatic processing possible, FLG1: automatic processing not possible), “server name” for setting server name information , ... and so on.
FIG. 4B shows a specific example of the data.

FIG. 2 is a flowchart showing the mechanism of the mail check processing unit 105 of the multiple server integrated monitoring system according to the present invention.
The mail check processing unit 105 extracts corresponding mail information from the mail server 103 regarding the mail information transmitted by e-mail, and processes each processing unit (processing authority check processing unit 106, server / command check processing unit 107, monitoring process). Unit 108, internal monitoring processing unit 109, and transmission processing unit 110).

Next, the flow of processing in the mail check processing unit 105 will be described with reference to FIG.
In step S201, the mail check processing unit 105 and the mail server 103 are connected. In step S202, the mail confirmation table 112 is read. In step S203, it is determined whether the case is registered in the mail confirmation table 112. If it has already been registered (step S203: Y), the flow is terminated because it is being processed or has already been processed. If not registered (step S203: N), in step S204, the mail text is read and the target server information is extracted.
In step S205, it is determined whether the transmitted electronic mail is a mail addressed to the own server.

When the mail addressed to the server exists (step S205: Y), various information is stored in the mail processing status table 113 in step S206. At this time, a unique number is assigned and stored in “No.”.
On the other hand, if the mail is not addressed to the own server (step S205: N), the flow ends.

  Next, in order to check the content of the received mail, control is transferred to the processing authority check processing step S207 (processing of the processing authority check processing unit 106 in FIG. 1) (argument: No.), and processing authority check processing is performed. I do. Details of the processing authority check processing step S207 will be described later (see the description of FIG. 3).

  After executing the processing authority check process 207, in step S208, it is determined whether there is no problem with the authority of the sender based on the processing authority check process result.

If there is no problem with the authority of the sender (step S208: Y), then control is performed to the server command check processing 209 (processing of the server command check processing unit 107) in order to check whether or not the corresponding server and command exist. Transfer (argument: No.) and check process of server command. Details of the server command check processing 207 will be described later (see FIG. 4).
On the other hand, if there is a problem with the sender's authority (step S208: N), the flow is terminated.

Next, in step S210, it is determined whether there is no problem in command execution. If there is no problem in command execution (step S210), control is transferred to monitoring processing step S211 (processing of the monitoring processing unit 108) in order to perform monitoring processing on the server. Details of the monitoring processing step S211 will be described later (see the description of FIG. 5).
On the other hand, if there is a problem in command execution (step S210: N), the flow is terminated.

FIG. 3 is a flowchart showing the mechanism of the processing authority check processing unit 106 of the multi-server integrated monitoring system (detailed processing in step S207 in FIG. 2).
In step S301, the sender information in the mail processing status table 113 of the common table stored in the mail check processing unit 105 is extracted.
In step S302, the extracted sender information and mail address information in the authority management table 114 are searched.

In step S303, it is determined whether the corresponding data exists.
If the corresponding data exists (step S303: Y), the password information of the mail processing status table 113 is acquired in step S304.

  On the other hand, if they do not match (data does not exist) (step S303: N), “1” is set in the update FLG of the mail processing status table 113 and “0” is set in the processing result 1 in step S308, and the processing ends. .

  In the next step S305, the acquired password information is compared with the password information in the authority management table 113, and in step S306, it is determined whether or not the corresponding data exists.

If the data exists (matches) (step S306: Y), “1” is set in the update FLG of the mail processing status table 113 and “1” is set in the processing result 1 in step S307, and the processing ends.
On the other hand, if the data does not exist (mismatch) (step S306: N), “1” is set in the update FLG of the mail processing status table 113 and “0” is set in the processing result 1 in step S308. finish.

  FIG. 4 is a flowchart showing the mechanism of the server / command check processing unit 107 of the multi-server integrated monitoring system (detailed processing in step S209 in FIG. 2). Here, the purpose is to check the validity of the mail sender information and server control commands sent by e-mail.

  In step S401, processing result 1 information is extracted from the mail processing status table 113 stored as a processing result in the processing authority check processing unit 106. In step S402, it is determined whether the processing result 1 information is “1”.

If the processing result 1 information is “1” (step S402: Y), the server information of the mail processing status table 113 is extracted in step S403.
On the other hand, if the processing result 1 information is other than “1” (step S402: N), the processing ends.

  In the next step S404, the monitoring server information of the monitoring definition table 116 is acquired. In step S405, the acquired server information of the mail processing status table 113 is compared with the monitoring server information of the monitoring definition table 116. In step S406, the monitoring server information is acquired. It is determined whether the server information in the mail processing status table 113 and the monitoring server information in the monitoring definition table 116 match.

If they match (step S406: Y), the mail text information in the mail processing status table 113 is acquired in step S407.
On the other hand, if they do not match (step S406: N), “0” is set in the processing result 2 of the mail processing status table 113 in step S411, and the processing ends.

  In step S408, the mail text information in the mail processing status table 113 and the server and command name information in the server management table 115 are compared. In step S409, it is determined whether they match.

If they match (step S409: Y), “1” is set in the processing result 2 of the mail processing status table 113 in step S410, and the processing ends.
On the other hand, if they do not match (step S409: N), “0” is set in the processing result 2 of the mail processing status table 113 in step S411, and the processing ends.

  FIG. 5 is a flowchart showing the mechanism of the monitoring processing unit 108 of the multi-server integrated monitoring system (detailed processing in step S211 in FIG. 2).

  In step S501, the interrupt FLG information in the monitoring definition table 116 is extracted. In step S502, it is determined whether or not the extracted interrupt FLG information is “1” (automatic processing is not possible).

  If it is other than “1” (step S502: N), information of processing result 1 and processing result 2 in the mail processing status table 113 is extracted in step S503. If “1” (step S502: Y), The process ends.

  In step S504, it is determined whether or not the processing result 1 is “0”. If the processing result 1 is other than “0” (step S504: N), the control is moved to step S505. On the other hand, if “0” (step S504: Y), “0” is set in the interrupt FLG of the monitoring definition table 116 in step S512.

  In step S505, it is determined whether or not the processing result 2 is “0”. If the processing result 2 is other than “0” (step S505: N), the control is transferred to step S506. On the other hand, if “0” (step S505: Y), interrupt FLG: 0 of the monitoring definition table 116 is set in step S512.

  In step S506, “1” is set in the interrupt FLG of the monitoring definition table 116. In the next step S507, the command is executed on the server.

  Next, in step S508, it is checked whether the processing has been completed normally. If the processing result is not normal (abnormal; step S508: N), the update FLG of the mail processing status table 113 is set to “2” in step S509. Set to. It should be noted that a failure can be made to correspond to a plurality of failure levels depending on the failure status and the failure content, and processing can be performed with priority assigned to the failure level. For example, the value to be set according to the failure level is set to multiple values of “2” or more, and processing according to the failure level (e-mails that each monitored server notifies the administrator automatically according to the failure level) Can also be made to be performed). If the processing result is normal (step S508: Y), step S509 is skipped.

In step S510, the command execution result is stored in the processing result information (log file) 117. In step S511, “0” is set in the interrupt FLG of the monitoring definition table 116.
Thereafter, control is transferred to the mail transmission process (argument: 1, No.) in step S513, and the process ends.

FIG. 6 is a flowchart showing the mechanism of the internal monitoring processing unit 109 of the multi-server integrated monitoring system.
In step S601, server management FLG information in the server management table 115 is extracted.
In step S602, the process is repeatedly executed until all of the monitoring processes for performing internal processes on each server side are completed.
In step S603, the internal processing command set in the server is executed.

  At this time, the master server 104 executes a command for checking a monitoring target server composed of a plurality of servers based on the server setting information (file) 118. Similarly, the sub master server (server A) also executes a command for checking the master server 104 based on the information of the server setting information (file) 118.

In step S604, the execution result is output to the processing result information (log) 117.
In step S605, after all the monitoring processes are completed, the iterative process is terminated.

  In step S606, the processing result is determined. If the processing result is determined to be abnormally terminated, the control is transferred to the mail transmission processing (argument: 2) in step S607, and the processing is terminated. If so, the process ends.

  FIG. 7 is a flowchart showing the mechanism of the mail transmission processing unit 110 of the multi-server integrated monitoring system.

  In step S701, it is determined whether the result information is from the internal monitoring process. If the argument is “1”, control is passed to step S702. On the other hand, if the argument is “2”, the reply mail address is acquired from the server management table 115 in step S707, mail reply setting information 709 (mail reply setting information file 119) is set in the mail text, and in step S708. Send emails to interested parties.

In step S702, the mail processing status table 113 is read.
In step S703, it is determined whether there is an abnormality in the server.
If there is an abnormality in the server (step S703: Y), the control is transferred to step S704.

On the other hand, if there is no abnormality in the server (step S703: N), the mail reply setting information (mail reply setting information file 119 in FIG. 1) is set in the mail body in step S706, and the mail is transmitted to the sender.
In step S704, the server management table is read.
In step S705, the mail reply setting information is set in the mail body, and the mail is transmitted to the sender and the related parties.

Next, in order to help understanding of the flow of processing according to the present invention, an explanation will be given using an example.
FIG. 13 is a diagram showing an example of the contents of a received mail for explaining the monitoring process in the present invention.

  The mails used in the present invention include “Date (reception date)”, “From (transmission source mail address)”, “To (reception source (management) mail address)”, “Subject (subject: processing content #password). ) ”And“ Body (text: target server: command (multiple designation possible)) ”are included, and in this example,“ 2008/9/15 11:45 ”,“ BBBB@xxx.ne.jp ”, respectively. ”,“ System@office.com ”,“ automatic monitoring request 1 # 23456 ”,“ A: reb ”.

  14A to 14E are diagrams illustrating specific processing examples in each step of the flowchart of FIGS. 2 to 5.7 when the mail of FIG. 13 is received.

Hereinafter, the case where the own server is the server A (submaster server) 120 will be considered.
First, it demonstrates using FIG. 14-A.
In step S201, the mail server 103 is connected and the mail having the contents shown in FIG. 13 is received.
In step S202, the mail confirmation table 112 is read.
In step S203, the processing content (automatic monitoring request 1) described in the subject of the mail is read to check whether the processing is registered in the mail confirmation table 112 (the processing ends if registered).

In step S204, the mail text is read (target server is acquired).
In step S205, it is determined whether the mail is addressed to the own server (server A) (if the address is not addressed to the own server, the process ends).

In this example, since the target server is A, various information is stored in the mail processing status table 113 in the next step S206. At this time, the number is assigned (unique number) and stored in “No.”.
Next, in step S207, control is passed to processing authority check processing (subroutine processing step S301 in FIG. 3).

14A, the sender information (BBBB @@ xxx.ne.jp) in the mail processing status table 113 is acquired using “No.” as a key in step S301.
In step S302, the sender information is compared with the mail address registered in the authority management table 114.

  In step S303, if the e-mail address registered in the authority management table 114 matches, the process proceeds to step S304. At this time, the password of the matching mail address in the authority management table 114 is acquired. If they do not match, the process proceeds to step S308.

  In step S304, the password (23456) in the mail processing status table 113 is acquired. In step S305, the password in the authority management table is compared with the transmitted password. If the password matches in step S306, the process proceeds to step S307. The process is transferred (the process is continued if the password of BBBB@xx.ne.jp is 23456). If they do not match, the process proceeds to step S308.

In step S307, the update flag (FLG) of the mail processing status table 113 is changed to “1”, and “1” is set to the processing result 1.
On the other hand, in step S308, the update flag (FLG) of the mail processing status table 113 is changed to “1”, and “0” is set to the processing result 1 (in the case of this specific example, the processing of step S308 is not performed). .

  When the processing authority check process is completed, in step S208, the processing result 1 of the mail processing status table 113 is acquired using “No.” as a key. If there is no problem with the authority of the sender (processing result 1 is “1”). ), The process proceeds to step S209. If there is a problem with the authority of the sender (when the process result 1 is “0”), the process ends. In this example, the process proceeds to step S209.

  In step S209, control is passed to the server command check process (step S401 of the subroutine in FIG. 4) (argument: No.).

Next, moving to FIG. 14C, in step S401, processing result 1 (“1”) in the mail processing status table 113 is acquired using “No.” as a key.
If the processing result 1 is “1” (no problem in authority) in step S402, the process proceeds to step S403. If the processing result 1 is “0”, the processing is terminated. In this example, the process proceeds to step S403. However, since the authority check is performed in the preprocess (step S208), the processes in steps S401 and S402 are not necessarily required.

In step S403, the server identification number “1” (corresponding to the server “A”) in the mail processing status table 113 is acquired using “No.” as a key.
In step S404, the monitoring server information in the monitoring definition table 116 is read. In step S405, the server "A" is compared with the monitoring target server information registered in the monitoring server information. In step S406, the server "A" If "" matches, the process proceeds to step S407. If not, the process proceeds to step S411. In the case of this example, since they match, the process proceeds to step S407.

  In step S407, the mail text information ("reb") in the mail processing status table 113 is acquired using "No." as a key. In step S408, the server management table 115 is stored in the server Z ("A") and the command name ( Read and compare with “reb”).

  In step S409, if there is a match as a result of the comparison, the process proceeds to step S410. If there is no match, the process proceeds to step S411.

  In step S410, “1” is set to the processing result 2 of the mail processing status table 113, and “0” is set to the processing result 2 of the mail processing status table 113 in step S411. In the case of this example, the process of step S411 is not performed.

  When the above server command check processing is completed, next, in step S210, the processing result 2 of the mail processing status table 113 is acquired by using “No.” as a key. In the case of “1”), the process proceeds to step S211. If the processing result 2 is “0”, the processing is terminated. In this example, the process proceeds to step S211.

  Next, moving to FIG. 14D, in step S501, the interrupt FLG information of the monitoring definition table 116 is acquired using the server identification number 1 (“A”) as a key. In the following figures, the server identification number is referred to as a server identifier. Server identification number 1 is server A, server identification number 2 is an identification number corresponding to server B,.

  In step S502, it is checked whether or not the interrupt FLG is “1”. If the interrupt FLG is “1” (when automatic processing is disabled because other processing is in progress), the processing ends. If the interrupt FLG is “0”, the process proceeds to step S503. In this example, since the interrupt FLG is “0”, the process proceeds to step S503.

  In step S503, processing result 1 “1” and processing result 2 “1” of the mail processing status table 113 are acquired using “No.” as a key. In step S504, it is checked whether processing result 1 is “0”. If the process result 1 is “0” (process end), the process proceeds to step S512. If the process result 1 is “1” (process continues), the process proceeds to step S505. In this example, the process proceeds to step S505.

  In step S505, it is checked whether or not the processing result 2 is “0”. If the processing result 2 is “0” (end of processing), the processing proceeds to step S512, and the processing result 1 is “1” (continuation of processing). In this case, the process proceeds to step S506. In this example, the process proceeds to step S506.

  In step S506, “1” is set in the interrupt FLG of the monitoring definition table 116.

  In step S507, the mail text (“reb”) in the mail processing status table 113 is acquired using “No.” as a key, and the command is executed. In step S508, the completion of the process is checked. If the process result is normal, the process proceeds to step S510. If the process result is not normal end (in the case of abnormality), the process proceeds to step S509. In this example, it is assumed that an abnormality has been detected.

  In step S509, “2” is set in the update FLG of the mail processing status table 113 using “No.” as a key.

  Next, in step S510, the processing result is stored as processing result information in the processing result information (log) 117, and in step S511, “0” is set in the interrupt FLG of the monitoring definition table 116 to release the exclusive control. Do.

  In step S512, “0” is set to the interrupt FLG in the monitoring definition table 116 (exclusion control may not be released due to some influence, so exclusive control release processing is performed again here. Step S511). If the control is transferred to step S512, step S512 is unnecessary). Next, control is transferred to the mail transmission process (subroutine process 701 in FIG. 7) in step S513 (argument: 1, No.).

  Next, moving to FIG. 14E, in step S701, it is confirmed whether the monitoring process is performed by an argument (“1” or “2”). If the argument is “1” (monitoring process), the process proceeds to step S702. If the argument is “2” (internal process), the process proceeds to step S707. In this example, the process proceeds to step S702.

  In step S702, the update FLG ("2") of the mail processing status table 113 is acquired using "No." as a key (acquired together with the server identification number and the command name). In step S703, whether there is an abnormality in the server. Check whether or not. If the update FLG is “1” (no abnormality), the process proceeds to step S706. If the update FLG is “2” (abnormal), the process proceeds to step S704. In this example, the process proceeds to step S704.

  In step S704, the server management table 115 is read using the server identifier (“A”) and the command name (“reb”) as keys, and the destination mail address (all addresses set to 1 = 3) is acquired. . In the case of this example, AA @ xxx. ne. jp, AA1 @ xxx. ne. jp, AA2 @ xxx. ne. jp is acquired.

  In step S705, the body of the reply mail is generated based on the mail reply setting information file 709 (mail reply setting information file 119 in FIG. 1), and the sender (the person who sent the mail (BBB@xxx.ne. jp) and the related person (the reply mail address acquired in step S704).

  In step S706, the body of the reply mail is generated based on the mail reply setting information file 709 (mail reply setting information file 119 in FIG. 1), and the sender (the person who sent the mail (BBB@xxx.ne. jp).

  In step S707, the server management table 115 is read using the server identifier (“A”) and the command name (“reb”) as keys, and the destination mail address (all addresses set to 1 = 3) is acquired. To do. In the case of this example, AA @ xxx. ne. jp, AA1 @ xxx. ne. jp, AA2 @ xxx. ne. jp is acquired.

  In step S708, based on the mail reply setting information file 709 (mail reply setting information file 119), mail is transmitted to the related parties (reply destination mail address acquired in step S707).

  In addition, each processing unit (mail check processing unit, processing authority check processing unit, server command check processing unit, monitoring processing unit, internal monitoring processing unit, mail transmission processing unit in the server monitoring system according to the present invention shown in FIG. And the means described with reference to FIG. 1 (server monitoring means (not shown), etc.) are realized by a CPU that is a component of each server executing a program corresponding to each means ( These programs can be distributed to the market via a recording medium such as a CD-ROM, DVD, or USB, or the Internet.

It is a block diagram which shows one Example of the structure which concerns on this invention of the multiple server integrated monitoring system (server monitoring system) which comprehensively monitors the multiple server of this invention. It is a flowchart which shows the operation example of the mail check process part which concerns on this invention of the server monitoring system in FIG. It is a flowchart which shows the operation example of the process authority check process part which concerns on this invention of the server monitoring system in FIG. It is a flowchart which shows the operation example of the server command processing part which concerns on this invention of the server monitoring system in FIG. It is a flowchart which shows the operation example of the monitoring process part which concerns on this invention of the server monitoring system in FIG. It is a flowchart which shows the operation example of the internal monitoring process part which concerns on this invention of the server monitoring system in FIG. It is a flowchart which shows the operation example of the mail transmission process part which concerns on this invention of the server monitoring system in FIG. 2 shows a record format of a server management table (issued command / administrator destination correspondence table) according to the present invention in FIG. FIG. 2 shows a record format of an authority management table according to the present invention in FIG. 1. It shows the record format of the mail confirmation table according to the present invention in FIG. Fig. 2 shows a record format of a monitoring definition table according to the present invention in Fig. 1. It shows the record format of the mail processing status table according to the present invention in FIG. It is a figure which shows the example of the content of the received mail for demonstrating the monitoring process in this invention. It is a figure which shows the specific process example in each step of the monitoring process in this invention at the time of receiving the mail of FIG. 13 (the 1). It is a figure which shows the specific process example in each step of the monitoring process in this invention at the time of receiving the mail of FIG. 13 (the 2). It is a figure which shows the specific process example in each step of the monitoring process in this invention at the time of receiving the mail of FIG. 13 (the 3). It is a figure which shows the specific process example in each step of the monitoring process in this invention at the time of receiving the mail of FIG. 13 (the 4). It is a figure which shows the specific process example in each step of the monitoring process in this invention when the mail of FIG. 13 is received (the 5).

Explanation of symbols

101: Communication device (cell phone terminal, etc.)
102: Communication line (network such as the Internet)
103: mail server 104: master server 105: mail check processing unit 106: processing authority check processing unit 107: server command check processing 108: monitoring processing unit 109: internal monitoring processing unit 110: mail transmission processing unit 111: common table 112 : Mail confirmation table 113: Mail processing status table 114: Authority management table 115: Server management table 116: Monitoring definition table 117: Processing result information (log file)
118: Server setting information (file)
119: Mail reply setting information (file)
120: Server A (submaster server)
121: Server B
122: Server C

Claims (5)

In a server monitoring system that monitors multiple servers connected to a network,
A memory for holding a common table that is accessible from all of the plurality of servers and stores information necessary for server monitoring;
Self-monitoring means for monitoring the server by referring to the common table is provided for all of the plurality of servers, and one of the plurality of servers is set as a master server, and the common table is set in the master server. Providing server monitoring means to monitor all other servers with reference to
Wherein the plurality of monitoring function by self-monitoring means provided to all servers and the monitoring by the server monitoring means provided in the master server, so as to monitor all of the plurality of servers,
Each of the plurality of servers, when a failure is detected by the self-monitoring means, executes a self-recovery process according to an instruction registered in advance in the common table, and then stores the situation and result in the common table in advance. E-mail is sent to the administrator's e-mail address of the registered administrator terminal, and the contents of the monitoring process, password, and one or more monitoring target servers and commands are included in the subject or text from the administrator terminal that received the e-mail. When an e-mail described and sent to a plurality of servers addressed to one common e-mail address is received, the contents described in the e-mail are extracted by a keyword registered in the common table in advance. To determine whether to execute or not execute the monitoring process on its own server based on the decoding result, and to execute it , Server monitoring system characterized by having a mail check processing means other monitoring process on the local server confirms whether it is running, to perform exclusively the monitoring process when it is not running. In claim 1 Symbol placement of server monitoring system,
Among the plurality of servers, one server other than the master server is set as a submaster server, and the submaster server monitors the master server, and when the master server fails, the master server A server monitoring system comprising means for continuing monitoring processing of another server in place of a server. In the server monitoring system according to claim 1 or 2 ,
When a fault is detected as a result of monitoring by the self-monitoring means, the fault is associated with a plurality of fault levels according to the fault status or fault content, and processing is performed with priority assigned to the fault level. A server monitoring system. The server monitoring system according to claim 3 , wherein
A server monitoring system comprising means for setting a mail transmission destination to which the monitoring result is sent according to the failure level. The program for functioning a computer as each means in the server monitoring system in any one of Claim 1 to 4 .

Images