[EMAIL PROTECTED] wrote on 10/25/2007 04:46:15 PM: > Hello all,
> Like many others I've read and re-read the webpage and searched the > mailing list for the past week and a half, and I'm still not getting where > I want to be. > I'm working with a two-node cluster whose configuration details are below. > To produce the logs, I performed the following: > 1. started heartbeat on both nodes > 2. started all resources > 3. unplugged 100 network on node1 > 4. waited exactly 5 minutes > 5. plugged 100 network back into node1 > First, all of my resources are in the "EnterpriseSprayer" group, and are > ordered and collocated. The startup order is always correct and and the > resources are always started on the same node. Using the gui, I can > manually standby the 1st node and all of the resources get transitioned > perfectly. The problem is that if I simulate a network failure on the 100 > subnet (by unplugging the cable), the resources never transition. > My desired behavior is: > 1. Only start the resources on a node where the gateway is reachable. > 2. Keep monitoring the gateway and transition the resources if the gateway > becomes unreachable. > 3. If any of the resources go down, restart them as necessary. > 4. I don't care where the resources run, as long as they are running. (I > don't need them to stick to one node or the other) Update: I've looked more closely at this issue, and tried ptest (as shown below). I'm convinced that this is an issue with constraints, but I just don't see what it is.... plspgen02:~ # ptest -L -VVVV ptest[19880]: 2007/10/26_16:43:11 notice: main: Required feature set: 1.1 ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'stop' for cluster option 'no-quorum-policy' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'true' for cluster option 'symmetric-cluster' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'false' for cluster option 'stonith-enabled' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'reboot' for cluster option 'stonith-action' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '0' for cluster option 'default-resource-stickiness' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '0' for cluster option 'default-resource-failure-stickiness' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'true' for cluster option 'is-managed-default' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '60s' for cluster option 'cluster-delay' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '20s' for cluster option 'default-action-timeout' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'true' for cluster option 'stop-orphan-resources' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'true' for cluster option 'stop-orphan-actions' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'false' for cluster option 'remove-after-stop' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '-1' for cluster option 'pe-error-series-max' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '-1' for cluster option 'pe-warn-series-max' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value '-1' for cluster option 'pe-input-series-max' ptest[19880]: 2007/10/26_16:43:11 notice: cluster_option: Using default value 'true' for cluster option 'startup-fencing' ptest[19880]: 2007/10/26_16:43:11 WARN: unpack_rsc_op: Processing failed op (pound_process_start_0) on plspgen02 ptest[19880]: 2007/10/26_16:43:11 WARN: unpack_rsc_op: Handling failed start for pound_process on plspgen02 ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource ip_10-1-100-180 cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource ip_10-1-100-181 cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource ip_10-1-100-182 cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource apache_process cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource pound_process cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 WARN: native_color: Resource gateway:0 cannot run anywhere ptest[19880]: 2007/10/26_16:43:11 notice: NoRoleChange: Leave resource gateway:1 (plspgen02) plspgen02:~ # Thanks, Justin _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
