Hi, > > Unfortunately, the latest package produced the same results. > > pgsql couldn't fail over using crm_resource -F. > > I think you perhaps misunderstand what -F does... it is intended to > tell the cluster that the resource failed. > Although it may move as well (depending on how you set up the scores), > this is not the primary goal.
pgsql is set as, moves to the other node if it fails. If crm_resrouce -F is called, pgsql's fail-count would be increased from 0 to 1, so pgsql should move to the appropriate node. but pgsql was just stopped, and not moved. Other resources were still running. Thanks, Junko > > > > > # rpm -qa | grep heartbeat > > > > heartbeat-resources-2.1.3-22.1 > > > > heartbeat-2.1.3-22.1 > > > > pacemaker-heartbeat-0.6.5-7.1 > > > > heartbeat-common-2.1.3-22.1 > > > > Thanks, > > Junko > > > > > >> You're seeing a bug that was introduced in 0.6.4. > >> Its fixed in the latest dev code (and the just released 0.6.5). > >> > >> On Fri, Jun 20, 2008 at 09:51, Junko IKEDA <[EMAIL PROTECTED]> > > wrote: > >> > Hi, > >> > > >> > I run this combination; > >> > Pacemaker:0df5ae633188 > >> > Heartbeat:c94051dc16a5 > >> > > >> > There are three Filesystem and one IPaddr on one node. > >> > If IPaddr is forced into the other node with crm_resource -F, > >> > > >> > # crm_resource -F -r prmIpPostgreSQLDB -H x3650a > >> > > >> > Three Filesystem would also move to that node because they are in the > > same > >> > group. > >> > see attached hb_report-without-pgsql.tar.gz. > >> > > >> > > >> > When I added pgsql to this configuration, > >> > I found a strange behavior. > >> > > >> > If I get pgsql move to the other node using crm_resource -F, > >> > > >> > # crm_resource -F -r prmApPostgreSQLDB -H x3650a > >> > > >> > pgsql would stop, but other resources wouldn't do any action. > >> > They would remain on the node which pgsql stopped. > >> > see attached hb_report-with-pgsql.tar.gz. > >> > > >> > What is the primary cause of the problem? > >> > pgsql?? > >> > > >> > > >> > Best Regards, > >> > Junko Ikeda > >> > > >> > NTT DATA INTELLILINK CORPORATION > >> > > >> > > >> > _______________________________________________ > >> > 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
