topic Package Startup in Operating System - HP-UX

Package Startup

Dave La Mar — Wed, 29 May 2002 01:10:12 GMT

I would like my package to startup on reboot, but not failover just because I am rebooting the primary machine.
Routinely, we have brought the package down, rebooted then brought the package up.
I am unsure of the AUTO_RUN parameter. If I set it to yes, will the package tried to failover if I reboot? This is not what I desire for a simple reboot to apply new kernel parms.

Thanks for any input.
dl

Re: Package Startup

melvyn burnard — Wed, 29 May 2002 05:57:26 GMT

If the AUTO_RUN is set to yes, and the package is running on th enode you are about to halt, AND it is enabled to switch to an alternative node, both locally and globally, then it will switch when you do the reboot.
The simple alternative is to either do cmmodpkg -d pkg_name, so it will not switch at all, or do cmmodpkg -d pkg_name -n alternate_node_name to tell it it cannot switch to the alternate node.
For safety, I always suggest the package is halted prior to doing work like this to ensure it halted cleanly, thus ensuring that it should restart in a stable state.

HTH

Re: Package Startup

BFA6 — Wed, 29 May 2002 06:22:56 GMT

Hi,

I normally halt the package before doing any kernel params reboots. But as said before you can disable the package from switching.

Hilary

Re: Package Startup

John Palmer — Wed, 29 May 2002 06:36:40 GMT

A solution that I adopted on a system that used to be rebooted regularly was to install a shutdown script that halted any packages running on the server and note what they were in a file. I then had a startup script which restarted them at reboot. Note that the startup script has to wait for the node to join the cluster before attempting to call cmrunpkg.

Regards,
John

Re: Package Startup

Justo Exposito — Wed, 29 May 2002 06:41:01 GMT

Hi Dave,

I usually use a cmhaltpkg before to stop the node unless I need that the pakage still runing in other node, then I stop the pakage in the node and force to run in other node with the "cmrunpkg -n nodename pakagename" command.

It's better to stop the pakage cleanly before to stop the node, I think.

Hope this helps,

Justo.

Re: Package Startup

Trond Haugen — Wed, 29 May 2002 06:50:14 GMT

Normally for SericeGuard packages switching is disabled and packages halted during shutdown. So you shouldn't need to do anything.
But I have seen packages failing to halt and switching when the system goes down so I do agree with Melwyn it's good practice to halt the packages before doing maintenance on the node.

Regards,
Trond

Re: Package Startup

Dave La Mar — Wed, 29 May 2002 15:04:29 GMT

Thanks for the quick answers.
I believe I need to go with a combination of Melvyn's and John's answers.

Note that I did state we do halt the package prior to any reboot.
I just want the package to start up on reboot.
With this in mind, I will also build the shutdown script.
With the failure of clean shutdown noted, I will probably shut down manually prior to reboot.
I have not had the occasion to have to perform a reboot without being present or online.

Thanks for all the input.
dl