topic cmclconfd entry in syslog. in Operating System - HP-UX

cmclconfd entry in syslog.

Stefano_65 — Fri, 13 May 2005 08:20:03 GMT

Hi everybody.
I've cloned via make_tape_recovery a node of a cluster.
AUTOSTART is set to 0 in the /etc/rc.config.d/cmcluster file of new server, because it will never join the cluster.
In syslog.log I found this entry every 30'':
---
Local node server1 claims to be in cluster CLUSTER_NAME, but CLUSTER_NAME cluster configuration does not include node server1. It contains node(s): server2 server3.

Why server1 (the cloned one) look for the cluster if autostart is set tu 0?
tnx.
S.

Re: cmclconfd entry in syslog.

Steven E. Protter — Fri, 13 May 2005 08:22:55 GMT

Either the clone did not happen as expected, or it was not done with the parmater set the way you thought.

Did you perhaps restore off an older tape?

SEP

Re: cmclconfd entry in syslog.

melvyn burnard — Fri, 13 May 2005 08:33:28 GMT

If you recovered from a make_tape_recovery of a cluster in a node, then it will have the /etc/cmcluster directory in place, which will include a cluster binary, and this has the onformation from the cloned node.
If this node is NOT to be a member of a cluster, remove the /etc/cmcluster directory and swremove Serviceguard

Re: cmclconfd entry in syslog.

Stefano_65 — Fri, 13 May 2005 08:36:24 GMT

No, I'm sure that AUTOSTART is set to 0, immediatly after the creation of the tape i start the cloning..
I think that I can delete /etc/cmcluster/*, I'ts a bad idea? Consider that in this server I've to build a single node cluster.

Re: cmclconfd entry in syslog.

melvyn burnard — Fri, 13 May 2005 08:38:20 GMT

whether AUTOSTART is set to 0 or not does not matter, the system is responding to probes out on the network from th eother cluster when they send out heartbeat and network probes
If you are going to create a single node cluster, then remove the cmclconfig file to delete the current binary on this node.

Re: cmclconfd entry in syslog.

Stefano_65 — Fri, 13 May 2005 08:41:35 GMT

Ok..
AUTOSTART=0 means only that node doesn't join cluster at boot time.. but cmclconfd works and cause the error..right?

thanx everybody.
s.

Re: cmclconfd entry in syslog.

Steven E. Protter — Fri, 13 May 2005 08:49:51 GMT

Just change the file, don't delete it.

You should be able to make some changes, reboot and then the machine will stop trying to join the cluster until you are finished configuring it.

SEP