On Tue, Mar 16, 2010 at 11:25 AM, Michael Schwartzkopff <[email protected]> wrote: > Am Dienstag, 16. März 2010 11:14:57 schrieb Alain.Moulle: >> Hi >> >> I've a question about the start of a VM with VirtualDomain , knowing >> that I have configured this : >> >> crm configure primitive vm15 ocf:heartbeat:VirtualDomain params >> config="/root/vms/vm15.xml" \ >> monitor_scripts="/usr/sbin/hakvm" force_stop="true" \ >> meta target-role="stopped" migration-threshold="1" \ >> op start on-fail="stop" \ >> op monitor start-delay=120 timeout=120 interval=60 >> >> when I do : >> crm resource start vm15 >> >> I can see in traces that as soon as the start vm is launched successfully : >> with virsh start ( rc=0 ) in VirtualDomain, there is a status request from >> VirtualDomain which returns : status=running >> and juste after several monitoring requests with the monitor_scripts >> given at configuration so /usr/sbin/hakvm (a script of mine which does >> ssh towards the vm). >> >> The problem is that the vm is "starting" but it takes a while before to get >> really "started" and reachable (about 30s) and the monitoring >> request from Pacemaker should not be launched before that. >> >> I tried to play on op monitor values but it seems to not be relative to >> my problem ... >> >> Where do I miss something ? > > Hi, > > Add a start-delay to your monitoring operation. You monitoring will only start > after that delay when the virtual server is able to answer your requests.
No, fix the agent instead :-) _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
