Hi again,
I’m still working on my tomcat master/slave resource-script.
Well... the script works fine, as far as ocf-tester can be believed. start /
stop / status / monitor / promote and demote are implemented and seem to work,
when called from ocf-tester.
Now I integradet the resource in crm like:
primitive tomcat_res ocf:ucrs:tomcat \
params java_home="/usr/lib/jvm/java-7-openjdk-amd64/jre/"
catalina_home="/usr/share/tomcat7" catalina_base="/var/lib/tomcat7"
tomcat_user="tomcat7" java_opts="lots of java opts" \
op start interval="0" timeout="60s" \
op stop interval="0" timeout="120s" \
op monitor interval="10s" timeout="30s"
ms ms_tomcat tomcat_res \
meta master-max="1" master-node-max="1" clone-max="2"
clone-node-max="1" target-role="Master" is-managed="true"
The resource stays in the state of
Master/Slave Set: ms_tomcat [tomcat_res]
Slaves: [ proto-cms-appl02 proto-cms-appl01 ]
even if I call “crm resource promote ms_tomcat”.
I let the tomcat script write some quite elaborate debug output, which NEVER
shows an attempt to promote the resource. Any ideas?
Cheers,
Andreas
--
CONET Solutions GmbH
----------------------------
CONET Solutions GmbH, Theodor-Heuss-Allee 19, 53773 Hennef.
Registergericht/Registration Court: Amtsgericht Siegburg (HRB Nr. 9136)
Geschäftsführer/Managing Director: Anke Höfer
----------------------------
_______________________________________________
Pacemaker mailing list: Pacemaker@oss.clusterlabs.org
http://oss.clusterlabs.org/mailman/listinfo/pacemaker
Project Home: http://www.clusterlabs.org
Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
Bugs: http://bugs.clusterlabs.org
