JP2002229870A - Server trouble monitoring system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To promptly and accurately monitor and recover an Internet server trouble regardless of place or time. SOLUTION: This server trouble monitoring system comprises a monitoring server computer and an auxiliary server computer. The monitoring sever computer comprises a database registering means recording distinguish information and administrator information of server computers to be managed in a memory means as an administrator database in advance; a remote monitoring means sending a specified sending signal to the server computers on the Internet registered in the administrator database through the Internet, and determining the presence/absence of trouble occurrence on each server computer on the basis of a response to the sending signal; and a notifying means notifying trouble information to a terminal of an administrator of the server computer wherein trouble occurs. The auxiliary server computer comprises a signal receiving means receiving a recovery command from the terminal of the administrator, and a controlling means recovering the server computer wherein the trouble occurs on the basis of the recovery command.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a server fault monitoring system for monitoring a fault of a server computer and automatically recovering the fault, and in particular, automatically notifies fault information to a remote manager terminal, The present invention relates to a server failure monitoring system which enables a failed server computer to be recovered from an administrator terminal of the server.

[0002]

2. Description of the Related Art Various failures may occur in server computers on the Internet or on a local area network. In order to monitor such a failure situation, the conventional method
There is no method of monitoring a server computer from another server computer on the Internet. A local machine for monitoring the server computer is installed on a local area network, and a person in charge of monitoring always has a local machine. While monitoring the status of the server computer, the operating status of the server computer is visually checked. When the person in charge finds a failure in the server computer, he / she notifies the server system administrator of the failure and detailed information on the failure by telephone, and the system administrator who receives the notification manually restarts the server computer. It is designed to start up and remove the fault.

[0003]

However, according to such a conventional fault monitoring method, a person in charge monitors the fault condition by monitoring on a local machine on a local network, and voices the contents of the fault to a system administrator by telephone or the like. , It is difficult to accurately communicate the failure situation. For this reason, there is a problem that it takes time to remove the failure of the server computer and restart it.

[0004] When the server computer is operated on the Internet, a general user is connected via the Internet, such as browsing a homepage, via another network or dial-up, so the server computer is always operated. It is preferable that if any trouble occurs, quick trouble elimination and restarting are required. If the system administrator is away from the server, it is difficult to notify promptly about the occurrence of the failure, and even if the system administrator of the failed server grasps the details of the failure, it can be immediately and accurately performed. It is very difficult to respond. In fact, most Internet servers are often far away from their owners and managers, and often have Internet servers abroad. For this reason, even if you know that your server is faulty, if you can not reach the place where your Internet server is installed, you can not restart the server, There is a problem that it takes time to recover the server.

On the other hand, Internet servers are usually
A mix of server processes with different functions, such as a WWW server (usually an Apache server) that outputs home pages, a mail server that manages e-mail distribution, an FTP server for file transfer, and a database server that manages databases Has been started. In conventional fault monitoring of a server computer, the local machine on the local area network determines whether or not the server computer itself is powered on. Even if a failure occurs in the server process, if other server processes are operating normally, it is determined that the server computer is operating normally because the server computer itself is powered on. Often. For this reason, system administrators or general users
It is difficult to know that a failure has occurred only after accessing the server, and to detect the failure before access.
If these Internet servers are monitored on the same network, a router or a DNS connecting the line of the network to the Internet network is used.
Even if a failure occurs in the server or the Internet line, it is difficult to detect the failure.

SUMMARY OF THE INVENTION The present invention has been made in view of such problems, and a server fault monitoring system capable of quickly and accurately monitoring faults and recovering a server, particularly an Internet server, regardless of location or time. To provide.

[0007]

According to one aspect of the present invention, there is provided a server failure monitoring system including a monitoring server computer and an auxiliary server computer, wherein the monitoring server computer includes a monitoring server computer and an auxiliary server computer. Is
Database registration means for pre-recording the identification information and the manager information of the server computer to be managed in the storage means as a manager database; Remote monitoring means for transmitting a transmission signal of the above, and determining whether or not a failure has occurred in each server computer based on a response to the transmission signal; and transmitting failure information to a terminal of an administrator of the server computer in which the failure has occurred. Notifying means for notifying, the auxiliary server computer, receiving means for receiving a recovery command from the terminal of the administrator, based on the recovery command, based on the recovery command, the server computer in which a failure has occurred And control means for restoring.

According to the first aspect of the present invention, the monitoring server transmits a predetermined transmission signal to the server computer registered in the administrator database via the Internet, and based on a response to the transmission signal, each server computer Since the presence / absence of a failure is determined, failure monitoring of a server constantly connected to the Internet line can be automatically and promptly performed. In the present invention,
If a failure occurs in the server computer, the monitoring server notifies the administrator's terminal of the failed server computer of the failure information. In such a case, the administrator can immediately obtain accurate fault information of the server computer. Moreover, since the fault information is notified to the administrator's terminal, more accurate fault information can be obtained as compared with a conventional server fault monitoring system that verbally notifies the fault status by telephone or the like.

Further, by installing a plurality of server fault monitoring systems of the present invention on the Internet and registering the identification information of the server computers installed in each administrator database, a plurality of server failure monitoring systems can be installed on the Internet. Another advantage is that fault monitoring can be performed mutually.

Further, according to the present invention, if the administrator who has received the failure notification transmits a restoration command of the server computer managed by the terminal to the auxiliary server from his / her own terminal, the auxiliary server receives the instruction based on the restoration instruction. Since the server computer in which the failure has occurred is recovered, even if the administrator is at a remote location from the server computer managed by the administrator, the failure can be quickly recovered. For this reason, the time required from the occurrence of a failure of the server computer to the completion of recovery is shortened, and quicker troubleshooting can be achieved when the server computer is operated on the Internet.

The identification information of the server computer registered in the administrator database in the present invention may be any information as long as the server computer can be identified on the Internet, such as the URL, IP address, and domain name of the server computer. .

The administrator's terminal in the present invention may be a personal computer (PC) or a workstation connected to the Internet, a personal digital assistant (PDA), a mobile terminal such as a mobile phone, or the like. Further, the terminal information of the administrator may be any information that can be directly notified to the administrator, and may include an e-mail address of the administrator, an e-mail address of a mobile phone, a telephone number of a mobile phone, and the like.

The predetermined transmission signal transmitted from the monitoring means of the monitoring server to the server computer may be a signal for accessing the server computer, and may be a signal designating the URL, IP address, domain name or the like of the server computer. The transmission of the transmission signal by the monitoring means
In order to enable constant monitoring, transmission may be performed at short intervals such as one second, or transmission may be performed at intervals of one hour or longer.

The response from the server computer is
In addition to a response signal indicating a failure or an error, a response indicating that a response to a transmission signal transmitted to the server computer has not elapsed for a predetermined time may be used as the response.

The fault information to be notified by the notification means of the monitoring server can be arbitrarily determined as long as the information is related to a fault. For example, the fault server name (IP address or domain), the type of the Internet server in which the fault occurred ( WWW server, mail server, FTP server, database), failure time, expected failure type, etc. In addition, the fault type may be any type that is expected to occur and can be detected by the remote monitoring means.For example, excessive access, insufficient memory, insufficient hard disk (HDD) capacity, power failure, hacking, hacker intrusion, unauthorized Access, virus infection, virus file storage, denial of service (DoS), and the like.

