Operating System - HP-UX
1830624 Members
1960 Online
110015 Solutions
New Discussion

Monitoring processes with Service Guard

 
SOLVED
Go to solution
Jerome Bellet
Advisor

Monitoring processes with Service Guard

Hi!

Apparently Service Guard is just able to monitor one process for each service we configure, and the process command must be the command that launches the service.
So if we want Service Guard to "monitor" a big service (let's say a DBMS), I think we have to write a script (SERVICE_CMD[]) that correctly launches all the required processes, then supervises them and exits if one of them dies.
Is this the optimal approach?

TIA, Jerome
4 REPLIES 4
MARTINACHE
Respected Contributor

Re: Monitoring processes with Service Guard

Hi,

If your DBMS is oracle, I suggest you to use the "Oracle Toolkit" for MC/Service Guard.
It will give you start/stop and monitoring scripts.

Regards,

Patrice.
Patrice MARTINACHE
Kent Ostby
Honored Contributor

Re: Monitoring processes with Service Guard

There are a few possibilities.

#1) As you mention above, you can add a
single service which launchs and monitors your
product and exits when one sub process fails.

#2) You can add multiple lines for any process that will stay up and ahve serviceguard monitor those processes.

#3) You can add steps in user defined run commands to be kicked off at the beginning of
the package start up.

#4) You can buy one of the pre-packaged packages for netscape or nfs or database services.

Best regards,

Oz
aka Kent M. Ostby
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"
Jerome Bellet
Advisor

Re: Monitoring processes with Service Guard

Oz, thanks for your answer. You wrote:

>#2) You can add multiple lines for any process that will >stay up and ahve serviceguard monitor those processes.

I thought we could only have SG monitor processes that are used to launch services. If a start-up script that spawns several processes already exists, we can not apply method #2), we can only use method #1). Am I right?
TFYT, Jerome
Kent Ostby
Honored Contributor
Solution

Re: Monitoring processes with Service Guard

Yes.. you are right... if you have a start up script already written that starts up sub processes then you'd have to use method #1.

Method #2 would be used if you wanted to pull out the subprocesses from your main script and
put them into the serviceguard script.

The advantage of using #1 is that you can then change your start up script without having to redo the cmapplyconf through Serviceguard.

If you use #2 and want to add or delete a service, then you would have to redo the cmapplyconf of that package.
"Well, actually, she is a rocket scientist" -- Steve Martin in "Roxanne"