Claims
- 1. A method for monitoring a server comprising:
providing a monitoring instance; establishing a connection between the monitoring instance and a server to be monitored; and determining the health status of the server as a result of communications between the monitoring instance and the server.
- 2. The method as claimed in claim 1 wherein said establishing a connection includes establishing an SSL connection.
- 3. The method as claimed in claim 1 wherein said determining the health status of the server includes detecting that the server has experienced server failure.
- 4. The method as claimed in claim 3 wherein detecting that the server has experienced server failure includes detecting that the connection established between the monitoring instance and the server to be monitored has failed.
- 5. The method as claimed in claim 1 further comprising:
performing maintenance on the server upon detecting the server has failed.
- 6. The method as claimed in claim 5 wherein performing maintenance includes restarting the server.
- 7. The method as claimed in claim 1 further comprising;
determining whether a failed server may be restarted; and restarting the failed server if it may be restarted.
- 8. The method as claimed in claim 7 wherein determining whether a failed server may be restarted includes determining whether a server has been restarted a maximum number of times within a certain period of time.
- 9. The method of claim 1 wherein the functionality of the monitoring instance may be controlled by an administration server.
- 10. The method of claim 9 wherein communication between the monitoring instance and administration server is encoded.
- 11. The method of claim 1 wherein said determining the health status of the server includes the monitoring instance automatically determining the health status of the server.
- 12. The method of claim 1 further comprising:
automatically performing maintenance upon detecting the server has failed.
- 13. The method as claimed in claim 12 wherein automatically performing maintenance includes automatically restarting the server.
- 14. The method of claim 1 wherein determining the health status of the servers is implemented using java language programming.
- 15. The method of claim 14 wherein the java language programming includes a java method instance.
- 16. The method of claim 15 wherein performing maintenance is implemented using java language programming.
- 17. The method of claim 16 wherein the java language programming includes a java method instance.
- 18. The method as claimed in claim 1 wherein providing a monitoring instance includes:
performing startup by the monitoring instance; receiving startup information by the monitoring instance from an administrative server, the startup information including instructions to start a server instance on a local machine and a request to provide information on servers previously monitored by the monitoring instance.
- 19. The method of claim 18 wherein determining whether a failed server may be restarted includes determining the value of an auto-restart parameter, the value of the auto-start parameter determining whether or not the server is restartable.
- 20. The method of claim 19 wherein the auto-restart parameter may be accessed and set by a java method.
- 21. The method of claim 18 wherein determining whether a failed server may be restarted includes determining the value of a max-restart parameter and a restart-interval parameter, the value of the max-restart parameter and restart-interval parameters determining the maximum times the server may be restarted in a certain time interval.
- 22. The method of claim 21 wherein the max-restart parameter and the restart-interval parameter may be processed and set by a java method.
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] The present application is related to the following United States patents and patent applications, which patents/applications are assigned to the owner of the present invention, and which patents/applications are incorporated by reference herein in their entirety:
[0002] U.S. patent application Ser. No. ______, entitled “METHOD FOR EVENT TRIGGERED MONITORING OF MANAGED SERVER HEALTH”, filed on Jan. ______, 2003, currently pending, which claims priority to provisional United States Patent Application entitled “ECS NODE MANAGER FOR ENSURING HIGH AVAILABILITY SERVER AND APPLICATION”, Patent Application No. 60/359,009, filed on Feb. 22, 2002; and
[0003] U.S. patent application Ser. No. ______, entitled “SYSTEM FOR MONITORING MANAGED SERVER HEALTH”, filed on Jan. ______, 2003, currently pending, which claims priority to provisional United States Patent Application entitled “ECS NODE MANAGER FOR ENSURING HIGH AVAILABILITY SERVER AND APPLICATION”, Patent Application No. 60/359,009, filed on Feb. 22, 2002;
[0004] U.S. patent application Ser. No. ______, entitled “METHOD FOR INITIATING A SUB-SYSTEM HEALTH CHECK”, filed on Jan. ______, 2003, currently pending, which claims priority to provisional United States Patent Application entitled “Server Self-Health Monitor”, Patent Application No. 60/359,010, filed on Feb. 22, 2002;
[0005] U.S. patent application Ser. No. ______, entitled “METHOD FOR MONITORING A SUB-SYSTEM HEALTH”, filed on Jan. ______, 2003, currently pending, which claims priority to provisional United States Patent Application entitled “Server Self-Health Monitor”, Patent Application No. 60/359,010, filed on Feb. 22, 2002; and
[0006] U.S. patent application Ser. No. ______, entitled “SYSTEM FOR MONITORING A SUBSYSTEM HEALTH”, filed on Jan. ______, 2003, currently pending, which claims priority to provisional United-States Patent Application entitled “Server Self-Health Monitor”, Patent Application No. 60/359,010, filed on Feb. 22, 2002.
Provisional Applications (1)
|
Number |
Date |
Country |
|
60359009 |
Feb 2002 |
US |