service guard query

[steven Burgess_2]

Hello

I had to swap out a non mirrored disk yesterday within a sg package. Due to an issue with the database I had a few rogue processes and a zombie kicking around, i therefore opted to reboot the server after I had replaced the disk etc. The data for the database hadn't yet been restored so i didn't want the package to try and start up after reboot.

To do this I cheated and stopped the cluster software from restarting during bootup by editing /etc/rc.config.d/cmcluster This of course stopped the other databases from restarting. (dev server, so no worries. I had tried to failover the other packages and disable switching, but thats another issue)

When the server came back I made the volume group cluster unaware

vgchange -c n vgsg02

Then activated it

vgchange -a y vgsg02

Before manually remounting my filesystem

What I have been searching through the documentation for is how to stop a single node from coming back after a reboot without having to stop the service guard software from starting

Thanks in advance

Steve

[Rajeev Shukla]

Let me say what i understand from you'r query
is that you want to bring up a cluster node but dont want it to join the cluster.

One way to do that is to stop the daemon from coming on that node by editing /etc/rc.config.d/cmcluster and make 0.

Other way is to remove this node from cluster.

If i am wrong in undertstanding let me know i'll try it again

[steven Burgess_2]

Hi Rajeev

Editing /etc/rc.config.d/cmcluster is what I did.

I want to stop one specific package from restarting after a reboot without having to stop them all, or removing the config for that particular package

Thanks

Steve

[aparna challagulla]

Hi Steve,

Instead if it just the package that you dont want to start after a reboot then u can modify the package control scripts to start the package manually.
i know this is not of much help but if you were thinking in this line pl recert back.
HTH
aparna

[Rajeev Shukla]

Ok, in just package case you can can not have a control of not starting that package, but alternatively what you cound do is remove that package from the cluster, which is very easy and doesn't delete any files and when required you can add it again to the cluster.
Other thing you could do is edit the package script and comment all the file systems from being mounting, comment all VG belonging to the package to be activated and also comment all services starting in the package. This way you'll have only a dummy package running with no applications running...
There are the only 2 options available

[aparna challagulla]

hi,

Sorry didnt see your reply to Rajeev's answer.You can find the control scripts in /etc/cmcluster/packagename.

HTH
aparna

[aparna challagulla · Accepted solution]

hi Steve,

here is a document which explains about how to prevent the package from starting in a cluster.

http://www1.itrc.hp.com/service/cki/docDisplay.do?docLocale=en_US&docId=200000063209051

HTH
aparna

[steven Burgess_2]

sheeez

I've been looking for that doc

Thanks guys

Steve

[Rajeev Shukla]

Hi Steve,
I went for a smoke and thinking in realised this solution to make
AUTO_RUN = NO in the package file and disable autoswitching by cmmodnet...

I was too late to reply...aaah..

Sorry , no points please...
This is just that the day is ending here and i needed a break

[Rajeev Shukla]

what is happening to me...
i mean cmmodpkg -d

...sorry i close and go home now