The control means of the auxiliary server only needs to restore the server computer, and may be configured to remove a fault or restart the server computer via the power controller.

Note that the server computer in the present invention includes a group of server computers such as workstations including a plurality of computers, in addition to a server computer configured by a single computer.

According to a second aspect of the present invention, there is provided a database registering means for recording identification information and manager information of a server computer to be managed in a storage means as a manager database in advance, and an Internet registered in the manager database. Remote monitoring means for transmitting a predetermined transmission signal to the above server computer via the Internet and determining whether or not a failure has occurred in each server computer based on a response to the transmission signal, and a server computer having a failure And a notifying unit for notifying the failure information to the terminal of the administrator of the server.

The invention according to claim 2 relates to a monitoring server computer of the server failure monitoring system according to claim 1. According to the present invention, a predetermined transmission signal is transmitted to the server computer registered in the administrator database via the Internet, and it is determined whether or not a failure has occurred in each server computer based on a response to the transmission signal. Failure monitoring of a server constantly connected to the Internet line can be automatically and quickly performed. Further, in the present invention, when a failure occurs in the server computer, the monitoring server notifies the terminal of the administrator of the failed server computer of the failure information, so that the administrator manages the failure. Even when the administrator is at a remote location from the server computer, the administrator can immediately obtain accurate fault information of the server computer. In addition, since fault information is notified to the administrator's terminal,
It is possible to obtain more accurate fault information as compared with a conventional server fault monitoring system that verbally notifies a fault status by telephone or the like.

Also, a plurality of server fault monitoring systems of the present invention are installed on the Internet, and the identification information of the server computers installed in each administrator database is registered, so that a plurality of server computers on the Internet can be connected. Can mutually monitor faults.

According to a third aspect of the present invention, in the server fault monitoring apparatus according to the second aspect, the remote monitoring means further transmits the transmission signal to a server computer on a local area network to which the own computer belongs. Then, it is determined whether or not a failure has occurred in each server computer.

According to the third aspect of the invention, in addition to the server computer on the Internet, the self (monitoring server)
Since the server computers connected to the local area network (LAN) to which the server belongs also are subject to fault monitoring, even if a fault occurs in the server computer on the LAN, it is possible to accurately and promptly notify the administrator of the fault information. it can.

In the present invention, the identification information of the server computer on the local area network to which the own computer belongs is registered in an administrator database and managed by a separate database to distinguish it from the server computer on the Internet. It is optional.

According to a fourth aspect of the present invention, in the server fault monitoring device according to the second or third aspect, the transmission signal is transmitted to a server process operating in its own computer, and a response from the server process is transmitted. Self-monitoring means for judging the presence or absence of a failure in the server process based on a start-up means for issuing a restart command to the server process when the self-monitoring means determines the occurrence of a failure in the server process. , Is further provided.

In the invention according to the fourth aspect, in addition to the server computer on the Internet, the server process operated by the self (monitoring server) server computer by the self-monitoring means is also subject to fault monitoring.
Even if a failure occurs in the server process of its own server computer, the failure information can be accurately and promptly notified to the administrator. Further, when the self-monitoring means determines that a failure has occurred in the server process of the server computer of the self (monitoring server), the activation means issues a restart command to the server process, so that the failure information is transmitted to the administrator terminal. The server process can be recovered without waiting for a notification or a recovery command from the administrator terminal. For this reason, the recovery work of the server computer operated on the Internet can be performed more quickly.

In the present invention, the identification information of the server computer of itself (monitoring server) may be registered in the administrator database, or may be managed by a database distinguished from the server computer on the Internet.

The fault occurrence detected by the self-monitoring means of the present invention may be any fault that is expected to occur and can be detected by the self-monitoring means, such as excessive access, insufficient memory, insufficient hard disk (HDD) capacity, and power failure. Hacking, hacker intrusion, unauthorized access, virus infection, virus file storage, denial of service (Do
S) and the like.

According to a fifth aspect of the present invention, in the server fault monitoring device according to any one of the second to fourth aspects, the remote monitoring means is provided for the plurality of different server processes in the server computer. A transmission signal is transmitted, and the presence or absence of a failure in the server process is determined based on a response from each server process.

[0029] The invention according to claim 5 is for monitoring when a plurality of server processes are executed on a server computer. Examples of such server processes include a WWW server that outputs a home page, a mail server that manages the distribution of electronic mail, an FTP server that transfers files, and a database server that manages a database.

In the present invention, failure monitoring is performed for each of a plurality of server processes operating on such one server computer. Therefore, if any of the plurality of server processes is operating normally, the server computer is monitored. It is possible to detect the occurrence of a fault more accurately than a conventional fault monitoring device in which a fault is less likely to be recognized.

According to a sixth aspect of the present invention, in the server fault monitoring device according to any one of the second to fifth aspects, the remote monitoring means transmits the transmission signal at regular intervals. It is characterized by.

According to the sixth aspect of the present invention, since the monitoring means transmits the transmission signal to the server computer at regular intervals, the occurrence of a failure in the server computer on the Internet can be determined at appropriate intervals as necessary. Can be monitored. Such a monitoring means can always monitor a failure by transmitting a transmission signal every short time such as one second. In addition, in addition to transmitting a transmission signal at regular intervals for all 24 hours, a transmission signal is transmitted at regular intervals during a time period when a failure is unlikely to occur, and monitoring is constantly performed during other time periods when a failure is likely to occur. You may comprise.

According to a seventh aspect of the present invention, in the server fault monitoring device according to any one of the second to sixth aspects, the database registration means transmits the identification information of the server computer and the information of the administrator from the administrator terminal. When the terminal information is input, the server computer and the administrator terminal are accessed based on the input identification information and the terminal information, and the input identification information and the terminal information are managed only when the terminal can be normally accessed. It is characterized in that it is to be registered in a user database.

According to a seventh aspect of the present invention, when registering the identification information of the server computer and the terminal information of the administrator in the administrator database, the server computer and the server computer are connected to each other based on the identification information and the terminal information actually input. Access to the administrator terminal and register the entered identification information and terminal information in the administrator database only when access is successful, so it is necessary to check whether the identification information and terminal information entered by the administrator are accurate. Automatic determination can be made, and registration of incorrect information can be prevented.

According to an eighth aspect of the present invention, there is provided an incoming call receiving means for receiving a recovery command from an administrator terminal of a server of a server computer in which a failure has occurred, and a restart command to the server computer based on the recovery command. And a control means for sending the server recovery message.

The invention according to claim 8 is an auxiliary server computer of the server failure monitoring system according to claim 1. According to the present invention, if the administrator who has received the failure notification transmits a restart command of the server computer managed by the terminal to the server recovery device from his / her own terminal, the server recovery device receives the failure based on the restart command. Since the server computer in which the error has occurred is restarted and recovered, even if the administrator is at a remote location from the server computer managed by the administrator, the recovery work can be quickly performed.
For this reason, the time required from the occurrence of a failure of the server computer to the completion of recovery is shortened, and quicker troubleshooting can be achieved when the server computer is operated on the Internet.

