AStallmann at CONET
Jun 28, 2012, 8:05 AM
Views: 429
Permalink
|
|
Resource is monitored only till promote... bug or config error?
|
|
Hi!
For some yet unknown reason, pacemaker does monitor the tomcat_ms resource on my dedicated master node (ucrs1) only until it gets promoted to Master. After that, there’s no further monitoring for tomcat on the master, while the slave (ucrs2) is still monitored.
This leads to some problems: If tomcat on ucrs1 dies, the cluster will never detect this and a failover won’t happen.
Here’s my configuration for tomcat:
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=”...” \
op start interval="0" timeout="60s" \
op stop interval="0" timeout="120s" \
op monitor interval="10s" role="Master" timeout="30s" \
op monitor interval="20s" role="Slave" timeout="30s"
ms ms_tomcat tomcat_res \
meta master-max="1" master-node-max="1" clone-max="2" clone-node-max="1" target-role="Started"
Strangely, when I ask crm what it thinks about tomcats state, it does not trigger a new check but seems to rely on “old” information from the cib; the tomcat resource script on the master remains untouched.
Any help welcome.
Thanks,
Andreas
PS: Some Version Information...
ubuntu 12.04 LTS
tomcat7 7.0.26-1ubuntu1 with self-written resource agent
pacemaker 1.1.6-2ubuntu3
corosync 1.4.2-2
resource-agents 1:3.9.2-5ubuntu4.1
--
CONET Solutions GmbH
Andreas Stallmann,
Theodor-Heuss-Allee 19, 53773 Hennef
Tel.: +49 2242 939-677, Fax: +49 2242 939-393
Mobil: +49 172 2455051
Internet: http://www.conet.de, mailto: AStallmann [at] CONET<mailto:AStallmann [at] CONET>
----------------------------
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
----------------------------
|
Resource is monitored only till promote... bug or config error?
