Try using a larger timeout value for the stop operation. I don't know if that is intentional (and I'm still waiting for an answer about that ;-) ) but the timeout value for migrate_from and/or migrate_to seems driven by the stop timeout value.
Alain Le 19 octobre 2009 11:41:09, Dejan Muhamedagic a écrit : > Hi, > > On Mon, Oct 19, 2009 at 10:45:19AM +0200, Sebastian Reitenbach wrote: > > Hi, > > > > I plan on updating heartbeat from heartbeat 2.1.X to now use pacemaker. I > > installed a test cluster. Further I want to use XEN VM live migration. > > Everything works fine so far, also the live migration, just one glitch I > > don't know where to fix. > > When initiating a migration of a VM, then, on the source host, I get a > > monitor timeout. I already raised the default monitor timeout value in > > the configuration for the resource, however, that doesn't seem to do the > > trick. I need to clean the resource manually to remove the failed monitor > > action from the source host to be able to migrate the resource back. > > > > Any idea what to do, or more information to provide? > > > > I use pacemaker-1.0.5 on SLES 11. > > Anything suspicious in the logs? Try grep lrmd.*rsc_name > /var/log... > > Thanks, > > Dejan > > > cheers > > Sebastian > > > > > > _______________________________________________ > > Pacemaker mailing list > > [email protected] > > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > -- Alain St-Denis Supercomputing, Systems and Storage / Superinformatique, systèmes et stockage, High Performance Computing Support / Soutien aux calculs en haute performance Chief Information Officer Branch / Direction Générale du dirigeant principal de l'information Environment Canada / Environnement Canada Tel: +1 514 421 4697 _______________________________________________ Pacemaker mailing list [email protected] http://oss.clusterlabs.org/mailman/listinfo/pacemaker