According to a ninth aspect of the present invention, a server computer on the Internet, which is registered in an administrator database in which identification information and administrator information of a server computer to be managed are registered in advance, transmits a predetermined information via the Internet. A transmission step of transmitting a transmission signal; a monitoring step of determining whether or not a failure has occurred in each server computer based on a response to the transmission signal; and failure information to a terminal of an administrator of the server computer in which the failure has occurred. And a remote monitoring program for causing a computer to execute the notification step.

According to a ninth aspect of the present invention, there is provided a program for realizing the server fault monitoring device according to the second aspect, which has the same operational effects as the second aspect of the invention.

According to a tenth aspect of the present invention, in the remote fault monitoring program according to the ninth aspect, the transmitting step further transmits the transmission signal to a server computer on a local area network to which a monitoring server belongs. It is characterized by being.

According to a tenth aspect of the present invention, there is provided a program for realizing the server fault monitoring device according to the third aspect, which has the same operation and effect as the second aspect of the invention.

The invention according to claim 11 is the invention according to claim 9 or 1
0, the transmitting step transmits the transmission signal to a plurality of different server processes in the server computer, and the monitoring step responds to a response from each server process. It is characterized in that the presence or absence of a failure in the server process is determined based on this.

The invention according to claim 11 is a program for realizing the server fault monitoring device according to claim 5, and has the same operation and effect as the invention according to claim 5.

The invention according to claim 12 is the invention according to claims 9 to 11
In the remote fault monitoring program according to any one of the above, the transmitting step transmits the transmission signal at regular intervals.

According to a twelfth aspect of the present invention, there is provided a program for realizing the server fault monitoring device according to the sixth aspect, which has the same operational effects as the sixth aspect of the invention.

The invention according to claim 13 is the invention according to claims 9 to 12
In the remote fault monitoring program according to any one of the above, when identification information of the server computer and terminal information of the administrator are input from the administrator terminal, the server computer is configured based on the input identification information and terminal information. And accessing the administrator terminal and causing the monitoring server computer to further execute a database registration step of registering the input identification information and terminal information in the administrator database only when the administrator terminal can be normally accessed. .

According to a thirteenth aspect of the present invention, there is provided a program for realizing the server fault monitoring device according to the seventh aspect, which has the same operational effects as the seventh aspect of the invention.

According to a fourteenth aspect of the present invention, a transmission step of transmitting a predetermined transmission signal to a server process operating in a monitoring server computer, and a step of generating a failure of the server process based on a response from the server process. A self-monitoring program for causing a computer to execute a monitoring step of determining presence / absence and a start step of issuing a restart command to the server process when the occurrence of a fault in the server process is determined by the monitoring step. It is related to.

According to a fourteenth aspect of the present invention, there is provided a program for realizing the server fault monitoring device according to the fourth aspect, which has the same operation and effect as the fourth aspect of the invention.

The invention according to claim 15 is an incoming call step of receiving a restoration command from a server administrator terminal of a server computer in which a failure has occurred, and a restart command to the server computer based on the restoration command. And a server recovery program for causing a computer to execute the program.

The invention according to claim 15 is a program for realizing the server restoration device according to claim 8, and has the same operation and effect as the invention according to claim 8.

[0051]

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Preferred embodiments of a server failure monitoring system, a server failure device, and a server failure program according to the present invention will be described below in detail with reference to the accompanying drawings.

(Overall Configuration of Server Fault Monitoring System) FIG. 1 is an overall configuration diagram of a server fault monitoring system according to the present embodiment, and shows a state where three systems are connected to the Internet. In FIG. 1, N1, N2,
N3 is a network in which server computers to be monitored for failure are installed. Each network includes a DNS server computer 7, an auxiliary server computer 5, a PC 9 (personal computer), a monitoring server computer X1, and a server computer X2. , A server computer X3 and the like are connected by an Ethernet (registered trademark) cable 13 to construct a local area network (LAN) environment. Each network is connected to the Internet via a firewall 8 and a router 11. The network N2
As for N3 and N3, only the monitoring server computer and the auxiliary server computer are shown for simplicity, and other configurations are omitted.

As shown in FIG. 1, the server fault monitoring system according to the present embodiment mainly includes a monitoring server computer X1 and an auxiliary server computer 5.

The monitoring server computer X1 has a CPU
And a memory (both not shown), and a hard disk 3 constituting storage means of the present invention, and has a power controller 4 for turning on the power again. . As shown in FIG. 1, WWW is stored in the memory of the monitoring server computer X1.
Server processes of a server, a mail server, an FTP server, and a database server are operating.

The server processes of the self-monitoring server 1, the remote monitoring server 2, and the administrator registration / correction server 14 are operating on the memory of the monitoring server computer X1. The self-monitoring server 1 self-monitors the occurrence of a failure in each server process of the WWW server, the mail server, the FTP server, and the database server in the monitoring server computer X1, and executes the self-monitoring program described later to execute the self-monitoring server computer. It is generated on the memory of X1. Also, the remote monitoring server 2
Indicates that a failure has occurred in each server process in the server computers X2 and X3 on the LAN (hereinafter, referred to as "LAN servers X2 and X3") and that the server computers Y1 and Y2 on the Internet (hereinafter, "Internet servers Y1 and Y2"). ) Is monitored on the memory of the monitoring server computer X1 by executing a remote monitoring program described later. The administrator registration / correction server 14 registers and corrects an administrator record in a self-server administrator database and a remote server administrator database (described later) in the monitoring server computer X1, and executes a database registration / correction program described later. By execution, it is generated on the memory of the monitoring server computer X1.

Although the Internet servers Y1 and Y2 have the same configuration as the monitoring server computer X1,
You may comprise so that it may belong to the network group of the internet-only server larger than X1.

The auxiliary server computer 5 is for turning on the power of the server computer to which it is connected again, and is therefore connected to the power controller 4 of the server computer. The auxiliary server computer 5 has a hard disk 6 and a communication device (not shown) such as a modem and a terminal adapter (TA). The communication device uses a mobile phone network, a public line network, and an ISDN.
It is also connected to a network, and the terminal 10 of the system administrator of each server computer (cellular phone 10a, PC 10b, PDA)
(A portable information device) 10c, etc.) to receive a later-described restoration command.

(Functional Configuration of Monitoring Server Computer)
FIG. 2A is a block diagram illustrating a functional configuration (software configuration) of the monitoring server computer X1. FIG.
As shown in (a), the monitoring server computer X1
It mainly includes a self-monitoring unit 202, a remote monitoring unit 205, a notifying unit 203, a starting unit 201, a database registration / correction unit 204, and an authentication unit 212. Each of these parts is a self-monitoring program, a remote monitoring program,
The information is generated on the memory by executing the administrator registration / correction program, and the units operate in cooperation with each other.

The self-monitoring section 202 constitutes the self-monitoring means of the present invention, and monitors the occurrence of a failure in each server process of the WWW server, the mail server, the FTP server, and the database server operating in the monitoring server computer X1. The remote monitoring unit 205 constitutes a remote monitoring unit of the present invention, and monitors the occurrence of a failure in each of the LAN servers X2 and X3 and the Internet servers Y1 and Y2.

