- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- Monitoring processes with Service Guard
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Forums
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2000 06:25 AM
12-13-2000 06:25 AM
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
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2000 06:36 AM
12-13-2000 06:36 AM
Re: Monitoring processes with Service Guard
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2000 06:39 AM
12-13-2000 06:39 AM
Re: Monitoring processes with Service Guard
#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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2000 06:59 AM
12-13-2000 06:59 AM
Re: Monitoring processes with Service Guard
>#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
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2000 07:28 AM
12-13-2000 07:28 AM
SolutionMethod #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.