you should get the latest crm code (which now part of Pacemaker not
Heartbeat):
http://www.clusterlabs.org/mw/Install
On Jul 23, 2008, at 9:45 AM, Ehlers, Kolja wrote:
I am using the Source tar ball for 2.1.3 (heartbeat-2.1.3.tar.gz) and
compiled with
./ConfigureMe
install --prefix=/usr --sysconfdir=/etc --localstatedir=/var --with-
group-id
=90 --with-ccmuser-id=90 --disable-rpath --enable-snmp-subagent
Still the problem remains. This is my resource:
<clone id="tomcat_1_clone" ordered="true" interleave="true"
notify="false">
<instance_attributes id="efceb096-786f-462e-b54f-c0beaf19ec94">
<attributes>
<nvpair name="clone_max" value="2"
id="bc8cbf76-11e0-429f-922a-24efe7c51683"/>
<nvpair name="clone_node_max" value="1"
id="cb659f4b-1df1-4d13-8681-eccfae4e47ed"/>
</attributes>
</instance_attributes>
<primitive class="ocf" id="tomcat_1" provider="heartbeat"
type="tomcat1">
<operations>
<op id="tomcat_1_start" name="start" interval="0" timeout="140s"/>
<op id="tomcat_1_mon" interval="5s" name="monitor" timeout="140s"/>
</operations>
<instance_attributes id="tomcat_1">
<attributes>
<nvpair id="tomcat_1-java_home" name="java_home"
value="/opt/j2sdk1.4.2_03_tomcat3"/>
<nvpair id="tomcat_1-catalina_home" name="catalina_home"
value="/opt/jakarta/tomcat-3"/>
<nvpair id="tomcat_1-statusurl" name="statusurl"
value="http://localhost:8083/studies/crf/test_1294_we"/>
<nvpair id="tomcat_1-catalina_pid" name="catalina_pid"
value="/opt/jakarta/tomcat-3/logs/catalina.pid"/>
<nvpair id="tomcat_1-startup-log" name="script_log"
value="/var/log/www/jakarta/tomcat3/startup.log"/>
<nvpair id="tomcat_1-name" name="tomcat_name" value="tomcat_1"/>
<nvpair id="tomcat_1-regex" name="testregex" value=".*SERVLET
OK.*DATABASE OK"/>
<nvpair id="tomcat_1-target-role" name="target_role"
value="started"/>
</attributes>
</instance_attributes>
</primitive>
</clone>
If I now manually use
crm_resource -r tomcat_1:0 -p target_role -v stopped; crm_resource -r
tomcat_1:0 -p target_role -v started
tomcat is unavailable for like 5 seconds. But is this not obvious?
tomcat_1:0 stopped
tomcat_1:1 stopped
here is the moment no tomcat_1 is available
tomcat_1:1 started
tomcat_1:0 started
I am starting to think that this will not work out with clones. And
I will
need two seperate resources for each node Tomcat_1-node1 and
Tomcat_1-node2.
Thanks
-----Ursprüngliche Nachricht-----
Von: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Auftrag von Andrew
Beekhof
Gesendet: Mittwoch, 23. Juli 2008 08:17
An: General Linux-HA mailing list
Betreff: Re: [Linux-HA] Date expression rule / SNMP LHAResourceName
On Tue, Jul 22, 2008 at 16:44, Ehlers, Kolja <[EMAIL PROTECTED]>
wrote:
I am still trying to find a solution for this. If noone knows how to
restart
a resource at a specific time, what is the savest way to restart a
resource
manually?
sorry, missed the second half of this question
If I use the tomcat LSB script to stop tomcat even the tomcat clone
on the
other node is being stopped and then started again. I dont want
this to
happen. I need at least one of the clones to be always available.
Is there a way to restart a single cloned resource without stoppin
the
other
one?
set ordered=true for the clone and you dont need to worry about
stopping the individual clones
what version are you using btw?
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
Geschäftsführung: Dr. Michael Fischer, Reinhard Eisebitt
Amtsgericht Köln HRB 32356
Steuer-Nr.: 217/5717/0536
Ust.Id.-Nr.: DE 204051920
--
This email transmission and any documents, files or previous email
messages attached to it may contain information that is confidential
or
legally privileged. If you are not the intended recipient or a person
responsible for delivering this transmission to the intended
recipient,
you are hereby notified that any disclosure, copying, printing,
distribution or use of this transmission is strictly prohibited. If
you
have received this transmission in error, please immediately notify
the
sender by telephone or return email and delete the original
transmission
and its attachments without reading or saving in any manner.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
