Hi,
Apologies for cross-posting but I'm not sure where this problem resides.
I'm running:
corosync-1.2.7-1.1.el5.x86_64
corosynclib-1.2.7-1.1.el5.x86_64
cluster-glue-1.0.6-1.6.el5.x86_64
cluster-glue-libs-1.0.6-1.6.el5.x86_64
pacemaker-1.0.10-1.4.el5.x86_64
pacemaker-libs-1.0.10-1.4.el5.x86_64
resource-agents-1.0.3-2.6.el5.x86_64
on RHEL5.
In one of my resource agents (tomcat) I'm directly outputting the result of:
$((OCF_RESKEY_CRM_meta_timeout/1000))
to an external file.
and its coming up with a value of '100'
Whereas the resource definition in pacemaker specifies timeout of '30'
specifically:
primitive tomcat_tc1 ocf:intact:tomcat \
params tomcat_user="tomcat" catalina_home="/opt/tomcat6"
catalina_pid="/home/tomcat/tc1/temp/tomcat.pid"
catalina_rotate_log="NO" script_log="/home/tomcat/tc1/logs/tc1.log"
statusurl="http://127.0.0.1/version/"; java_home="/usr/lib/jvm/java" \
op start interval="0" timeout="70" \
op stop interval="0" timeout="20" \
op monitor interval="60" timeout="30" start-delay="70"
Is this a known bug? Does it affect all operation timeouts?
Thanks,
--
Best Regards,
Brett Delle Grazie
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
