>>> Pritam Kharat <pritam.kha...@oneconvergence.com> schrieb am 28.10.2015 um >>> 09:51 in Nachricht <CAKXxEYwN-jpYvbq=hbtuna5r580h5oak1xcmea_uynucaxk...@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@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