On Thu, Mar 18, 2010 at 04:21:03PM +0100, Dejan Muhamedagic wrote:
> Hi,
>
> On Thu, Mar 18, 2010 at 03:40:54PM +0100, Alain.Moulle wrote:
> > HI
> > As Florian explained, start-delay does not solve the problem
> > so I workarounded it in another way, but what do you call
> > exactly "my RA" ? I can't see any link to resource-agent ... ?
>
> ?
>
> > I can admit that virsh should not return until the vm is really
> > started and reachable, but I can't change "virsh" ...
>
> Well, virsh is fine, that's how xm create works too. What you can
> do is add a monitor script (monitor_scripts) as, I think, Florian
> already suggested. The RA is going to wait then for all the
> monitor scripts to succeed. Perhaps something like "ssh xen0
> true" would do.
I think that is what he does already. And it does not work. That is
how this thread started, anyways. Or I am misunderstanding something :(
This was the config in the first post:
crm configure primitive vm15 ocf:heartbeat:VirtualDomain \
params config="/root/vms/vm15.xml" \
monitor_scripts="/usr/sbin/hakvm" force_stop="true" \
meta migration-threshold="1" \
op start on-fail="stop" \
op monitor start-delay=120 timeout=120 interval=60
Maybe it is all a misunderstanding?
Alain: can you post your hakvm script, and and example logs from a start
attempt to the first "monitoring failure"?
--
: Lars Ellenberg
: LINBIT | Your Way to High Availability
: DRBD/HA support and consulting http://www.linbit.com
DRBD® and LINBIT® are registered trademarks of LINBIT, Austria.
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
