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...
In hacmp.out there is nothing useful. The cluster is new, it has been installe on the 1st of August and worked. Then I do not know what is happened: what I see now is that the clstrmgrES daemon (that should always be on) cannot start: it crashes 1 second after been started with the "unknown...
Hi,
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...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.