[ClusterLabs] Antw: VIP monitoring failing with Timed Out error

[Pritam Kharat]

Hi Ulrich/Anyone,

Could you please reply to the mail ?

On Wed, Oct 28, 2015 at 3:22 PM, Pritam Kharat <
pritam.kharat at oneconvergence.com> wrote:

> Resource migration to STANDBY node failed. And log on STANDBY node says
>  Timed Out of VIP monitoring . What might be the reason for VIP TimedOut.
>
> HA configuration is this way ->
>
> root at sc-node-2:~# crm configure show
> node $id="1" sc-node-1
> node $id="2" sc-node-2
> primitive oc-service-manager upstart:oc-service-manager \
> meta allow-migrate="true" migration-threshold="5" failure-timeout="120s" \
> op monitor interval="15s" timeout="60s"
> primitive sc_vip ocf:heartbeat:IPaddr2 \
> params ip="192.168.20.188" cidr_netmask="24" nic="eth0" \
> op monitor interval="15s"
> colocation sc-node inf: sc_vip oc-service-manager
> order SCVIP-BEFORE-SM 0: sc_vip oc-service-manager
> property $id="cib-bootstrap-options" \
> dc-version="1.1.10-42f2063" \
> cluster-infrastructure="corosync" \
> stonith-enabled="false" \
> cluster-recheck-interval="3min" \
> default-action-timeout="180s"
> rsc_defaults $id="rsc-options" \
> resource-stickiness="100"
>
>
>
> On Wed, Oct 28, 2015 at 2:50 PM, Ulrich Windl <
> Ulrich.Windl at rz.uni-regensburg.de> wrote:
>
>> >>> Pritam Kharat <pritam.kharat at oneconvergence.com> schrieb am
>> 28.10.2015 um 09:51
>> in Nachricht
>> <CAKXxEYwN-jpYvbq=HbTuna5r580h5OaK1XCmEA_UynUCaXkMPg at mail.gmail.com>:
>> > Hi All,
>> >
>> > I am facing one issue in my two node HA. When I stop pacemaker on ACTIVE
>> > node, it takes more time to stop and by this time VIP migration with
>> other
>> > resources migration fails to STANDBY node. (I have seen same issue in
>> > ACTIVE node reboot case also)
>>
>> Can you migrate to a STANDBY node?
>>
>> >
>> >
>> > Last change: Wed Oct 28 02:52:57 2015 via cibadmin on node-1
>> > Stack: corosync
>> > Current DC: node-1 (1) - partition with quorum
>> > Version: 1.1.10-42f2063
>> > 2 Nodes configured
>> > 2 Resources configured
>> >
>> >
>> > Online: [ node-1 node-2 ]
>> >
>> > Full list of resources:
>> >
>> >  resource (upstart:resource): Stopped
>> >  vip (ocf::heartbeat:IPaddr2): Started node-2 (unmanaged) FAILED
>> >
>> > Migration summary:
>> > * Node node-1:
>> > * Node node-2:
>> >
>> > Failed actions:
>> >     vip_stop_0 (node=node-2, call=-1, rc=1, status=Timed Out,
>> > last-rc-change=Wed Oct 28 03:05:24 2015
>> > , queued=0ms, exec=0ms
>> > ): unknown error
>> >
>> > VIP monitor is failing over here with error Timed Out. What is the
>> general
>> > reason for TimeOut. ? I have kept default-action-timeout=180secs which
>> > should be enough for monitoring
>> > I have added order property -> when vip is started then only start other
>> > resources.
>> > Any clue to solve this problem ? Most of the time this VIP monitoring is
>> > failing with Timed Out error.
>> >
>> > --
>> > Thanks and Regards,
>> > Pritam Kharat.
>>
>>
>>
>>
>>
>> _______________________________________________
>> Users mailing list: Users at clusterlabs.org
>> http://clusterlabs.org/mailman/listinfo/users
>>
>> Project Home: http://www.clusterlabs.org
>> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
>> Bugs: http://bugs.clusterlabs.org
>>
>
>
>
> --
> Thanks and Regards,
> Pritam Kharat.
>



-- 
Thanks and Regards,
Pritam Kharat.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/users/attachments/20151028/6a063225/attachment.htm>