Hoy, everybody. As previously recommended here, I'm using those versions
heartbeat.x86_64 2.1.3-21.1 heartbeat-common.x86_64 2.1.3-21.1 heartbeat-resources.x86_64 2.1.3-21.1 pacemaker-heartbeat.x86_64 0.6.2-14.1 from this repository: http://download.opensuse.org/repositories/server:/ha-clustering/CentOS_5/ My system info, your format: System info db-sql1.ripe.net: Heartbeat version: 2.1.3 CRM Version: 0.6.2 (node: 000d7573fbf8ac5f0c2835c8739973e826d0671b) Platform: Linux Kernel release: 2.6.18-53.1.14.el5 Architecture: x86_64 Distribution: /etc/redhat-release CentOS release 5 (Final) The problem I'm facing now is with resource stickiness. It seems to me that even with <nvpair name="default-resource-stickiness" value="INFINITY" id="be9e55b8-92b5-433b-ac85-8ed27ae6e183"/> Resources prefer to run in one of the nodes, doesn't matter how I add/remove the node from the cluster. I just figured out that this is because I didn't had <nvpair name="symmetric-cluster" value="TRUE" id="8b795ac3-6142-459d-a79d-bcbcf563364d"/> That's listed here: http://www.linux-ha.org/ciblint/crm_config as being the "default" value. I believe that this is a documentation error, but can also be a bug. Kind regards. -- Luis Motta Campos (a.k.a. Monsieur Champs) is a software engineer, Perl fanatic evangelist, and amateur {cook, photographer} _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