The notifying unit 203 constitutes a notifying means of the present invention, and generates an e-mail including fault information when a fault occurs in the server computer monitored by the self-monitoring unit 202 or the remote monitoring unit 205. The e-mail is transmitted to the e-mail address of the notification destination of the system administrator of the corresponding server or the e-mail address of the mobile phone.

The activating unit 201 constitutes activating means of the present invention, and the self-monitoring unit 202 controls the monitoring server computer X
When a failure occurs in any of the server processes operating in the server 1, a restart command is issued to automatically restart the failed server.

The self server administrator database 206
This is a database for managing information of the system administrator of the monitoring server computer X1, and is created on the hard disk 3 of the monitoring server computer X1. Figure 1
0 is a data structure diagram of an administrator record registered in the server administrator database 206. All administrators are thus registered as administrator records in the self-server administrator database 206. As shown in FIG. 10, each administrator record includes a management name (ID), a password, an administrator name, a notification destination mobile phone e-mail address (multiple fields), a mobile phone number, a notification destination e-mail address (multiple fields), a general Phone number, target server 1
URL (WWW server name, FTP server name, mail server name, database server name, other server name, etc.) of 5 (target server 6 or more can be specified), whether or not there is monitoring for each target server, and the periodic report of the monitoring result Each field is composed of a management name (ID) as a key. The monitoring presence / absence field specifies whether or not each target server is to be monitored. If "monitor" is specified in this field, the failure monitoring is performed by the self-monitoring server. If "No" is specified, failure monitoring is not performed. The monitoring result periodic report field is a field for specifying whether or not to periodically receive a monitoring result report mail to the server. When “receive” is set in this field, the monitoring result The report mail is periodically received, and if “not received” is set, processing is performed so that the failure notification mail is received only when a failure is found.

The remote server administrator database 207
Is a database for managing information of system administrators of the LAN servers X2 and X3 to be monitored and the Internet servers Y1 and Y2, and is created on the hard disk 3 of the monitoring server computer X1.
FIG. 11 is a data structure diagram of an administrator record registered in the remote server administrator database 207. In the remote server manager database 207, managers of all monitored Internet servers and LAN servers are registered as manager records in this manner. As shown in FIG. 11, each administrator record has a management name (ID), a password,
Administrator name, notification destination mobile phone email address (multiple fields), mobile phone number, notification destination email address (multiple fields), general phone number, target servers 1-5
URLs (WWW server name, FTP server name, mail server name, database server name, other server names, etc.) of (target server 6 or more can also be specified), whether or not there is monitoring for each target server, and periodic reports of monitoring results Field, and also the managed server domain and the managed server IP
It has an address field. This remote server administrator database 207 also has a management name (ID) as a key. The monitoring presence / absence field specifies whether or not each target server is to be monitored. If "monitor" is specified in this field, it is regarded as a failure monitoring target by the remote monitoring server, and the "monitoring" field is displayed. do not do"
If is specified, it will not be monitored by the remote monitoring server. In addition, the regular report field of the monitoring result is similar to the self server administrator database 206,
This field is used to specify whether or not to receive the report mail of the monitoring result to the server periodically. If "receive" is set in this field, the report mail of the monitoring result is received periodically. If "not received" is set, processing is performed so that a failure notification mail is received only when a failure is found. The own server administrator database 206 and the remote server administrator database 207 constitute an administrator database of the present invention.

The database registration / correction unit 204 constitutes a database registration unit of the present invention. The database registration / correction unit 204 performs registration and correction processing of administrator information (administrator record) in the self server administrator database 206 and the remote server administrator database 207, and also executes the administrator terminal 10 ( The server checks whether the URL of the server, the notification destination e-mail address, and the notification destination mobile phone mail address input and transmitted from the mobile phone 10a or the PC 10b) are correct.

The authentication unit 212 includes the administrator terminals 10a, 10
b, 10c to the monitoring server computer X1
When there is an access for registration and correction of the administrator information in the self server administrator database 206 or the remote server administrator database 207, the administrator is authenticated.

In the description, the server computer X1 is mainly described, and for convenience, X1 is a monitoring server computer and Y1
And Y2 are Internet servers, but the Internet servers Y1 and Y2 also have a function as a monitoring server computer, and the monitoring server computer X1
It has the same functional configuration as. For this reason, in the server fault monitoring system of this embodiment, the fault monitoring can be mutually performed between the server computers X1, Y1, and Y2. Further, in the present embodiment, the self server administrator database 206 and the remote server administrator database 207 are provided on the hard disk of the monitoring server computer X1, but are not limited thereto, and may be provided on the hard disk of the auxiliary server computer. In this case, the self server administrator database 206 and the remote server administrator database 207 may be further integrated with the auxiliary server administrator database.

(Functional Configuration of Auxiliary Server Computer)
FIG. 2B is a functional block diagram showing a functional configuration (software configuration) of the auxiliary server computer. As shown in FIG. 2B, the auxiliary server computer 5
It mainly includes a receiving unit 208, a control unit 210, an authentication unit 209, a server check unit 213, and an auxiliary server administrator database 211. These units are generated on the memory by executing the recovery program and the server check program, respectively. In addition, network N
The auxiliary server computers in N2 and N3 have the same functional configuration.

The receiving section 208 receives an incoming call from the mobile phone 10a of the system administrator of the auxiliary server computer 5,
It receives a restoration command. The authentication unit 209 authenticates the administrator using the password of the administrator.

The control unit 210 controls the mobile phone 10a of the administrator.
The power supply is turned on again via the power controller 4 to the server computer in which the failure has occurred in response to a command from the server computer.

The server check unit 213 accesses the specified server when the administrator issues a server operation confirmation command and confirms the operation of the server.

The auxiliary server administrator database 211
This is a database for managing information of the system administrator of the auxiliary server computer 5, and is stored on the hard disk 6 of the auxiliary server computer 5. FIG.
9 is a data structure diagram of an administrator record registered in the auxiliary server administrator database 211. FIG. All the administrators of the auxiliary server computer 5 are thus registered as administrator records in the auxiliary server administrator database 211. As shown in FIG. 12, each administrator record includes a management name (ID), a password, an administrator name, an e-mail address, a connection destination mobile phone number (multiple fields), and a connection destination general telephone number (multiple fields). have. This auxiliary server administrator database 211
Has a management name (ID) as a key.

(Self-monitoring process in monitoring server) Next, the self-monitoring server 1 in the monitoring server computer X1
Will be described. The self-monitoring server 1 executes the self-monitoring program stored in the executable form on the hard disk 3 of the monitoring server computer X1 to execute the self-monitoring unit 202, the notification unit 203, the activation unit 201, and the database registration / correction described above. It is generated on a memory as a server process having a unit 204. FIG.
5 is a flowchart of a self-monitoring process performed by the self-monitoring server 1. The self-monitoring server 1 can set whether to constantly monitor the server processes of the WWW server, mail server, FTP server, and database server in the monitoring server computer at the time of start-up or by setting options in advance, or to periodically monitor the server processes. It has become.

