Monitoring processes in a Service Guard environment
We recently changed several of our systems that are managed by Service Guard to automatic failover. They were previously a manual failover only. Now - it is impossible to predict which system in the cluster will have the critical processes active. The Service Guard managed pseudo hostname and IP address, as well as disk, processes, etc. may be on any system in the cluster at any time. I run a client on each system in the cluster, but cannot monitor the processes effectively.
- Is there a way to run a client against the Service Guard owned hostname and IP address?
- How well would adding the client to the cluster work? Inother words, if the package switches to another host system in the cluster, so would the client. The actual hostname of the new system would be different and I am guessing this would cause problems.
- Any other ideas how to effectively monitor Service Guard controlled processes?
Thanks!
Terry Barnes Siemens Com @ HFHS 248-853-4968 (Office) 586-489-4513 (Cellular) 248-844-3030 (Fax) tbarnes1 at hfhs.org
============================================================================== Go to http://henryford.com We're Henry Ford. We Can.
HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed.
Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com. Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
I basicly run a bbclient with my cluster ressource groups. The trick is to customize the etc/bbaliasname file to the same as the cluster address. This works very well for apache, mysql and normal cpu/process monitoring.
I expect the same would be possible with a hobbit client.
Terry Barnes wrote:
We recently changed several of our systems that are managed by Service Guard to automatic failover. They were previously a manual failover only. Now - it is impossible to predict which system in the cluster will have the critical processes active. The Service Guard managed pseudo hostname and IP address, as well as disk, processes, etc. may be on any system in the cluster at any time. I run a client on each system in the cluster, but cannot monitor the processes effectively.
- Is there a way to run a client against the Service Guard owned hostname and IP address?
- How well would adding the client to the cluster work? Inother words, if the package switches to another host system in the cluster, so would the client. The actual hostname of the new system would be different and I am guessing this would cause problems.
- Any other ideas how to effectively monitor Service Guard controlled processes?
Thanks!
Terry Barnes Siemens Com @ HFHS 248-853-4968 (Office) 586-489-4513 (Cellular) 248-844-3030 (Fax) tbarnes1 at hfhs.org
============================================================================== Go to http://henryford.com We're Henry Ford. We Can.
HFHS CONFIDENTIALITY NOTICE: This email contains information from the sender that may be CONFIDENTIAL, LEGALLY PRIVILEGED, PROPRIETARY or otherwise protected from disclosure. This email is intended for use only by the person or entity to whom it is addressed. If you are not the intended recipient, any use, disclosure, copying, distribution, printing, or any action taken in reliance on the contents of this email, is strictly prohibited. If you received this email in error, please contact the sending party by replying in an email to the sender, delete the email from your computer system and shred any paper copies of the email you printed.
Note to Patients: There are a number of risks you should consider before using e-mail to communicate with us. These risks are described in our Privacy Policy at http://henryford.com. Review that policy carefully before continuing to communicate with us by e-mail. For greater Internet security, our policy describes the Henry Ford MyHealth electronic communication process - you may register at http://henryford.com. If you do not believe that our policy gives you the privacy and security protection you need, do not send e-mail or Internet communications to us.
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Fri, Sep 16, 2005 at 12:17:17PM -0400, Terry Barnes wrote:
We recently changed several of our systems that are managed by Service Guard to automatic failover. They were previously a manual failover only. Now - it is impossible to predict which system in the cluster will have the critical processes active. The Service Guard managed pseudo hostname and IP address, as well as disk, processes, etc. may be on any system in the cluster at any time. I run a client on each system in the cluster, but cannot monitor the processes effectively.
- Is there a way to run a client against the Service Guard owned hostname and IP address?
- How well would adding the client to the cluster work? Inother words, if the package switches to another host system in the cluster, so would the client. The actual hostname of the new system would be different and I am guessing this would cause problems.
I think 2) answers your 1). Let the client migrate along with the other critical processes, and it shouldn't be a problem to check if those processes are running.
The Hobbit client picks up the hostname from the "uname -n" command command, but you can start it with a "--hostname=MY.PSEUDO.HOSTNAME" (at least in the current snapshot) and it will use that instead.
Another solution that I am looking at - it was suggested some time ago here on the list - is to have a process check that isn't related to any one host, but rather goes like "process foo must run on N of the nodes X, Y and Z". (E.g. "httpd" must be running on at least 5 out of our 10 web servers). That is on the to-do list.
Henrik
participants (3)
-
henrik＠hswn.dk
-
tbarnes1＠hfhs.org
-
tlp-hobbit＠holme-pedersen.dk