Re: [ClusterLabs] Failcount not resetting to zero after failure-timeout

Hi Guys, We are facing this issue again and again. Fail count is not being reset to zero and bec of this some of the resources are not being started on any node. Can some one plz tell what might be the cause. Help is appreciated :-) On Mon, Nov 23, 2015 at 11:06 AM, Pritam Kharat < pritam.

Re: [ClusterLabs] Failcount not resetting to zero after failure-timeout

Could some one please reply ? On Thu, Nov 19, 2015 at 10:28 PM, Pritam Kharat < pritam.kha...@oneconvergence.com> wrote: > > Hi All, > > I have 2 node HA setup. I have added migration_threshold=5 and > failure-timeout=120s for my resources. When migration threshold is rea

[ClusterLabs] Failcount not resetting to zero after failure-timeout

: unpack_rsc_op: Clearing expired failcount for oc-service-manager * -- Thanks and Regards, Pritam Kharat. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting

[ClusterLabs] Resources not starting some times after node reboot

="eth1" \ op monitor interval="15s" group sc-resources sc_vip oc-service-manager oc-fw-agent oc-lb-agent oc-vpn-agent property $id="cib-bootstrap-options" \ dc-version="1.1.10-42f2063" \ cluster-infrastructure="corosync" \ stonith-enabled="fa

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

+ case "${__OCF_PRIO}" in + __OCF_PRIO=ERROR + '[' ERROR = DEBUG ']' + ha_log 'ERROR: Setup problem: couldn'\''t find command: ip' + local loglevel + '[' none = '' ']' + tty + '[' x = x0 -a x = xdebug '

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

, Dejan Muhamedagic wrote: > Hi, > > On Thu, Oct 29, 2015 at 10:40:18AM +0530, Pritam Kharat wrote: > > Thank you very much Ken for reply. I will try your suggested steps. > > If you cannot figure out from the logs why the stop operation > times out, you can also try to

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

Thank you very much Ken for reply. I will try your suggested steps. On Wed, Oct 28, 2015 at 11:23 PM, Ken Gaillot wrote: > On 10/28/2015 03:51 AM, Pritam Kharat wrote: > > Hi All, > > > > I am facing one issue in my two node HA. When I stop pacemaker on ACTIVE > >

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

Hi Ulrich/Anyone, Could you please reply to the mail ? On Wed, Oct 28, 2015 at 3:22 PM, Pritam Kharat < pritam.kha...@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

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

ync" \ 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.wi...@rz.uni-regensburg.

[ClusterLabs] VIP monitoring failing with Timed Out error

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: h

Re: [ClusterLabs] Current DC becomes None suddenly

Hi Ken, Please see inline comments of last mail On Thu, Oct 8, 2015 at 8:25 PM, Pritam Kharat < pritam.kha...@oneconvergence.com> wrote: > Hi Ken, > > Thanks for reply. > > On Thu, Oct 8, 2015 at 8:13 PM, Ken Gaillot wrote: > >> On 10/02/2015 01:47 PM, Pritam Khar

Re: [ClusterLabs] Current DC becomes None suddenly

Hi Ken, Thanks for reply. On Thu, Oct 8, 2015 at 8:13 PM, Ken Gaillot wrote: > On 10/02/2015 01:47 PM, Pritam Kharat wrote: > > Hi, > > > > I have set up a ACTIVE/PASSIVE HA > > > > *Issue 1) * > > > > *corosync.conf* file is > > > > #

Re: [ClusterLabs] Current DC becomes None suddenly

Could some one please reply to this query ? On Sat, Oct 3, 2015 at 12:17 AM, Pritam Kharat < pritam.kha...@oneconvergence.com> wrote: > > Hi, > > I have set up a ACTIVE/PASSIVE HA > > *Issue 1) * > > *corosync.conf* file is > > # Please read the

[ClusterLabs] Current DC becomes None suddenly

rvice1_start_0 (node=sc-node-2, call=-1, rc=1, status=Timed Out, last-rc-change=Fri Oct 2 23:38:53 2015 , queued=0ms, exec=0ms -- Thanks and Regards, Pritam Kharat. ___ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listi