First, the self-monitoring server 1 refers to the self-server administrator database 206 and reads the server URL field (target server field, monitoring presence / absence field) of the administrator record (step 301). Then, of the target servers (WWW server, mail server, FTP server, database server, and other servers) operating in the monitoring server computer, the target server whose monitoring presence / absence field is "monitored" A check signal (transmission signal) is transmitted to the process (step 302). The transmission of the check signal refers to checking whether or not a predetermined process is operating for each of the servers operating on its own monitoring server computer X1, and for each server actually registered as a server URL. Is to access the address of the URL.

For example, for the WWW server, http
p to check for the existence of the process
"Http: //xxx.xx" registered as L
x. co. jp ". In addition, for the FTP server, the presence / absence of the ftp process is checked, and “ftp: // x registered as the server URL” is registered.
xx. xxx. co. jp ". The mail server is checked for sendmail, POP3 or IMAP as a receiving server, and SMTP as a sending server.
x. xxx. co. jp ". On the other hand, the database server operates in cooperation with a specific program operating under the WWW server by its nature,
No method is used to check for the presence or absence of a predetermined process. For example, if an SQL server is running as a database server, the self-monitoring server cooperates with the SQL server to determine whether or not the cooperation is operating normally. To check. Here, cooperating with the SQL server means that, for example, an arbitrary database program is prepared in advance, this database program is started by the self-monitoring server, and when started normally, the database server is operating normally. (No failure has occurred), and if the database program does not start, it may be determined that a failure has occurred in the database server. However, the method is not limited to this method.

Here, in the case of performing the constant monitoring, the server monitoring is repeatedly performed by the above-described method when the check process of each server has been completed and a response is returned from each server. In this case, the server monitoring interval is very short (for example, within 1 second, 5 seconds, 10 seconds, 30 seconds, and 1 minute), and can be arbitrarily set according to the hardware performance of the monitoring server computer. . On the other hand, when periodic monitoring is performed, a relatively long time (for example, 10
Every 30 minutes, 1 hour, etc.).

Then, the operation of each server process is confirmed, and if the server URL can be normally accessed, it is determined that the server process that has responded is operating normally and no failure has occurred (step 303, 32
3). On the other hand, if the operation of the server process cannot be confirmed, it is determined that a failure has occurred in this server process (steps 303 and 304). If there is no response within a certain period of time, a check signal is sent again (or several times) (operation check of the server process and access to the server URL are performed). If there is still no response, the server process fails. May be determined to have occurred.

When it is determined that no failure has occurred in the server process (step 312), if “receive” is set in the field of the periodic report of the monitoring result of the registered administrator record, Notification section 203
Creates an e-mail of a periodic report including server information such as server name, URL, etc. and the contents that the server is operating normally, and specifies the e-mail address of the notification destination of the administrator or the e-mail address of the notification destination mobile phone Then, the periodic report mail created is transmitted (steps 313 and 314). Then, the check signal is transmitted again after a lapse of a predetermined time (step 302), and the above processing from step 303 is repeated.

On the other hand, if it is determined that a failure has occurred in the server (step 304), the restart unit 201 issues a restart command to the failed server process (step 305). Restart the server process. Then, a recovery confirmation command is issued (step 306), and it is confirmed whether the restarted server process is operating normally (step 307).

If the restarted server process is operating normally, a check signal is sent to the server process again to access (step 310), and it is checked whether the server process is unstable (step 311). . If it is determined that the server process is unstable, a restart command is issued to the server process again (step 305). If it is determined that the restarted server process is stable, a periodic report e-mail is created and transmitted to the administrator in steps 313 and 314 when necessary.

If the restarted server process does not operate normally (if the failure is not eliminated), the notification unit 20
Then, an e-mail for a failure notification including the failure information is created (steps 307 and 308). Here, the failure information of the server to be notified is as follows.

Failure server name (IP address or domain) Failure server type (WWW server,
Mail server, FTP server, database) Failure time Predicted server failure types (excessive access, insufficient memory, insufficient hard disk (HDD) capacity, power outage, hacking, hacker intrusion, unauthorized access, virus infection, virus file storage, service Interference (DoS) etc.).

When error information can be obtained, the error notification mail may include error information, error progress information (log), and the like.

Then, the failure notification mail created by designating the notification destination electronic mail address or the notification destination mobile phone mail address of the administrator is transmitted (step 309).

The above processing is repeated for each server process at regular intervals (or short intervals in the case of constant monitoring).

(Remote monitoring processing in the monitoring server)
Next, processing of the remote monitoring server 2 in the monitoring server computer X1 will be described. The remote monitoring server 2 is connected to the hard disk 3 of the monitoring server computer X1.
By executing the remote monitoring program stored in an executable format, the remote monitoring unit 20 described above is executed.
5. Notification unit 203 and database registration / correction unit 204
Is generated on the memory as a server process having

FIG. 4 is a flowchart of the remote monitoring process by the remote monitoring server 2. The remote monitoring server 2 is also activated at start-up or by setting options in advance.
Internet servers Y1, Y2 and LAN server X
2. It is possible to set whether the server processes of the WWW server, the mail server, the FTP server, and the database server in X3 are constantly monitored or periodically monitored.

First, the remote monitoring server 2 refers to the remote server administrator database 207 and reads the server URL field (target server field, monitoring presence / absence field), IP address field, and server domain field of all administrator records (see FIG. 1). Step 401). Then, among the target servers (WWW server, mail server, FTP server, database server, other servers) running in each server computer,
Check signal (transmission signal) for the process of the target server whose monitoring status field is set to "monitor"
Is transmitted (step 402). Here, the transmission of the check signal refers to an access to an access port such as a URL or an IP address of the server to be monitored based on the remote server administrator database 207 registered in advance by the administrator.

For example, for the WWW server, “http: // xxx.
xxx. co. jp ". For the FTP server, access is made to “ftp://xxx.xxx.co.jp” registered as the server URL. For the mail server, "mail.xxx.xxx.co.j" registered as the server URL
p ". For the database server,
Access the "database server" port registered as the server domain field.

Here, in the case of performing the constant monitoring, the server monitoring is repeatedly performed by the above-described method at the time when the checking process of each server is completed and a response is returned from each server. In this case, the server monitoring interval is very short (for example, within 1 second, 5 seconds, 10 seconds, 30 seconds, and 1 minute), and can be arbitrarily set according to the hardware performance of the monitoring server computer. . On the other hand, when periodic monitoring is performed, a relatively long time (for example, 10
Every 30 minutes, 1 hour, etc.).

Then, each server process responds to the transmission of this check signal within a fixed time (for example, 30 seconds to 6 seconds).
If there is a response within 0 seconds, it is determined that the server that has responded is operating normally (step 403,
407). On the other hand, if there is no response after a certain period of time, it is determined that a failure has occurred in this server process (steps 403 and 404). If there is no response within a certain period of time, a check signal may be transmitted again (or several times), and if there is still no response, it may be determined that a failure has occurred in the server process. .

When it is determined that the server process is operating normally (step 407), if “receive” is set in the field of the periodic report of the monitoring result of the registered administrator record, The notifying unit 203 creates an e-mail of a periodic report including server information such as a server name, a URL, an IP address, and a server domain, and contents indicating that the server is operating normally. The notification destination mobile phone mail address is specified and transmitted (steps 408 and 409).
Then, the check signal is transmitted again after a lapse of a predetermined time (step 402), and the above processes from step 403 are repeated.

