HPE GreenLake Administration
- Community Home
- >
- Servers and Operating Systems
- >
- Operating Systems
- >
- Operating System - HP-UX
- >
- MC/SG Service Scripts / Halting
Operating System - HP-UX
1830036
Members
8682
Online
109998
Solutions
Forums
Categories
Company
Local Language
back
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
back
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
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- 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
07-08-2003 06:04 AM
07-08-2003 06:04 AM
MC/SG Service Scripts / Halting
Hi All,
I have a new MC/SG cluster I am setting up.
I have three services and one startup and shutdown script.
The three service scripts launch another process in the foreground so that if the process dies it will get re-started. This seems to work fine but when I halt the cluster, MC/SG kills the script and then the process dies right away. One of the process usually takes 30 to 60 seconds to stop when killed normally.
If in the service script file I put a exec in front of the program I am launching, MC/SG will wait while the service stops (process is killed). This seem to me like what I should it so that any service process I launch is allowed to fully exit.
Is this the best way to do this or are there other suggestions?
Thanks!
- Justin
I have a new MC/SG cluster I am setting up.
I have three services and one startup and shutdown script.
The three service scripts launch another process in the foreground so that if the process dies it will get re-started. This seems to work fine but when I halt the cluster, MC/SG kills the script and then the process dies right away. One of the process usually takes 30 to 60 seconds to stop when killed normally.
If in the service script file I put a exec in front of the program I am launching, MC/SG will wait while the service stops (process is killed). This seem to me like what I should it so that any service process I launch is allowed to fully exit.
Is this the best way to do this or are there other suggestions?
Thanks!
- Justin
3 REPLIES 3
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 09:32 AM
07-08-2003 09:32 AM
Re: MC/SG Service Scripts / Halting
Justin,
you need to configure a SERVICE_HALT_TIMEOUT for the services in question in your package configuration.
See the comments in SG's configration template:
# SERVICE_HALT_TIMEOUT is represented in the number of seconds.
# This timeout is used to determine the length of time (in
# seconds) the cluster software will wait for the service to
# halt before a SIGKILL signal is sent to force the termination
# of the service. In the event of a service halt, the cluster
# software will first send a SIGTERM signal to terminate the
# service. If the service does not halt, after waiting for the
# specified SERVICE_HALT_TIMEOUT, the cluster software will send
# out the SIGKILL signal to the service to force its termination.
# This timeout value should be large enough to allow all cleanup
# processes associated with the service to complete. If the
# SERVICE_HALT_TIMEOUT is not specified, a zero timeout will be
# assumed, meaning the cluster software will not wait at all
# before sending the SIGKILL signal to halt the service.
Best regards...
Dietmar.
you need to configure a SERVICE_HALT_TIMEOUT for the services in question in your package configuration.
See the comments in SG's configration template:
# SERVICE_HALT_TIMEOUT is represented in the number of seconds.
# This timeout is used to determine the length of time (in
# seconds) the cluster software will wait for the service to
# halt before a SIGKILL signal is sent to force the termination
# of the service. In the event of a service halt, the cluster
# software will first send a SIGTERM signal to terminate the
# service. If the service does not halt, after waiting for the
# specified SERVICE_HALT_TIMEOUT, the cluster software will send
# out the SIGKILL signal to the service to force its termination.
# This timeout value should be large enough to allow all cleanup
# processes associated with the service to complete. If the
# SERVICE_HALT_TIMEOUT is not specified, a zero timeout will be
# assumed, meaning the cluster software will not wait at all
# before sending the SIGKILL signal to halt the service.
Best regards...
Dietmar.
"Logic is the beginning of wisdom; not the end." -- Spock (Star Trek VI: The Undiscovered Country)
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-08-2003 12:29 PM
07-08-2003 12:29 PM
Re: MC/SG Service Scripts / Halting
Thanks for the reply. I do have SERVICE_HALT_TIMEOUT set to 120.
The problem is a basic one I think. Say you have the following script named testapp:
===========Start=============
export VAR1=test
export VAR2=test2
/path/to/app/appname
============End==============
If you run just /path/to/app/appname it will take it 30 to 60 seconds to shutdown once killed. However if you run the testapp script and kill the testapp script, appname will not take the normal 30 to 60 seconds to shutdown. Because the script that was running it was killed.
If I change my script to have exec in front of the /path/to/app/appname then when the script/sg service is killed it will take its normal time to shutdown.
- Justin
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
07-09-2003 07:01 AM
07-09-2003 07:01 AM
Re: MC/SG Service Scripts / Halting
Justin:
Have you tried replacing the service command string (where you currently would have "/path/to/testapp") with a direct call to the application? Yes, you can get the environment variables set, like this:
VAR1=test VAR2=test2 /path/to/application
-dlt-
Have you tried replacing the service command string (where you currently would have "/path/to/testapp") with a direct call to the application? Yes, you can get the environment variables set, like this:
VAR1=test VAR2=test2 /path/to/application
-dlt-
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
Company
Events and news
Customer resources
© Copyright 2025 Hewlett Packard Enterprise Development LP