Stefano wrote on tek-tips about having a HACMP problem. Me having the same problem at work found his post, and I wanna thank Stefano for the solution to this problem.

the clstrmgrES daemon crashes as soon as it is started.

I see it from the log:

lpar6# cat /tmp/clstrmgr.debug
Fri Aug 29 12:09:50 HACMP/ES Cluster Manager Version 5.3
Using ODMDIR=/etc/es/objrepos
Fri Aug 29 12:09:50 HA_DOMAIN_TYPE=HACMP
Fri Aug 29 12:09:50 ReadTopsvcs: called.
Fri Aug 29 12:09:50 GetObjects: Called with criteria:
Fri Aug 29 12:09:50 ReadTopsvcs: hbInterval = 1, fibrillateCount = 4, fixedPriLevel = 38, runFixedPri = 1 instanceNum = 20
Fri Aug 29 12:09:50 ReadTopsvcs: Calculated fixed priority is 39
Fri Aug 29 12:09:50 /usr/es/sbin/cluster/clstrmgr: Unrecognized argument ‘?’.
Fri Aug 29 12:09:50 die: clstrmgr on node 0 is exiting with code 2

read more for solution!

The problem was that somehow the clstrmgrES module was configured to start with an incorrect parameter: in the startup argument there was the “-d” switch but it was not followed by a number (that is the debug level).

I performed the following steps.

1 – check the parameters of the modules

lpar6# odmget -q “subsysname like clstrmgrES” SRCsubsys
SRCsubsys:
subsysname = “clstrmgrES”
synonym = “”
cmdargs = “-d”
path = “/usr/es/sbin/cluster/clstrmgr”
uid = 0
auditid = 0
standin = “/dev/null”
standout = “/dev/null”
standerr = “/dev/null”
action = 2
multi = 0
contact = 3
svrkey = 0
svrmtype = 0
priority = 20
signorm = 0
sigforce = 0
display = 0
waittime = 15
grpname = “cluster”

2 – redirected the output to file to see what happened

chssys -s clstrmgrES -o /tmp/output.log -e /tmp/error.log

3 – see the log to understand (and to find that the problem was related to the “debug” switch

lpar6# more /tmp/error.log
/usr/es/sbin/cluster/clstrmgr: A flag requires a parameter: d

lpar6# more /tmp/output.log
/usr/es/sbin/cluster/clstrmgr: Unrecognized argument ‘?’.
Usage: clstrmgrES [-d debug_level]
-d debug_level           Set the debugging level
-f log length           Set the max log length
-p priority             Set the process priority
-v version              Set the cluster version
-w wait                 Set the stabilization wait time

4 – delete the “-d” from the argument list

chssys -s clstrmgrES -a “”

5 – restart all: it works now.