On the other hand, when it is determined that a failure has occurred in the server (step 404), the notifying section 203 creates a failure notification e-mail including the failure information (step 405). Here, the failure information of the server to be notified is as follows as in the self server monitoring.

Failure server name (IP address or domain) Failure Internet server type (WWW server,
Mail server, FTP server, database) Failure time Predicted server failure types (excessive access, insufficient memory, insufficient hard disk (HDD) capacity, power outage, hacking, hacker intrusion, unauthorized access, virus infection, virus file storage, service Interference (DoS) etc.).

When error information can be obtained, the failure notification mail may include error information, failure progress information (log), and the like.

Then, the failure notification mail created using the notification destination e-mail address of the administrator is transmitted (step 406).

The above processing is repeated for each server process at regular intervals (or short intervals in the case of constant monitoring).

As described above, according to the server fault monitoring system of the present embodiment, the fault monitoring of the Internet server constantly connected to the Internet line can be automatically and promptly performed, and the administrator can monitor the fault from the server computer managed by himself / herself. Even in a remote location, the administrator can immediately obtain accurate fault information of the server computer.

Further, since each server process of the WWW server, mail server, FTP server, and database server operating on one server computer is monitored for failure, any one of the plurality of server processes operates normally. Even if it is, it can detect the exact occurrence of the fault.

(Recovery Process in Auxiliary Server) Next, a description will be given of a server recovery process executed by the auxiliary server computer 5 by access of the administrator who has received the failure notification mail. FIG. 5 is a flowchart of an administrator's exchange procedure with the auxiliary server computer 5 and a flowchart of server recovery processing in the auxiliary server computer 5.

When the administrator receives the failure notification mail of the server computer managed by himself / herself from the e-mail of the manager terminal 10 (mobile phone 10a, PC 10b, PDA 10c) or the mobile phone mail (step 50).
1) After confirming the contents of the failure, the telephone number of the auxiliary server computer 5 is input from the administrator terminal 10 and connected to the auxiliary server computer 5 (step 502).

In the auxiliary server computer 5, an access from the administrator terminal 10 of the administrator is received by the receiving unit 208 (step 503), and the management name (I
D) and transmits a password input request screen to the administrator terminal 10 (step 504). Then, the manager inputs a management name (ID) and a password from the manager terminal 10 (step 505). In the auxiliary server computer 5,
With reference to the auxiliary server manager database 211, the input and transmitted management name (ID) is searched, and the personal authentication process is performed using the input password (step 506).

If the management name (ID) or the password does not match the one registered in the auxiliary server manager database 211, an error message “ID or password is different” is displayed on the manager terminal 10 of the manager.
(Step 508), and the input request screen is displayed again (step 505).

On the other hand, if the management name (ID) and the password match those registered in the auxiliary server administrator database 211, access from the administrator terminal is permitted, and the administrator terminal 10 You will be logged in to.

Next, the administrator designates the URL of the server managed by himself / herself and sends an operation confirmation command to the auxiliary server computer (step 509). The auxiliary server computer 5 that has received the operation check command activates the server check program, and accesses the server specified by the administrator by the server check unit 213 (step 510). If there is a failure in the server, there is no response to the access. Therefore, if there is no response from the accessed server for a certain period of time, a message that there is no response if there is a response, and a message that there is a response if there is a response. The data is transmitted to the terminal 10 (step 511).

The administrator receiving such a message makes a self-determination as to whether or not the server managed by the administrator is completely stopped (step 512).

In the present embodiment, the server is accessed by the auxiliary server computer by transmitting the server operation confirmation command to the auxiliary server computer. However, the method of confirming the server operation is not limited to this. is not. For example, the administrator may directly access the server managed by the administrator from the administrator terminal 10 and check the operation status of the server by himself / herself depending on whether or not there is a response. Also, a program for sending a predetermined command to the server to be managed is provided in the administrator terminal 10 in advance, and the operation of the server is checked by sending a command from the program to the server to be managed. Is also good.

If it is determined by the administrator that the server is completely stopped, the administrator terminal 10 sends a request to the auxiliary server computer to recover the failed server if necessary. A restart command is transmitted (step 513).

On the side of the auxiliary server computer 5 which has received the restart command, the control unit 210 transmits a confirmation message of "Are you sure you want to turn on the power again?" To the administrator terminal 10 and waits for a response (step 514). ). When the response “Y” is input and transmitted from the administrator terminal 10, the server power controller 4 is started by the control unit 210 of the auxiliary server computer 5, and the server computer is restarted (step 515). , 5
16). Then, the administrator sends the operation confirmation command again from the administrator terminal 10 to the auxiliary server computer 5, and the auxiliary server computer 5 accesses the server in the same manner as described above, and sends the result to the administrator terminal 10. Transmit (step 519).

At step 515, the administrator's mobile phone 10a
Sends a response "N" from the server, the auxiliary server computer 5 forcibly logs out the administrator using the administrator terminal 10 and terminates the line connection (step 51).
5, 517).

As described above, according to the server fault monitoring system of the present embodiment, even if the administrator is at a remote location from the server computer managed by himself / herself, the fault recovery work can be quickly performed, and the server computer can be restored from the fault occurrence. The time required for the restoration to be completed is shortened, and troubleshooting of the server computer when operating on the Internet is expedited.

(Registration / Correction Processing for Self-Server Manager Database) Next, registration of manager information (manager record) in the self-server manager database 206 by the database registration / correction unit 204 of the manager registration / correction server 14. The correction process will be described. FIG. 6 is a flowchart of a process of registering and correcting administrator information in the own server administrator database 206. The registration / modification processing in the present embodiment is performed by the monitoring server computer X
A monitoring server computer X managed by a first administrator from a management terminal 10 such as a mobile phone 10a or a PC 10b to a monitoring server computer X1 through a mobile phone network, a public line network, an ISDN network or the Internet network.
This is performed by connecting to 1.

When there is an incoming call from the administrator terminal 10 (step 601), the administrator registration / correction server 14 returns to FIG.
A selection screen for “new registration” and “registration information correction” shown in (a) is displayed on the administrator terminal 10 (step 604).

An administrator who has not registered the management name and password in the self-server administrator database 206 selects "new registration" on the registration reception / modification screen. In this case, the manager registration / modification server 14 displays a screen of a new registration form shown in FIG. 7B on the manager terminal 10 (steps 603 and 604). An unregistered administrator enters necessary items on this new registration form. Here, a plurality of addresses can be input to the notification destination electronic mail address and the notification destination mobile phone mail address, respectively.

On the other hand, the self server administrator database 20
The administrator who has already registered the management name and password in 6 selects “registration information correction” on the registration reception / correction screen (see FIG. 9A). In this case, the administrator registration / modification server 14 displays a login screen including input fields of a management name (ID) and a password, as shown in FIG. 9B, and provides the manager with his / her own management name (ID). And prompting for a password (steps 603 and 605). The administrator registration / correction server 14 performs an authentication process using the management name and the password input by the authentication unit 212 (step 60).
6), a screen of a registration correction form in which the current settings are displayed in each field as shown in FIG. 9C is displayed (step 607). The administrator enters necessary items on this registration correction form. Here, a plurality of addresses can be input to the notification destination electronic mail address and the notification destination mobile phone mail address, respectively.

