On Tue, Jun 17, 2008 at 09:02, HIDEO YAMAUCHI <[EMAIL PROTECTED]> wrote: > Hi, > > When the lrmd process falls, lrmd reboots. > But, the monitor stops after having rebooted. > > In this status, lrmd cannot detect the obstacle of the resource after it.
You mean it doesn't know which resources are active? Actually its not supposed to - the cluster is already designed to handle this scenario. The cluster will find this what is or is not active by asking the new lrmd process to run a status operation for every cluster resource. It will of course do this _before_ starting any resources elsewhere. > Actually, there may be little possibility that lrmd reboots. > But, I think that it is necessary when I think about the worst case. > > When it is necessary for lrmd to restart, I hope that a system reboots. > Like ccm and crmd .... > (Possibly a similar thing may apply to a stonithd process.) > > Will it be difficult to hope for this improvement in Heartbeat? > > Best Regards, > Hideo Yamauchi. > > _______________________________________________ > 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
