<div dir="ltr">David,<div><br></div><div>Thank you, this is it! Option name is not that self-explaining... </div><div><br></div><div>Best regards,</div><div>Alexandr A. Alexandrov</div></div><div class="gmail_extra"><br><div class="gmail_quote">2014-09-15 20:46 GMT+04:00 David Vossel <span dir="ltr"><<a href="mailto:dvossel@redhat.com" target="_blank">dvossel@redhat.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=""><br>
<br>
----- Original Message -----<br>
> Hi!<br>
><br>
> I guess it would be better to start a separate thread on this.<br>
><br>
> I have a VM with pacemaker-remote installed.<br>
><br>
> Stack: cman<br>
> Current DC: wings1 - partition with quorum<br>
> Version: 1.1.10-14.el6-368c726<br>
> 3 Nodes configured<br>
> 2 Resources configured<br>
><br>
><br>
> Online: [ oracle-test:vm-oracle-test wings1 wings2 ]<br>
<br>
</span>The remote-node in this case is named 'oracle-test'. The remote-node's container resource<br>
is 'vm-oracle-test'. Internally pacemaker makes a connection resource named after the<br>
remote-node. That resource represents the pacemaker_remote connection.<br>
<br>
Kind of confusing I know. Here's the point. The connection resource 'oracle-test' is what is<br>
timing out here, not the vm itself. By default the connection resource has a 60 second<br>
timeout. If you want to increase that timeout use the remote-connect-timeout resource<br>
metadata option. You don't have to fully understand how all this works, just know that the<br>
remote-connection-timeout option needs to be greater than the time it takes for the virtual<br>
machine to fully initialize.<br>
<br>
<a href="http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-options" target="_blank">http://clusterlabs.org/doc/en-US/Pacemaker/1.1-pcs/html-single/Pacemaker_Explained/index.html#s-resource-options</a><br>
<br>
Hope that helps!<br>
<br>
-- Vossel<br>
<div><div class="h5"><br>
><br>
> vm-oracle-test (ocf::heartbeat:VirtualDomain): Started wings2<br>
><br>
> 2 resources configured...<br>
><br>
> However,<br>
><br>
> # pcs resource show<br>
> vm-oracle-test (ocf::heartbeat:VirtualDomain): Started<br>
><br>
> As I understand, pacemaker considered pacemaker-remote on the VM as some sort<br>
> of 'virtual resource' (called 'oracle-test' in my case), since I have only<br>
> one 'primitive' section (VirtualDomain) in my CIB.<br>
><br>
> Well, the problem is here:<br>
><br>
> Sep 15 12:28:13 wings1 crmd[13553]: error: process_lrm_event: LRM operation<br>
> oracle-test_start_0 (8397) Timed Out (timeout=60000ms)<br>
> Sep 15 12:28:13 wings1 crmd[13553]: warning: status_from_rc: Action 7<br>
> (oracle-test_start_0) on wings1 failed (target: 0 vs. rc: 1): Error<br>
> Sep 15 12:28:13 wings1 crmd[13553]: warning: update_failcount: Updating<br>
> failcount for oracle-test on wings1 after failed start: rc=1<br>
> (update=INFINITY, time=1<br>
> 410769693)<br>
><br>
> Timeout is 60 seconds! Even though I have:<br>
><br>
> <primitive class="ocf" id="vm-oracle-test" provider="heartbeat"<br>
> type="VirtualDomain"><br>
> <instance_attributes id="vm-oracle-test-instance_attributes"><br>
> <nvpair id="vm-oracle-test-instance_attributes-hypervisor" name="hypervisor"<br>
> value="qemu:///system"/><br>
> <nvpair id="vm-oracle-test-instance_attributes-config" name="config"<br>
> value="/etc/libvirt/qemu/oracle-test.xml"/><br>
> </instance_attributes><br>
> <operations><br>
> <op id="vm-oracle-test-monitor-interval-60s" interval="60s" name="monitor"/><br>
> <op id="vm-oracle-test-start-timeout-300s-interval-0s-on-fail-restart"<br>
> interval="0s" name="start" on-fail="restart" timeout="300s"/><br>
> <op id="vm-oracle-test-stop-timeout-60s-interval-0s-on-fail-block"<br>
> interval="0s" name="stop" on-fail="block" timeout="60s"/><br>
> </operations><br>
><br>
> Moreover, VirtualDomain RA has this:<br>
><br>
> <actions><br>
> <action name="start" timeout="90" /><br>
> <action name="stop" timeout="90" /><br>
> <action name="status" depth="0" timeout="30" interval="10" /><br>
> <action name="monitor" depth="0" timeout="30" interval="10" /><br>
> <action name="migrate_from" timeout="60" /><br>
> <action name="migrate_to" timeout="120" /><br>
><br>
><br>
> My VM is unable to start in 60 seconds. What could be done here?<br>
><br>
> --<br>
> Best regards,<br>
> Alexandr A. Alexandrov<br>
><br>
</div></div>> _______________________________________________<br>
> Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
> <a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
><br>
> Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
> Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
> Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
><br>
<br>
_______________________________________________<br>
Pacemaker mailing list: <a href="mailto:Pacemaker@oss.clusterlabs.org">Pacemaker@oss.clusterlabs.org</a><br>
<a href="http://oss.clusterlabs.org/mailman/listinfo/pacemaker" target="_blank">http://oss.clusterlabs.org/mailman/listinfo/pacemaker</a><br>
<br>
Project Home: <a href="http://www.clusterlabs.org" target="_blank">http://www.clusterlabs.org</a><br>
Getting started: <a href="http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf" target="_blank">http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf</a><br>
Bugs: <a href="http://bugs.clusterlabs.org" target="_blank">http://bugs.clusterlabs.org</a><br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>С уважением, ААА.
</div>