In these forms, the server UR
L, the notification destination e-mail address, and the notification destination mobile phone mail address are entered, and the administrator registration / correction server 14 is entered.
The database registration / correction unit 204 checks whether these registration contents are correct. That is, access is performed by specifying the input server URL (step 60).
8) If there is a response, it is determined that the URL is correct. On the other hand, if there is no response within a certain period of time, it is determined that an incorrect URL has been entered, and the administrator's mobile phone 10a or PC1
0b is prompted for re-input (steps 609, 606, 6
07). If a notification destination e-mail address or a notification destination mobile phone e-mail address is input, a mail transmission signal is transmitted by designating the input e-mail address (step 610), and whether the mail transmission can be performed normally is determined. Is checked (step 611). If the e-mail was sent successfully, the entered e-mail address is determined to be accurate.If the e-mail was not sent successfully, the entered e-mail address is incorrect or It is determined that the mail address does not exist, and the user is prompted to re-enter the mail address (step 604,
607).

As a result, the server UR entered by the administrator
It is automatically checked whether L, the notification destination e-mail address, and the notification destination mobile phone mail address are correct, thereby preventing erroneous information from being registered. If the input contents of these three fields are correct, the manager record is registered or updated with the contents input in each form, and the registration is completed (step 612).

(Registration / Correction Processing for Remote Server Administrator Database) Next, the administrator registration / correction server 1
The registration and correction processing of administrator information (administrator record) in the remote server administrator database 207 by the database registration / correction unit 204 of No. 4 will be described. FIG. 8 is a flowchart of a process for registering and correcting administrator information in the remote server administrator database 207. This processing is also performed by the administrator of the Internet server and the LAN server by the administrator terminal 1 such as a mobile phone or a PC 10b.
0 to the monitoring server computer X1 from the public network or I
It is executed when connected to a server computer managed by itself through an SDN line network or the Internet network.

When there is an incoming call from the administrator terminal 10 (step 801), the administrator registration / correction server 14 executes the process shown in FIG.
A registration reception / modification screen for selecting one of “new registration” and “registration correction information” shown in FIG.
(Step 802).

Remote server administrator database 207
The administrator who does not register the management name and password in the "register" selects "new registration" on the registration reception / modification screen. In this case, the manager registration / modification server 14 displays a screen of a new registration form shown in FIG. 13B on the manager terminal 10 (steps 803 and 804). An unregistered administrator enters necessary items on this new registration form. Here, a plurality of addresses can be input to the notification destination electronic mail address and the notification destination mobile phone mail address, respectively.

On the other hand, the administrator who has already registered the management name and password in the remote server manager database 207 selects “Register registration information” on the registration reception / correction screen (see FIG. 14A). In this case, as shown in FIG. 14B, the administrator registration / modification server 14
A login screen including input fields for D) and a password is displayed, and the administrator is prompted to enter his / her own management name (ID) and password (steps 803 and 805). The administrator registration / correction server 14 performs an authentication process based on the management name and the password input by the authentication unit 212 (step 806), and the current setting contents are displayed in each field as shown in FIG. 14C. A screen for a registration correction form is displayed (step 807). The administrator enters necessary items on this registration correction form. Here, a plurality of addresses can be input to the notification destination electronic mail address and the notification destination mobile phone mail address, respectively.

In the new registration form and the registration correction form, when a server URL, a notification destination electronic mail address, and a notification destination mobile phone mail address are entered, the database registration / correction unit 204 determines whether or not these registration contents are correct. Is checked (steps 808 to 811).
The method of such a check is the same as the check method in the registration / correction processing in the self-server manager database 206, and thus the description is omitted.

By this checking process, it is automatically checked whether the server URL, the notification destination electronic mail address, and the notification destination mobile phone mail address entered by the administrator are correct. For this reason, registration of incorrect information can be prevented. If the input contents of these three fields are correct, the administrator record is registered or updated with the contents input in each form, and the registration is completed (step 812). Further, the notifying unit 203 creates an e-mail of the registration notification including the registration information, and specifies and transmits the e-mail address of the notification destination or the e-mail address of the notification destination mobile phone (step 813). When the administrator receives the registration notification mail, it can be understood that his / her own administrator information has been correctly registered or corrected in the remote server administrator database 207.

In the server monitoring system of the present embodiment, the registration and correction processing in each administrator database is performed by activating the administrator registration / correction server 14 for each monitoring server computer, as shown in FIG. So, instead of the administrator registration / correction server of the monitoring server computer,
A registration reception server 12 is installed on the registration Internet, and the registration reception server 12 performs the above-described administrator registration / correction processing on the respective administrator databases of all the Internet servers existing on the Internet via the Internet. May be configured. In this case, there is an advantage that security enhancement and unification of registered contents can be maintained.

In the server monitoring system of this embodiment, an auxiliary server computer is installed for each Internet server. As shown in FIG. 15, one auxiliary server computer is installed on the Internet. The restart of all server computers connected to the Internet may be controlled by this one auxiliary server computer. In this case, the administrator information of all the Internet servers to be managed is registered in the auxiliary server administrator database, and the restart command is issued to the server power controller 4 in the above-described recovery processing. What is necessary is just to be comprised so that it may be performed via a computer. By configuring in this way, the administrator can manage the server
Since the administrator terminal 10 only needs to connect to one auxiliary server computer at all times, the trouble of accessing a different auxiliary server computer for each server to be managed can be avoided, and the failed server can be easily re-created. There is an advantage that it can be activated.

Further, as shown in FIG. 15, a center server 15 is provided on the Internet, and a statistical program (statistical unit) is operated by each monitoring server computer.
Statistics such as hourly, daily, monthly, and yearly access statistics, server check time, response time, failure occurrence time, failure details, and failure details of monitored servers by the self-monitoring server or remote monitoring server , Center server 1
5 may be transmitted. At this time, the center server 15 can be configured to display statistical information on the server managed by the administrator on the home page of the center server 15 by accessing from the administrator terminal.

[0126]

As described above, according to the present invention,
Automatically and quickly monitors faults on servers that are constantly connected to the Internet line. Even if the administrator is remotely located from the server computer managed by the administrator, the administrator can immediately obtain accurate fault information on the server computer. It has the effect of being available.

Further, according to the present invention, even if the administrator is at a remote place from the server computer managed by the administrator, the recovery work can be performed quickly, and the time required from the occurrence of the failure of the server computer to the completion of recovery can be reduced. This has the effect of speeding up troubleshooting when the server computer is operated on the Internet.

Further, according to the fifth and eleventh aspects of the present invention, a fault is monitored for each of a plurality of server processes operating on one server computer, so that one of the plurality of server processes is operating normally. However, there is an effect that an accurate failure occurrence can be detected.

Further, according to the seventh and thirteenth aspects of the present invention, when registering and correcting the manager information in the manager database, it is determined whether or not the identification information and the terminal information input by the manager are correct. Is automatically determined, and registration of erroneous information can be prevented beforehand.

[Brief description of the drawings]

FIG. 1 is an overall configuration diagram of a server fault monitoring system according to an embodiment.

FIG. 2A is a block diagram illustrating a functional configuration of a monitoring server computer according to the embodiment;
(B) is a block diagram showing a functional configuration of the auxiliary server computer of the present embodiment.

