Clean-up the /etc/cmcluster directory

[Sandman!]

I am trying to de-clutter the /etc/cmcluster directory as there are unknown files in it and I was wondering if it is safe to delete them? The files in question are.

cmknowncmds
cmclconfig.tmp
config.lck

~thanks

[A. Clay Stephenson]

Whatever you do, do not delete cmknowncmds even if it is a null file unless you don't want your cluster to start.

[Sandman!]

Appreciate the prompt reply Clay (may the force be with you). Fact is that all three files are null files and I know for a fact that "cmclconfig.tmp" appears magicly when the binary cluster config file "cmclconfig" is created. So is it safe to delete it? What makes cmknowncmds special? Any restrictions on removing the config.lck file?

~thanks

[Geoff Wild]

config.lck - I believe that's no longer used - what SG version are you using?

DO NOT DELETE cmknowncmds

"What was the problem? A new internal file called cmknowncmds now exists in /etc/cmcluster. The file was originally shipped as an empty file giving the customer no idea the importance of the file. If this file is accidentally deleted the cluster can fail to start and messages are logged in syslog that say:
Error opening /etc/cmcluster/cmknowncmds

What was the resolution? A comment was added to this file to instruct the customer not to remove the file."

From: http://www.docs.hp.com/en/B3935-90091/ch01s06.html

cmclconfig.tmp - can be deleted - I believe it's created when changing packages - supposed to cleanup after itself.

Rgds...Geoff

[Sandman!]

Geoff...thanks for the explanation. So the config.lck depends on the SG version. I have to cleanup 40 odd servers and I am not sure what SG version is loaded on each of them. So it would help to know from what version of MC/SG onwards was the config.lck file discontinued??

File cmknowncmds can't be deleted as it keeps the cluster up and running...in some way and the cmclconfig.tmp file can be removed unconditionally.

~thanks

[Geoff Wild]

The only thing I can find about the lck file is:

http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=106482&admit=-682735245+1192464355160+28353475

Seems it only was needed in SG 11.13 maybe 14 as well as I see it too...

Rgds...Geoff

[Geoff Wild · Accepted solution]

I asked HP to be sure - here's their response:

I found the same file on my 11.18 cluster and renamed it

---------- 1 root root 0 Nov 29 2006 config.lck.OFF


Interestingly, the same file on the other node has a different date stamp:

---------- 1 root sys 0 Jun 7 2005 config.lck


I was able to perform cluster configuration changes and view the cluster without effect, so, yes â you may delete the file. I believe it is an artifact of cluster creation, but I am not certain â the Managing Serviceguard manual does not mention it.

Rgds...Geoff

[Sandman!]

Geoff appreciate your help for digging into this. So it looks like cmclconfig.tmp and config.lck can be removed unconditionally as the config.lck file has nothing to do with the version of MCSG, correct??

~thanks

[Geoff Wild]

That's correct.

I'm currently testing on my test cluster....

No issues so far.

Rgds...Geoff

[Sandman!]

Alright then I will proceed with removing cmclconfig.tmp and config.lck. I was bewildered owing to the diversity of SG versions installed across the servers. From 11.09 all the way upto 11.17. Thank you for your help Geoff.

[Sandman!]

Thanks for your help Geoff and Clay :)