andrew at beekhof
Nov 6, 2009, 3:09 AM
Post #9 of 10
(1154 views)
Permalink
|
On Fri, Nov 6, 2009 at 11:27 AM, Matt <mattmoran76 [at] gmail> wrote:
> ITEM 1 configure show output:
> node $id="8d5816b1-a3d0-4fb8-b741-a090c2afb8b1" test-02.sl.local \
> attributes standby="off"
> node $id="ea6257d7-d639-434f-8581-e5c7a831325a" test-01.sl.local \
> attributes standby="off"
> primitive haproxy lsb:haproxy \
> op monitor on-fail="standby" interval="15s"
> primitive haproxy_vip_1 ocf:heartbeat:IPaddr \
> params ip="192.168.0.111" \
> op monitor interval="10s" nic="eth1"
> primitive haproxy_vip_2 ocf:heartbeat:IPaddr \
> params ip="192.168.0.112" \
> op monitor interval="10s" nic="eth1"
> clone cl-haproxy haproxy
> location loc-1-1 haproxy_vip_1 \
> rule $id="rule-1" 100: #uname eq test-01.sl.local
> location loc-1-2 haproxy_vip_2 \
> rule $id="rule-2" 90: #uname eq test-01.sl.local
> location loc-2-1 haproxy_vip_2 \
> rule $id="rule-3" 100: #uname eq test-02.sl.local
> location loc-2-2 haproxy_vip_1 \
> rule $id="rule-4" 90: #uname eq test-02.sl.local
> property $id="cib-bootstrap-options" \
> dc-version="1.0.5-462f1569a43740667daf7b0f6b521742e9eb8fa7" \
> cluster-infrastructure="Heartbeat" \
> stonith-enabled="false" \
> last-lrm-refresh="1257450377"
>
> ITEM 2 crm_mon output:
> Online: [ test-02.sl.local test-01.sl.local ]
>
> haproxy_vip_1 (ocf::heartbeat:IPaddr): Started test-01.sl.local
> Clone Set: cl-haproxy
> Started: [ test-01.sl.local test-02.sl.local ]
> haproxy_vip_2 (ocf::heartbeat:IPaddr): Started test-02.sl.local
>
> ------------
> This works great. When I stop haproxy on a node the VIP gets moved to
> its brother which is exactly what I want. crm_mon then outputs this:
> ------------
> ITEM 3 crm_mon output:
> Node test-02.sl.local (8d5816b1-a3d0-4fb8-b741-a090c2afb8b1): standby (on-fail)
> Online: [ test-01.sl.local ]
>
> haproxy_vip_1 (ocf::heartbeat:IPaddr): Started test-01.sl.local
> Clone Set: cl-haproxy
> Started: [ test-01.sl.local ]
> Stopped: [ haproxy:1 ]
> haproxy_vip_2 (ocf::heartbeat:IPaddr): Started test-01.sl.local
>
> Failed actions:
> haproxy:1_monitor_15000 (node=test-02.sl.local, call=5, rc=7,
> status=complete): not running
> --------------
> Now when I start haproxy running again nothing happens (which is
> fine), but i'm unable to find a command that gets test-02 out of this
> standby (on-fail) mode, the only way I have found to do it if is I
> restart heartbeat process.
crm resource clean cl-haproxy test-02.sl.local
if the node is still in standby after that, check the call id of the
failed action... if its different then the haproxy RA is probably
broken.
>
> I tried crm node online test-02.sl.local
>
> but if I do /etc/init.d/heartbeat restart - this gives me the same
> output of crm_mon as Item 2, and the cluster is back to normal.
>
> Thanks,
>
> Matt
>
> 2009/11/6 Andrew Beekhof <andrew [at] beekhof>:
>> On Thu, Nov 5, 2009 at 9:51 PM, Matt <mattmoran76 [at] gmail> wrote:
>>> DIdn't seem to do anything. The only way I can get it to come out of
>>> this mode is restarting heartbeat on that node.
>>>
>>> Node test-01.sl.local (ea6257d7-d639-434f-8581-e5c7a831325a): standby (on-fail)
>>>
>>> Tried cleaning up both resources on test-01 but it just stays like this.
>>
>> help me out here... you've got to give me something to go on :-)
>> logs? crm_mon output? crm configure show output?
>> _______________________________________________
>> Linux-HA mailing list
>> Linux-HA [at] lists
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
>>
> _______________________________________________
> Linux-HA mailing list
> Linux-HA [at] lists
> http://lists.linux-ha.org/mailman/listinfo/linux-ha
> See also: http://linux-ha.org/ReportingProblems
>
_______________________________________________
Linux-HA mailing list
Linux-HA [at] lists
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
|