FIG. 3 is a flowchart of a self-monitoring process executed by the monitoring server computer of the embodiment.

FIG. 4 is a flowchart of a remote monitoring process executed by the monitoring server computer of the embodiment.

FIG. 5 is a flowchart illustrating a procedure of an administrator accessing an auxiliary server computer according to the present embodiment, and a flowchart of a recovery process executed by the auxiliary server computer.

FIG. 6 is a flowchart of processing for registering and correcting an administrator record in a self-server administrator database according to the present embodiment.

FIG. 7A is a schematic diagram of a selection screen displayed on an administrator terminal in the self-monitoring server according to the embodiment;
FIG. 7B is a schematic diagram of a new registration form screen for administrator information.

FIG. 8 is a flowchart of a process of registering and correcting an administrator record in the remote server administrator database according to the embodiment.

FIG. 9A is a schematic diagram of a selection screen displayed on an administrator terminal in the self-monitoring server according to the embodiment;
FIG. 9B is a schematic diagram of a login screen, and FIG. 9C is a schematic diagram of a registration information correction form screen of administrator information.

FIG. 10 is a data structure diagram of an administrator record of a self-server administrator database.

FIG. 11 is a data structure diagram of an administrator record of a remote server administrator database.

FIG. 12 is a data structure diagram of an administrator record of an auxiliary server administrator database.

FIG. 13A is a schematic diagram of a selection screen displayed on an administrator terminal in the self-monitoring server according to the present embodiment, and FIG. 13B is a schematic diagram of a new registration form screen for administrator information; It is.

14A is a schematic diagram of a selection screen displayed on an administrator terminal in the remote monitoring server of the present embodiment, FIG. 14B is a login screen, and FIG. 14C is an administrator. It is a schematic diagram of a registration information correction form screen of information.

FIG. 15 is an overall configuration diagram showing another aspect of the server fault monitoring system of the present embodiment.

[Explanation of symbols]

X1: Monitoring server computer X2, X3: Server computer on LAN (LAN server) Y1, Y2: Server computer on the Internet (Internet server) N1, N2, N3: Network 1: Self-monitoring server 2: Remote monitoring server 3 : Hard disk (storage means) 4: Power controller 5: Auxiliary server computer 6: Hard disk 7: DNS server computer 8: Firewall 9: PC 10: Administrator terminal 10a: Mobile phone 10b: Administrator PC 10c: Administrator PDA 11: Router 12: Registration reception server computer 13: Ethernet cable 14: Administrator registration / correction server 15: Center server computer 201: Activation unit 202: Self-monitoring unit 203: Notification unit 204: Database registration Recording / correcting unit 205: Remote monitoring unit 206: Self server administrator database 207: Remote server administrator database 208: Receiving unit 209: Authentication unit (auxiliary server side) 210: Control unit 211: Auxiliary server administrator database 212: Authentication Section (Registration / Modification Server Side) 213: Server Check Section

Claims (15)

[Claims] 1. A server failure monitoring system comprising a monitoring server computer and an auxiliary server computer, wherein the monitoring server computer identifies identification information and administrator information of a server computer to be managed by an administrator in advance. Database registration means for recording in a storage means as a database, transmitting a predetermined transmission signal via the Internet to a server computer on the Internet registered in the administrator database, and each server computer based on a response to the transmission signal Remote monitoring means for determining whether or not a failure has occurred, and a notifying means for notifying failure information to a terminal of an administrator of the server computer in which the failure has occurred. Receives a recovery command from the administrator's terminal A server failure monitoring system, comprising: a receiving means for receiving a message, and a control means for recovering a failed server computer based on the recovery command. 2. A database registration unit for recording identification information and manager information of a server computer to be managed in a storage unit in advance as a manager database, and a server computer on the Internet registered in the manager database. A remote monitoring unit that transmits a predetermined transmission signal via the Internet and determines whether or not a failure has occurred in each server computer based on a response to the transmission signal; and a terminal of an administrator of the server computer in which the failure has occurred. A server for notifying failure information to the server. 3. The remote monitoring means further transmits the transmission signal to a server computer on a local area network to which the own computer belongs to determine whether or not each server computer has a failure. The server fault monitoring device according to claim 2, wherein 4. A self-monitoring unit that transmits the transmission signal to a server process operating in its own computer and determines whether a failure has occurred in the server process based on a response from the server process. 4. The device according to claim 2, further comprising: a start unit that issues a restart command to the server process when a self-monitoring unit determines that a failure has occurred in the server process. 5. Server fault monitoring device. 5. The remote monitoring unit transmits the transmission signal to a plurality of different server processes in the server computer, and determines whether a failure has occurred in the server process based on a response from each server process. The server fault monitoring device according to any one of claims 2 to 4, wherein the server fault monitoring device performs the process. 6. The server fault monitoring device according to claim 2, wherein the remote monitoring unit transmits the transmission signal at regular intervals. 7. The database registration means, when identification information of a server computer and terminal information of an administrator are input from the administrator terminal, the server computer and the administrator based on the input identification information and terminal information. The terminal according to any one of claims 2 to 6, wherein the input identification information and the terminal information are registered in the administrator database only when the terminal is accessed and the terminal is normally accessed. Server fault monitoring device. 8. A receiving means for receiving a restoration command from a server administrator terminal of a server computer in which a failure has occurred, and a control means for sending a restart command to the server computer based on the restoration command. , A server recovery device. 9. Transmission for transmitting a predetermined transmission signal via the Internet to a server computer on the Internet in which identification information of a server computer to be managed and administrator information are registered in advance in an administrator database registered in advance. A monitoring step of determining whether or not a failure has occurred in each server computer based on a response to the transmission signal; and a notifying step of notifying failure information to a terminal of an administrator of the server computer in which the failure has occurred. , A remote monitoring program to make your computer run. 10. The remote fault monitoring program according to claim 9, wherein the transmitting step further transmits the transmission signal to a server computer on a local area network to which a monitoring server belongs. 11. The transmitting step transmits the transmission signal to a plurality of different server processes in the server computer, and the monitoring step performs a server process based on a response from each server process. 11. The remote fault monitoring program according to claim 9, wherein the remote fault monitoring program determines whether a fault has occurred. 12. The remote fault monitoring program according to claim 9, wherein the transmitting step transmits the transmission signal at regular intervals. 13. When the identification information of the server computer and the terminal information of the administrator are input from the administrator terminal, the server computer and the administrator terminal are accessed based on the input identification information and the terminal information. 13. The monitoring server computer further executes a database registration step of registering the input identification information and terminal information in the administrator database only when the user can access the server. Remote fault monitoring program described in section. 14. A transmission step of transmitting a predetermined transmission signal to a server process operating in a monitoring server computer, and a monitoring step of determining whether a failure has occurred in the server process based on a response from the server process. A self-monitoring program for causing a computer to execute a start step of issuing a restart instruction to the server process when the occurrence of a fault in the server process is determined by the monitoring step. 15. A receiving step of receiving a restoration command from an administrator terminal of a server of a server computer in which a failure has occurred, and a control step of sending a restart command to the server computer based on the restoration command. , A server recovery program to make your computer run.