Method for initiating a sub-system health check

• US 7,360,122 B2
• Filed: 01/10/2003
• Issued: 04/15/2008
• Est. Priority Date: 02/22/2002
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: BEA Systems Incorporated (Oracle Corporation)
• Inventors: Srivastava, Rahul, Halpern, Eric M.
• Primary Examiner(s): Baderman; Scott
• Assistant Examiner(s): Contino; Paul F
• Application Number:
  US10/340,496
• Publication Number:
  US 20030221002A1
• Time in Patent Office: 1,922 Days
• Field of Search: 714/47
• US Class Current: 714/47.3
• CPC Class Codes: G06F 11/0709 in a distributed system consisting of a plurality of standalone computer nodes, e.g. clusters, client-server systems
• CPC Class Codes: G06F 11/0757 by exceeding a time limit, i.e. time-out, e.g. watchdogs
• CPC Class Codes: G06F 11/0793 Remedial or corrective actions recovery from an exception in an instruction pipeline G06F9/3861; by retry G06F11/1402; for recovering from a failure of a protocol instance or entity H04L69/40
• CPC Class Codes: G06F 11/3006 where the computing system is distributed, e.g. networked systems, clusters, multiprocessor systems multiprogramming arrangements G06F9/46; allocation of resources G06F9/50
• CPC Class Codes: G06F 11/3055 Monitoring arrangements for monitoring the status of the computing system or of the computing system component, e.g. monitoring if the computing system is on, off, available, not available error or fault processing without redundancy G06F11/0703; error detection or correction by redundancy in data representation G06F11/08; error detection or correction by redundancy in operation G06F11/14; error detection or correction by redundancy in hardware G06F11/16
• CPC Class Codes: G06F 11/3082 the data filtering being achieved by aggregating or compressing the monitored data

Abstract

A server self health monitor (SHM) system monitors the health of the server it resides on. The health of a server is determined by the health of all of a server'"'"'s sub-systems and deployed applications. The SHM may make health check inquiries to server sub-systems periodically or based on external trigger events. The sub-systems perform self health checks on themselves and provide sub-system health information to requesting entities such as the SHM. Sub-systems self health updates may be based on internal events such as counters or changes in status or based on external entity requests. Corrective action may be performed upon sub-systems by the SHM depending on their health status or the health status of the server. Corrective action may also be performed by a sub-system upon itself.

Claims

1. A method for monitoring the health of a server comprising:

maintaining a server having a sub-system and a server self health monitor wherein the sub-system is either part of the server, deployed on the server, or has functionality that can be traced to the server;

detecting the occurrence of a health check event by the server self health monitor;

transmitting a request by the server self health monitor to the sub-system for the sub-system health information wherein the request is triggered by the detection of the health check event;

determining sub-system health information as a result of the health check by receiving a response from the sub-system to the server self health monitor;

determining the health of the server by the server self health monitor using the sub-system health information; and

performing a corrective action upon the sub-system, by the server health monitor or the sub-system, wherein the corrective action is based on the health of the sub-system and the corrective action includes restarting the sub-system; and

wherein a parameter specifies the maximum number of times a server can be restarted within a period of time specified by another parameter.

2. The method as claimed in claim 1 wherein the health check event is the expiration of a period of time.

3. The method as claimed in claim 1 wherein the health check event is a request from an administration server.

4. The method as claimed in claim 1 wherein the health check event is an event occumng external to the server, the occurrence of the event communicated to the server self health monitor.

5. The method as claimed in claim 1 wherein said transmitting a request includes transmitting a request from the sewer self health monitor to all sub-systems in a sewer for each sub-system'"'"'s health information.

6. The method as claimed in claim 1 wherein the server provides its health information to requesting entities.

7. The method as claimed in claim 1 wherein said determining sub-system health information includes the sewer self health monitor failing to receive sub-system health information from a sub-system, the sewer self health monitor determining the sub-system is failed as a result of the failure to receive sub-system health information from the sub-system.

8. The method as claimed in claim 1 wherein said determining the health of the sewer includes determining whether all the sub-systems are in a failed state.

9. The method as claimed in claim 1 wherein said determining the health of the sewer includes determining whether a critical sub-system is in a failed state.

10. The method as claimed in claim 1 further comprising:

processing the server health information.

11. The method as claimed in claim 10 wherein said processing includes restarting a failed sub-system.

12. The method as claimed in claim 10 wherein said processing includes restarting all sub-systems if a critical sub-system is failed.

13. The method as claimed in claim 10 wherein said processing includes storing the sub-system health information.

14. The method as claimed in claim 10 wherein said processing includes determining if a condition is met.

15. The method as claimed in claim 14 wherein said processing includes determining if the sub-system'"'"'s health status has changed.

16. The method of claim 1, wherein the health update indicates that the sub-system is at one of multiple pre-defined health levels.

17. The method of claim 16, wherein one health level corresponds to good, another health level corresponds to failed, and additional health levels that correspond to conditions between good and failed.

18. The method of claim 17, wherein the additional health levels include a warning level and a critical level.

19. The method of claim 18, wherein the sub-system is set to the critical level if a minimum number of transactions have timed out.

20. The method of claim 1, wherein an error message can trigger a heath update.

21. The method of claim 1, wherein the health of a server is determined by the health of all of the server sub-systems and deployed applications.

22. The method of claim 1, wherein the sub-system performs a health check upon itself and provides sub-system health information to requesting entities.

23. The method of claim 22, wherein the sub-system health updates are triggered by external entity requests, internal events such as counters, or changes in status.