cmdeleteconf hangs

[Ricky_4]

Hi Everyone,

We are trying to delete our previous cluster configuration but it only hangs. This is the command we used "cmdeleteconf -v -f -c CLUSTER_NAME". Please provide other options to delete previous cluster configuration so we can proceed recreating new cluster.

Thanks.

Ricky

[Prashant Zanwar_4]

I am not sure what you want to do exactly..you can stop the whole cluster instead of deleting configuration.
then rename all config files and again do the configuration.
this will include ASCII config file
package control scripts
might be anything else as part of customisation you might have done,,rename those also...
Hope this helps
Thanks
Prashant

[Ricky_4]

Hi,

What we would like is to create new cluster but it prompt us that there is existing cluster configuration. So we tried to delete the existing cluster configuration but the cmdeleteconf hangs.What other options to delete the previous cluster configuaration aside from cmdeleteconf?

Thanks.

Bal

[bhavin asokan]

hi,

have you halted the cluster before doing activity.

first try deleting package .

cmdeleteconf -f -v -c CLUSTER_NAME -p pkg_name

you can view the logs (open other window and view this log at the time of giving delete command ) in /etc/cmcluster/pkg/control.sh.log provided pkg is your package configuration folder and control.sh is your control script.

regds,

[Ricky_4]

slu cluster was already halted and there were not packages configured on this. But we still encountered hanging.

[Bharat Katkar]

Ricky,
if the cluster is halted..then simply move the files in /etc/cmclluster/* to some other location and keep that directory empty.

Then create Configuration template files for CLuster and Packages...Modify them as per your setup and check the configuration using cmcheckconf. If it run without any errors go ahead and start the cluster.

Hope that helps.
Regards,

[bhavin asokan]

hi,

a part of manual mcs11.16,


With root login, you can delete a cluster configuration from all cluster
nodes by using Serviceguard Manager, or on the command line. The
cmdeleteconf command prompts for a verification before deleting the
files unless you use the -f option. You can only delete the configuration
when the cluster is down. The action removes the binary configuration
file from all the nodes in the cluster and resets all cluster-aware volume
groups to be no longer cluster-aware.
NOTE The cmdeleteconf command removes only the cluster binary file
/etc/cmcluster/cmclconfig. It does not remove any other files from
the /etc/cmcluster directory.
Although the cluster must be halted, all nodes in the cluster should be
powered up and accessible before you use the cmdeleteconf command.
If a node is powered down, power it up and boot. If a node is inaccessible,
you will see a list of inaccessible nodes together with the following
message:
It is recommended that you do not proceed with the
configuration operation unless you are sure these nodes are
permanently unavailable.Do you want to continue?
Reply Yes to remove the configuration. Later, if the inaccessible node
becomes available, you should run the cmdeleteconf command on that
node to remove the configuration file.


from mcs11.14
You can delete a cluster configuration from all cluster nodes by using SAM or by issuing the cmdeleteconf command.

The cmdeleteconf command removes only the cluster binary file
/etc/cmcluster/cmclconfig. It does not remove any other files from
the /etc/cmcluster directory.


copy all files from /etc/cmcluster and /etc/cmcluster/pkg to another folder and remove it from original folders.

then create new cluster.

attached procedure for cluster configuration may be useful for you.

regds,

[bhavin asokan]

hi,

on my procedure one line is left.make it sure that /etc/services contains the following entries.
hacl-hb 5300/tcp # High Availability (HA) Cluster heartbeat
hacl-gs 5301/tcp # HA Cluster General Services
hacl-cfg 5302/tcp # HA Cluster TCP configuration
hacl-cfg 5302/udp # HA Cluster UDP configuration
hacl-probe 5303/tcp # HA Cluster TCP probe
hacl-probe 5303/udp # HA Cluster UDP probe
hacl-local 5304/tcp # HA Cluster Commands
hacl-test 5305/tcp # HA Cluster Test
hacl-dlm 5408/tcp # HA Cluster distributed lock manager



regds,

[John Bigg]

cmdeleteconf deletes the binary config file cmclconfig from /etc/cmcluster on all nodes and clears the cluster bit on any old cluster VG's. You can get away without running cmdeleteconf by simply deleting the binary config file. However I'm sure that if cmdeleteconf hangs future configuration commands such as cmquerycl and cmapplyconf will hang.

Probably what is happening is that you have a device out there that is not responding and is causing a cmclconfd process to hang.

I'd suggest you need to determine why cmdeletconf is hanging otherwise you are only delaying future problems. Maybe check for running hung cmclconfd processes and use something like losf or glance to determine what device file is currently being accessed and check this device out. If you know how you can turn on logging on cmclconfd (adding -T 5 onto the command in /etc/inetd.conf) which will then allow you do watch what it is doing as it runs for see what device it gets stuck on.

Hope this helps.

[Sanjay_6]

Hi Ricky,

You can try to remove the cluster configuratin without any option. Just run "cmdeleteconf" on the local node with the cluster and all the packages down.

Hope this helps.

Regds