I see. It looks forward to the release of Ver2.0.9. Thanks.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Andrew Beekhof Sent: Saturday, May 19, 2007 3:01 PM To: General Linux-HA mailing list Subject: Re: [Linux-HA] A problem in one node(DC node) On 5/18/07, YAMAUCHI HIDEO <[EMAIL PROTECTED]> wrote: > Hi,Andrew. > > It tried today. > It doesn't stop in the state of S_TERMINATE if this SLE10-SP1.tar.bz2 is > used. great > However, the resource monitor stops though the process and the state return. > > Perhaps, this > bug(http://old.linux-foundation.org/developer_bugzilla/show_bug.cgi?id=1575) > might be related. yes, that is the bug that i suggested. > > Are you canceled by a formal version 2.0.9? There is a release planned but I don't know when it will arrive as its not under my control. > #The log to stopping of the monitor is appended by way of precaution. > > Regards, > Yamauchi. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of YAMAUCHI HIDEO > Sent: Thursday, May 17, 2007 12:01 PM > To: General Linux-HA mailing list > Subject: RE: [Linux-HA] A problem in one node(DC node) > > > OK > It confirms and the result will be reported tomorrow. > > -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Andrew Beekhof > Sent: Wednesday, May 16, 2007 6:06 PM > To: General Linux-HA mailing list > Subject: Re: [Linux-HA] A problem in one node(DC node) > > > On 5/16/07, YAMAUCHI HIDEO <[EMAIL PROTECTED]> wrote: > > Sorry..the explanation was insufficient. > > > > >> 1.When a problem happens in pengine/tengine after resource > > >> start in one node, pengine/tengine does not restart. > > >> (example. -9 pengine or tengine) > > > > >are you saying that if you kill the TE or PE, that it does not get > > restarted? > > >does it get started on the other node instead? > > > > It started only by one node though the composition of two nodes. > > In this case, it is not reactivated. > > It stops in the state of S_TERMINATE at this time. > > Moreover, the process of other heartbeat remains starting. > > ok, i believe i fixed something like this recently. > is there any chance you could grab > http://hg.linux-ha.org/dev/archive/SLE10-SP1.tar.bz2 and re-test? > > > >> 2.When a problem happens in crmd after resource start in > > >> one node, a monitor of a resource stops after restart. > > >> (example.kill -9 crmd) > > > > >i dont understand the question > > > > Sorry.. > > Only the node of composition 1 of two nodes started here. > > After it starts by one node, the resource and the monitor are begun. > > However, the monitor stops though the resource remains being begun when > crmd > > is killed. > > I believe you're talking about: > http://old.linux-foundation.org/developer_bugzilla/show_bug.cgi?id=1575 > > > > > Regards, > > Yamauchi > > > > -----Original Message----- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Andrew Beekhof > > Sent: Tuesday, May 15, 2007 6:21 PM > > To: General Linux-HA mailing list > > Subject: Re: [Linux-HA] A problem in one node(DC node) > > > > > > On 5/14/07, 山内 英生 <[EMAIL PROTECTED]> wrote: > > > Hi > > > > > > When a problem happened for a process of Heartbeat, will > > > this action be right? > > > > > > 1.When a problem happens in pengine/tengine after resource > > > start in one node, pengine/tengine does not restart. > > > (example. -9 pengine or tengine) > > > > are you saying that if you kill the TE or PE, that it does not get > > restarted? > > does it get started on the other node instead? > > > > > 2.When a problem happens in crmd after resource start in > > > one node, a monitor of a resource stops after restart. > > > (example.kill -9 crmd) > > > > i dont understand the question > > > > > > > (configuration) > > > Heartbeat ver2.0.8 > > > node 2node(Active/standby) > > > Resource IPaddr/ocf > > > crm yes > > > > > > Regards, > > > 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 > > > > _______________________________________________ > > 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 > > _______________________________________________ > 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 > > _______________________________________________ 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
